Start with one job that already matters
A useful first-customer hypothesis for data integration is that a report silently omits records after a source schema changes. Start by speaking with a data engineering lead responsible for reliable reporting inputs. The people doing the work are analysts depending on refreshed source data; the person feeling the friction and the person authorizing a purchase may be different.
The existing alternative is often custom export scripts and manual spreadsheet reconciliation. 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: “Our nightly import still succeeds but a renamed source field is now empty. We need a way to catch schema drift before reports go out.” 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 a new source or schema revision breaks an established reporting job. That is a hypothesis to confirm, not evidence inferred from the person's job title alone.
| Check | What matters for this category |
|---|---|
| User | analysts depending on refreshed source data |
| Budget or decision owner | a data engineering lead responsible for reliable reporting inputs |
| Poor fit | buyers requiring connectors or data residency conditions that have not been implemented |
| Implementation question | retries, backfills, and schema changes must preserve data identity |
Offer one bounded pilot
A concrete starting offer is to load a bounded source sample, introduce a field change, and verify the failure is explicit. 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 consumer can reconcile row counts and required fields to the source snapshot. 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 source changes should stop publication rather than fill missing values?
- Check feasibility next: How do you know the destination has every expected record?
- 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: retries, backfills, and schema changes must preserve data identity. 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 .