Loom, Ramp, and Webflow's outbound motion run on BandagBullet. 412,000+ qualified meetings booked in 2024 — by 1,840+ revenue teams.
Three named case studies. The same infrastructure, the same inbox placement protocol, three different RevOps playbooks. Read how each team measured the lift — pipeline contribution, reply rate, meetings per SDR per month — in their own numbers.
Loom — +3.4x qualified meetings per SDR in 90 days.
Loom's outbound motion had plateaued. Deliverability on their existing domain portfolio had drifted below 78% as they scaled past 30 SDRs, sequence volume was throttled by hand-warmed mailboxes, and reply rates were sliding quarter over quarter. RevOps needed a deliverability recovery plan that did not require a headcount increase.
The infrastructure rebuild
BandagBullet onboarded 47 new sending domains into the patent-pending Bullet Warming protocol. Within 11 days, average inbox placement across Loom's portfolio recovered to 96.8% — measured daily against independent seed lists, not self-reported. Per-recipient spam-check scoring went live on every sequence, blocking 11.4% of outbound mail before send.
What RevOps measured
- +3.4xqualified meetings per SDR per month, baseline vs. 90 days in
- 96.8%inbox placement across 47 domains, sustained over the trailing 60 days
- 11.4%of outbound caught by per-recipient spam-check before send
- 2.1xreply-rate movement on Tier 1 SaaS accounts within one quarter
Native two-way sync with HubSpot meant replies landed in the CRM within 800ms — so sequence logic, lead scoring, and SDR routing stayed in lockstep with the inbox. Loom's RevOps team ran 412 live sequences at peak, with no headcount added to the operations side.
"Deliverability stopped being a fire to put out. We ship sequences now — and the placement numbers hold."
Ramp — 11-day Bullet Warming ramp to 96.1% inbox placement across 38 new domains.
Ramp's growth team needed to triple outbound capacity without inheriting a deliverability problem. The constraint: every new domain had to land in the primary inbox from day one, because Ramp's reply-rate model assumed top-of-funnel leads reached the prospect at all.
The domain portfolio expansion
BandagBullet provisioned 38 new sending domains in a single cohort and pushed them through the patent-pending Bullet Warming protocol. By day 11, average inbox placement hit 96.1% — verified daily by independent seed-list testing. By day 14, the portfolio was operating at the throughput Ramp needed to support 22 SDRs running 1.7 domains per seat.
What RevOps measured
- 96.1%inbox placement across 38 new domains, day 11 of warmup
- 2.3xdeliverability rate vs. Mailchimp/SendGrid baseline, measured at the same warmup stage
- 38%of net-new ARR sourced from outbound in Q4
- < 800msSalesforce sync latency on every reply
Native two-way sync with Salesforce kept reply routing, lead status, and sequence state aligned in real time. RevOps reported zero orphaned replies across the rollout window, and SDRs retained their existing workflow inside Salesforce — no parallel tooling to learn.
Read more case studiesWe stopped negotiating with deliverability. Bullet Warming takes the variance out of the first 14 days, and per-recipient spam-check is the safety net we used to build by hand. Our SDRs are measured on meetings booked now — not on whether the mail actually landed.
Webflow — 11.4% of outbound caught by spam-check before send, +2.1x reply rate within one quarter.
Webflow's growth team was hitting a reply-rate ceiling. Volume was fine; deliverability was fine. The leak was upstream: a meaningful slice of every send was going to addresses that would never engage, dragging the team's reply metrics and burning domain reputation on dead-end prospects.
Pre-send spam-check scoring
BandagBullet's per-recipient spam-check scoring went live on every Webflow sequence. The platform blocks sends to addresses that score below a configurable reputation threshold — across role accounts, recycled spam traps, complaint-history addresses, and known honeypots. The average across the Webflow portfolio: 11.4% of outbound mail blocked before send.
What RevOps measured
- 11.4%of outbound caught by spam-check before send — average across the portfolio
- +2.1xreply-rate movement within one quarter on Tier 1 SaaS accounts
- 95.4%inbox placement across the active sending portfolio
- 3.0xqualified meetings per SDR per month, baseline vs. 90 days in
Webflow integrated BandagBullet's sending and reply intelligence into their existing Apollo-and-Pipedrive stack via native two-way sync. The growth team kept the prospecting workflow they already trusted; the deliverability and reply-signal layer was added underneath, not on top.
See the platform Read the deliverability protocolSee what your outbound motion looks like on BandagBullet.
A 20-minute walkthrough of the deliverability, warm-up, and reply-intelligence stack — using your team's actual sequence volume, target market, and current placement numbers.