Generate an ICP
Runs on Cloudflare Workers AI. Free: 10 generations an hour, 25 a day per visitor, and a shared daily allowance for everyone. Nothing you enter is stored.
How it works
Describe the business
What you sell, the specific offer this campaign is for, pricing band, geography — and your best existing customers if you have them, because the ICP should look like them.
Get the profile
Firmographics, two or three personas, pains and triggers, disqualifiers, and the filters to find them — structured the same way every time so it drops into a doc.
Build the list
Take the filters section to Apollo or Sales Navigator. Titles, industries, headcount, keywords and technologies map directly to their fields.
Write to the angles
The three messaging angles feed the cold email generator; each maps to a pain so the first email says something the reader recognises.
Why most ICPs are useless for outbound
They are written for a pitch deck. “Fast-growing B2B SaaS companies with a modern data stack and a culture of experimentation” describes a feeling, and no list-building tool has a filter for it. An outbound ICP has to answer the questions the tool asks: which industries, how many employees, which countries, which titles, which technologies, which recent events. It also has to say who not to contact, because the exclusions are what keep the bounce rate and the complaint rate down. This generator is instructed to produce that document and nothing softer, and to name specifics rather than categories.
Feed it your best customers
The single most useful input is two or three of your best existing customers — the ones that closed fast, stayed, and did not need hand-holding. The model uses them to anchor the firmographics and personas in reality rather than in the average of every ICP it has read. If you are pre-customer, describe the customer you would clone if you could. The disqualifiers matter as much: a note like “in-house teams under five inboxes never convert” removes a third of a typical list.
From profile to campaign
The filters section goes into Apollo or Sales Navigator; the pattern finder and verifier turn names into addresses; the messaging angles go into the cold email generator. That is the whole pipeline from “who do we sell to” to a first send, and each piece checks the one before it.
How the generator is tuned
The model behind this page is an open-weight model running on Cloudflare's network, and the instructions it follows are mine — the same rules I apply when I edit a client's sequence: short sentences, no marketing words, open with the reader, one question at the end, keep merge tags intact. Those instructions are edited over time as I see what it gets wrong, so the output improves without the page changing. It is a starting draft, not a finished campaign: read it as you would a junior writer's work, cut what does not fit, and run the result through the readability checker and spam word checker before it goes into a sequence.
Limits and privacy
Each visitor gets ten generations an hour and twenty-five a day, and there is a shared daily allowance across the whole site that resets at 00:00 UTC — when it runs out the tool says so rather than failing silently. Inputs are sent to the model and discarded; nothing is stored, logged with your text, or used to train anything. The generated text is yours.
Frequently asked questions
How many personas should an ICP have?
Two or three for one campaign. More than that is several campaigns wearing one ICP; split them so each gets its own messaging.
What if my market is very niche?
Say so in the description — the model narrows to what you give it. Niche markets produce the most usable ICPs because the filters are concrete.
Can it use my CRM data?
Not directly. Paste a few example customers into the field; that is usually enough to anchor it. CRM import is on the roadmap for the app version.
Is my company description stored?
No. It is sent to the model once and not kept.
Limits?
Ten generations an hour, twenty-five a day per visitor, plus a site-wide daily allowance resetting at 00:00 UTC.
Last reviewed
What to run next
The checks that most often follow this one.
More in this category
Guides that go deeper
When the tools tell you something is wrong
The diagnostics here are free and always will be. When the fix is bigger than a DNS record, this is the work I do.
Deliverability rescue
Mail landing in spam, replies gone quiet, or a domain suddenly blocked. I find the actual cause rather than guessing, and fix it.
- Authentication and alignment failures
- Blocklist delistings and reputation repair
- Gateway and filter-level blocks
- A written report on what broke and why
Email & sending infrastructure
Sending domains, inboxes, authentication and warmup, built to survive volume instead of burning down in a month.
- Domain and inbox fleets at any scale
- SPF, DKIM, DMARC and tracking domains
- Google Workspace and Microsoft 365 inboxes
- Handover documentation you actually own
Domain, DNS & migration
Changing registrar, mail provider or host without a day of downtime or a week of mail silently failing.
- Registrar and nameserver moves
- Workspace and Microsoft 365 migrations
- MX, SSL and subdomain cutover
- Staged rollout with rollback at every step
Monitoring & retainer
Infrastructure drifts. Records get edited, certificates expire, domains get listed. Ongoing eyes on the fleet.
- Scheduled checks across every domain
- Alerts before your clients notice
- Monthly reporting
- Priority response when something breaks
Start with a call
Bring a domain and the symptom. I will tell you what is actually wrong and whether you need me at all — plenty of people leave that call able to fix it themselves.
Thirty minutes, no pitch
We will run the checks together on your actual domains, and you will leave knowing what is broken, what it takes to fix, and what it should cost. If that is a job you can do in-house, I will say so.