How do I find the strongest pain point to lead with in my GTM?

What makes one pain the right campaign lead?

The right lead pain connects a real buyer situation, a current decision and a change your product can deliver. It should be specific enough to attract a suitable buyer and honest enough to let an unsuitable buyer recognize the mismatch.

This is especially important for a post-seed startup deciding where to concentrate its next acquisition effort. Several pains can be genuine. The choice is which one deserves the first focused campaign, not which complaint sounds most dramatic in a headline.

Start after the basic positioning work: a plausible buyer, a deliverable offer and credible alternatives should already be visible. If those remain unclear, use the first go-to-market strategy for a seed startup before comparing campaign angles.

Which buyer evidence matters most?

Look for recent events and actual allocations of effort, attention or resources. They show how a problem competes with other priorities more clearly than a general statement that the problem is important.

In his Demand-Side Sales talk, Bob Moesta discusses the buyer’s struggling situation, circumstances and trade-offs. He also separates purchase from first use and ongoing use. This is firsthand practitioner guidance, not a quantitative scoring model.

Ask the buyer to reconstruct a specific episode. What happened? Who had to respond? What did they do instead? What was postponed when they addressed it? Who joined the decision, and what made waiting acceptable or unacceptable?

Preserve the buyer’s explanation and its source. A seller’s interpretation that an account must have a budget is different from a buyer explaining an active project. Do not infer priority from company size, a job title or the emotional force of a complaint.

Read also: turning recorded customer pain points into evidence-backed GTM content.

How do you compare several credible pains?

Compare candidate pains against the same questions and keep missing evidence visible. A useful comparison exposes disagreements instead of hiding them inside a total score.

Criterion	Evidence to collect	What it does not prove
Recent trigger	A concrete event that changed the situation	Every similar account has the same trigger
Current workaround	What the team actually does today	The workaround is unacceptable to them
Consequence	The buyer’s account of the impact	Your product removes the whole impact
Actual trade-off	What was funded, reassigned or postponed	A future commitment to your offer
Decision ownership	Who can advance or stop the project	That the person reporting pain controls purchase
Product coverage	Demonstrated capability and prerequisites	A customer outcome before use
Switching burden	Access, migration, learning and uncertainty	That a stronger message can remove every barrier
Counterevidence	A relevant account choosing otherwise	That the entire pain should be abandoned

Product Talk’s opportunity-prioritization advice explicitly recognizes that assessment dimensions can disagree and rejects manufactured mathematical precision. Use the comparison to make a reasoned decision, not to claim a scientifically established winner.

Keep account groups separate. If one pain comes from current users and another from uncontacted prospects, the evidence has different depth. Note that difference before comparing their apparent strength.

How would you choose between two different problems?

When two problems both appear relevant, compare the buyer’s actual choice between them and the product’s present ability to help. Do not let the campaign select the pain merely because its wording is easier.

Recurring reporting handoffs and inconsistent customer onboarding are possible comparison topics, not findings about a company. Use this decision record after collecting the evidence above. Keep each entry linked to its source.

Decision field	What to record	Condition for the campaign choice
Selected pain and buyer situation	The problem, affected workflow and recent incident	A complaint without a concrete episode stays in discovery
Priority over the competing pain	What the buyer actually funded, reassigned or postponed, and who decided	Choose the pain receiving attention, rather than the more dramatic wording
Present product coverage	Demonstrated action, prerequisites and unresolved constraints	Delay or rescope if a necessary capability is unavailable
Reason to defer the other pain	Accepted workaround, lower priority or a binding constraint	Preserve the competing pain as a revisitable option
First test	The next commitment to request and what it would establish	Separate a workflow review from purchase and delivered value
Reopening condition and owner	Contrary evidence to watch for and who reviews it	Reopen when priority or product coverage no longer supports the choice

Lead with reporting handoffs if the evidence shows buyers prioritizing that work and the product can support the required change now. Lead with onboarding if those conditions favor onboarding. If priority is unknown, investigate before choosing; if neither problem can be credibly improved, delay the campaign. These are decision conditions, not reported outcomes.

Which interview questions expose a real trade-off?

Ask about decisions the buyer has already made before asking for hypothetical preferences. A useful conversation reconstructs the situation without suggesting that buying your product is the expected answer.

1. What happened the last time this problem occurred?
2. What did the team do next, and who was involved?
3. What had already been tried or ruled out?
4. Which other work lost attention when this was addressed?
5. Who decided that this project should proceed or wait?
6. What would make the current workaround acceptable for longer?
7. What would you need to verify before changing it?

Follow the answer rather than a rigid script. If the person cannot describe a relevant episode, record that limitation. If the actual decision owner is absent, ask whether a conversation with that person would be useful and appropriate.

Do not convert a private frustration into public copy without checking meaning and intended use. The purpose is to understand the buyer’s decision and improve mutual fit, not to intensify discomfort.

How do you check whether the product can help today?

Map the chosen pain to an available capability, its prerequisites and a credible first outcome. A roadmap promise should not carry the campaign’s central claim.

Ask product and delivery to inspect the buyer workflow. Can the needed data be accessed? Does implementation require work outside the current offer? Is the expected outcome dependent on a process change the buyer cannot make?

Separate what the demonstration proves from what remains to be tested after use. A feature may perform its stated action while the buyer’s wider problem remains. Use turning product features into provable sales messages to keep those distinctions in the campaign wording.

Refuse or rescope a deal when the required capability is unavailable or the conditions would prevent value. That decision protects the buyer and gives the founder better evidence than a sale followed by avoidable disappointment.

What should the first campaign test ask a buyer to do?

Choose a next commitment that tests the selected problem and offer honestly. Interest in an explanation, willingness to inspect a solution and willingness to purchase are separate observations.

Strategyzer’s value-proposition testing roadmap separates testing needs, solution and willingness to pay. Apply that distinction without pretending an unavailable product is already ready for use.

The next step might be a workflow review, an agreed technical check or a clearly scoped paid start. State what exists, what the buyer receives and what remains uncertain. Record the actual action rather than labeling every positive reply as demand.

Keep segment, pain, offer and wording distinguishable. If you change all of them between batches, the result cannot isolate the effect of a headline. Select the learning question before the activity, using which GTM experiments to run first.

What would make you reverse the campaign choice?

Write the strongest reason to reopen the choice before launching. A disconfirmation condition makes it easier to use unwelcome evidence instead of explaining every poor result away.

Possible reasons include repeated absence of a relevant decision owner, a necessary capability the product cannot supply, or buyers consistently prioritizing the competing problem. These are examples to tailor, not universal rejection rules.

Product Talk describes opportunity choice as revisitable when new information arrives. Keep the selected pain, evidence, decision owner and review trigger together. Preserve declined opportunities and post-sale outcomes as part of that evidence.

If the evidence challenges the account definition rather than the pain, use refining the startup ICP from sales evidence. Do not quietly redefine the segment to make the campaign appear successful.

When should you wait instead of increasing campaign pressure?

Wait when the buyer cannot benefit under current conditions, the product cannot deliver the central promise or the evidence only supports general interest. More forceful messaging does not resolve those limitations.

Ask about uncertainty and competing priorities when a suitable buyer declines. Respect a clear refusal and record the reason. There is no universal interview count, conversion benchmark or pain score that proves your first campaign will work. The useful result can be a narrower test, a different problem or a decision not to proceed yet.

Building the campaign around a useful buyer decision

Piet Baudoin of Poldermarketing works remotely in Dutch and English with post-seed startups seeking a first customer, a second and a repeatable go-to-market process that reaches customers who are genuinely happy with the product. He can connect buyer research to positioning and visibility in Google and AI answers.

He builds and runs AI automations with care, including lead follow-up, enrichment and qualification, CRM setup, reporting, content distribution and tool integrations. He can set up a CRM and read Search Console queries while the founder keeps the strategic decision. Explore positioning and messaging or request the free growth scan.