B2B SaaS · Infrastructure
SaaS lead gen case study: Helix Cloud
Added $42k MRR in 90 days
From a stalled founder-led motion to a productized outbound engine that booked qualified infra buyers on a $90k ACV.
Challenge
A mid-market infra platform with a $90k ACV and a founder-led outbound motion that stalled at 11 meetings a month. Deliverability was burned, lists were scraped, and SDRs were writing from cold inboxes.
Solution
We installed a full DFY outbound stack — new domains, warmed mailboxes, buying-committee data, and three concurrent sequences — then ran reply handling until meetings landed on the AE calendar.
The DFY system we installed
- 8 sending domains, 16 inboxes, 21-day warmup
- ICP: VP Eng / Head of Platform at 80–400 person SaaS
- 3 campaigns: net-new, expansion, and competitor-displace
- Slack-based reply desk with AE handoff in under 12 minutes
The constraint was infrastructure, not copy
Helix had a sharp offer and a real buyer. What they did not have was a sending system that survived week three. We rebuilt domains, DNS, and warmup before a single sequence launched. That is the unglamorous first week of every DFY engagement — and the reason their previous agency never got past spam.
Targeting the committee, not a title
We mapped the buying committee around the VP of Engineering: platform leads, FinOps, and the CTO on deals over $75k. Enrichment pulled tech-stack signals (Kubernetes spend, multi-cloud) so the first line referenced a real constraint instead of a guessed pain.
Execution that books, then gets out of the way
Once replies started, we did not dump a CRM login on Helix. Positive threads were worked to a 20-minute discovery on the AE calendar. Negative or nurture replies were tagged and recycled. Ninety days in, outbound was a product: three live campaigns, a weekly creative test, and a meeting run-rate the sales team could forecast against.
Want the same machine?
Qualify in two steps. The calendar only opens if the numbers make the call worth both sides of the table.