BuyerState

BuyerState methodology

Research should make a seller more certain. Not more impressed.

BuyerState is designed around an evidence-first standard: establish fit, identify meaningful change, separate fact from inference and only surface a “why now” when the evidence earns it.

BuyerState researches prospects to reduce uncertainty before a seller spends time on an account. The goal is not to produce the longest company profile or the most confident-sounding AI summary. The goal is to make the reasoning reviewable.

That means the research has to answer a small number of commercial questions, show the evidence underneath the answer and be willing to leave a question unresolved when the evidence is weak.

The four questions behind a BuyerState record

  1. Is this company relevant? Does it genuinely match the target criteria and the problem the offer solves?
  2. What is happening there? What material changes, behaviours or events can be observed?
  3. Why does it matter? Is there a defensible connection between the evidence and the commercial problem?
  4. Is there a reason to act now? Is the evidence recent and strong enough to change the account's priority today?

The first question is about fit. The next two are about context. The fourth is about timing. A useful prospect needs more than one of them.

Fact, supported inference and unknown are different things

AI is very good at turning incomplete information into a fluent story. That makes a strict boundary between evidence and interpretation essential.

Observed fact

“The company opened 12 revenue-operations roles across the UK and Germany in the last 90 days.”

This should be traceable to the underlying evidence.

Supported inference

“The company appears to be expanding its revenue-operations capability.”

This is an interpretation, but the evidence clearly supports it.

Unknown

“We cannot establish whether the company is actively evaluating a sales-intelligence platform.”

Unknown is a valid research result. BuyerState should not turn absence of evidence into a convenient buying story.

A practical source hierarchy

Not every source deserves equal weight. For material conclusions, BuyerState's research standard prefers evidence in roughly this order:

  1. First-party company sources, such as official websites, newsrooms, careers pages and leadership announcements.
  2. Official filings and public records where they are relevant and available.
  3. Trusted professional or commercial sources for structured company, people or market information.
  4. Reputable media and trade publications for externally reported events and context.
  5. Aggregators and weaker secondary sources only when the claim can be corroborated.

If two sources conflict, the answer should not simply choose the more convenient version. Prefer the stronger source, downgrade confidence where necessary and keep the uncertainty visible.

A signal is a reason to investigate, not proof of intent

A funding round, leadership hire, hiring spike or technology change can be commercially useful. None of those events proves that a company wants to buy your product.

BuyerState therefore treats a signal as observable evidence that may change an account's relevance or timing. The next step is to ask what changed, whether it connects to the problem you solve and whether another piece of evidence supports the same hypothesis.

This is why several modest but related signals can be more useful than one dramatic alert.

When the evidence is weak, fail closed

A research system becomes untrustworthy if every account is required to produce a persuasive “why now.” Some companies fit the ICP but show no current reason to prioritise them. Some show activity that is irrelevant to the offer. Some simply do not have enough reliable public evidence.

In those cases the correct output is not a better-written guess. It is a lower-confidence conclusion, a request for more evidence, or no “why now” at all.

A worked example

The company below is fictional. It demonstrates the reasoning standard, not a real BuyerState customer or prospect.

Observed evidence: Northstar Systems appoints a new CRO, posts eight sales-operations roles and announces expansion into two European markets.

Fit: Northstar matches the target company's size, geography and business model.

Supported inference: Its commercial operation appears to be entering a period of change and investment.

Potential relevance: A supplier that helps scale sales operations could reasonably investigate whether the expansion is creating pressure around process, data or tooling.

What is not known: There is no evidence that Northstar is currently evaluating that supplier's category, has approved budget, or intends to replace an existing system.

That last sentence matters. It keeps a useful prospect hypothesis from becoming a fabricated buying claim.

What BuyerState is, and what it is not

BuyerState is a prospect-research and sales-intelligence layer. It is designed to turn scattered account evidence into a concise view of fit, change, people and timing.

It is not:

  • a claim that BuyerState can see a company's private buying plans;
  • a raw alert feed that treats every company event as intent;
  • a replacement for specialist contact-data verification when verified email or phone data is required;
  • an excuse to manufacture superficial personalisation from weak evidence.

The standard is deliberately less theatrical: show the evidence, make the inference explicit, and let the strength of the research determine the strength of the conclusion.

Read the framework in practice

Start with B2B prospect research, then see how BuyerState thinks about buying signals, sales trigger events and when the evidence says not to contact an account.