Enquirer Consulting Group

Reachable Buyer Map

Prepared for Luke White · PDF Butler · August 2026
A read of your market, built without asking you for anything first. Because your product is native to one CRM platform, the map is not every company in Europe. It is the accounts inside that install base, plus the partner layer that carries products into them, and the incumbent tools you displace on the way in. This covers who signs in each, and roughly how many sit there. It describes market structure rather than your business, and there is nothing to buy at the end of it.
Large European enterprises, 250 people and up
The outer population your install base sits inside. Document work here is owned by a platform team and funded by whoever carries the compliance or throughput problem, which is why the evaluation and the budget usually live in two different rooms. Long cycles, wider deployments, and the segment most likely to already run something.
Who signs: the platform owner or CRM architect, head of revenue operations, the IT director, and the operations or compliance lead who actually feels the document problem.
53,000 to 56,000
EU enterprises at 250 or more people, all sectors; how many run your platform is not published anywhere and is established account by account
European mid-market, 50 to 249 people
The band where one administrator owns the whole org, the buying committee is two people, and a document decision closes in weeks rather than quarters. By count this is five times the size of the band above, and it is the part of the market a marketplace listing serves worst, because nobody there is running a formal evaluation.
Who signs: the operations manager, sales operations lead, the single platform administrator, and the finance controller who signs.
245,000 to 255,000
EU enterprises in the 50 to 249 employee band, all sectors
The United Kingdom, counted separately
Outside the counts above and close to home for your team. Same buyer roles, same size split, different data source, and a market where the partner and freelance administrator layer is unusually dense, so a product recommendation travels quickly once it starts.
Who signs: the same set: platform owner, revenue or sales operations, IT director, operations and compliance leads.
7,500 to 8,500
UK businesses at 250 or more employees, with a mid-market band behind it several times larger
Document heavy and regulated sectors
Financial services, insurance, life sciences, public sector and education. Where the document is the product of record rather than an output, the cost of getting it wrong is external, and the buyer is a compliance or quality owner rather than a sales operations one. Sector counts are public. Which of them run your platform is not.
Who signs: compliance officer, head of client onboarding, quality or regulatory lead, and the program owner for the system of record.
Not published at platform level
sector company counts exist; platform installs inside them do not appear in any register and are identified one company at a time
The implementation and consulting partner layer
The multiplier segment. A practice that standardizes on your product carries it into every implementation it delivers, which turns one relationship into a stream of accounts. Small by count and high in value, and the only segment on this page where the buyer is a person rather than a company.
Who signs: the alliances or partnership director, the practice lead, the delivery manager, and the presales architect who picks the tooling.
Listed, not registered
consulting practices appear in platform directories rather than in any register, and practice size is not published, so this list is built by named person
The displacement pool
Your public position is switching, and every switch has an incumbent behind it. That makes timing the whole game: a renewal date, a migration, a failed rollout, a new administrator inheriting somebody else's build. None of it sits in a register, and all of it is visible from outside if a fixed list is being watched every month.
Who signs: whoever inherited the incumbent tool, usually the platform owner, with the operations lead who has to live with it.
No public register
installed tooling surfaces through job posts, listings, community threads and release notes, account by account; the difficulty is why the segment stays open

Where the openings are

1
The person who evaluates and the person who suffers are not the same person. The platform owner runs the evaluation. The operations or compliance lead carries the deadline and the budget line. A marketplace listing reaches the first, and only in the weeks they happen to be looking. Nothing currently reaches the second at all, and the second is the one who can create a project where there was not one.
2
The partner layer is small enough to work by name. One practice lead can carry a product into a dozen implementations without a single marketing touch reaching the end client. Practices are not in any register, but the people who run them are findable and countable, which makes this the highest value list on the page and the one that rewards being worked by hand rather than by campaign.
3
Displacement runs on timing, not on persuasion. Nobody switches because a better product exists. They switch at a renewal, a migration, a failed rollout, or when a new administrator inherits a build they did not make. Watching a fixed list of several thousand accounts for those moments is mechanical work that runs every month. Waiting to be found in a marketplace only catches the ones already in motion.
Built from public market data, counts banded deliberately. Enterprise counts come from published European and United Kingdom business statistics and describe companies by size band, not software installs. Platform install bases, incumbent tooling and partner practice sizes are held in no public register and are established account by account.
ENQUIRER CONSULTING GROUP
enquirerconsulting.com