Define an ICP around the problem a company is trying to solve, the workflow where it appears, and the business result attached to it. Test whether your offering can solve that problem before spending time describing the account or writing outreach. Choosing the problem can take as much work as choosing the customer.1 Talking to the wrong people can make a strong idea seem bad and lead you to give up.2
Use fit as a gate
Run the account through the problem before letting the account define the pitch. Start with a problem hypothesis, trace it to the workflow where it appears, and then identify the business reason to solve it.
| Stage | What you are trying to learn | Example question |
|---|---|---|
| Define | whether the company has a problem you can solve3 | "What is the problem that we expect this company or this prospect to have?"4 |
| Trace | the root cause and business impact | What causes it, and what does it affect? |
| Prioritize | whether it is the highest-priority business problem5 | What makes this worth solving now? |
| Map | the job and workflow behind the use case6 | What job is the team trying to complete? |
| Match | whether the offering fits the problems and challenges7 | Where would this fit in the current workflow? |
| Validate | whether there is a compelling reason to buy8 | Why change now? |
An ICP exercise should identify the companies most likely to have use cases where the offering will help most.9 Without a relevant problem, prospects tend to struggle to understand how to use a product or achieve its benefits.10
Start with a problem hypothesis
Start with a working view of the problem before asking the prospect to confirm or correct it. The hypothesis keeps the conversation focused while leaving room for the prospect's own account of what is happening.
Before a discovery call, have a clear sense of the problems you solve and their root causes.11 Write down the problems you hope the prospect has before the conversation begins.12 Connect each problem to its cause and impact, then turn that line into a question to test.
A customer pain point is an unmet need or frustration identified during the sales process that remains unresolved.13 Pain can appear as an operational hurdle, a financial constraint, or a technological limitation.14 Keep the wording close to the work the prospect has to do. Ask what happens, who it affects, and what follows from it.
Trace the workflow
Pain becomes useful for ICP work when you can place it inside the workflow that produces it. Ask the prospect to walk through the work, then separate the visible symptom from the underlying cause.
Build a problem identification chart with the problem, its impact, and its root causes.15 Break down what ideal users need to do to achieve value.16 Once you know the ICP, customer challenges tend to be similar, with subtle differences.17 Use those differences to sharpen the profile and the questions while keeping the underlying problem consistent.
Ask where the workflow starts, what triggers it, where it slows, and who feels the result. Ask what the team does when the problem appears and what prevents that response from working. Record the prospect's language for the task, the obstacle, and the consequence. Move on when you can describe the workflow, its root cause, and its impact in terms the prospect recognizes.
Prioritize the business pain
A problem can exist for a long time without earning attention. Find out whether it carries enough business weight to support a change.
Test whether the offering can solve the prospect's highest-priority business problems.5 Check whether the target customer has a compelling reason to buy.8 Connect the observed workflow to the business case.18
Ask which problem receives attention when tradeoffs appear. Ask what the problem costs in time, money, risk, missed output, or blocked work. Ask what makes the issue worth addressing now and what happens if the company leaves it alone. Move on when the prospect can explain why this problem outranks other work and what result would justify solving it.
Match the workflow to the use case
Turn the problem map into a specific use case. It should show where the offering enters the workflow, what task it supports, and which business problem that task addresses.
A relevant use case matches a pain the customer is currently facing and that you have just identified.19 Check that the offering fits the problems and challenges you uncovered.7 Frame the use case around the function that owns the task, then explain why the offering fits that function.20
Ask who performs the task, what they do today, and where the offering would change the process. Ask which part of the workflow would produce the business result. Keep the use case narrow enough for the prospect to recognize it in current work.
Validate and refine the ICP
Validation links the problem hypothesis to the responses you get from outbound. Keep the profile specific enough to guide targeting, and update it when the use cases change.
Great ICPs consist of specific, measurable qualities.21 A precise ICP supports targeting the right personas and building a repeatable sales motion with the same messages and levers.22 Data from outbound sales is a better signal of what is working than leads from investors and friends.23 Refine the ICP as the products and use cases grow.24
Record which account conditions appear alongside the problem, which workflow produces the use case, and which business result creates urgency. Compare those patterns across conversations. Keep an attribute when it helps predict the problem, workflow, or business reason. Remove it when it adds description without improving your ability to choose the next account.
What not to do
Use these checks before a call and after a run of conversations.
- Do not assume you know what is troubling the customer. Ask appropriate questions and listen carefully.25
- Do not flatten every account into the same pain statement. Customer pain points are more varied than expected.26
- Do not let a loosely described ICP steer scaling decisions. Few late-stage founders can describe their ICP with enough granularity to steer the business.27
- Do not ignore the cost of a poorly defined ICP. It can show up as high CAC, low conversion rates, high marketing spend, and bogged-down product roadmaps.28
- Do not pitch before checking whether the product fits the prospect's use case.29
Before your next call, write the expected problem, its cause, its impact, and the workflow where it appears. During the conversation, connect that workflow to a high-priority business problem, then record what the outbound response says about the ICP. Use that record to decide which accounts deserve the next conversation.