What do Apollo credits actually pay for?
Apollo credits are not all prospecting costs. Teams also spend hours refining filters, checking buyer fit, deduplicating, and importing rows. Apollo says saved-contact CSV exports themselves do not use credits, while access to net-new verified emails can. Measure actual plan usage and labor before comparing with a one-time batch.
The phrase 'Apollo charges for every export' is inaccurate. Apollo says exporting saved contacts to CSV does not use credits. Selecting net-new people from search saves them first, and each net-new person with a verified email uses one credit under the cited export guide. Its separate data-request guidance says accessing a verified email or phone for a net-new contact can consume credits, while an office phone found with an email request does not add a charge.
Apollo's pricing page describes Free, Basic, Professional, and Custom plans and says credits are pooled across a team, granted at the beginning of each billing cycle, and do not roll over if unused. Plan features and rate details can change, and different teams may have different entitlements. Record your own invoice, credit balance, and usage report before calculating unit cost.
Sources: Apollo current pricing and credit FAQ · Apollo: Export Contacts to a CSV · Apollo: Request Contact Data · Apollo: Review Credit Usage
Where does self-service time enter the bill?
Self-service prospecting requires someone to define the audience, tune filters, inspect matches, access fields, remove duplicates, and map the export into a campaign. That labor can be small for an experienced operator with a repeatable workflow or large for a niche search. Measure hours rather than assuming a fixed burden.
Track the time by task, not by application open time. Search setup includes company, industry, territory, seniority, exclusions, and the person-role logic that turns a large database into a useful campaign. Review time covers spot checks on current role and company fit. Export work covers ownership, suppression, formatting, and CRM field mapping. Rework covers records rejected by sales.
A credit can be well spent on a record that fits the audience and supports a qualified conversation. It can also be spent on a person the team later excludes. Because some Apollo functions are integrated, compare the entire workflow you will actually run. Do not infer a bad outcome merely from the presence of credits, and do not treat unused credits as equivalent to used qualified contacts.
| Work item | Apollo self-service | Managed brief-based batch |
|---|---|---|
| Define audience | Buyer configures filters and exclusions | Buyer writes the brief and exclusions |
| Find people | Buyer searches and selects records | Research service assembles candidates |
| Access data | Plan and credit rules apply | Included in the quoted file scope |
| Quality review | Buyer inspects selected output | Buyer audits delivered rows |
| Outreach | Buyer configures and runs it | Buyer configures and runs it |
Sources: Apollo current pricing and credit FAQ · Apollo: Export Contacts to a CSV · HEED terms for managed research and accepted rows
How do credits and labor change cost per contact?
Compare the same period: allocated platform cost plus labor, divided by contacts that pass the buyer brief. In a hypothetical Apollo scenario, $600 of platform cost and ten hours at $60 produce 150 qualified contacts, or $8 each. A managed-batch comparison needs its actual price and an accepted yield.
Imagine a team's two-month campaign allocates $600 of its Apollo bill to contact access. It uses 300 net-new verified-email credits under its actual plan and spends ten staff hours on search, review, cleaning, and CRM mapping at a loaded $60 an hour. From the 300 accessed records, 150 meet the agreed role, territory, company, and suppression criteria. All-in cost is ($600 + $600) divided by 150, or $8 per qualified contact. The model treats the $600 platform amount as inclusive of its allocated credits; it does not add a fictional per-credit price.
For comparison, imagine a managed 250-row file costs $549 and requires three staff review hours at the same rate. If 150 pass the exact same qualification test, all-in cost is ($549 + $180) divided by 150, or about $4.86. These numbers do not establish an actual quality advantage. They show the exact break-even calculation a buyer can repeat with real invoices and acceptance counts.
Change the assumed yield or staff hours and the winner may flip. If Apollo's filters produce 240 qualified contacts from the same allocated spend and labor, its modeled cost falls to $5.00 each. If the managed batch needs extensive rework, its modeled cost rises. Report both costs with confidence ranges if your sample is small.
| Measure | Apollo scenario | Managed batch scenario |
|---|---|---|
| Relevant platform/file cost | $600 | $549 |
| Internal labor | 10 × $60 = $600 | 3 × $60 = $180 |
| Qualified contacts | 150 | 150 |
| All-in cost/contact | $8.00 | $4.86 |
Sources: Apollo current pricing and credit FAQ · HEED terms for managed research and accepted rows
When does Apollo deserve the operating time?
Apollo can fit teams that prospect continuously, need direct control over filters, and use its sequencing, enrichment, or integration tools enough to justify the plan. The same setup can serve several campaigns. A managed batch may fit a narrow, occasional audience where staff time is scarcer than search flexibility.
A full-time SDR team may explore new territories every day and prefer an in-house operator who can save searches, adjust criteria, and work inside one platform. A founder preparing a single regional campaign may prefer to specify the target and receive a file. Neither choice removes the need to understand the buyer, comply with outreach rules, and inspect a sample of the output.
Apollo's free option makes it especially important not to claim a subscription is mandatory to use it. Compare the plan that gives your team the necessary actions at the needed volume. Confirm the current terms in the app before estimating credit usage.
What should a managed-batch brief contain?
A useful brief specifies industry, geography, company size, decision-maker role, exclusions, required fields, quantity, and delivery format. It also defines what counts as an acceptable row. These choices give the research team a target and give the buyer a fair standard for inspection when the file arrives.
Write the objective first: for example, operations leaders at independent businesses in three counties, excluding franchise chains and existing customers. State whether a checked business phone can be a main line or whether the campaign truly requires a direct dial. HEED's published standard B2B definition permits direct or main business lines, labeled when known; it does not promise direct dials.
Keep the source URL and checked date through the import. The checked date identifies a research snapshot; it is not a permanent freshness guarantee. Suppress existing customers, opt-outs, and owned accounts before any outreach. A paid record does not imply the person opted in, expressed interest, or will reply.
Ask how shortfalls and reported defects are handled before purchase. HEED's current terms describe a 48-hour delivery window from confirmed payment, a proportional remedy for confirmed undelivered rows, and a 14-day review of eligible delivered-row defects. Read the terms for your order instead of turning a summary into a broader guarantee.
Sources: HEED terms for managed research and accepted rows
Review HEED B2B filesSpecify the buyer role, territory, and exclusions first.
How should RevOps decide after a pilot?
Run a matched-audience pilot and record spend, credits consumed, staff hours, rejected-row reasons, and accepted qualified contacts. Compare both models over the same period and with the same buyer definition. Keep meetings and revenue as later funnel measures so a strong message does not hide poor data or vice versa.
The pilot's final sheet should show credits requested, credits actually used, files or rows delivered, rows sampled, accepted qualified rows, and median review minutes per row. Store the rejection reasons. A single all-in dollar figure tells you little unless the team can explain where each input came from.
Sources: Apollo: Review Credit Usage · HEED offer overview · HEED terms for managed research and accepted rows
Choose a 25-contact starterCurrent published price is $75 once; paid rows depend on your order brief.
Common questions
Does Apollo charge a credit every time I export a saved CSV?
No. Apollo says exporting saved contacts to CSV does not itself use credits. Accessing a net-new verified email during the export flow can use a credit. Other enrichment actions may have separate charges.
Do unused Apollo credits roll over?
Apollo's current public pricing FAQ says credits are granted at the beginning of a billing cycle and do not roll over. Check your plan and account terms for the exact entitlement.
Is Apollo always more expensive than a managed batch?
No. The answer depends on the plan, use of other platform features, staff time, campaign frequency, and qualified yield. The worked figures are scenarios, not observed vendor performance.