Category-only targeting
Labels such as SaaS, agency, or healthcare are too broad to express the business model, customer type, maturity, or problem the offer solves.
B2B ICP Definition and Search Build
Advazon converts a broad target market into documented account criteria, buyer-role logic, title variations, exclusions, and platform-ready filters. We test the search against real companies and people before enrichment begins, so your budget goes toward prospects who match the offer instead of records that merely look complete.
B2B ICP Definition and Search Build defines the companies that fit an offer, the buyer roles involved in the decision, and the criteria needed to find them accurately. It translates business requirements into filters, keywords, Boolean logic, exclusions, and platform rules for tools such as Apollo and LinkedIn Sales Navigator.
The result is more than a broad description such as “mid-market SaaS founders.” It is a versioned search specification that documents account fit, buyer roles, title variations, exclusions, data sources, platform logic, and the sample QA required before lead sourcing begins.
Why Searches Fail
Poor targeting affects enrichment, validation, scoring, personalization, and outreach. A strong B2B ICP Definition and Search Build establishes the account and buyer rules before more data, tools, or outreach volume are added.
Labels such as SaaS, agency, or healthcare are too broad to express the business model, customer type, maturity, or problem the offer solves.
Searching only for CEO, founder, or marketing manager misses real title variants and often includes people with seniority but no relevant responsibility.
Competitors, customers, unsupported regions, unsuitable business models, tiny firms, and irrelevant functions remain hidden inside the result count.
A database may return thousands of matching titles at companies that never met the account-level definition. Clean contact data can still be commercially wrong.
Industry, seniority, function, technology, and location definitions differ by provider. A business rule may need a platform-specific approximation.
Large result counts create false confidence. Without reviewing accepted and rejected edge cases, the search can scale a hidden targeting error.
ICP Specification
Define each criterion using your offer, customer evidence, sales feedback, delivery capacity, and market constraints. Every rule should have a clear definition, source, inclusion logic, and exclusion logic before it becomes part of the search.
| Criterion | Business question | Search translation | QA rule | Decision |
|---|---|---|---|---|
| Market and model | What does the company sell, and to whom?Distinguish B2B, B2C, SaaS, services, marketplace, agency, and other motions. | Industry, keywords, company description, category, and manual evidence. | Do not trust one self-reported industry field as the full business model. | Include, exclude, or research. |
| Company size | What operating complexity can support the offer?Choose employee and, when useful, revenue ranges. | Headcount bands, revenue estimates, department size, or growth range. | Document whether the range is inclusive and how missing values behave. | Primary segment or near-fit. |
| Geography | Where can the team sell and deliver?Account headquarters and buyer location may require separate rules. | Country, state, region, city, timezone, or headquarters location. | Keep legal, language, service, and scheduling constraints visible. | Include or block. |
| Technology | Which tools imply compatibility, need, or displacement?Use technology only when it changes commercial relevance. | Current technology, complementary stack, competitor stack, or missing capability. | Record detection date and avoid treating old technology evidence as permanent. | Fit rule or context signal. |
| Growth context | What indicates timing or operational change?Hiring, funding, leadership, expansion, and intent can alter priority. | Headcount growth, job openings, recent changes, saved-account alerts, or intent filters. | A timing signal should not rescue a company that fails the core ICP. | Prioritize, not automatically qualify. |
| Buyer role | Who owns, feels, evaluates, approves, or uses the solution?Map the buying committee, not one generic title. | Function, seniority, exact titles, title keywords, persona, and current role. | Review actual responsibilities because title language varies widely. | Role group and contact priority. |
| Exclusions | Who should never enter this motion?Protect sales time, client relationships, compliance, and reputation. | Named companies, domains, industries, roles, geographies, customers, competitors, and suppression lists. | Blocking exclusions override every positive inclusion. | Reject or route elsewhere. |
| Coverage rule | How many relevant people should each account contain?Match contact depth to sales capacity and deal complexity. | One owner, multiple buying roles, seniority mix, department coverage, or fallback role. | Do not mistake more contacts for better account coverage. | Complete, partial, or no-buyer account. |
Define the eligible company universe before adding people.
Model the people involved in the decision and the evidence for each role.
Search Quality Matrix
Strong account fit is not enough if the search misses the people involved in the buying decision. Map decision-makers, influencers, operators, and relevant title variations without adding contacts that weaken overall relevance.
Account relevance controls the universe; role coverage controls access.
Add title variants, functions, seniority combinations, stakeholder roles, and a documented fallback.
Review a sample, save the search logic, estimate volume, and move accepted accounts into enrichment.
Rewrite the core ICP before purchasing data or expanding the query.
Refine business-model, size, industry, keyword, geography, technology, and exclusion rules.
Workflow
Move from commercial evidence to an approved search through defined account criteria, buyer-role mapping, platform filters, exclusions, and sample QA. Each stage produces a decision that can be reviewed before sourcing volume increases.
Define the problem, promise, use case, buying trigger, sales motion, delivery limits, and evidence behind the target market.
Translate customer evidence into core company criteria, near-fit conditions, exclusions, and priority signals.
Define responsibilities, role groups, title families, seniority, exclusions, coverage, and fallback buyers.
Map each business rule to Apollo, Sales Navigator, or the selected source and record any unavailable criterion.
Review matched, rejected, and borderline accounts and contacts; revise the logic before saving the production search.
Operational Guardrails
Store the ICP version, search owner, platform, date, filter values, assumptions, and approval state.
Preserve account eligibility independently from buyer coverage so contact availability does not rewrite fit.
Apply customers, competitors, do-not-contact records, unsupported markets, and known bad fits before enrichment.
Review strong matches, weak matches, rejected results, title edge cases, and accounts with no preferred buyer.
Saved searches and databases change. Recheck volumes, taxonomy behavior, and sample quality before each production run.
Use structured rejection reasons and opportunity outcomes to refine criteria rather than adding arbitrary filters.
Deliverables
Primary and near-fit account criteria, buyer roles, responsibilities, title families, exclusions, signals, and assumptions.
Exact filters, include and exclude values, Boolean logic, saved-search structure, unavailable criteria, and approximations.
Matched accounts and contacts with pass, reject, or review decisions plus edge-case notes and revision history.
Expected account volume, role coverage, no-buyer rate, exclusion impact, segment splits, and recommended sourcing order.
Current Platform Guidance
Platform filters execute the search, but your business still defines what qualifies. advazon. translates account criteria, buyer roles, title variations, exclusions, and fallback logic into platform-ready search rules while accounting for taxonomy differences.
Apollo documents include and exclude filters across people and company searches. It also notes that industry is a self-reported single value, while company keywords can draw from structured tags and free-text sources. That is why one field should not carry the entire ICP.
Read Apollo search-filter guidanceApollo personas can package recurring groups of people filters and be combined with other search filters. The persona should implement an approved buyer-role definition, not replace the responsibility and title analysis behind it.
Read Apollo persona guidanceLinkedIn documents separate account and lead filters, include and exclude options, live result updates, and saved searches. Its suggestions include account industry, headquarters, and headcount, plus lead company, geography, seniority, and function.
Read Sales Navigator search guidanceOfficial platform documentation reviewed August 2026. Filter names, plan availability, limits, taxonomies, and data coverage can change; verify the saved search before each production run.
FAQ
A B2B ideal customer profile is a documented set of account-level and buyer-level criteria that defines who the offer is designed for, who should be excluded, and how matching companies and people can be found and reviewed.
The ICP describes the type of company most likely to benefit from the offer. A buyer persona or role profile describes the people inside those accounts who influence, evaluate, approve, use, or block a purchase. Both are needed for account-based prospecting.
Account-first search establishes the eligible company universe before contacts are added. It prevents clean contact data from hiding poor account fit and makes buyer coverage easier to measure.
Raw titles are grouped into controlled role families using exact titles, functions, seniority, keywords, synonyms, and exclusions. A sample is reviewed because title language varies by company size, country, and industry.
No. The business definitions can stay consistent, but each platform has different taxonomies, filters, data coverage, and Boolean behavior. The search specification should map each rule to the selected platform and document any approximation.
It is ready when inclusion and exclusion rules are documented, platform filters are reproducible, a sample passes account and buyer review, expected volume is understood, and edge cases have an explicit decision.
Related Work
Build the Right Search First
Share your offer, target-market assumptions, customer examples, won and lost deals, current filters, exclusions, sales feedback, platform access, and desired volume. advazon. will turn them into a documented B2B ICP and reusable search your team can test, approve, and scale.