ICP Definition & Account Fit Scoring

Turn your ICP into criteria sellers can inspect.

Make fit explainable.

Define and review the attributes that describe a good-fit account, then apply them to researched accounts with visible reasons, evidence and explicit disqualifiers.

Fit and signals kept separateReasoning visible to the repSources remain inspectable
Live account intelligence
Recognisable accounts. Real changes. Clear evidence.
Priority accounts•••
Why now?Public signal
Palo Alto Networks completed its acquisition of Portkey to expand security for AI agents. OneSales shows the source beside the account’s ICP fit and known stakeholders, so the rep can decide whether the change creates a relevant reason to engage.

Illustrative public signals. Companies shown are not necessarily OneSales customers.

One connected account viewRead-only CRM contextCompany developmentsPeople movesSeller contextSource evidence
The use case

What is ICP definition and account-fit scoring?

It translates an ICP into reviewed attributes, requirements and exclusions, then measures researched accounts against those inputs. OneSales keeps the score, reasons, evidence and any applicable cap visible for inspection.

An ICP only helps when its criteria are explicit enough for a seller to use and a manager to inspect. A broad label or hidden score cannot explain why an account fits.

Terms such as enterprise, digital-first or fast-growing need explicit criteria and exclusions. Otherwise every territory interprets the ICP differently and the score becomes difficult to govern.

01

Reps interpret the ICP differently across territories.

Labels such as enterprise, strategic or digital-first mean different things to different teams. Without explicit attributes and exclusions, territories build their own version of a good-fit account.

02

Disqualifiers are applied inconsistently or only after work has started.

A clear disqualifier discovered after research and outreach wastes seller capacity. It also makes pipeline inspection harder because accounts entered the motion on inconsistent assumptions.

03

A fit score becomes difficult to govern when the underlying criteria are hidden.

A number cannot be governed if RevOps cannot see the active inputs, evidence and any cap applied to the result. Sellers are unlikely to trust a score they cannot explain.

The operating change

Turn ICP language into a shared qualification standard.

RevOps and sellers need to see the inputs behind fit, understand explicit disqualifiers and keep fit separate from recent changes or assumptions about readiness.

The current motion

The ICP is open to interpretation

  • Territories apply broad labels differently.
  • Disqualifiers appear after work starts.
  • The score is difficult to explain.
  • Fit is confused with immediate readiness.
With OneSales

The active fit criteria remain reviewable

  • The seller profile records approved attributes and exclusions.
  • Accounts are measured against active criteria.
  • Reasons, evidence and score caps remain visible.
  • Current changes stay separate from fit.
How it works

The scoring model has to be governable.

A useful model starts with reviewed inputs, makes exclusions explicit and preserves the reasoning. It should help a seller explain fit—not replace judgement with a number.

01

Research the seller profile

Use supported company sources and supplied documents to create a starting ICP profile.

Baseline
02

Review and edit the criteria

RevOps or the seller can inspect the proposed industries, geographies, size ranges, department requirements, technologies, vendor relationships and exclusions before activation.

Research
03

Score researched accounts

Measure account fit against the active ICP attributes and preserve the reasons and supporting evidence.

Decide
04

Use the result in account work

Filter and inspect accounts by fit while keeping current company and people changes as a separate decision input.

Execute
Your data. Supported workflows.

Use the context where OneSales supports it.

Work in OneSales. When full-suite access is enabled, retrieve supported account intelligence read-only from Claude through MCP. Supported CRM account and contact context can be imported read-only, and reviewed drafts can be opened in Gmail or Outlook.

The workflow can change. The evidence and seller review remain visible.

OneSales app

Research and act in one place

Review context, inspect evidence, map stakeholders, and move into supported account work.

Claude via MCP

Retrieve supported context

Use read-only account intelligence when full-suite MCP access is enabled.

CRM source

Use supported CRM context

Import account and contact context read-only. OneSales does not currently write changes back.

Email workflow

Keep the seller in control

Review and refine a draft, then open it in Gmail or Outlook. The email client remains the sending surface.

What changes for the team

A shared definition of fit. Fewer qualification arguments.

The result is a clearer basis for territory decisions, inspection and coaching without claiming the model discovers the whole market or predicts buying intent.

01

Creates a shared, reviewable definition of account fit.

Give sellers and RevOps one editable set of attributes, requirements and exclusions for evaluating account fit across territories and planning cycles.

02

Helps sellers understand why an account fits—not only the score.

Show the reasons and supporting evidence alongside the fit result, so a seller can explain the assessment and identify what still needs validation.

03

Makes explicit disqualifiers and exclusions easier to govern.

Apply required conditions, exclusions and score caps consistently instead of relying on individual interpretation after work has already started.

04

Keeps fit separate from recent signals or assumptions about readiness.

Treat fit as one decision input. Recent company or people changes remain separate, and neither a high score nor a public signal is presented as proof that an account is ready to buy.

The CRO asks:

“Does our account focus match the segments, operating problems and outcomes we have chosen to pursue?”

RevOps asks:

“Can we review the active criteria, exclusions and evidence behind every fit decision?”

The seller asks:

“Why does this account fit, what could disqualify it and what still needs to be validated?”

Common questions

What sales and RevOps usually want to know.

Visible answers—no accordions—cover seller trust, data ownership, supported workflows, and day-to-day adoption.

Does OneSales calculate TAM?

No. OneSales supports ICP definition and account-fit scoring. It does not currently calculate market size or discover every account in an addressable market.

Which ICP inputs are supported?

Inputs can include segments, industries, geographies, revenue and employee ranges, ownership type, required departments, technologies, vendor relationships, notes, disqualifiers and excluded industries.

Does a high fit score mean the account is ready to buy?

No. Fit explains whether the account matches the active ICP. Recent company or people changes are separate inputs, and neither is third-party buying intent.

Can RevOps change the model?

Yes. The proposed seller profile and ICP inputs can be reviewed and edited before use. Fit reasons, evidence, disqualifiers and any score cap remain inspectable.

Test the workflow against a real territory.

Bring a representative account list and the sales logic your team uses today. See how OneSales keeps the evidence visible and the seller in control.

Book a Demo