Customer story · anonymous

GTM agency: verify permutations before the sequence

A multi-client outbound agency was generating first-name/last-name email permutations from enrichment tools, then importing the full matrix into sequencers. Hard bounces spiked on catch-alls and dead pattern-matches. They inserted Verifly as a PAYG verify gate — without naming clients or proprietary stacks here.

Situation

  • 10–20 client workspaces; bursty volume tied to campaigns, not calendar seats
  • Enrichment produced 3–8 email guesses per contact
  • Monthly verifier seat felt expensive on quiet weeks and still constrained launch weeks

Approach

  1. Generate permutations in the enrichment sheet / Clay table as before
  2. Batch or bulk verify every guess via Verifly API (Bearer vf_ key)
  3. Keep deliverable only (optional risky policy per client); drop undeliverable / disposable
  4. Import survivors to the sequencer; report remove-rates back to clients
curl -X POST "https://verifly.email/api/v1/verify/batch" \
  -H "Authorization: Bearer vf_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"emails":["j.smith@acme.com","john.smith@acme.com","jsmith@acme.com"]}'

Results (directional)

  • Material drop in first-touch hard bounces after filtering undeliverables
  • One prepaid credit pool across clients — no per-workspace monthly seat
  • Clearer client reporting: “X% of permutations removed before warmup”

Figures vary by list quality; this page intentionally omits client names and exact percentages.

Try the same pattern

Start with the agencies use case, size credits on the credit calculator, or grab a sample CSV.

Start free

Questions: hello@veriflyemail.com — only contact route. No competitor bashing; independent PAYG verification API.