What a relevant buying signal looks like
A useful signal for referral software connects a problem, a plausible buyer, and a reason to investigate now. In this category, examine whether the team cannot tell which referrals produced an eligible new customer. The relevant decision owner may be a growth owner designing a customer referral program, while the daily experience belongs to satisfied customers inviting appropriate peers.
A signal supports a question. It does not establish budget, permission to contact, a purchase deadline, or a promise to buy. Verify those separately as the conversation develops.
Compare strong, ambiguous, and disqualifying evidence
These are original hypothetical examples for learning how to qualify evidence. They do not identify real people or report observed customer outcomes.
| Example | Interpretation | Next check |
|---|---|---|
| Our customers already introduce friends, but we lose track of which introductions qualify for the reward. How do we reconcile this? | A specific task and request are visible. | What verified event makes a referral eligible, and what invalidates it? |
| A founder wants rewards to compensate for a product nobody uses yet. | Activity or interest alone does not establish a buying need. | Read the original context; do not infer budget or urgency. |
| The team says a small manual referral experiment has produced enough activity to strain reconciliation. | A possible change in operating conditions. | Ask whether the change creates a problem that needs solving now. |
| teams expecting a referral tool to create product satisfaction or guarantee viral growth | The request falls outside the proposed product scope. | Qualify out or refer to an appropriate category; do not promise missing capabilities. |
Verify the source and the proposed solution
Start with the original discussion, not a copied list or an automated summary. Check date, author role, and replies that may already resolve the request. Look for a current workaround such as coupon codes reconciled manually in a spreadsheet; a workaround helps reveal the exact job and the effort of switching.
Before describing a fit, check whether your product can trace a test invitation through an eligible event and an ineligible event without issuing real rewards. Pay particular attention to this constraint: reward rules and abuse controls need explicit definitions before automating payouts. A relevant problem with an incompatible implementation is still a poor-fit lead.
- What verified event makes a referral eligible, and what invalidates it?
- Who resolves duplicate attribution, refunds, or a disputed reward?
- Keep the observed statement separate from any inferred timing or budget.
- Revisit older evidence before initiating a conversation; the underlying situation may have changed.
Choose an action proportional to the evidence
When the source is current and the need fits, propose a narrow next step around this outcome: a qualifying test referral is attributed once while the ineligible case is excluded. When source quality is weak, gather context first. When the need falls outside the product, record the exclusion.
Use a qualification score to organize the review, and retain the original evidence alongside it. A high numerical total does not override a missing source, a material capability gap, or an inappropriate contact route. The next useful action may be a question, a pilot proposal, or a decision to leave the record alone.
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 .