Start with one job that already matters
A useful first-customer hypothesis for bookkeeping software is that month-end reconciliation stalls because transaction explanations and receipts are missing. Start by speaking with a bookkeeping practice owner managing client record collection. The people doing the work are bookkeepers chasing missing source documents; the person feeling the friction and the person authorizing a purchase may be different.
The existing alternative is often email requests, shared folders, and an outstanding-items 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: “We spend the first week of every month chasing the same missing receipts. Is there a client request workflow tied to each open item?” 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 the practice adds clients faster than it can reconcile missing documents. That is a hypothesis to confirm, not evidence inferred from the person's job title alone.
| Check | What matters for this category |
|---|---|
| User | bookkeepers chasing missing source documents |
| Budget or decision owner | a bookkeeping practice owner managing client record collection |
| Poor fit | buyers requiring unverified accounting certification, tax advice, or an unsupported ledger integration |
| Implementation question | financial records require access controls and compatibility with the practice's authoritative ledger |
Offer one bounded pilot
A concrete starting offer is to rehearse collection for a sanitized set of unresolved bookkeeping items. 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 returned source document is attached to the correct open item and reviewed by its owner. 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: Which missing item prevents the next reconciliation step?
- Check feasibility next: Where must received evidence be stored to preserve the client's audit trail?
- 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: financial records require access controls and compatibility with the practice's authoritative ledger. 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 .