A starting plan for this customer problem
Use this referral software customer acquisition plan as an editable hypothesis. The audience is satisfied customers inviting appropriate peers; the proposed decision owner is a growth owner designing a customer referral program. The central problem is that the team cannot tell which referrals produced an eligible new customer. Replace any assumption that does not match your actual product or intended customer.
The example is built around a bounded offer: trace a test invitation through an eligible event and an ineligible event without issuing real rewards. It does not assume that DemandBolt supplies the category software itself. DemandBolt helps you organize the acquisition work for the product you are building or selling.
Review the example before using it
The worksheet below starts with your existing locally saved draft when one exists. Choose Use this example plan to load this category's suggestions into the editable fields. That choice does not overwrite the saved draft until you save again.
| Plan field | Suggested hypothesis |
|---|---|
| Audience | satisfied customers inviting appropriate peers |
| Buyer | a growth owner designing a customer referral program |
| Problem | the team cannot tell which referrals produced an eligible new customer |
| Current alternative | coupon codes reconciled manually in a spreadsheet |
| Potential trigger | a small manual referral experiment has produced enough activity to strain reconciliation |
| Research query | "referral program" "manual tracking" |
| Disqualifier | teams expecting a referral tool to create product satisfaction or guarantee viral growth |
| Pilot | trace a test invitation through an eligible event and an ineligible event without issuing real rewards |
| Observed value event | a qualifying test referral is attributed once while the ineligible case is excluded |
Replace assumptions with evidence
Begin with this question: What verified event makes a referral eligible, and what invalidates it? Then check feasibility: Who resolves duplicate attribution, refunds, or a disputed reward? Save an actual source or a dated interview note for each answer instead of turning a suggestion into a customer fact.
This implementation concern deserves a deliberate decision: reward rules and abuse controls need explicit definitions before automating payouts. If the current product cannot satisfy it, narrow the pilot or choose a different audience. Do not hide the gap in an optimistic acquisition plan.
Make the plan measurable
For this example, define activation as the point when a qualifying test referral is attributed once while the ineligible case is excluded. Count research notes, qualified prospects, invitations, replies, pilots, and payments as separate stages. Agree on a review date and record what would change the next decision.
Saving and downloading the worksheet are free and require no account. Use in DemandBolt carries the draft toward project creation through signup; you still review it in the product. Keep private customer material out of a shared-device worksheet, and use the clear control when the local draft is no longer needed.
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 .