Start with one job that already matters
A useful first-customer hypothesis for procurement software is that purchase requests arrive without a clear budget owner or approval record. Start by speaking with a procurement manager responsible for purchasing controls. The people doing the work are department staff requesting purchases and managers approving them; the person feeling the friction and the person authorizing a purchase may be different.
The existing alternative is often email threads and an approval 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 cannot tell which laptop requests are approved before the invoice arrives. Looking for a request-to-approval workflow.” 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 new departments are gaining purchasing authority. That is a hypothesis to confirm, not evidence inferred from the person's job title alone.
| Check | What matters for this category |
|---|---|
| User | department staff requesting purchases and managers approving them |
| Budget or decision owner | a procurement manager responsible for purchasing controls |
| Poor fit | teams expecting supplier discovery or financing from an approval-only workflow |
| Implementation question | approval software must fit the accounting and purchasing systems already in use |
Offer one bounded pilot
A concrete starting offer is to route one purchase category through named budget owners and approval thresholds. 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: an approved request produces a complete handoff record for purchasing. 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 amount, category, or department changes the required approver?
- Check feasibility next: Where does an approved request become an actual purchase order?
- 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: approval software must fit the accounting and purchasing systems already in use. 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 .