Pick the Stack

The stack that fits the numbers you just ran.

Every outbound motion runs on three layers: data (who you contact), sending infrastructure (domains and inboxes that land in the inbox), and reply handling (where replies get booked). How much of each you need depends on your monthly email volume. Not sure of yours? Run the calculator first →

Quick guide · by where you are

Solo seller or founder

Under ~1,500 emails a month
  • Up to 300 contacts a month
  • 3 warmed inboxes on 2 separate domains
  • Reply by hand

Small team, 2–5 reps

~1,500–8,000 emails a month
  • 300–1,600 contacts a month
  • 3–13 inboxes across 2–7 domains
  • Replies routed to the rep who owns the account

Agency or outbound team

8,000+ emails a month
  • 1,600+ contacts a month
  • 13+ inboxes across 7+ domains, with rotation
  • Someone triaging replies every day

Rough guides from the calculator’s starting assumptions (5 touches per contact, 30 sends per inbox per day, 21 sending days a month, 2 inboxes per domain), not benchmarks.

01 · Data

Data and contacts

Sourcing and verifying the contacts your monthly number requires.

  • Verified emails. Verify before you send; bounces hurt every inbox you own.
  • Filters that match your ideal customer. Role, company size, industry, and the triggers you write about in the first line.
  • A clean way out. Export or sync to your sending tool and CRM without manual cleanup.
  • Pricing that fits your contact count. Check how credits or seats scale at your monthly volume before you commit.

Plays for this layer

02 · Sending

Sending infrastructure

Domains, warmup, and inbox rotation so the sequence lands.

  • Separate sending domains. Keep cold email off the domain your team uses every day.
  • SPF, DKIM and DMARC on every domain. Authentication is the baseline for landing in the inbox.
  • Warmup before volume. New inboxes ramp up before they send full sequences.
  • Daily limits you control. Set sends per inbox per day yourself, and rotate across inboxes.

Plays for this layer

03 · Replies

Reply handling

Where positive replies get triaged and booked.

  • One place replies land. A shared inbox or your CRM’s sequence tool, not a dozen separate inboxes.
  • Fast booking. A calendar link ready to send the moment someone says yes.
  • CRM sync. Every reply tied to the contact and account, so nothing falls through.
  • Clear ownership. Someone checks replies every day and knows who follows up.

Plays for this layer

Compare the tools, layer by layer

The plays above name the tools in each layer, what they cost, what they cap and who should skip them. Every tool we cover, grouped by job, is on the tools hub.

See every tool we coverBrowse the Tools plays

Stack questions, answered

What tools do I need for cold email?

Three layers: a data source for contacts, sending infrastructure (separate domains and inboxes that are warmed up), and a place where replies get handled and booked. How big each layer needs to be depends on your monthly email volume.

Should I send cold email from my main company domain?

No. Use separate sending domains so a deliverability problem can’t damage the domain your team uses for everyday email.

How many sending domains do I need?

Inboxes needed ÷ inboxes per domain. The calculator works it out from your revenue target.

Which specific tools should I look at?

Each layer has plays that compare the tools, state the trade-offs and give the date we checked prices. Start with the plays linked under each layer on this page, or browse every tool we cover, grouped by job. Today no page on this site contains an affiliate link.