Technographic ICP criteria tell you when an account's existing stack creates a reason to care, a path to integrate, or a barrier to adoption. Treat each technology signal as a fit condition to test. Ask whether the stack changes the value, implementation, or problem your offer can address. Technographics can show which problems are likely to occur because the stack reveals what may break.1 Build criteria around that connection, then let account outcomes decide whether each signal belongs in the ICP.
Set the outcome
Start with the result a good account needs to achieve for your offer to make sense. This keeps the technology list tied to a commercial result instead of turning it into an inventory of familiar platforms.
A business should identify what it is trying to accomplish when defining success criteria for its ideal customer.2 Write that outcome plainly, then ask which parts of the account's environment affect it. A technology belongs in the ICP when its presence, absence, or configuration changes whether the account can gain value, adopt the offer, or support the required integration.
Ask:
- What result should this account reach after adopting the offer?
- Which part of its existing environment affects that result?
- What would make the offer difficult or impossible to use?
Move on when you can explain why each proposed technology signal matters to the outcome.
Map the stack
Map the account's environment in layers that help you understand fit. Keep the map broad enough to find dependencies and narrow enough for outbound work.
Technographic dimensions include the current stack, the integration surface, and technology maturity.3 Useful fields can cover the CRM, marketing tools, infrastructure host, and daily sales platforms an account uses.4
For each account, record the systems already in place, the systems your offer must connect to, the infrastructure or hosting condition that affects delivery, and the maturity signal that shows whether the account can support the change.
Ask:
- Which systems run the process today?
- What has to connect before the offer can work?
- Where does the account host the relevant infrastructure?
- What capability needs to exist before implementation can start?
Record the answer at account level. A vague field such as uses modern tools will not help you decide who to contact or what to ask.
Find the fit signal
A stack description becomes an ICP criterion when it changes your decision. Separate a required condition from a prioritization signal and from a detail that has no effect on fit.
A solution may have to integrate with certain technologies to be a fit for the seller's company.5 Integration dependencies and integrated technology are a major consideration for IT stakeholders.6
Turn that into a testable condition. A required connection can act as a gate. A common adjacent platform can help prioritize an account. A maturity indicator can tell you whether the account has the capacity to implement the offer.
Ask:
- Which existing system must this work with?
- Which integration would block adoption if it were missing?
- What does the current stack suggest about the problem you may uncover?
- Which technical condition would change your outreach plan?
Listen for concrete dependencies. If the answer stays at the level of general interest, keep the technology signal as a hypothesis and continue the conversation.
Write checkable criteria
Write every criterion so another person can inspect the account record and reach the same fit decision. The wording should tell you what to look for, how to interpret it, and what action follows.
Use a simple structure:
- Technology: the installed platform or category.
- Dependency: the connection or infrastructure condition that matters.
- Maturity: the capability that makes adoption possible.
- Decision: the outreach or routing action triggered by the finding.
For each field, define acceptable values and the evidence that supports them. Keep a must-have condition separate from a preference. If missing the condition blocks value, treat it as a gate. If it changes priority without blocking use, treat it as a ranking signal.
Ask:
- Can this field be answered from an account record or a direct conversation?
- Would a different answer change whether the account enters the sequence?
- Does the field describe fit, or does it merely describe the account?
Remove fields that produce interesting descriptions without changing a decision.
Validate against outcomes
Use actual account outcomes to test whether a technology signal belongs in the ICP. This is where an appealing theory earns a place in the operating model or gets removed.
Win/loss analysis is the most reliable input for building an ICP definition.7 Closed-won data shows which firmographic and technographic attributes predicted purchase, while churned-customer data shows which attributes predicted failure.8
Compare the technology conditions in accounts that purchased with those in accounts that later failed. Look for signals that separate the groups, then ask whether the difference makes sense operationally. Outbound sales data is a better signal of what is working than leads from investors and friends.9
Ask:
- Which technology conditions appeared in accounts that bought?
- Which conditions appeared in accounts that failed to reach value?
- Did the signal affect implementation, adoption, or the problem itself?
- Does the signal improve account selection when tested against outbound results?
Keep the criterion when it helps separate outcomes and you can explain the mechanism. Remove it when it appears everywhere or has no clear effect on fit.
Score and rank
Scoring helps you use several technology signals without letting a convenient field dominate the decision. Apply it after the criteria have a clear meaning and the outcome review has exposed weak signals.
An ICP score can be calculated as the sum of each attribute match multiplied by its attribute weight.10 Attribute match can be binary or scaled to show how closely an account fits a criterion.11 Attribute weight should represent the importance of the criterion based on its relationship to win rate or lifetime value.12
Keep blocking conditions visible outside the total score. An account can have several favorable signals and still fail a required integration. Use the score to rank accounts that pass the gates, then set the action for each range of fit.
Ask:
- Which criteria should stop outreach when they fail?
- Which criteria should change priority?
- Does the weight reflect an observed outcome or a personal preference?
- What action should follow a high, medium, or low fit result?
A score should make a decision easier to repeat. If people need to debate what each field means, fix the criteria before adjusting the arithmetic.
Put criteria into daily work
A useful definition has to appear where account decisions happen. Keep the operating version close to the records, filters, and routing actions that shape outbound work.
Operationalizing an ICP requires queryable CRM fields, scoring logic or filters, automated writing of criteria to the Account object, and a shared ICP definition used by sales, marketing, and Customer Success.13
Map every criterion to a field that can be searched or filtered. Make the fit result visible before outreach begins, and connect it to a clear action such as prioritization, exclusion, or a different question. When the account record changes, update the fit signal so the workflow reflects the current stack.
Review the fields after enough account outcomes have accumulated to expose false positives and missed fits. Change the criterion when the observed result no longer matches the decision it was meant to support.
What not to do
These mistakes turn technographics into decoration or false certainty. Keep them out of the workflow.
- Do not keep a technology field simply because you can collect it when product fit does not depend on adjacent tools.14
- Do not assign scoring weights before comparing both closed-won and churned-customer data.15
- Do not leave ICP criteria in a shared drive when they need to constrain daily go-to-market decisions.16
- Do not assume the initial ICP is correct, since most founders initially got their ICP wrong.17