Apollo or a Done-for-You Decision-Maker Service: Which Should a Small UK Team Pick?

Published 2026-10-21 by Dale Taylor

In short

A small UK team should pick Apollo if someone on the team has the hours to research, check and tidy the list every week. Pick a done-for-you decision-maker service if that someone is the founder, who is also selling and delivering, and you already know who you want to reach. The tool is rarely the deciding factor. The deciding factor is whose time goes into turning raw records into a list you would trust enough to email. Work out those hours first, then compare them with what each option costs.

Four questions: Apollo or a done-for-you service Apollo or a done-for-you service? Ask in this order. Each question settles it or passes you on. QUESTION 1 Does someone on the team have research as part of their job? IF YES Take the database. QUESTION 2 How many hours a week would checking take, and who loses them? IF THE HOURS ARE SMALL Take the database. QUESTION 3 Do you already know exactly who you want to reach? IF NOT Spend a month with a database first. QUESTION 4 How much does one bad address cost you? IF A BOUNCE HARMS your sending domain, take the service. BEFORE YOU COMMIT Test either option on twenty companies you know. Count how many records you had to fix by hand.
Four checks in order. Each one either settles the choice or passes you to the next.

What are you actually choosing between?

Apollo is a self-serve contact database. You log in, set filters for company size, location and job title, and pull records. It is a capable product, and we use it ourselves as one source among several.

A done-for-you decision-maker service is a different kind of thing. Someone else runs the research and hands you a finished list. You get names, roles and checked work emails, not a login.

So this is not a comparison of two databases. It is a choice between buying access and buying a result. Access is cheaper per month on paper. A result costs more on paper and takes work off your desk. Which one is cheaper in practice depends on what your time is worth and how many hours the access really costs you.

Where does the time go with a self-serve database?

The data is the easy part. Four jobs sit between a database and a list you can send to.

Deciding who matters. A company record is not a buying decision. Someone has to work out whether the person who signs off the spend is the managing director, the head of marketing or an operations lead. At a ten-person company the title on file may be stale or may not exist.

Checking the person. A record can show a name and a job title that were right two years ago. Checking one person against the company's own website and LinkedIn takes a couple of minutes. Fifty people take an afternoon.

Checking the email. An address that exists in a database has not necessarily been checked recently. I covered that gap in the piece on finding a named decision-maker rather than a generic inbox. For this decision, the point is simpler: a bounce costs you more than the minutes it took to find the address, because a high bounce rate can damage the domain you send from.

Keeping it tidy. Duplicates, wrong companies, people who have left, and records that landed in the export but do not match your profile. This work is dull, and it never quite ends.

None of that is a criticism of Apollo. It is what any self-serve tool leaves with you, because that is what self-serve means. If you have a researcher, those four jobs are theirs and the model works well.

What does a done-for-you service take off your desk?

A done-for-you service does those four jobs for you. Aigentic Intelligence is one. It finds companies that match a target profile, identifies the named decision-maker at each, and returns a verified work email. It is built, and we run it for our own outbound.

Our offer is one instance per customer. Each customer's data would sit in its own database, and they would own it. We would not mix one customer's data with another's.

Every lead is meant to carry a company, a domain, a contact name, a role and an email, and the email's domain has to match the company's. Our terms are that a lead which fails that standard is replaced and credited.

We leave some things out on purpose. In our own testing, none of the "growth signal" links our research produced held up when checked, so we do not hand those over. The only signal we cite is one we have fetched and read ourselves. If a fact cannot be sourced, it does not go in the lead.

There is no guarantee of meetings, and nobody honest can give one. A list is an input to selling. It is not selling.

What do you give up with a service?

Two things, and you should weigh them before you decide.

Control. With a database you choose every filter and look at every record. With a service you describe the target, and someone else makes the calls on edge cases. If you have a very particular idea of who counts as a good prospect, you will want to see that profile written down and agreed before anything is delivered.

The learning. Doing the research yourself teaches you who buys and why. Some founders get real value from that in the first few months. If you are still working out who your customer is, do the searching yourself for a while. Pay for a service once you know.

There is also the plain cost. A service charges for work rather than access, and the monthly figure will usually be higher than a database subscription. The sensible comparison is not the two prices side by side. It is the service price against the database price plus the hours you would spend.

How do you work out the real cost?

Do this on paper before you talk to anyone, including us.

  1. Count the hours. How many hours a week would you spend on research, checking and tidying to produce the list you need? If you have not done it before, run twenty companies by hand and time it, then scale up.
  2. Price the hours. Use what an hour of your time would earn if spent selling or delivering. If you are the founder, that is not a low number.
  3. Add the database. Add the subscription and any credits you would spend on records you end up discarding.
  4. Add the cost of errors. Estimate what a bounced or wrongly addressed email costs you, in sender reputation or an awkward reply.
  5. Compare with the service quote. If the service price is lower than the sum of the first four, the service is cheaper. If it is higher, the database is cheaper, and you should take it.

I am not giving you numbers for this, because they are yours, not mine. The sum is the point. Most people who compare monthly fees alone skip steps one and two.

Which should a small UK team pick?

Ask four questions, in this order. Each one either settles it or passes you on.

1. Does someone on the team have research as part of their job? If yes, take Apollo or a similar database. You are paying for access, which is what it sells. If no, go to question two.

2. How many hours a week would the checking take, and who loses those hours? If the honest answer is "me, on a Sunday", the database costs more than its price. Go to question three. If the hours are small and nobody minds, take the database.

3. Do you already know exactly who you want to reach? If you have a stable profile and can write it down in a paragraph, a service can work from it straight away. If you are still guessing, spend a month with a database first.

4. How much does one bad address cost you? If a bounce could harm a sending domain you rely on, checked addresses are worth paying for. If you send a handful of personal emails, they matter less.

If you answer yes to question one, take the database. If you reach question four with a stable profile and a domain you cannot afford to damage, take the service. Anywhere in between, run the test below and let the result decide.

What should you test before you commit?

Whichever you lean towards, run the same small test first.

  1. Pick twenty companies you already know well, including some small ones.
  2. Ask the database or the service for the decision-maker and email at each.
  3. Check each person against the company's own website and LinkedIn.
  4. Count how many records you would have had to fix by hand.
  5. Send to a small batch first and watch for bounces before sending a large one.

That count of fixes is your real price. A cheap tool that leaves you correcting half the list is not cheap. An expensive service that leaves you correcting none may be.

Do not take our word for how Apollo works or what it costs. Read its own pricing page and terms, and ask the vendor how credits are used. Tools change their plans, and a summary written by a competitor is the worst place to get them from.

What neither option fixes

Neither one fixes weak targeting. If the profile is wrong, a perfect list of the wrong companies is still the wrong list.

Neither fixes the message. A verified address on a poor email still gets ignored.

And neither is a substitute for talking to customers. A list tells you who to contact. It does not tell you why they would buy.

Key takeaways

  • Choose Apollo if someone on your team has the hours to research, check and tidy the list every week.
  • Choose a done-for-you service if the person doing the searching is also the person selling and delivering.
  • The real comparison is the service price against the database price plus your hours, not the two monthly fees side by side.
  • A service gives up some control and some learning, and costs more per month on paper.
  • Test either option on twenty companies you know, and count how many records you had to fix by hand.
  • Neither option fixes a wrong target profile or a poor message.

Start with the Sample Five, five leads in your niche with a named decision-maker and a verified work email.