Price
£29 / £49 GBPOne exact-batch handoff bundle. £29 up to 1,000 rows, £49 up to 5,000 rows.
Lead List QA
ListSift lets you paste a lead CSV, inspect invalid emails, weak domains, and duplicates, then pay once to unlock the exact-batch handoff bundle before the batch reaches outreach, import, or client handoff. Version 1 previews one batch for free and releases one exact-batch handoff bundle up to 5,000 rows: the client-ready handoff CSV, browser-openable handoff report, stricter import packs, and rejects files. No subscription, no sales call, no account setup.
Price
£29 / £49 GBPOne exact-batch handoff bundle. £29 up to 1,000 rows, £49 up to 5,000 rows.
Payment
Hosted by StripeCard details stay inside Stripe Checkout, not this app.
Output
Instant bundle releaseThe client-ready CSV, strict HubSpot and Apollo import packs, rejects files, and handoff report unlock only after the paid session is verified server-side.
Use This Tool When
Interactive Tool
Run the same preview flow a buyer would use, then unlock the exact batch only if the visible damage justifies the payment. Version 1 previews and unlocks one exact-batch handoff bundle up to 5,000 rows.
Paste a lead list or load a UTF-8 CSV file to see what would make a buyer hesitate before delivery. The live preview accepts comma, semicolon, and tab-separated exports up to 5,000 rows in version 1.
Version 1 rules
The preview should make the quality gap obvious enough that the paid handoff bundle feels like an execution-ready operator pack, not speculative analysis.
Run a preview first.
| Row | Domain | Status | Issues | Action | |
|---|---|---|---|---|---|
| Run a preview to inspect flagged rows. | |||||
The preview intentionally shows only a slice of flagged rows. The paid handoff bundle turns the full batch into row-by-row keep, remove, dedupe, replace-contact, or verify-domain instructions with confidence, reasons, priority, handoff notes, duplicate context, and the included report and stricter import packs.
Free sample includes up to 3 example rows with batch grade, next step, and handoff note. The full paid handoff remains locked.
Paid export
Buy a one-off exact-batch handoff bundle for this CSV, up to 5,000 rows. The bundle includes the client-ready handoff CSV, browser-openable handoff report, row-by-row next steps, confidence scores, priority, buyer-friendly reasons, handoff notes, domain-source context, duplicate groups, stable row hashes, strict import-ready subsets, and separate rejects files for a more defensible handoff.
£29 GBP
Up to 1,000 rows. Larger batches up to 5,000 rows are £49 GBP.
Free preview
Paid handoff bundle
Included strict import packs
Run a preview first.
What Unlocks
Client-ready handoff
The full handoff CSV keeps keep, review, and remove decisions visible so the next operator or client can understand what changed.
Strict import packs
The HubSpot-ready and Apollo-ready files are narrower than the handoff CSV and exclude rows that still need judgment.
Reject files
Each strict import pack includes its own rejects file so blocked rows do not disappear silently into the main handoff.
Paid Output Sample
This example export comes from the same anonymized proof batch shown elsewhere on the page. The paid file turns visible damage into a more defensible handoff CSV with a batch grade, normalized next steps, priority, domain-source context, duplicate sizing, plain-English reasons, and operator notes.
| email_normalized | next_step | action | priority | domain_source | duplicate_size | handoff_note |
|---|---|---|---|---|---|---|
| amira.bennett@northforge.io | verify_domain | keep | low | email_derived | 1 | Domain was derived from the email; verify company match before client handoff. |
| sales@latticeworks.co.uk | dedupe | review | medium | supplied | 2 | Review duplicate group of 2 rows before sending or importing. |
| owen@@latticeworks.co.uk | remove | remove | high | missing | 1 | Remove before handoff: invalid email; missing domain. |
Next step: verify_domain
Action: keep
Priority: low
Why: No issues found.
Note: Domain was derived from the email; verify company match before client handoff.
Next step: dedupe
Action: review
Priority: medium
Why: risky shared or disposable email; duplicate email.
Note: Review duplicate group of 2 rows before sending or importing.
Next step: remove
Action: remove
Priority: high
Why: invalid email; missing domain.
Note: Remove before handoff: invalid email; missing domain.
Buyer-friendly reasons make the cleanup defensible without explaining raw issue codes.
Next-step values, priority, and handoff notes tell the operator what to act on first.
Stable row hashes, domain-source context, and duplicate group sizes make decisions easier to track.
Handoff Summary
This summary uses the same anonymized proof batch as the preview and export samples. The paid CSV is the operational file; the summary is the fast explanation layer around what was checked and what changed.
Example batch summary
Priority split
First actions
ListSift is not trying to be a broad deliverability platform, enrichment suite, or long-term data workspace.
The paid result is a review-ready CSV plus a fast explanation layer for the exact batch you inspected, so the next person can trust the file more quickly.
You return to the success page, the Stripe session is verified, and the exact-batch handoff bundle unlocks immediately: the client-ready CSV, strict HubSpot and Apollo subsets, both rejects files, and the handoff report.
Version 1 support is manual and email-only. If the paid handoff files do not release as expected, send the checkout email or Stripe session details so the batch can be checked quickly.
The preview is the commitment filter. Inspect visible issue counts and flagged rows first, then skip payment if the batch already looks usable.
The first step is a manual fix or rerun for that exact paid batch. If verified paid files still cannot be released after that check, the batch charge should be refunded.
Use the free preview to decide whether the visible damage justifies cleanup before a client, SDR, or system inherits the file.
Use the paid handoff when you want the next person to inherit a batch with clearer row decisions, reasons, duplicate context, and a short summary instead of a raw spreadsheet.