Dial the inputs, watch the plan rebuild itself. The numbers below come from today's call with Tyler and Jorge. Adjust the volume target once Eric weighs in.
Conservative defaults follow the call. Pull the sliders to model 100/day, 200/day, 300/day, or a partial rollout. Cost and timeline below adjust live.
Each square is one mailbox. Hover any cell to see the domain it lives on. SDRs are stacked vertically; mailboxes for each SDR fan out horizontally across the available domains.
Domain age, then mailbox warmup, then ramp. Each phase exists for a reason. Skipping any of them is how teams torch their sender reputation before they even start.
The primary domain (artera.io) is sacred. It carries customer communications, support, contracts, billing. Cold outbound deliverability swings get isolated to dedicated secondary domains.
Outbound prospecting runs on secondary domains. Your primary stays clean for customer comms only.
If a prospecting sender gets flagged or burned, the cost is contained to that domain. Customers keep getting through. Renewals keep going out. Support tickets keep landing.
Stay recognizable. The prospect should still see "Artera" or read a believable variant. Avoid random strings or sketchy TLDs.
Each new domain needs three records configured before any send goes out:
SPF · authorizes Apollo IPs to send mail as your domainDKIM · cryptographically signs every outgoing messageDMARC · sets policy for messages that fail SPF or DKIMApollo provides the exact values during mailbox setup. Set them once at the registrar, then let propagation run for 24-48 hours before mailbox creation.
Apollo credits, current pricing.
| Domain | 1,500 cr / year |
| Mailbox | 300 cr / month |
At today's plan (12 SDRs, 200/day target, 50/day per mailbox, 3 per domain):
Drop the volume target to 100/day and the build halves. The calculator tab shows live numbers.
Each SDR runs prospecting from four mailboxes on different domains. If one mailbox gets flagged, the others keep producing. Warmup is sequential, not parallel.
At the 200/day target with 50/day per fully-warmed mailbox: 4 mailboxes per SDR.
Each mailbox lives on a different domain. So one SDR has, for example:
tyler@getartera.comtyler@tryartera.comtyler@artera-io.comtyler@joinartera.comApollo handles which mailbox sends each step automatically. The rep sees one unified inbox view; replies route back to a single thread.
Each new mailbox follows this ramp. Apollo can drive it automatically with the warmup feature.
| Day | Volume | Sends/day |
|---|---|---|
| 1-3 | 5 | |
| 4-7 | 10 | |
| 8-14 | 20 | |
| 15-21 | 30 | |
| 22-28 | 40 | |
| 29+ | 50 |
Three numbers to watch on every mailbox, every week, especially during ramp:
Not your cold prospecting list. The warmup window is for building trust signals.
It happens. Spam complaint spike, sudden bounce wave, blacklist hit.
Most of these unblock the build. The first one unblocks everything else.
The whole build sizes around this number. 100/day, 200/day, 300/day each produce a different domain and mailbox plan. Calculator tab models all three live.
P0 · This weekClose the loop on next steps from today's call. Confirms the path forward and triggers the working session.
This weekAdd the custom field for email subject to the existing Slack notify workflow. Already firing 78 times; v2 adds the missing context.
Next weekThis artifact. Use it to model scenarios with Eric before purchasing.
DoneSequence states, task types, and reporting fields all map differently. Worth reviewing before finalizing the field map.
This weekBuild the backfill workflow and the sequence rule set live, side by side. Optional but recommended once Eric confirms the volume target.
Once target confirmedSet the open-to-call task threshold to 1, confirm rule sets are scoped correctly, and align the warmup schedule with the volume ramp.
Pre-launchRun a quick check on the four naming variants in the Domains tab. Confirm availability and brand alignment before purchase.
After Eric confirms