BUILD 01 · PIPELINE THIS QUARTER
Somewhere in your company, a senior person is spending evenings being an amateur systems integrator — gluing together tools that were each sold as “easy to set up” while the quarter runs down. That was never the job. The vendors sell parts; nobody sells the working machine, or the revenue engineer to build it.
The Lead-Gen Stack is a professional outbound build, from $4,999: intent-rich lead generation, email automation, and CRM automation wired into one working system by people who do both revenue and engineering. Tuned to your business at a two-day diagnostic, live in two weeks, on tools and accounts you own — Apollo, Instantly, Zoho, and HubSpot among them.
WHAT YOU GET
Reps spend their calls on people who are in-market right now — not chasing a list that went stale before it was finished.
Your outreach actually reaches people — and your company’s own domain never carries the risk of it.
No interested prospect slips through a forwarded-email crack again — and the pipeline report finally matches what actually happened.
This is the build you need? Start here.
Book a scoping callTHE CASE · WHAT THE RESEARCH SAYS
Stand up outbound yourself and the real cost isn’t time on a calendar — it’s the spend that sits idle, the mistakes learned by making them, and the market that doesn’t wait while you catch up:
The tools are already paid for. The only question left is how fast they start paying you back.
The tools were bought to produce pipeline. Every week they sit unwired while you learn the setup by hand is a week of spend with nothing coming back.
The margin for error is thin: Gmail and Yahoo require every bulk sender to authenticate — SPF, DKIM, DMARC — and cap spam complaints at 0.3%, or the mail stops landing. Miss it once, and the fix isn’t a setting — it’s weeks rebuilding a domain’s reputation from zero.
Every week spent debugging by trial and error is a week competitors spend closing the deals your list was built to reach.
It’s rarely a junior hire who inherits the domain and the tangled list — it’s the best closer on the team, because they’re the only one who can untangle it. Every hour there is an hour not spent selling, and DIY never puts that line on the invoice.
The rest of the numbers point the same direction:
60%
of a rep’s week goes to everything except selling — Salesforce, State of Sales, 7th Edition (2026)
That’s the admin tax. CRM automation — capture, attribution, and routing with no manual entry — is where those hours come back.
22.5%
of a B2B contact list goes stale every year — people change jobs, roles, and inboxes — HubSpot, database-decay research
The list you bought last quarter is already wrong. Intent-rich lead generation builds from live signals, not a decaying export.
45%
less likely to hit quota — the sellers who feel overwhelmed; half of all sellers are overwhelmed by the amount of sales technology alone — Gartner, 1,026 B2B sellers surveyed, 2024
More tools won’t fix too many tools. Wiring the ones you already have into one system will.
None of this gets shorter by trying harder — expertise doesn’t skip a step, it skips the mistakes. What it buys back is the weeks DIY teams lose relearning the same pitfalls, and the ROI that stays parked until the system is actually running. The build hands you that system in two weeks, on accounts you own, with your team selling the whole time. We run the same system we ship — ask on the scoping call and we’ll walk it live.
HOW IT RUNS · DAYS 1–14
Every build opens with the two-day diagnostic. On the Lead-Gen Stack the warmup clock starts the same day — it is the schedule’s one fixed law, so it runs first. Scoped and priced at the diagnostic — the number we lock is the number you pay.
A working diagnostic on your live stack: existing domain reputation posture, list quality, Apollo and Instantly configuration, CRM field map. Sending domains are ordered and warmup begins now. Findings land in the Kickoff Findings Brief, reviewed with you line by line.
Scope quotes the findings verbatim and the price locks against it in the SOW. If part of your setup is already sound, it stays out of scope — you don’t pay to have working things rebuilt.
Sending domains authenticated — SPF, DKIM, DMARC — inboxes created, lists built from Apollo triggers, sequence architecture drafted in Instantly, while warmup ramps in the background.
The direct webhook goes in: replies begin landing in the CRM as attributed leads, routing rules put them in front of the right rep, and the playbooks get written against the system as it actually behaves.
A live end-to-end test — a real reply walks the full path while you watch. Then the runbook, the acceptance checklist, every credential confirmed in your accounts, and hands-on training. Warmup’s remaining ramp hands over with its checklist.
Want the plan mapped to your stack?
Book a scoping callTHE TERMS · EVERY BUILD, NO EXCEPTIONS
Locked at the diagnostic, before build hours start. The number on the SOW is the number on the invoice — and no retainer follows it.
Two weeks — two to three for AI grounding — with the diagnostic, the build, and the handover on the calendar before work begins.
Code, domains, credentials, playbooks — on your accounts from day one. If we disappeared tomorrow, your system wouldn’t notice.
The people who scope your build lead the build itself. No juniors learning on your instance, no account layer between you and them.
FAQ · ANSWERED STRAIGHT
Yes — ours. Rad Shift’s own outbound runs on the exact architecture this build ships: Apollo feeding Instantly, replies firing a direct webhook into Zoho CRM, every record attributed to its campaign and sequence. Our CRM has never been manually updated. On the scoping call we share a screen and walk a live reply through the whole path — campaign, webhook, record, routing.
Nothing in the build fails silently. Each handoff is a direct webhook with defined failure behaviour: failed deliveries retry, and anything that still can’t complete is logged and raised to a named owner instead of vanishing. The runbook you receive documents every failure point in the chain — what the system does about it, and who gets told.
By name: Apollo, Instantly, Zoho, and HubSpot. The stack we run ourselves is Apollo → Instantly → Zoho over a direct webhook, so those three we operate daily, not just configure. CRM wiring for HubSpot follows the same webhook pattern. If your stack differs, the two-day diagnostic is where it gets mapped — before any build hours are spent.
Fixed scope, fixed price, no retainer. The category norm is a custom quote at the end of a discovery arc; ours is a number that locks at the two-day diagnostic — the Lead-Gen Stack starts at $4,999 USD — and goes into the SOW before a build hour is spent. It doesn’t move mid-build, and nothing recurring follows it.
You’re handed a running system and everything needed to run it without us: the runbook, the playbooks, an acceptance checklist you sign against, and every credential — registrar, DNS, inboxes, CRM — in your own accounts. There’s no retainer and nothing that phones home to us. Dependency after handover would be a defect.
Yes — the build doesn’t send from your existing domains at all. We provision fresh custom sending domains, separate from your primary, authenticate them with SPF, DKIM, and DMARC, and start warmup on day one; the ramp to full volume runs about three weeks and hands over with its checklist. Your primary domain stays out of the sending path entirely — which also protects the reputation your everyday email depends on.
Yes — outright. They’re registered in your registrar account, the DNS lives with you, and the inboxes are yours. Like everything else in the build, they pass through at handover: we hold nothing back and keep no access you didn’t grant.
Deliverability is a practice, and the practice is what we hand over: authenticated domains, the warmup ramp checklist if the window is still running, and playbooks that spell out sending volumes, rotation, and list hygiene. The system runs entirely on your accounts, so nothing degrades because we stepped away — the posture you inherit is documented, not tribal knowledge.
No. The build runs on the licences and accounts you already own — the diagnostic maps what’s configured well and keeps it. If part of your setup is already sound, the findings brief says so and the scope narrows; findings are never padded into work.
The wiring is a direct webhook into the CRM, and the pattern is CRM-agnostic by design. Zoho and HubSpot we’ve integrated by name; Salesforce and others follow the same pattern. Which CRM you run is one of the first things the two-day diagnostic maps, so the answer is confirmed before the price locks — nothing is replaced by default.
The people who scope it lead it. Named owners run the diagnostic, the build, and the handover — no juniors learning on your instance, no account layer between you and the person doing the wiring. If a disclosed delivery partner ever executes a piece, they’re named in the SOW with your consent before any access exists — never silently.
The two-week schedule holds because the thing that usually blows it — unmapped scope — is removed before the build starts: scope quotes the diagnostic’s findings and locks. The one clock that runs longer by design is domain warmup, which starts on day one and ramps about three weeks; it’s named in the SOW with its date and hands over with its checklist. The build doesn’t drift, because the scope can’t.
THE SCOPING CALL
We’ll look at your outbound together — the domains, the tools, where replies actually go today — and map it against this build. You’ll leave knowing whether it’s the right fix, what the diagnostic would cover, and the number it locks at. If it isn’t your build, you’ll hear that plainly too.
The calendar reserves a 30-minute slot. The call is the 20 minutes we committed to — the extra ten is buffer, yours back if we don’t need it.
Solving a different problem? CRM + Data Foundation · AI Grounding — or prefer the diagnosis first? The standalone audit: five days, $2,500, credited in full to any build within 90 days.