Technographic ICP criteria

Technographic ICP criteria should show whether an account can adopt, connect, and get value from an offer. Build them around the systems that shape product fit, then place useful signals where they can change account selection and follow-up. A stack list alone is a weak ICP. Current stack, integration surface, and technology maturity turn installed technology into a fit question.¹

Define the use case

State what the account must be able to do before choosing which technologies to track. Each field should answer a practical question about adoption, integration, or value.

Many B2B companies spend as much time choosing the problem as identifying who to solve it for.² Companies that skip the customer side often regret it.³

Write the use case first, then ask:

• What must already exist for the account to use the offer?
• Which systems must the offer connect with?
• What technical condition would make adoption difficult?
• Which technology signal would change who gets worked first?

A criterion belongs in the technographic ICP when its presence, absence, or condition changes the answer to one of those questions. If you cannot trace a field to adoption, integration, delivery, or customer value, leave it out.

Map the dimensions

Lay out the stack in layers so each signal has a clear job. Start with what the company runs, then record what the offer needs to touch and what the stack says about the account's ability to adopt change.

Technographic criteria can include the CRM, marketing tools, infrastructure host, and daily sales platforms a company uses.⁴ Keep integration dependencies in a separate view because integrated technology is a major consideration for IT stakeholders.⁵

Ask:

• What systems already run across the account?
• Which adjacent tools are required for the use case to work?
• Where does the account host the infrastructure involved?
• Which platforms are part of the daily operating workflow?
• What does the existing stack suggest about technical maturity?

Keep current tools separate from required integrations and maturity signals. This lets you distinguish a hard compatibility condition from a weaker preference. Record each technology's role in the use case, not just its presence.

Test patterns against customer outcomes

Use customer outcomes to decide which stack patterns deserve weight. Win/loss analysis is the most reliable input for building an ICP definition.⁶ Closed-won data shows which firmographic and technographic attributes predicted purchase, while data from customers that churned shows attributes that predicted failure.⁷ Both views are required before you assign any scoring weight.⁸

For each account outcome, record the technology condition and the result. Ask:

• What did the accounts that purchased already have in place?
• Which integration conditions appeared in successful implementations?
• Which stack patterns appeared in accounts that failed to reach value?
• Which signals recur across both the purchase and failure views?

Keep a signal when you can explain why it matters to the use case. A technology earns a place in the ICP when the account outcome gives you a reason to keep watching it.

Turn patterns into criteria

What must be present

What counts as evidence

Whether the signal is

What account action follows

• What must be present
• What counts as evidence
• Whether the signal is
• What account action follows

Convert the patterns into rules that someone can apply to an account record. Each rule should be clear enough that two people reach the same fit decision from the same account information.

An ICP score can be calculated as the sum of each attribute match multiplied by its attribute weight.⁹ An attribute match can be binary or scaled from 0 to 1 or from 0 to 100.¹⁰ The weight should reflect the importance of the criterion based on its relationship with win rate or lifetime value.¹¹

For each technology signal, write:

• what must be present;
• what counts as evidence;
• whether the signal is required or adds confidence;
• what account action follows from the result.

Use account language. A rule such as a required integration condition gives someone a clear check. A rule that says an account should have a sophisticated stack leaves the decision open to interpretation. Keep unknown values separate from negative matches so missing information does not quietly become a poor-fit verdict.

Put the rules into workflow

Make the criteria usable before outbound activity depends on them. A fit definition earns its place when it changes account selection, prioritization, or handoff inside the working system.

Operationalizing an ICP means converting a static profile document into an active, system-embedded signal that constrains daily go-to-market decisions.¹² In practice, that requires structured CRM fields, scoring logic or filters, automatic writing of criteria to the Account object by enrichment and workflow tools, and one shared ICP definition used by sales, marketing, and Customer Success.¹³

Create queryable fields for current stack, integration surface, maturity, and the conditions that affect adoption. Make the result visible in the account record and usable in filtering. A criterion that cannot change a list, route, campaign, or handoff is documentation rather than an operating signal.

Validate with outbound

Treat the first version as a testable hypothesis. Outbound activity shows whether the criteria help you choose accounts that respond and progress.

Data from outbound sales is the best signal for what is working, compared with leads from investors and friends.¹⁴ Compare outcomes among accounts that fit the technology rules and accounts that do not. When a recurring outcome conflicts with a criterion, inspect the rule and the underlying integration or maturity assumption before expanding the target set.

Keep the feedback loop tied to the fields you defined. A response pattern is useful when you can trace it to a recorded stack condition, and a poor result is useful when it shows which condition failed to predict fit.

What not to do

These errors make a technology list look precise while leaving account selection unchanged.

• Product fit should determine whether you include a technology signal, even when the signal is easy to find.¹⁵
• An ICP that exists only in a slide deck has no measurable effect on pipeline, campaign, or retention decisions.¹⁶
• Pipeline coverage numbers are unreliable when they are not segmented by ICP tier.¹⁷
• Most founders initially got their ICP wrong.¹⁸