What product question can you test before building
The test is for a business hypothesis, not a finished product: a new service, an additional line of business, an implementation format or an offer for one industry. The point is not to collect approval. We test whether a recipient is ready to discuss the problem in their company and take a next step: a call, a solution outline or a commercial proposal.
“We will build a procurement automation platform” is too broad to test. A usable version is more specific: “We are checking whether manufacturing companies are looking to reduce manual matching of invoices and requests.” The first framing invites silence or a generic request for a deck. The second can produce a useful answer: matching is not the issue; approvals are delayed. That is evidence for a product decision.
If you first need to define target companies and decision-making roles, start with B2B lead list building. When the hypothesis depends on a named set of strategic accounts, an account-based marketing campaign may fit better.
Who to contact so that a reply is evidence
A smoke test does not need “all B2B companies.” We define one narrow operating context: business type, the situation in which the problem appears and the person who can confirm it. In Russia and CIS, decision-makers often read their own email and may continue a business conversation in Telegram, so the contact must be chosen for their connection to the problem, not simply their job title.
| Hypothesis | Weak recipient | Recipient for validation |
|---|---|---|
| A service shortens contract approvals | Any company with a legal team | A company where contracts pass through several functions |
| A new IT support model | Any organisation with a website | A business with distributed infrastructure and a dedicated IT function |
| A service for sales teams | Any commercial director | A company with a specific complex B2B sales model |
We do not confuse a segment with a title. “Sales director” is not a reason to write. A visible business situation is: entering a region, an overloaded process, a change in operating model or a need to recruit partners. See when B2B outreach is the right move for the kinds of tasks the channel can address.
What happens in week one and week two
- Define the assumption: who it is for, which problem it addresses and what counts as a meaningful answer.
- Build a narrow list of companies and relevant roles, excluding businesses the offer clearly does not fit.
- Prepare a sequence centred on one question a decision-maker can answer without a meeting or presentation.
- Launch outreach, classify replies by meaning and adjust the next wording if the market points to a different problem.
- Deliver a conclusion: continue, change the hypothesis or stop development.
Week one checks whether the reason for contact is clear and produces the first substantive reactions. Week two separates isolated interest from a repeated signal and gathers objections. A 1–2 week period is realistic for testing a defined hypothesis, not for building a full sales pipeline.
A first sentence that invites an honest answer
Instead of “We offer an innovative solution for process optimisation,” start with the situation being tested: “We see that you are expanding your service network. We are checking whether businesses at this stage need to reduce manual coordination of field work.” This does not pretend the product already exists. It gives the decision-maker room to say the issue is covered, the problem is elsewhere or they want to understand the approach.
Which replies are signals and which are noise
A successful smoke test is not measured by opens or a polite “interesting.” A meaningful signal appears when a recipient relates the offer to their own operation: asks about conditions, describes the current approach, names an obstacle, requests material or agrees to discuss the task. Across our campaigns, 6,500 companies have given an explicit yes by requesting details, a proposal or a meeting; for your test, the content of each reply matters more than applying that number to a new idea.
- Confirmation: “The problem exists; we are ready to look at an approach.”
- Clarification: “How would this work with our current system or process?”
- Useful objection: “We would not proceed until rollout across branches is addressed.”
- Noise: an automatic reply, a request to use a general inbox without context or a formal opt-out.
If several decision-makers recognise the pain but are not ready to change an established process, that is not a failed email. It may show that the value is understood while the barrier lies in implementation time, trust in a new supplier or unclear process ownership. We record the objection itself rather than treating silence as a market rejection.
If substantive replies need to reach your team without losing context, agree the handoff in advance through reply handling and lead qualification.
What you receive after the market signal
The output is a hypothesis summary, not a list of emails sent. It shows who was contacted, which business trigger was used, what replies arrived, which objections repeated and what they mean for the product. Explicit requests for details, a proposal or a meeting are marked separately so your team can continue those conversations without delay.
- One defined hypothesis and segment boundaries
- Decision-makers’ actual questions and objections
- A list of contacts with specific interest for follow-up
- A recommendation to develop, narrow, change or stop the hypothesis
A negative decision is a valid result. The market may confirm the problem but not the proposed solution, or one segment may remain unresponsive while another asks for details. Either way, development budget is grounded in evidence rather than the team’s general impression. See how we work for reporting and control points.
When a demand smoke test is not for you
We are not the right fit when there is not even a draft hypothesis and you expect the market to invent the product for you. It is also unsuitable when you need a guaranteed contract immediately: cold outreach tests willingness to have a conversation; it does not replace a long procurement or approval cycle.
The test may not be appropriate if the offer cannot be described without a confidential demonstration, legal review or an existing prototype. If value only emerges after a long integration, market interviews may be a better first step than testing an offer through outreach.
Do not launch with a broad brief such as “find demand for everything we can do.” It produces mixed replies that cannot support a decision. Choose one proposition first, then test it in one defined part of the market.