# Cost examples: worked totals for common tasks

Source: https://listplus.ai/en/help/plans-credits-billing/cost-examples
Last updated: 2026-09-27

These are worked-through totals for tasks people actually do, built from the
per-action prices in the price list. Real results vary — how many contacts a
lookup actually finds is never guaranteed — so each example states its "hit
rate" as a clearly labeled assumption, not a promise. One credit is worth
about €0.03. For the reasoning behind each price, see "What does one contact
cost?" and the price list.

## 1. Emails for 1,000 names + companies

Starting point: a list of 1,000 rows with first name, last name and company,
no LinkedIn URL and no email yet.

| Step                                                                 | Rate        | Count            | Credits  |
| -------------------------------------------------------------------- | ----------- | ---------------- | -------- |
| "Contact Brief (by Name & Company)" — Prospeo                        | 2 cr on hit | up to 1,000      | 2 × hits |
| "Find Email (by Name & Company)" — FullEnrich, fallback for the rest | 6 cr on hit | remaining misses | 6 × hits |

Two Enrich-menu entries share the exact label "Find Email (by Name &
Company)" — Prospeo's cheaper 2-credit lookup and FullEnrich's 6-credit
one. The credit amount shown on the button is how you tell them apart; for
this fallback step, pick the one showing 6 credits.

- **Best case** — Contact Brief finds all 1,000: 1,000 × 2 = **2,000 credits** (≈ €60).
- **Worst case** — Contact Brief finds none, but the 6-credit fallback finds
  every one of them: 1,000 × 6 = **6,000 credits** (≈ €180).
- **Realistic estimate** (assumption: 60% found by Contact Brief, another
  20% by the fallback, 20% not found at all): 600 × 2 + 200 × 6 = **2,400
  credits** (≈ €72) for about 800 emails.

1,000 records fit comfortably within Basic's 10,000-record limit across all
your lists.

**Spend less:** let Contact Brief run first and only send the rows it missed
to the pricier fallback — don't run both on every row. Select just the rows
still missing an email before you enrich, so you're not re-paying for ones
you already have.

## 2. Clean & verify 5,000 CRM contacts

Starting point: a 5,000-row export from a CRM, imported as a file.

| Step                                                                     | Rate                           | Count       | Credits        |
| ------------------------------------------------------------------------ | ------------------------------ | ----------- | -------------- |
| File import                                                              | 1 cr flat                      | 1 list      | 1              |
| AI column detection (runs automatically on every import)                 | billed by usage, no fixed rate | 1 list      | small          |
| Analyze: checks, fixes, duplicate merging (rule-based)                   | free                           | 5,000 rows  | 0              |
| "Verify Email Deliverability" (only once the service is actually called) | 0.1 cr                         | up to 5,000 | 0.1 × verified |

Analyze's own checks and fixes — deduplication, formatting, placeholder
detection and the like — are rule-based and free. AI-based checks or fixes,
such as the Enrich menu's AI-derived fields, are billed separately by usage
and aren't part of "cleaning" in this example.

- **Best case** — most addresses are caught for free as obviously invalid,
  disposable, role-based or test-domain, so few ever reach the paid
  verification step: close to the cost of the import plus column detection
  alone, both small.
- **Worst case** — every address looks plausible and needs the paid
  verification call: 5,000 × 0.1 + 1 = **501 credits** (≈ €15), plus the
  small column-detection charge.
- **Realistic estimate** (assumption: a typical CRM export is mostly
  plausible-looking addresses, so about 85% reach the paid check and 15%
  are caught free): 5,000 × 0.85 × 0.1 + 1 = **426 credits** (≈ €13),
  including the import.

5,000 records fit within Basic's 10,000-record limit across all lists.

**Spend less:** run Analyze first (free) and only verify rows that don't
already have a known-good status, instead of re-verifying the whole list
every time.

## 3. 500 database leads with verified email (Segment Search)

Starting point: a Segment Search matching your audience; you want 500
results and a verified email where available. There's no bulk "reveal
email" inside Segment Search itself — you add results to a list page by page,
then enrich them from the list.

| Step                                                                     | Rate        | Count     | Credits  |
| ------------------------------------------------------------------------ | ----------- | --------- | -------- |
| Segment Search page fetch (up to 25 results each)                        | 2 cr/page   | 20 pages  | 40       |
| "Add To List" (copies only the current page; click it once per page)     | free        | 20 times  | 0        |
| "Contact Brief (by LinkedIn URL)" — Prospeo, from the list's Enrich menu | 2 cr on hit | up to 500 | 2 × hits |

If a page returns fewer than 25 results, you'll need more than 20 pages to
reach 500.

- **Fewest credits spent** — no Contact Brief lookup finds a value: **40
  credits** (≈ €1.20) for 500 leads with no email found.
- **Full yield** — every lookup finds a verified email: 40 + 500 × 2 =
  **1,040 credits** (≈ €31).
- **Realistic estimate** (assumption: about 60% of the 500 leads get a
  verified email via Contact Brief): 40 + 500 × 0.6 × 2 = **640 credits**
  (≈ €19).

500 leads fit easily within Basic's 10,000-record limit.

**Spend less:** the masked email/mobile preview on a Segment Search result
is always free to browse, so shortlist which leads you actually want before
adding pages and enriching — the page fetch is the one cost you can't avoid
per batch of 25.

## 4. One AI Research run

AI Research has no fixed total: the agent's reasoning is billed by actual
usage, the same way AI commands are, so it scales with how many steps a run
takes rather than a flat rate. If your balance runs out mid-run, the run
simply stops and keeps whatever it already found. Only the optional paid
sources have a fixed per-call price.

| Step                        | Rate                          | Count (assumption) | Credits  |
| --------------------------- | ----------------------------- | ------------------ | -------- |
| Reasoning steps             | billed by usage, no flat rate | —                  | variable |
| Reddit search (opt-in)      | 6 cr/call                     | 2 calls            | 12       |
| X (Twitter) search (opt-in) | 3 cr/call                     | 1 call             | 3        |
| Tech-stack lookup (opt-in)  | 0.25 cr/call                  | 2 calls            | 0.5      |

- **Best case** — no paid sources switched on, a short run: just the
  (variable, usage-billed) reasoning cost, no source charges at all.
- **Worst case** — Reddit, X and the tech lookup are all called many
  times over the course of a long run: source charges alone can add up to
  several dozen credits, on top of reasoning.
- **Worked example** (the source-call counts in the table above — 2 Reddit
  searches, 1 X search, 2 tech lookups): 12 + 3 + 0.5 = **15.5 credits** in
  source charges, plus reasoning billed separately.

You need at least 1 credit in your balance to start any run, and a run
delivers up to 25 matches.

**Spend less:** leave Reddit, X and the tech lookup off unless you need
them — Google search, used throughout every run, is always free.

## 5. Mobile numbers for 100 people

Starting point: 100 rows that already have a name and company (or a
LinkedIn URL), selected in the grid. For one person, the record panel's
"Reveal Mobile Number" is the direct route. For a batch like this, select
the rows, click **Enrich** in the selection bar, and pick Person → Contact
details → **Mobile** in the field picker that opens — the same underlying
lookup, with the maximum cost shown before you confirm (check it shows 12
credits per row).

| Step                                                                                                | Rate         | Count     | Credits   |
| --------------------------------------------------------------------------------------------------- | ------------ | --------- | --------- |
| "Phone" (selection bar → Enrich → Contact details) — Prospeo, same lookup as "Reveal Mobile Number" | 12 cr on hit | up to 100 | 12 × hits |

- **Fewest credits spent** — no reveal finds a number: **0 credits** (an
  unlikely outcome, since you'd get no mobiles either).
- **Full yield** — every reveal finds a number: 100 × 12 = **1,200
  credits** (≈ €36).
- **Realistic estimate** (assumption: mobile coverage is lower than email
  coverage, about 30% of people have a discoverable verified mobile):
  100 × 0.3 × 12 = **360 credits** (≈ €11).

**Spend less:** a company's main phone number already comes free with a
2-credit "Contact Brief" lookup — only select rows you actually need a
personal number for before running the Mobile field, so you're not paying
to check people you won't call.

## 6. Import a 2,000-row Excel and fill company data

Starting point: a 2,000-row Excel file with a company domain or name per
row, no company data yet.

| Step                                                                                 | Rate                           | Count       | Credits           |
| ------------------------------------------------------------------------------------ | ------------------------------ | ----------- | ----------------- |
| File import                                                                          | 1 cr flat                      | 1 list      | 1                 |
| AI column detection (runs automatically on every import)                             | billed by usage, no fixed rate | 1 list      | small             |
| "Company Lookup" (by domain) — only when it isn't already free from the shared cache | 0.25 cr on hit                 | up to 2,000 | 0.25 × rows found |

"Company Lookup" checks ListPlus's shared company cache first — a domain
another user recently looked up costs nothing. The figures below assume
every match calls the paid provider, so they're an upper bound; your actual
cost can be lower.

- **Fewest credits spent** — few domains resolve to a company, or most hit
  the free cache: close to the cost of the import plus column detection
  alone, both small.
- **Full yield, all paid** — every domain resolves and none is cached:
  2,000 × 0.25 + 1 = **501 credits** (≈ €15).
- **Realistic estimate — upper bound** (assumption: about 70% of domains
  resolve to a company profile, all via the paid lookup): 2,000 × 0.7 ×
  0.25 + 1 = **351 credits** (≈ €11) or less.

2,000 rows fit comfortably within Basic's 10,000-record limit across all
your lists.

**Spend less:** only run "Company Lookup" on rows that actually have a
domain or company name — skip blanks. "Company Lookup" checks ListPlus's
shared company cache first, so domains already in the cache cost nothing.

## 7. Sales Navigator import of 500 leads + LinkedIn enrichment

Starting point: a Sales Navigator search URL, importing up to 500 leads.
Sales Navigator leads don't include email addresses, so finding one is a
separate step afterwards.

| Step                                                                                            | Rate                     | Count               | Credits          |
| ----------------------------------------------------------------------------------------------- | ------------------------ | ------------------- | ---------------- |
| Sales Navigator import                                                                          | 30 cr base + 1 cr/result | up to 500 results   | 30 + 1 × results |
| Optional: "Enrich LinkedIn Data?" dialog — Contact Profiles + Company Profiles, both pre-ticked | 0.5 cr/row each          | up to 500 rows each | up to ~500 total |
| "Contact Brief (by LinkedIn URL)" — Prospeo, from the Enrich menu                               | 2 cr on hit              | up to 500           | 2 × hits         |
| "Find Email (by Name & Company)" fallback — FullEnrich, the entry showing 6 credits             | 6 cr on hit              | remaining misses    | 6 × hits         |

The import itself is charged once it finishes, based on the results actually
returned — only the 30-credit base fee is charged if it returns zero leads.
Right after a successful import, an "Enrich LinkedIn Data?" dialog offers
richer LinkedIn profile fields (job title, education, skills for people;
industry, size, website for companies) with both checkboxes pre-ticked and
an "Enrich Now (~credits)" button showing the live estimate — click **Skip**
if you only want emails, since this step is optional and separate from
finding one. As with the earlier examples, two menu entries share the label
"Find Email (by Name & Company)"; pick the one showing 6 credits for the
fallback.

- **Best case** — full 500 leads imported, Contact Brief finds every
  email: (30 + 500) + 500 × 2 = **1,530 credits** (≈ €46).
- **Worst case** — full 500 leads imported, Contact Brief misses
  everyone but the 6-credit fallback finds them all: 530 + 500 × 6 =
  **3,530 credits** (≈ €106).
- **Realistic estimate** (assumption: 60% found by Contact Brief, 20% by
  the fallback, 20% not found): 530 + 300 × 2 + 100 × 6 = **1,730
  credits** (≈ €52).

These figures don't include the optional "Enrich LinkedIn Data?" step —
keeping both its checkboxes ticked for all 500 leads adds up to about 500
more credits (less once shared companies are deduplicated).

500 leads fit within Basic's 10,000-record limit.

**Spend less:** starting a Sales Navigator import needs the full 530-credit
maximum available in your balance up front, even though you're only charged
for results actually returned — check your balance before you start a large
one. Click Skip on "Enrich LinkedIn Data?" if you only need emails, run
Contact Brief before the pricier fallback, and only enrich the leads you'll
actually contact.

**Related topics:** price-list · price-list-ai-research-imports ·
price-list-profile-add-ons · what-does-one-contact-cost · credits-explained
· buying-credits · plans-and-pricing · which-plan-do-i-need.

## FAQ

### How much does it cost to find emails for 1,000 contacts?

Assuming a mix of hit rates, a realistic estimate is around 2,400 credits (≈ €72) for about 800 emails found: 60% found via the 2-credit "Contact Brief" and another 20% via the 6-credit fallback. Best case (everyone found by the cheap route) is 2,000 credits; worst case (everyone needs the expensive fallback) is 6,000 credits. 1,000 rows fit within Basic's 10,000-record limit.

### What does cleaning and verifying 5,000 contacts cost?

Cleaning — Analyze's rule-based checks, fixes and duplicate merging — is free; only automatic column detection and email verification cost credits, both billed by usage, with verification at 0.1 credits per address once the service is actually called. A realistic estimate, including the 1-credit import, is around 426 credits (≈ €13), assuming most addresses look plausible enough to need the paid check. 5,000 records fit within Basic's 10,000-record limit.

### What do 500 leads with verified emails from Segment Search cost?

Fetching 500 results (20 pages of up to 25) costs a flat 40 credits, added to your list page by page with the free "Add To List" button — there's no bulk email reveal inside Segment Search itself. From the list, "Contact Brief (by LinkedIn URL)" costs 2 credits per hit, so a realistic estimate assuming about 60% of leads get a verified email is around 640 credits (≈ €19); the range runs from 40 credits (no hits) up to 1,040 credits (every lead hits).

### How much is one AI Research run?

There's no fixed total — the agent's reasoning is billed by actual usage, scaling with how many steps the run takes, and the run stops itself if your balance runs out. Only the optional paid sources have a fixed rate: for example, 2 Reddit searches, 1 X search and 2 tech-stack lookups add up to 15.5 credits (12 + 3 + 0.5) in source charges, on top of the separately billed reasoning. You need at least 1 credit in your balance to start a run.

### What do mobile numbers for 100 people cost?

Mobile lookups cost 12 credits per hit either way: "Reveal Mobile Number" in a single contact's record panel, or, for a batch, select the rows and pick Person → Contact details → Phone after clicking Enrich in the selection bar. Assuming a realistic 30% of people have a discoverable verified mobile, 100 people costs around 360 credits (≈ €11); the range runs from 0 credits (no hits) up to 1,200 credits (every one hits).

### How much is a Sales Navigator import of 500 leads?

Importing up to 500 leads costs 30 credits base plus 1 credit per result — 530 credits (≈ €16) for a full 500, charged once the import finishes. Adding email enrichment on top ("Contact Brief" at 2 credits per hit, with a 6-credit fallback for the rest) brings a realistic estimate to around 1,730 credits (≈ €52) for the import plus enrichment together; the optional post-import "Enrich LinkedIn Data?" dialog for fuller profiles is separate and skippable.

### What does filling company data for 2,000 rows cost?

A realistic estimate is around 351 credits (≈ €11), including the 1-credit import, assuming about 70% of domains resolve to a company via the paid "Company Lookup." That figure is an upper bound — "Company Lookup" checks ListPlus's company cache first, so some domains cost nothing.

### Can I do this with the 25 free credits?

Not at this scale — 25 credits covers roughly a hundred 0.25-credit Company Lookups on their own, less once an import's 1-credit charge and column detection's small usage-based cost are taken out. It's enough to test one or two lookups, not a 1,000-row or 500-lead task — see "[Buying credits](https://listplus.ai/en/help/plans-credits-billing/buying-credits)" for pack sizes to cover a real batch.

### How many credits do I need per month?

There's no fixed number — credits are usage-based, so size your own need by estimating your typical monthly volume of lookups, imports and AI use and multiplying by the price list's per-action rates. Reusing a worked total above for a similarly sized task is the fastest way to get a rough monthly figure.
