FIELD GUIDE 03 · SELL TO LEARN
A practical chapter for independent and aspiring niche B2B SaaS founders. Set a price around a buyer’s real alternatives, start focused conversations, and use early behavior to decide what to improve next.
Work from an actual buyer and workflow
STEP 01 · PRICE FOR VALUE
Price is a hypothesis about what a specific buyer values. Compare it with the cost of the current workaround and other ways to get the job done, then check whether the economics work for your business too.
A WILLINGNESS-TO-PAY BRIDGE
Define what is included, what is out of scope, the price, and how delivery works.
See whether qualified buyers will pay for the outcome and which parts repeat across customers.
STEP 02 · ILLUSTRATIVE ARR MATH
Annual recurring revenue (ARR) is commonly expressed as monthly recurring revenue multiplied by 12. These rounded examples assume every customer pays the listed monthly price for a full year; they are arithmetic illustrations, not a forecast or target for every niche.
$1,000,000 ÷ ($100 × 12) = 833.33, so round up to 834 customers.
834 × $100 × 12 = $1,000,800 ARR.
$1,000,000 ÷ ($1,000 × 12) = 83.33, so round up to 84 customers.
84 × $1,000 × 12 = $1,008,000 ARR.
The price point changes the count, not the work of earning and retaining each account. Actual revenue depends on discounts, payment terms, churn, and the product’s fit with a particular buyer.
STEP 03 · DIRECT SELLING
The purpose of early direct selling is to learn whether a particular buyer has this problem, how they handle it, and whether they will commit to a defined offer.
Name the kind of organization, the person who owns the work, and the situation that brings the problem up. Add one clear qualification, such as the workflow happening regularly or already consuming paid staff time.
For [organization], [role] handles [job] when [trigger] happens.
Start with people you can reach through your network, industry directories, professional groups, or public role and company searches. Record why each person matches, the specific workflow clue you found, and where that clue came from.
Keep the list focused enough that every person has a real reason to hear from you.
Mention one accurate detail about the person’s work, explain the workflow you are trying to understand, and ask for a short conversation. A useful first message asks about the problem; it does not assume your product is the answer.
“I’m learning how [role] handles [job] when [trigger]. Would you have 20 minutes to walk me through the last time it came up?”
Ask what happened the last time, who was involved, what tools or workarounds they used, and what the problem cost in time, money, or risk. Listen for existing spend and the person who can approve a change. Keep the buyer’s words and your interpretation separate in your notes.
Ask “Could you show me how that works today?” before asking what they might want.
When the problem, buyer, and timing fit, propose a paid pilot or pre-sale with a written scope, price, start and end point, and clear deliverable. Ask whether they can take that step and who needs to approve it. A compliment is not a commitment; record what happens without assuming a sale.
A clear “not now” or “no” is useful information too. Do not promise a result you have not demonstrated.
STEP 04 · EARLY FEEDBACK
Speak with buyers during onboarding and after they try the workflow. Ask for the last concrete example, where the product helped or disappointed them, and what they did next. Follow up on a specific action rather than treating polite interest as proof.
“How disappointed would you be if you could no longer use [product]?”
The supplied research snapshot mentions “very disappointed” answers above 40% as a signal to investigate. Treat that threshold as a heuristic, not proof of product-market fit; the source bibliography was not available to verify it.
A GROUNDED NEXT STEP
Separate the buyer’s exact words, observed behavior, and your interpretation. Use the gaps to choose the next conversation or a small test.