Qualify the job before the account
A promising invoicing software lead needs more than a company in the right sector. Confirm the job: the owner cannot tell which invoice is awaiting approval, payment, or correction. Identify administrative staff preparing invoices and following up as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is a small business owner responsible for collecting approved invoices.
Ask about the current workaround, document templates and a payment-status spreadsheet, and what would make changing it worthwhile. Do not assign a budget or procurement timeline from company size, funding, or job title alone.
Use a category-specific qualification rubric
Use the calculator below to organize your judgment after reading the source. Unknown evidence should remain unknown. Its weights are a transparent prioritization convention, not a prediction of purchase probability.
| Dimension | Evidence to seek | Reason to pause |
|---|---|---|
| Problem | What event changes an invoice from drafted to sent, disputed, or paid? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you trace a fictional invoice through issue, query, correction, and reconciled test payment? | businesses requiring jurisdiction-specific capabilities that have not been verified |
| Timing | the business takes on recurring clients with different billing terms | The proposed change has no confirmed date or relevance. |
| Implementation | Which source proves payment, and who reconciles partial payments? | tax fields, payment methods, and regional invoice requirements must match the supported product |
| Value | an authorized user can identify the correct next action from verified invoice status | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “I lose track of whether an invoice was sent, queried, or paid. I need a clear status before following up with clients.” That supports investigating the problem, but it does not yet settle purchasing authority or technical compatibility. A reviewer should ask the two discovery questions above and preserve the answers beside the source.
Compare that with: A search for a free invoice image with no billing workflow need. This weaker example should not receive the same pain or timing score. A relevant public topic is not evidence of a current evaluation.
Even a strong problem signal should be rejected when the need belongs to businesses requiring jurisdiction-specific capabilities that have not been verified. Qualifying out prevents a misleading promise and preserves time for a prospect the product can help.
Create a reviewable handoff
A qualified opportunity should contain the original evidence, a summary of the job, confirmed and unknown constraints, the buyer/user distinction, and an agreed next step. Keep a score attached to those facts so another teammate can challenge the conclusion.
Propose a pilot only when the critical gap is addressed: tax fields, payment methods, and regional invoice requirements must match the supported product. Evaluate the pilot through a real observation that an authorized user can identify the correct next action from verified invoice status, and keep that observation separate from the initial qualification score.
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 .