Define the question before collecting names
For email marketing software, investigate whether every subscriber receives the same message despite different product needs. Research is useful when it explains a workflow, its owner, and an unresolved constraint. A list of companies in a sector cannot establish that those companies have this problem.
Begin with marketers segmenting opted-in audiences and check how their work relates to a lifecycle marketer accountable for relevant subscriber communication. Map the current process around one mailing list and manual campaign exclusions. You are looking for the step where the workaround stops being adequate, rather than asking people to validate an abstract product idea.
Search for the language of the problem
Try the queries below in a search engine or the search feature of a relevant professional community. Read the original discussion and its date. Results are starting points for research; these query examples do not claim any particular search volume or the existence of a matching prospect.
| Query to adapt | What to extract |
|---|---|
| "email segmentation" "trial users" | The failed task, current workaround, author role, and unresolved question. |
| "onboarding emails" "manual" "segments" | An evaluation request, required capability, and reason to change. |
| "email marketing software" "recommend" "alternative" | Specific constraints in recommendation requests; separate vendor promotions from user experience. |
Write an evidence note you can revisit
Illustrative source text: “Our trial users and paying customers get the same onboarding sequence. I need segmentation based on their actual stage.” Save the actual source URL and date when researching a real example. Keep a short relevant excerpt and your interpretation in separate fields. Do not rewrite your interpretation as something the author said.
The working hypothesis is that the product adds a second customer segment or onboarding path. The missing information includes whether the author is a lifecycle marketer accountable for relevant subscriber communication, whether the need is still open, and which implementation requirements remain unverified. Keep this constraint visible: deliverability and permission handling require proof beyond an attractive editor.
- Observed: the original words, the visible date, the task described, and any explicit requirements.
- To verify: whether the current process is one mailing list and manual campaign exclusions.
- Disqualify when the need belongs to buyers seeking unsolicited bulk sends or unsupported data imports.
- Next step: one context-appropriate question, or no contact when there is no suitable route.
Use a short discovery interview
Ask about a recent event before showing your product. Let the person explain the sequence in their own words; do not treat agreement with a leading question as validation.
- Which verified customer event should change the next email?
- How are permission, unsubscribes, and suppression handled in the current system?
- What would need to be true for you to preview a single lifecycle sequence on permitted test contacts with two different stages?
- How would you verify that the correct test segment receives its expected preview while an excluded contact remains suppressed?
Turn notes into a research decision
Compare independently sourced accounts of the same task. Keep an example that contradicts your hypothesis, such as this ambiguous scenario: A request for a database of email addresses to blast. It may justify more reading, but it is insufficient to label someone a buyer.
At the end of a bounded research session, decide whether to narrow the audience, ask a specific follow-up, change the pilot, or stop. Keep unknowns visible and store only the information needed for that decision. Research quality is measured by a better decision, not by how many names are collected.
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 .