The company fits your ICP. The problem might not.
Two companies can fit the same ICP and need different next steps. Research the use case and timing separately before assigning buying urgency.
Imagine two companies with the same industry label, similar headcounts and the same broad software category. One has a problem your team can help with. The other is quite happy with the way it works.
Put them into a spreadsheet with only company attributes and they can look almost identical.
A FullFunnel.io LinkedIn post argues for researching use cases, challenges and buying triggers alongside a broad customer profile. It is consultancy advice, not a measured account of how all buying teams behave. The distinction is still useful: an ideal customer profile describes where your offer could fit. It cannot establish that a particular company has a problem worth solving now.
The same profile can hide different work
Consider two fictional software-services buyers. Both sell B2B software and have growing engineering teams. Both appear to fit a consultancy’s target profile.
The first is bringing an acquired product into its platform and has asked for help evaluating integration options. The second is hiring to maintain its existing product. A generic “growing software company” label hides the difference between those situations.
The second company might become a suitable buyer later. It might also have all the capability it needs internally. Neither conclusion follows from its headcount.
Keep both companies in the fit review. For the acquisition, investigate who owns the integration decision. For the hiring company, first find out what the new team is there to do. Give the two records different questions before giving either an urgency score.
Ask a use-case question before assigning urgency
For each account, write what the offer could help it do. If the answer is “improve efficiency” or “scale faster,” make it more specific.
In the fictional acquisition example, the question is whether the team needs to compare ways to connect two products. That is a task someone can confirm, reject or refine. It also gives the seller a basis for choosing relevant past work.
Record the evidence behind it. A buyer statement carries different weight from a public acquisition announcement. The announcement may justify a question; it does not prove that external integration help is needed.
Then investigate timing separately. What event or constraint makes the task worth discussing now? Has the buyer named a date? Is there an existing review? If you have no evidence, keep timing unknown.
Give fit, need and timing their own fields
A simple account review can use three questions without turning them into one opaque score:
| Question | What would support an answer? |
|---|---|
| Could we serve this account? | Relevant offer, operating constraints and a credible delivery fit. |
| Is there a problem we could address? | A stated need or a clearly labeled hypothesis grounded in evidence. |
| Is a conversation appropriate now? | A buyer-agreed step, relevant current event or another legitimate reason to investigate. |
Add contact eligibility and account ownership before taking action. A promising use case does not cancel an existing relationship or a request to stop contact.
An unknown is a useful result. It tells the next person what to investigate instead of disguising the gap inside a score.
Choose different next steps for different accounts
A good-fit account with a confirmed need and an agreed review can move toward that discussion. A good-fit account with a plausible need but no timing evidence may need a modest research question. A company with a current event but poor service fit may belong outside the queue.
For the two fictional buyers, the first needs a discussion of the integration decision. The second might need no outreach at all. Treating them differently is the point of doing the research.
Avoid a forced urgent category for every account. It encourages the team to turn ordinary company news into buying intent.
Learn from the deals you can inspect
Review a small set of completed opportunities with the people who worked on them. Keep the actual customer statements and constraints beside the outcomes. Ask which use cases made your work relevant and which apparent matches turned out to be weak.
Include losses and decisions to do nothing. A collection of successful examples alone can make the offer appear suitable for more situations than the evidence supports. Record the selection method and avoid presenting a small internal review as a market study.
Use the findings to improve the questions your team asks. The why-now outreach guide shows how to carry a supported hypothesis into a message without overstating it.
RevQ connects prospect context with offerings and past work in its sales-preparation approach. The useful test is whether that connection survives inspection of the specific use case.
At the next account review, pick two companies your spreadsheet ranks alike. Write the work each might need help with, then mark what you actually know. If one row is mostly unknowns, that is where the next research task belongs.
About this article: AI-assisted writing and editing, informed by the linked public discussion. Illustrative examples are labelled; they are not customer case studies. Read our editorial approach.
Updated October 3, 2026