Build a one-page B2B ICP in 5 steps, turn it into a Getlead-ready search spec and download the criteria your team will use to qualify every prospect.
Customer reviews
Don't take our word for it
An ideal customer profile should do more than describe an attractive company. It should tell our sales and growth teams which accounts to search for, which people to include, which records to reject and which assumptions still require manual review.
The Getlead ICP Builder turns a business hypothesis into:
We begin with the company-level conditions:
Company size, stage and triggers can strengthen qualification, but we do not present them as active Getlead filters when the current B2B Search interface does not support them.
An account ICP answers “which companies?” Buyer-role criteria answer “which people?”
We define:
For the approved example:
Account: US B2B SaaS company
Function: Sales
Primary buyers: CRO, VP Sales, Head of Sales
Operational champions: RevOps Director, Sales Operations Director
Exclude: unrelated junior/assistant roles
Use the decision-maker guide to map economic buyers, champions, users and evaluators.
Current supported B2B Search criteria:
Manual qualification can include:
This separation prevents the search team from assuming a strategic requirement has already been enforced by the product.
| Rule class | Meaning | Example | |---|---|---| | Must-have | Record fails without it | US + Software + Sales function | | Preferred | Raises priority, not eligibility | Documented SDR hiring | | Exclude | Removes an otherwise attractive record | B2C-only business |
Every rule should have a “why” field. If we cannot explain why a criterion changes account suitability, it may be unnecessary complexity.
The builder scores completeness across:
The score is deterministic and editable. It does not predict revenue.
Result bands:
basic;search_ready;highly_constrained.“Highly constrained” is not automatically better. We recommend a calibration search before scaling.
The output contains:
Offer and problem
Account must-haves
Preferred traits
Exclusions
Supported Getlead filter specification
Buyer title families
Manual review checklist
Suggested segment names
Calibration plan
Download options follow the implementation logic specification. At least one real download format must exist; output cannot be a generic text block unrelated to inputs.
The next workflow is:
Use the full B2B prospect list guide, then create role coverage with JTBD-02 or enrich an existing company CSV with JTBD-03.
The CTA carries only supported search state. Free-text offer, company names and sensitive notes are not sent to analytics.
{
"event": "seo_tool_completed",
"content_id": "ft-03",
"result_band": "basic|search_ready|highly_constrained"
}
{
"event": "seo_get_started_click",
"content_id": "ft-03",
"content_cluster": "prospecting",
"cta_name": "icp_to_get_started",
"cta_position": "result",
"destination": "register",
"state_transfer": true,
"tool_completed": true
}
The ICP defines best-fit accounts. Buyer criteria define people and buying roles inside those accounts.
No. The builder labels supported search criteria separately from manual qualification rules.
Yes. Exclusions prevent the definition from expanding until nearly every company appears attractive.
No. It measures definition completeness and search readiness, not campaign or revenue performance.
Transfer supported criteria to Getlead, review a calibration sample and continue through the connected prospect-list workflow.