Start with one job that already matters
A useful first-customer hypothesis for referral software is that the team cannot tell which referrals produced an eligible new customer. Start by speaking with a growth owner designing a customer referral program. The people doing the work are satisfied customers inviting appropriate peers; the person feeling the friction and the person authorizing a purchase may be different.
The existing alternative is often coupon codes reconciled manually in a spreadsheet. Treat that as a competitor with real advantages: it is familiar, already available, and does not require a migration. Your first conversation should uncover a specific reason the buyer would accept the effort of changing it.
Recognize a plausible early adopter
The following is an original illustrative scenario, not a quotation from a prospect: “Our customers already introduce friends, but we lose track of which introductions qualify for the reward. How do we reconcile this?” It is useful because it describes a workflow and a need. Verify the author's role, date, context, and whether the problem remains unresolved before treating it as an opportunity.
A possible reason to act is that a small manual referral experiment has produced enough activity to strain reconciliation. That is a hypothesis to confirm, not evidence inferred from the person's job title alone.
| Check | What matters for this category |
|---|---|
| User | satisfied customers inviting appropriate peers |
| Budget or decision owner | a growth owner designing a customer referral program |
| Poor fit | teams expecting a referral tool to create product satisfaction or guarantee viral growth |
| Implementation question | reward rules and abuse controls need explicit definitions before automating payouts |
Offer one bounded pilot
A concrete starting offer is to trace a test invitation through an eligible event and an ineligible event without issuing real rewards. State the required inputs, who will participate, what access is needed, and how the pilot can be stopped. Agree on the boundary before asking for customer data or a production integration.
Define the first proof of value as this observable event: a qualifying test referral is attributed once while the ineligible case is excluded. A positive reply, a demo attendance, and a completed pilot are different observations; record them separately.
- Write the buyer hypothesis and the current workaround in one project brief.
- Use this discovery question before presenting a solution: What verified event makes a referral eligible, and what invalidates it?
- Check feasibility next: Who resolves duplicate attribution, refunds, or a disputed reward?
- Ask whether the person wants to explore the bounded pilot. Record their answer, including a refusal, without converting it into a sale.
Decide what to learn from the first attempt
The strongest reason to pause is an unresolved implementation issue: reward rules and abuse controls need explicit definitions before automating payouts. Change the scope or qualify out the prospect when that gap prevents the pilot from delivering value.
If buyers recognize the problem but decline the pilot, investigate the offer and switching effort. If they do not recognize the problem, revisit the audience. If they complete the pilot but do not continue, inspect the value delivered and the next recurring job. Avoid expanding outreach until the evidence tells you which assumption changed.
About these playbooks and examples
Prepared by DemandBolt with AI assistance as practical planning resources for people building and selling software. The category scenarios and message examples are illustrative, not quotations from real prospects or claims of customer results. Adapt the hypotheses to your product, verify original sources, and review capabilities before making an offer.
The workflow follows our first-customer guide and buying-signal review method. Our PyInvesting and Rae records distinguish actual internal work from targets. Published .