Apollo

Most outbound stacks are assembled from three purchases: somewhere to find companies and people, something to enrich and keep those records current, and something to actually send the email and log the call. Apollo's pitch is that a small team should not have to buy three products, three seats and three integrations to do one job. It sells a B2B contact and company database, filtering and list-building on top of it, enrichment that pushes into a CRM, and an engagement layer that sequences the outreach — under one subscription with one credit balance.

That consolidation is the reason Apollo matters editorially, and also the reason it needs reading carefully. A platform that spans data, prospecting and sending has to be judged on each layer separately, because buyers rarely need all three equally, and the credit model that binds them together is where most of the confusion — and most of the unexpected cost — lives.

What Apollo actually is

Apollo positions itself as a go-to-market platform rather than a database, and its own site organises the product into four solution areas — outbound, inbound, data enrichment and deal execution — sitting on a platform layer it describes as Apollo Data, an AI assistant, an Apollo MCP server, integrations, a Chrome extension and workflow automation. Its published use-case list runs from B2B database and lead scoring through inbound lead routing, sales engagement, meeting scheduling, deal management, call recording, conversation intelligence, sales analytics and coaching, cold calling, email deliverability and website visitor identification.

Read that list honestly and Apollo is two products in one seat: a prospecting-data product and an outbound-execution product, with a growing amount of pipeline and conversation tooling attached to the right-hand end. What it is not is a system of record. Apollo has an Opportunities feature for managing a pipeline, and Apollo's own pricing FAQ describes using it to manage sales conversations — but the platform documents deep integrations into Salesforce and HubSpot, which tells you where Apollo expects the customer record to live.

Sales and contact intelligence — the data layer

The data layer is what people buy Apollo for first. Apollo says its database covers 210 million contacts across 35 million companies (Apollo's own figure, published in its magazine and read 3 September 2026), assembled through what it calls a proprietary data-contributor network. Apollo also states that it charges a credit only for email addresses it can verify, and that it never charges more than one credit per contact for an email.

Those are vendor claims and we present them as vendor claims. TTML has not checked a single Apollo record, has not measured coverage in any territory or seniority band, and has not tested whether a “verified” email actually delivers. Anyone evaluating Apollo should treat database size as a starting condition rather than a quality signal: what matters is coverage of *your* segment, which on this kind of platform varies by geography, company size and seniority, and which only a trial against your own target list can answer. Apollo's own privacy documentation is also worth reading before purchase — it describes holding business-contact attributes such as job history, titles, professional responsibilities and professional social-media profile information, and states that Apollo may make inferences about business contacts, including their likelihood of being interested in a product. That is a compliance conversation in the EU and the UK, not a footnote.

Prospecting and list building

Prospecting in Apollo means filtering the database into a saved, exportable list. Two documented mechanics deserve attention before you pick a plan:

• Record selection limits. Apollo's pricing FAQ explains that lower plans impose a limit on how many new records you can select from the database at a time — its own worked example is that saving 10,000 leads under a 25-record selection limit means clicking through 2,000 times, versus one click without the limit. This is a plan-gated workflow tax, not a data limit, and it is easy to miss.
• Export is a separate spend. Apollo defines export credits as credits consumed whenever a contact leaves Apollo — CSV, CRM sync, or Person API enrichment pushed into anything external such as Salesloft or Outreach. It also notes that credits may sometimes be consumed when exporting company data.

The practical consequence: the cost of a prospecting workflow in Apollo is not the seat price, it is the seat price plus the number of records you reveal and move. Teams that treat Apollo as a data tap feeding another sequencer will burn export credits faster than teams that work inside it.

Enrichment and data workflow

Enrichment is a first-class part of the product rather than an add-on — Apollo lists data enrichment as one of its four solution areas and describes keeping contact data fresh across a connected stack through its integrations. Apollo's credits documentation states that, depending on plan, credits are consumed to reveal emails and phone numbers, enrich records, run AI-powered research, use email warmup and complete other credit-consuming actions.

Two documented constraints matter for anyone planning a recurring enrichment job. First, Apollo states that credits expire at the end of each billing cycle and do not roll over, with annual plans unlocking the full allowance at the start of the annual cycle (or in tranches on quarterly and semi-annual billing). Second, Apollo's pricing page states that its standard plans are licensed for internal business use only: using them to power an external product, share data with customers or resell Apollo data requires a separate agreement with custom pricing. If you were planning to enrich a customer-facing dataset, that is a contract conversation, not a plan upgrade.

Engagement and sequencing

This is where Apollo separates itself from pure data vendors. Apollo documents sequences with A/B testing, call recording, automated follow-ups and open tracking, and its pricing FAQ states that email campaigns are included on every account — with the caveat that non-paying plans can only connect Gmail accounts, while paid plans can connect Microsoft Office or any other provider. Trial accounts carry the same restriction: Apollo says linking a non-Gmail/Microsoft account for campaigns requires a paid plan or a direct trial arranged by its sales team.

One thing no vendor can sell you is sender reputation. Apollo provides the sequencer, the warmup feature and deliverability tooling; whether your mail lands depends on your domain, your volume ramp, your list hygiene and your copy. We have measured none of that here, and no buyer should read “verified email” as a delivery guarantee.

Integrations and workflow

Apollo documents integrations with Salesforce, HubSpot, Outreach, Salesloft, Marketo, SendGrid, LinkedIn and email providers generally, plus a Chrome extension for working inside other tools, workflow automation, an AI assistant and an Apollo MCP server for agent-based access. API access, per Apollo's pricing FAQ, is offered on its Custom plans for more advanced integrations — so an API-driven build is a sales conversation rather than a self-serve checkbox.

For readers pairing tools rather than replacing them: Apollo is comfortable sitting beside a CRM and beside a separate sequencer. The question is which of the three layers — data, enrichment, sending — you actually want it to own, because paying for all three and using one is the most common way this category wastes money.

Pricing and the credit model

Apollo's pricing page renders its plan table dynamically, so the honest position is that per-seat list prices must be read live rather than quoted from a review. What Apollo does publish as first-party structured data on that page, read 3 September 2026, is a four-tier shape:

• A free plan at $0.
• A Basic plan published at $49 per user per month on monthly billing.
• A Professional plan published at $99 per user per month on monthly billing.
• An Enterprise/Custom tier with no list price — contact sales.

Treat those as the structured-data figures on the day we read them, not as a durable price list: Apollo runs annual-billing discounts, add-ons and configurable credit volumes, and its own FAQ describes admins customising how many credits a team gets per billing cycle. Currency, region and negotiated terms will move the number. Check apollo.io/pricing before you budget.

The credit model is the part worth understanding properly, because it — not the seat price — determines what Apollo costs a working team. From Apollo's own credits documentation and pricing FAQ:

• Credits unlock data and certain features — revealing emails and phone numbers, enriching records, AI-powered research and email warmup among them.
• Email costs at most one credit per contact, and Apollo says you are only charged for email addresses it can verify.
• Phone numbers are charged separately — mobile, direct and office extensions all cost the same per verified number, and mobile credits are tracked as their own allowance.
• Export credits are consumed when data leaves Apollo — CSV, CRM sync, or Person API enrichment into an external system.
• Credits renew on the first day of each billing cycle and expire at the end of it. They do not roll over, including at renewal. Extra credits can be purchased mid-cycle and remain usable to the end of that period.
• “Unlimited” is governed by a fair-use policy. Apollo states the limit as 10,000 credits per account per month for non-paying accounts on an unlimited plan, and for paying accounts the lesser of amount-paid divided by $0.025 or one million credits per account per year.
• There are two credit systems in circulation. Apollo says all new customers are on the newer credit system and that some documented features are only available on it, while existing customers may still be on a legacy system pending a gradual rollout. If you are comparing Apollo notes with a colleague, you may not be describing the same product.

Trials and the free tier: Apollo says trial plans include 50 credits and 5 mobile credits plus almost all features of the selected plan, and that when a trial ends you can convert to a paid plan or drop to its free plan, which its FAQ describes as free forever. Note the naming drift — Apollo's FAQ calls the free tier “Starter” while its pricing structured data labels it “Free”. Cancellations take effect at the end of the term; plan and seat upgrades apply immediately; downgrades apply immediately for plans and seats but at cycle end for add-ons, with no mid-term refunds.

Ease of adoption and operational considerations

Apollo is self-serve at the bottom and sales-led at the top, and the seam shows. A founder can sign up free and build a list the same afternoon. A team that wants API access, governance, the security and integration posture of a large organisation, or permission to use Apollo data in anything customer-facing is in Custom-plan territory. Apollo also documents tiered onboarding, including live sessions with an onboarding manager on its Professional onboarding option, which it aims at teams of 20 or more — a reasonable signal that the platform's full surface is not self-explanatory.

The operational risks are governance risks rather than technical ones: credit consumption spread across a team, export credits leaking value to a second sequencer, and — most importantly in Europe — the compliance work of processing third-party contact data. On that last point Apollo publishes a substantial security posture: it states it is ISO 27001 and SOC 2 certified through A-LIGN, GDPR compliant as both processor and controller, certified under the EU–US Data Privacy Framework, with encryption in transit and at rest, annual third-party penetration testing, quarterly internal and external audits, and backups with a maximum 24-hour RTO and RPO. Those are Apollo's published claims, read 3 September 2026; we have not audited them. Certification is not the same thing as your own lawful basis for outreach.

Strengths

• Genuine consolidation — database, enrichment and sequencing under one subscription instead of three.
• A free tier and a documented trial, so the data can be evaluated against your own segment before spending.
• An unusually explicit credit model: Apollo publishes what consumes credits, when they expire and what “unlimited” means.
• Broad documented integrations, including Salesforce, HubSpot, Outreach, Salesloft and Marketo, plus a Chrome extension and an MCP server.
• A published, certified security and privacy posture — useful when procurement asks.

Limitations

• Credit expiry at the end of every cycle with no rollover punishes uneven prospecting rhythms.
• Export credits mean using Apollo as a data source for another sequencer costs more than working inside it.
• Record selection limits on lower plans are a workflow tax that is easy to overlook when comparing tiers.
• Per-seat prices are dynamically rendered, and annual, add-on and negotiated terms make like-for-like comparison genuinely hard.
• Two credit systems in circulation mean documented features may not match what an existing account sees.
• Standard plans are internal-use only — customer-facing or resold use requires a separate agreement.
• Third-party contact data carries compliance obligations that sit with you, not with Apollo, and its documented inference-making deserves legal review in the EU and UK.
• Data quality is unverified here, and no vendor's verification claim substitutes for testing coverage on your own target list.

How Apollo sits next to the alternatives

The useful comparison is not Apollo against every sales tool, it is Apollo against each of the layers it bundles.

Against orchestration and enrichment tools such as Clay, Apollo is the simpler, more opinionated purchase: one database and one sequencer rather than a canvas that composes many data providers. Against CRM suites such as HubSpot or Salesforce, it is not a substitute at all — those own the customer record, and Apollo documents integrating with both. Against Gong, the overlap is narrow and at the wrong end of the funnel: Gong analyses conversations that have already happened, while Apollo's core job is finding people to have them with. And against event-scoped research tools such as Lensmor, the difference is scope rather than quality — an always-on database answers “who matches this profile anywhere”, while event-shaped research answers “who is worth an hour at this specific show”.

Two further categories of alternative exist that TTML does not yet cover and therefore will not rank: enterprise data platforms sold on annual contracts, and compliance-first European data providers. If your constraint is procurement scale or EU data provenance rather than price, those belong on your shortlist even though we cannot yet point you at our own review of them.

Verdict