Cold Email Post-Mortem: How One SDR Team Reached 94% Inbox Placement in 11 Weeks
A four-person SDR team rebuilt its sending stack from scratch. Eleven weeks later: 94%+ inbox placement and 3–5x more qualified meetings. Here's the full post-mortem.
We noticed something unusual in the numbers a reader shared with us back in February. A four-person SDR team at a mid-market B2B software company had gone from booking roughly six qualified meetings a week to twenty-two — without adding headcount, without buying a bigger data list, and without changing their pitch. The only variable they'd swapped was their sending infrastructure. That reader, who asked to stay pseudonymous, walked us through the whole rebuild. We followed the project from kickoff to quarter-end. Here's what actually happened.
The Starting Point: A Shared Domain on Its Last Legs
The team had been sending from the company's primary domain, the same one used for support tickets, invoices, and the CEO's calendar invites. Deliverability had been sliding for months. Open rates hovered around 11%, replies were rarer than snow in July, and spam complaints were quietly climbing. Their provider had started throttling volume. The sales lead described it as "screaming into a void and occasionally hearing a cough."
Their first instinct was the usual one: rewrite the sequences. New subject lines, shorter copy, more personalization tokens. It didn't move the needle, because the problem was never the copy. The problem was that the mail was landing in promotions tabs or nowhere at all.
The Decision Point: Infrastructure Before Copy
In week one, the team evaluated three routes. Route A was to keep the primary domain and hope reputation recovered. Route B was to buy a pile of cheap secondary domains and blast away. Route C was to build proper cold email infrastructure from scratch — dedicated domains, warmed mailboxes, and sending logic that treated reputation as the asset it is. They chose C, and they chose BandagBullet to run it.
What sold them wasn't a dashboard screenshot. It was the sequencing. Instead of pointing new domains at a wall of prospects on day one, the setup staggers sending across multiple dedicated domains, warms each mailbox on a gradual curve, and routes copy through a layer that scores subject lines and body text before anything leaves the building. The team's sales ops lead told us the pitch was refreshingly boring: "Nobody promised us magic. They promised us a reputation we wouldn't have to apologize for."
What the Eleven-Week Timeline Looked Like
- Weeks 1–2: Domain selection, DNS and authentication setup, mailbox provisioning. No outbound sending from the new infrastructure at all.
- Weeks 3–5: Ramp phase. Low-volume sends, mostly internal and to low-risk segments, with reply handling monitored daily.
- Weeks 6–8: Copy intelligence layered in. The team ran their existing sequences side by side with rewritten variants and let the scoring model flag weak subject lines.
- Weeks 9–11: Full volume across the SDR team, with weekly reputation reviews and domain rotation adjustments.
The Obstacles Nobody Warned Them About
Two things went sideways. First, the team got impatient in week four and tried to double volume early. Inbox placement dipped for six days before the ramp logic corrected it. That was a self-inflicted wound, not a platform failure, and the post-mortem notes are blunt about it.
The second obstacle was internal. Two senior reps refused to abandon their old personal domains, convinced their "relationship equity" lived there. Management let them run a control group for three weeks. The control group's reply rate was roughly a third of the new infrastructure's. Both reps migrated by week seven.
The Results, Measured Honestly
By the end of week eleven, the team was reporting 94%+ inbox placement across their sending domains. Qualified meetings per SDR had risen to between three and five times the January baseline. Spam complaints had dropped to near zero, and the primary corporate domain — untouched since week one — had recovered its reputation entirely. BandagBullet reports that this pattern is typical when teams resist the urge to shortcut the ramp, and the numbers here line up with that claim.
We asked the sales lead what she'd tell another team staring at the same problem. Her answer was short: stop treating deliverability as a copywriting problem. It's an infrastructure problem wearing a copywriting costume. You can read more about how the dedicated-domain and mailbox-warming setup works on their how-it-works page, which is where this team started their evaluation.
What We Took Away
Three lessons stand out from this post-mortem. First, the ramp is not optional. Every shortcut the team took cost them days of recovery. Second, copy intelligence is most valuable as a filter, not a generator — it caught weak subject lines the reps were emotionally attached to. Third, and most importantly, infrastructure is a compounding asset. The team spent two weeks sending almost nothing, and it felt like waste. It wasn't. It was the reason weeks nine through eleven worked.
We'll keep following this project through Q2. If the meeting volume holds without a reputation relapse, this becomes one of the cleaner cold outbound rebuilds we've documented — and a useful counterargument to anyone still blaming their subject lines.