An ICP is a filter. A list is a set of accepted rows.
“Mid-market companies with operational pain” may describe your market. A researcher cannot apply it. A SaaS ICP list only works when every inclusion rule can be checked from public evidence, and every exclusion is written down before the first company is added.
- Company type, geography and a size proxy you can observe.
- The workflow or use case the product actually serves.
- One buying trigger you can point to without guessing internal politics.
- The role most likely to own that use case.
- Exclusions for segments, tools or company shapes you cannot serve.
Towncenter builds that list as a one-off, human-verified CSV for SaaS builders. It is not a subscription database you search yourself. Coverage is worldwide; location is optional.
A buying trigger is an observation, not a claim of intent.
A trigger makes outreach more relevant than industry alone. It does not prove the company will buy. Record what is visible, then write the message as a question about that condition.
| Trigger you can observe | Why it belongs on the row | What not to invent |
|---|---|---|
| A manual customer or staff journey is still public. | The product has a specific path to improve. | Hours wasted or revenue lost. |
| Hiring for work the product organises. | The team is investing in that function now. | That the hire will choose your tool. |
| Several locations or teams share one workflow. | Coordination is a plausible use case. | That current tools have already failed. |
| A current tool or workaround is visible. | You can describe an alternative honestly. | A teardown of a product you have not verified they use. |
| A public operational or regulatory change. | There is a timely reason to review the process. | A deadline or budget you cannot see. |
Separate fit, trigger and hypothesis.
The company matches the ICP, and one current signal makes the use case relevant. A hypothesis about internal impact can shape the question you ask. It cannot be stated as fact in the opening line.
The full method for turning those levels into research lives on prospect lists for SaaS builders. This page is the buying-intent version: what a SaaS outreach list is for, and when a bulk B2B export will waste the first week of a campaign.
Why a database export is usually the wrong unit.
Searchable B2B databases are strong when you want to explore a market yourself, save accounts, and run an ongoing pipeline. They are a weak substitute for a short, brief-specific list: filters encode firmographics, not the buying trigger your product needs.
If the question is “should I subscribe to a database or order researched rows?”, compare that choice in Apollo.io vs a human-verified prospect list. If the question is listing discovery versus verification, see Google Maps scraping vs human-verified leads.
Order a list you can send, not a market you can browse.
Independent dental groups with 3–15 locations in Belgium or the Netherlands whose public patient journey still depends on phone or email intake, excluding hospital networks and groups already offering online intake. The trigger is the visible intake path; the product is one workflow across locations.
Choose a territory if you have one, describe the ICP and trigger, and pick 10, 25, 50 or 100 companies in the order form. Towncenter researches each row and emails the CSV. The list does not promise replies or customers; it removes the first research queue so you can test the hypothesis with people who actually match it.