Plan the outbound machine before you buy the infrastructure.

Set a meeting target, then inspect the contact volume, sending capacity, and cost required to support it. The assumptions stay visible, so you can replace them with your own data.

How the calculation works.

The planner works backwards from meetings through positive replies and booked calls. It then turns the required send volume into mailbox, domain, and operating-cost estimates.

How to use the result.

Use the output to test whether the motion is realistic before you buy domains or add more tools. If the contact requirement looks too high, improve targeting, offer quality, or conversion before increasing volume.

Formula behind the result.

Contacts
Meetings ÷ positive reply rate ÷ reply-to-meeting rate
Monthly sends
Contacts × touches per contact
Mailboxes
Daily sends ÷ daily mailbox capacity
Mailbox and domain cost
Monthly mailbox cost + amortized annual domain cost

Worked example.

With a goal of 10 meetings, a 3% positive reply rate, and a 35% reply-to-meeting rate, the planner requires about 953 contacts before sequence touches and sending capacity are applied.

Questions worth asking.

What does this outbound planner calculate?

It estimates the contacts, sends, mailboxes, domains, and mailbox-and-domain cost required to support a monthly meeting target.

Are the defaults a performance benchmark?

No. They are editable planning assumptions. Use your own campaign data when you have it.

Why are domains and mailboxes included?

Sending capacity has a practical limit. The planner makes that operating requirement visible before a campaign starts.

Does this guarantee meetings or inbox placement?

No. Market quality, targeting, positioning, copy, and inbox-provider policies all affect results.

Keep the working notes.

One practical worksheet for turning this plan into a working launch list.

Target account list sizer

Turn market fit, buying intent, and sales capacity into a target account list your team can actively cover.

Open tool