The machine, built and handed over.
Four to six weeks. Qualification, enrichment, routing, conversion, onboarding and retention tracking — built, instrumented and documented, then handed to the team that runs it. I build it myself, so your engineers never see a ticket, and you own it when I leave.
What gets built
Scope is set by the diagnostic, or by a first conversation if you already know where the problem is. Most builds cover some subset of this.
Qualification and enrichment. Every lead resolved to a company record carrying the context a rep needs before the call — size, sector, what they said they wanted — with the historical base enriched too, not just new arrivals.
Routing. Leads assigned by the rules that actually matter to you — account size, territory, vertical, product — so the opportunities worth a conversation reach the right owner on arrival rather than queuing behind everything else.
De-duplication that holds. Idempotent matching on email and domain, so a repeat submission updates the record instead of creating a second one. The data stays clean on its own rather than degrading between cleanups.
Conversion instrumentation. Pipeline stages that match how you sell, speed-to-first-response measured, and calls transcribed and logged against the right record automatically so context survives between touchpoints.
Onboarding and activation tracking. An activation funnel showing every milestone from signature to delivered value as a share of customers — so the stage losing the most people is named rather than guessed at.
Retention scoring. Every customer in exactly one state with a grounded risk score, a save queue that fills itself, and post-mortems that reconcile every system to explain a specific loss.
Reporting that maintains itself. One operating surface that pulls live data on a schedule, re-scores, and pushes each team's priorities to the channel they already work in. No dashboard for someone to keep updated.
How I build
The constraints matter as much as the features.
Around your workflow, not a template. Stages and rules match how your team already sells and delivers, which is why nobody has to be trained out of their own process to use it.
Verified, not self-reported. Wherever a claim could be entered by hand — a save, a reply, a completed step — the system checks it against the authoritative source instead of trusting the label. This catches real problems: on one build it surfaced customers marked as saved who had in fact been refunded.
One source of truth for every number. Scoring and status logic live in shared modules, so the number a rep sees on a record is the number leadership sees on the scorecard. No two versions of the truth to argue about in a meeting.
Root cause, not patches. When something comes back wrong, the historical data gets repaired and the live automation gets rebuilt so it can't recur.
No engineering time. No tickets, no sprint capacity, no dependency on your product roadmap. The whole system is built and shipped from outside it.
How the weeks run
What you own at the end
The system itself, in your accounts, on your tooling.
Documentation deep enough to change it. Not a user guide — the architecture and the workflow internals, so your team can extend it rather than only operate it.
A team that can run it without me. That's the deliverable. A system that only works while I'm still being paid isn't one.
A front-of-funnel rebuild that went live in three weeks and produced £25,000 a month in net new revenue. A retention and activation system that took £500k off the refund line. Both handed over documented; both still running without me.
Tell me where it hurts. I'll tell you what it takes.
Thirty minutes. No brief required. We'll work out where your customer lifecycle is losing money and whether it's a problem I can fix — and if it isn't a fit, I'll tell you inside the first ten minutes.