An ideal customer profile (ICP) example is a filled-in description of the type of company most likely to buy, pay full price, and stay a customer, built from real attributes like industry, company size, funding stage, tech stack, and the trigger that made them buy, not from a generic buyer persona. Below are five worked examples across different B2B business models, each with the fields actually filled in, followed by how to build one for your own company.
This is for founders, sales leaders, RevOps, and SDRs who have read the standard "ICP vs buyer persona" explainer already and want to see what a finished profile looks like with real values in every field, not a blank template.
What does a filled-in ideal customer profile actually look like?
Most ICP guides give you a template with blank fields (industry, company size, geography) and one or two abstract example sentences like "targets small to medium businesses." That's a starting shape, not a working example. A useful ICP example fills every field with a specific, checkable value, the kind you could hand to someone doing prospecting and have them build a matching list from it without asking follow-up questions.
The five examples below cover different B2B business models on purpose, because the fields that matter shift depending on what you sell. A usage-based dev tool cares about tech stack and team size. A services agency cares about budget and decision-maker access. A compliance product cares about regulatory triggers that a generic "company size" filter won't catch.
What are five ideal customer profile examples across different B2B business models?
Example 1: B2B SaaS selling to mid-market companies
| Field | Value |
|---|---|
| Industry | Software, fintech, e-commerce (verticals with a dedicated ops or RevOps function) |
| Company size | 50-500 employees |
| Revenue | $5M-$50M ARR |
| Funding stage | Series A or Series B (has budget authority but still cares about proving ROI) |
| Tech stack signal | Already runs a CRM and at least one marketing automation tool |
| Buying trigger | Recently hired a RevOps or Sales Ops lead, a signal that process is becoming a priority |
| Disqualifier | Pre-seed companies with no dedicated ops headcount; they lack both budget and a champion |
Example 2: Agency selling B2B lead generation services
| Field | Value |
|---|---|
| Industry | Any B2B vertical with a sales team, most commonly software and professional services |
| Company size | 10-100 employees |
| Revenue | $1M-$20M |
| Average deal size | $10,000+ average contract value on the client's own product, so the ROI math on outsourced lead gen makes sense |
| Buying trigger | Recently posted an open SDR or BDR role, then paused hiring, a signal they need pipeline but don't want to build the team in-house yet |
| Disqualifier | Companies with an in-house SDR team of 5 or more; they've already solved the problem this agency sells |
Example 3: Usage-based developer tool (API or infrastructure product)
| Field | Value |
|---|---|
| Industry | Software companies building products with a technical core: fintech, healthtech, developer tools themselves |
| Company size | 20-200 employees |
| Team signal | Has an engineering team of 5+ and a named platform or infrastructure owner, not just a generalist CTO |
| Tech stack signal | Already uses adjacent infrastructure (a specific cloud provider, message queue, or observability tool) that predicts the product fits their stack |
| Buying trigger | Job postings mentioning the specific technical problem the product solves, for example "reduce latency" or "improve observability" |
| Disqualifier | Teams under 5 engineers; the coordination overhead of adopting new infrastructure usually isn't worth it yet at that size |
Example 4: Compliance or security software for regulated industries
| Field | Value |
|---|---|
| Industry | Healthcare, financial services, insurance (regulatory requirement is the core driver, not a nice-to-have) |
| Company size | 100-1,000+ employees (large enough to carry real regulatory exposure) |
| Geography | Operates in a jurisdiction with the specific regulation the product addresses |
| Buying trigger | A recent leadership hire in compliance, security, or a "Head of Trust" style role, or a recent funding round that typically comes with new audit requirements |
| Disqualifier | Companies below the regulatory threshold that triggers the requirement; the product solves a problem they don't legally have yet |
Example 5: Marketplace or vertical SaaS selling to SMBs
| Field | Value |
|---|---|
| Industry | A specific vertical the marketplace serves (for example, home services, healthcare clinics, or independent retail) |
| Company size | 1-50 employees, often owner-operated |
| Geography | Concentrated in the metro areas or regions the marketplace has already built supply or demand density in |
| Buying trigger | Recently opened a second location, or posted a job for a role the product replaces or supports |
| Disqualifier | Businesses outside the marketplace's active geography; density matters more than company quality at this end of the market |
What fields should every ideal customer profile example include?
Across all five examples above, the same categories of field keep showing up, even though the actual values differ by business model:
- Firmographic: industry, company size, revenue or funding stage, geography.
- Technographic: the specific tools or infrastructure a good-fit company already uses.
- Behavioral or trigger-based: a recent, checkable event (a hire, a funding round, a job posting) that indicates the company needs the product now rather than in the abstract.
- Disqualifiers: the traits that make a company look like a fit on paper but aren't, which matter as much as the positive criteria because they keep a prospect list from bloating with dead-end accounts.
A profile missing the trigger and disqualifier fields still describes a market segment, not an ideal customer profile. The trigger is what turns a static description into something a sales or marketing team can actually act on.
How do you build your own ideal customer profile?
- Start from your best existing customers, not your whole customer base. Pull the accounts with the highest retention, the fastest sales cycle, and the least discounting, and look for what they have in common.
- Separate firmographic facts from behavioral triggers. "50-500 employees" describes a segment; "recently hired a RevOps lead" describes a moment. You need both, but they get validated differently, one from your CRM's historical data, the other from watching what your best deals had in common right before they started.
- Write down disqualifiers explicitly, not just target criteria. If you know a segment looks like a fit but consistently churns or never closes, name it so the profile filters it out instead of quietly attracting it.
- Test the profile against real companies, not just against your own customer list. If you can't find close matches beyond the customers who already inspired the profile, the criteria are probably too narrow, or too dependent on one field you happened to have data for.
- Revisit the profile when your product or market changes. An ICP built around your first ten customers rarely still fits once you've moved upmarket or added a feature that opens a new segment. See how to calculate TAM for a related exercise: once your ICP is defined, counting how many real companies actually match it is what turns the profile into a market-size number.
Once the profile is written down, the next problem is finding the companies that currently match it, which is a different task from defining the profile itself. A manual approach, for example searching company names and filters on LinkedIn, can confirm individual companies but struggles to surface every company matching triggers like "recently hired a RevOps lead" at once, since that kind of signal isn't a standard filter field.
How does Retriever help here?
Retriever is a semantic ICP search engine: instead of translating a profile like the ones above into a set of filter boxes, you describe it in plain English, including the trigger and disqualifier fields, and Retriever returns a ranked list of matching companies with a match score and the source evidence behind each one.
Because the firmographic and technographic fields in an ICP example don't change often but the trigger fields do, Retriever also sets up and continuously tracks hiring, funding, tech-stack, and leadership signals, plus LinkedIn and other social listening, so a company resurfaces automatically when it newly matches the profile and carries a relevant signal, instead of requiring someone to re-run the search by hand.
See the product page for how the matching and signal tracking work, or book a demo to test it against your own ICP.
Frequently asked questions
What's the difference between an ideal customer profile and a buyer persona? An ICP describes the company (industry, size, revenue, tech stack) that is the best fit to sell to. A buyer persona describes the individual person inside that company (their title, goals, and objections) who makes or influences the buying decision. Most B2B teams need both: the ICP to find the right companies, personas to know who to talk to once you're in.
How many ideal customer profiles should a company have? Most B2B companies are best served by one primary ICP to keep messaging and targeting focused, though it's common to have a small number of secondary profiles for a different product line or market segment. Splitting into many ICPs at once usually spreads sales and marketing effort too thin to validate any of them properly.
Should an ideal customer profile include company size or just industry? Both, along with the other firmographic fields, since industry alone is usually too broad to be useful. A company size range narrows an industry down to companies that can actually afford and operationally support the product, which industry alone doesn't tell you.
How often should an ideal customer profile be updated? Whenever the product, pricing, or target market changes meaningfully, and at minimum reviewed against recent won and lost deals every few months, since a profile built from a company's first customers often stops matching who actually buys once the company moves upmarket or adds new features.