You have a CRM. Your team still runs the business out of spreadsheets.

One system to market, sell and serve your clients and the change work to make it stick.

Book a Revenue System Audit See what we build

Two weeks, $4,500 fixed, refunded if you say it wasn't worth it.

Built by Jack, ex-EY change and governance, and Seb Hodge, ex-HubSpot.

Our own HubSpot. This is the review screen Seicho runs on, with the client name removed. It is also the last thing we build for you.

You've said one of these out loud this quarter.

Three partners are talking to the same client and don't know it.
Cross-function visibility
We rolled it out. Nobody logs in anymore.
Adoption after go-live
The board wants AI. Our CRM data would poison it.
AI readiness

One system. One number. Everyone using it.

Right now sales quotes one figure, marketing reports another, and service holds a client history neither of them can see. We clean up the CRM your last provider gave up on, rebuild HubSpot around the way your firm actually wins and delivers work, and put all three teams on it with a named owner in every practice. The board pack stops coming out of a spreadsheet nobody else has seen. Your team owns the result, and nothing we leave behind needs us to keep running.

One source of truth

A CRM your team actually uses, because it briefs them before every meeting instead of nagging them for data entry.

Cross-practice visibility

Sales, marketing and service see the same client history, so no one finds out a deal existed after it's already closed.

Stack and integration audit

We map what's connected, what's duplicated, and what you're paying twice for, before we add anything new.

See how we build the system

Half of CRM projects fail. The software is rarely the part that broke.

Gartner has put CRM implementation failure at around 50 per cent and Forrester at around 47 per cent. Those numbers count the failures. They don't explain them. What we find in portals is consistent: the data underneath is wrong, nobody owns the change, and the team quietly stops logging in. The fix is unglamorous. Clean data, a process your team recognises, and one person accountable for making it stick. That is where we spend our time, long before AI enters the conversation.

Where a CRM or AI project's outcome comes from

10%
The AI itself
20%
Data and technology
70%
Process, people and adoption

Most teams buy the 10 per cent and skip the rest. We spend our time on the other 90. The proportions are indicative rather than measured. The ranking is the point.

AI made our build work faster. We gave the time back to your people.

Cleaning data, mapping fields, migrating records and wiring integrations used to eat the schedule. It doesn't anymore. We don't take that time back as an early finish. It goes into the part that decides whether the system survives: named owners, stakeholder workshops, training, and the reinforcement after go-live, when most providers have already moved on to the next project.

How we run the change side

ADKAR, tracked per team

We track Awareness, Desire, Knowledge, Ability and Reinforcement for every team the system touches, the same Prosci change model used in enterprise transformations, sized to a firm your size.

Agile delivery cadence

Short cycles, visible progress, and a working system your team can react to early, instead of a reveal at the end.

Led by someone who's done it

Jack ran change programmes at EY before this. Adoption is the part most builds skip and the part that decides whether yours survives.

See the full change methodology

AI with an audit trail.

AI gets the same terms as a new hire. It can propose. It can't decide. Nothing touches a client record without a person approving it and a log saying who.

01 · Suggest

AI proposes

The AI reads your calls, emails and records, then proposes a change: update this deal, brief this partner, fix this contact. It proposes. It doesn't act.

02 · Review

Your team approves

A named person on your team sees the suggestion, the reasoning, and the source. They approve it, edit it, or reject it. The decision is theirs, in one click.

03 · Apply

Change is logged

The approved change is applied and written to a permanent log: what changed, who approved it, when, and why. If anyone ever asks, you can show them.

See the full governance model

Before you commit to a build, spend two weeks.

Fixed fee · Two weeks · Under four hours of your team's time

In 14 days, you'll know exactly what your CRM is costing you.

Two weeks answering two questions. Where is the revenue, and can your system go and get it? We map your addressable market and build your ICP from your own won and lost work, then assess your data, your pipeline process, your stack, and your exposure if AI were switched on tomorrow.

TAM mapping and an ICP built from your own won and lost work
A scorecard across data, process, stack and AI readiness
A prioritised roadmap with a dollar impact against each item
A fixed price and a fixed scope for the build, if a build is warranted
A live readout with your leadership, delivered by both founders
A research agent and 3,000 Clay credits, in a workspace you own
Refunded in full at the readout if you don't think it was worth the fee

Fixed fee

$4,500

Proceed to a build within 30 days and the full audit fee comes off the price. Say at the readout that it wasn't worth it and we refund it. Either way you keep the findings.

Book a Revenue System Audit

Jack and Seb collaborate on every audit and deliver every readout together. Four a month. Nothing is payable on the first call.

Who this is for. And who it isn't.

We do one thing well, and we'd rather tell you upfront than waste your fortnight finding out.

A strong fit if you are

A professional services or manufacturing firm, roughly 30 to 300 people
Running HubSpot, or committed to moving onto it
Accountable to partners or a board that needs numbers they can trust
Under pressure to "do something with AI" and unwilling to do it carelessly

Not a fit if you want

Whole-of-business automation rather than a revenue system, at any size. Good operators do that work; we'll point you to one.
AI writing to your CRM unsupervised. We won't build it, on principle and on evidence.
A provider to run your systems for you forever. Your team owns everything we build.

Asked on almost every call.

Yes. We work with professional services and manufacturing firms of roughly 30 to 300 people running HubSpot. If you're outside that, or you want whole-of-business automation rather than a revenue system, we'll say so on the first call. We'd rather lose a sale than take on work we can't do well.
We publish named results with a number against them and the client's sign-off, or we publish nothing. Today there are no client results on our results page, and we'd rather show you an empty page than a vague one. What we can show you is the system we run our own firm on, the way we record your baseline before a build starts, and a live walkthrough of our own portal on the first call. The rule and the working are on our results page.
That's the part most implementations skip, and it's why most fail. The audit's process and adoption module maps who needs to change what before we touch a workflow. Jack ran change programmes at EY before this. Every build ships with a named owner and a system your team recognises, not just a database that's technically complete. If nobody's using it three months in, we haven't finished the job.
It stays in your HubSpot, in your accounts, under your access controls. We work inside your environment under NDA, we don't copy client records to our systems, and nothing you give us is used to train AI models. When an engagement ends, our access ends with it.
Everything. Workflows, integrations, prompts, configuration and documentation all live in your accounts and belong to you. If you parted ways with us tomorrow, the system keeps running. We're removable by design.
Because you should know the cost before you commit, not after. The Revenue System Audit is $4,500, takes two weeks, and the scope doesn't move. If you proceed to a build within 30 days, the audit fee comes off the build price.
Tell us at the readout and we refund the $4,500 that day. Say it on the call, or email him afterwards if you'd rather not raise it in the room. Same day, same outcome, no difference to us. You keep the scorecard, the written findings and the roadmap. No form, no conditions, nothing to prove. We run four audits a month and we'd rather lose one than have a firm paying us for a report it didn't need.
Because a free audit is sales collateral. It exists to produce a quote, so the finding is largely decided before the looking starts, and a proposal is what you keep at the end. Paying for this one means the findings are yours whether you build with us or not, it's run by the person who'd run your build, and it's allowed to conclude that you shouldn't spend anything yet. Proceed within 30 days and the $4,500 comes off the build anyway.
We don't quote a build off a website, because the honest answer depends on the state of your data and how many practices the system has to serve. The audit is what produces the number: a fixed price and a fixed scope for your build, put in front of you before you commit a dollar to it. Proceed within 30 days and the $4,500 audit fee comes off that price. For firms with several practices, we build the first end to end, then template and tune it across the others, so each additional practice costs and takes less than the first. After the build there is an optional monthly governance retainer, quoted then rather than now. It runs month to month and the build is designed to stand without it.
With numbers, not a pitch. The audit puts dollar impacts against the specific gaps in your pipeline, so the build is sized against the value it unlocks rather than a flat list of features. You go into the decision with a roadmap a CFO can read, the fixed price, and the audit fee already credited. If the impact doesn't justify the build, the audit will tell you that too, and you'll still keep the findings.
Not in anything we build for client records. Every change to a client record is proposed by the AI, reviewed by a named person on your team, approved, and logged. Low-risk housekeeping like formatting can be set to apply automatically, but you decide where that line sits, and it's documented.
The Revenue System Audit. Two weeks, $4,500 fixed fee, under four hours of your team's time. You receive TAM and ICP analysis, a scorecard, written findings, a live readout with your leadership, and a roadmap with dollar impacts. You also keep a research agent and 3,000 Clay credits in a workspace of your own. Whether you build with us or not, you keep all of it.
We build governed AI: a suggestion engine your team approves, not an autonomous agent acting unsupervised on your CRM. If you're comparing the two, we've written about exactly where the line sits.

Find out what your CRM is actually costing you.

Two weeks, $4,500 fixed, under four hours of your team's time, and refunded at the readout if you don't think it was worth it. The findings are yours either way.

Book a Revenue System Audit

It takes you to Jack's calendar. Nothing is payable on that call.