The ideal customer profile (ICP)
An ideal customer profile describes the kind of account worth acquiring: the company, not the person, that gets the most value from your product and returns the most value to your business. In B2B it is a firmographic and situational sketch, industry, size, budget, the tools already in place, the trigger events that signal readiness. Its purpose is exclusion. A good ideal customer profile tells a team who to ignore, which is the harder and more valuable half of targeting.
The ideal-customer concept grew out of B2B sales qualification and account-targeting practice, where reps had long sorted prospects by fit before spending time on them. The framework most associated with the term in software is Lincoln Murphy's, developed through his customer-success and SaaS-growth writing. Murphy frames the ideal customer around being Ready, Willing, and Able: ready because they know they have the problem and feel urgency, willing because there is a champion and a catalyst for change, and able because they have the budget and authority to act.
Murphy's stronger claim is about consequence. The ideal customer profile should dictate everything from the features you build to the words you use in marketing, because a product optimised for the wrong account decays into churn no matter how good the funnelFunnelGrowthA conversion funnel tracking user progressionView reference → looks. The profile is a forward decisionDecisionStrategyA recorded decision with context, rationale, and consequencesView reference →, not a backward description of whoever happened to buy.
Account-based marketing tightened the definition through the 2010s, drawing a clean line between the ideal customer profile (the account) and the buyer personaPersonaUserAn archetype representing a user segmentView reference → (the individuals inside it). The mature practice builds the profile from evidenceEvidenceValidationData supporting or refuting a hypothesisView reference →: analyse your best existing customers, the ones who retain, expand, and refer, then abstract their shared firmographics and trigger events into a profile you screen new demand against. The discipline lives in keeping it narrow, because a profile that admits everyone guides nothing.
A workflow-automation startup notices its retained, expanding accounts cluster tightly. They are operations teams at companies of 50 to 200 people, in logistics and e-commerce, already running a specific CRM, and they tend to adopt right after a funding round or a new operations hire. The team writes that as the ideal customer profile and screens inbound demand against it.
A 2,000-person enterprise arrives with a large potential contract but no fit on tooling or team shape. The profile says decline, or at least deprioritise, because past accounts of that shape churned after a long, costly sales cycle. Holding the line, the team concentrates spend on the 50-to-200 logistics segment, and pipeline quality rises even as raw lead count falls. The profile earned its keep by making a tempting but wrong deal easy to refuse.
In the Unified Product Graph, ideal_customer_profile is a hub in the Go-To-Market domain within the Business, GTM and Growth region, sitting second in the canonical sequence right after GTM StrategyGo-To-MarketA go-to-market strategyView reference →. It is targeted through gtm_strategyGTM StrategytargetsIdeal Customer Profilehierarchy and then drives the rest of go-to-market: gtm_strategy_targets_ideal_customer_profileIdeal Customer ProfileinformsPositioningcausal, ideal_customer_profile_informs_positioningIdeal Customer ProfileshapesMessagingcausal, and ideal_customer_profile_shapes_messagingIdeal Customer ProfileshapesSales Motioncausal. It crosses into the Users and NeedsNeedUserA user need, pain, desire, or constraintView reference → region through ideal_customer_profile_shapes_sales_motionIdeal Customer Profilemaps toPersonacross-domain, which is where the graph keeps the account-versus-individual distinction honest. Its structured properties, ideal_customer_profile_maps_to_personacompany_size in standard B2B buckets, industry, trigger_events, tools_used, are what make profiles across products comparable, so the targeting decision is recorded as data rather than left in a deck.
Type-specific fields on BaseNode
company_sizestringTarget company size. Standard B2B segmentation buckets so ICPs across products are comparable.
industrystringTarget industry vertical
budget_rangestringExpected budget range for the solution
trigger_eventsstring[]Events that signal buying readiness
tools_usedstring[]Technologies the ideal customer already uses
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
9 edge types connected to this entity.
gtm_strategy_targets_ideal_customer_profileideal_customer_profile_maps_to_behavioral_segmentideal_customer_profile_maps_to_personaideal_customer_profile_targets_behavioral_segmentideal_customer_profile_targets_market_segmentdeal_references_ideal_customer_profileideal_customer_profile_informs_positioningideal_customer_profile_shapes_messagingideal_customer_profile_shapes_sales_motion