Data quality
Duplicates, decay, and empty fields where decisions expect facts — measured on the live records, not sampled from a demo.
THE STANDALONE AUDIT · DIAGNOSIS FIRST
The diagnosis, on its own.
The standalone audit is a $2,500 USD flat-fee diagnostic of your CRM and go-to-market stack — the same diagnostic that opens every Rad Shift build, run on its own: five days on your live systems, ending in a written findings register and a 45-minute readout instead of a build.
Most teams skip straight to a build, because this same diagnostic is already days 1–2 of every build at no separate price. Buy it standalone when you want the diagnosis first — to fix it yourself, or to decide with evidence before committing budget.
- $2,500 USD — flat, not a “from”
- Five business days
- Findings register + 45-minute readout
- Read-only, core team only, revoked at the end
- 100% against any build started within 90 days
- One intake call, one readout — nothing between
WHAT SHIPS · FIVE DAYS ON YOUR LIVE STACK
Five findings areas. One register.
Fieldwork on your live systems — not a questionnaire, not a workshop. Where the revenue-relevant gaps are, with the evidence attached.
Field + pipeline architecture
Whether the stages, fields, and ownership model can carry reporting you’d send upstairs without caveats.
Routing + reply handling
Where a hand-raise physically goes today, how long it waits, and what never makes it onto the record.
Deliverability posture
What your sending rides on — domain separation, authentication, volume discipline — and what your primary domain is exposed to.
Integration integrity
Every path data takes between tools: what’s wired, what’s quietly manual, and what fails without telling anyone.
The findings register
Every finding written with its evidence, a severity graded by revenue relevance, and the fix — in functional terms any competent implementer can execute.
STRAIGHT ANSWER · WHO THIS IS FOR
When to buy it — and when not to.
You’ll act on the findings yourself.
You have the ops or admin capacity in-house and want the map, the evidence, and the priority order — then you take it from there. That’s exactly what the register is written for.
You need the independent read first.
Budget needs a case, or you’re genuinely unsure which problem you have. A paid, unconflicted diagnosis you own outright is the evidence — whoever ends up doing the work.
You already know you’ll hire the fix.
Then don’t buy this standalone. The same diagnostic is days 1–2 of every build at no separate price. Start with a scoping call instead — buying the audit first wouldn’t cost you anything extra, but it adds a step you don’t need.
Steering you to the cheaper path is the point: the audit exists for the buyer who wants it, not as a toll booth in front of the builds.
Start a build within 90 days, and the audit was free.
The $2,500 credits in full against any build started within 90 days. Days 1–2 of that build become a two-hour refresh of the findings instead of a repeat diagnostic, and the build quote locks against the register. Audit first, then build — same total price as going straight in. The only thing the standalone path adds is certainty.
HOW IT RUNS · FIVE BUSINESS DAYS
Two meetings. The rest is fieldwork.
-
Access + intake
Read-only credentials, the map of what runs where, and what you already suspect. The only meeting before the readout.
-
Fieldwork
The live stack, not a questionnaire — records, fields, pipelines, reply paths, sending posture, and every integration between them.
-
The register
Findings written and graded by revenue relevance — each with its evidence and its fix, in functional terms.
-
The readout
45 minutes with your team: the priority order, what we’d fix first, and why. Then the register is yours — to act on with anyone.
FAQ · ANSWERED STRAIGHT
The questions a diagnosis-first buyer actually asks.
What exactly do I get for $2,500?
A findings register — a written report on your live stack covering data quality, field and pipeline architecture, reply routing and deliverability posture, and integration integrity. Every finding carries the evidence behind it, a severity graded by revenue relevance, and the fix. Plus a 45-minute readout where we walk your team through the priority order. The register is the deliverable; there is no gated summary and no teaser version.
Do you need access to our systems?
Read-only access to the CRM and the sending and integration tooling, granted on day one and yours to revoke the moment the engagement ends. Only the core delivery team touches it — access is never subcontracted — and nothing is written, changed, or exported beyond the evidence quoted in the register.
What if the findings say we don’t need a build?
Then the register says that, in writing. The audit is priced to be worth doing on its own precisely so the findings owe nothing to a sale — if the honest read is that your stack is sound, or that your next constraint isn’t wiring at all, that’s what the readout will tell you.
Can I take the report to another vendor — or fix it in-house?
Yes. It’s your report. Findings are written in functional terms — what’s broken, why it matters, what fixed looks like — so any competent implementer, including your own team, can execute them. Nothing in it depends on hiring us.
What happens if I do want a build afterwards?
The $2,500 credits in full against any build started within 90 days, and days 1–2 of that build become a two-hour refresh of the findings instead of a repeat diagnostic. The build quote locks against the register — so the audit-first path costs the same as going straight to a build; it just adds certainty before the commitment.
Why does it cost money when others audit for free?
Because it’s five days of real work on your live systems, and pricing it is what keeps it honest. A free audit has to pay for itself somehow, and the usual way is a report written toward whatever its author sells. This one is paid for by you, owned by you, and credited back if you build — which is as close to unconflicted as a vendor diagnosis gets.
BOOKING · NO PITCH ATTACHED
Book the audit — or just ask about it.
A 20-minute call before anything is billed: what access looks like, which systems are in scope, and whether the audit is even the right instrument for what you’re seeing. If a build is plainly the better path for you, you’ll hear that on the call — see the section above.
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.
Already know you’ll hire the fix? Start at the builds — the diagnostic opens every one of them.