One record for every conversation
Email, texts, chat apps and call notes land in one record per customer or partner. Nobody hunts through five apps to find out what was promised.
Operations transformation
Run the business. Not the inbox.
We map how work really moves through your company, build the system it should run on -- CRM, project management, automation, AI follow-up and calling -- train your people on it, and then run it with you. The follow-up and the calls reach only people who agreed to be contacted, and every opt-out is honoured.
We built these tools while building several hundred call centers, hiring more than 10,000 people and managing them day to day. We saw the gaps, so we built what was missing.
Most companies don't have an AI problem. They have an operating problem that AI would have made faster and worse.
Delivery is senior-led, so we cap how many engagements run at once.
01 / The problem
Most companies run on memory, inboxes and four different apps.
- 01
The follow-up you promised two weeks ago is still sitting in an inbox.
It was nobody's job to chase it, so nobody did.
- 02
Five channels, no single record.
Email, texts, calls and chat apps -- and nowhere that shows the whole customer.
- 03
One person is the system.
When they are out, the work waits for them to come back.
- 04
Contracts get retyped by hand, from memory.
So the wrong terms go out, and somebody finds out later.
- 05
Monday's scorecard is a best guess.
Typed in by hand, from whatever somebody remembered.
- 06
You find out a process broke when a customer tells you.
Nothing was watching it, so the first alarm is a complaint.
-
None of that is an AI problem. Put a model on top of it and the wrong number just arrives sooner.
02 / What we build
One system, set up around how your team actually works.
The CRM and the project management platform, configured to your process, with the follow-up, the calling and the paperwork built in. Every text, email and call goes only to people who agreed to be contacted, and every opt-out is honoured.
Example Co. Customer · 3 conversations this week
Proposal sent - Email
Asked for the revised quote for three locations.
- Text
Confirmed the site visit for Thursday morning.
- Call note
Wants last year's contract terms carried over.
Drafted next message
Following up on the three-location quote: the revised numbers are attached, the site visit is set for Thursday, and last year's terms are carried over.
EditApprove and send
- Send the revised quoteSales lead · Wed
- Prepare the site visitOperations · Thu
- Carry over the contract termsAccount manager
Project management that writes itself
Meetings turn into tasks with a named owner and a date. The list stays true because nobody has to type it up afterwards.
Follow-up that never forgets
The system reads the history and drafts the next text or email, so open deals stay warm. It writes only to people who agreed to hear from you, and every opt-out is honoured.
AI calling inside the CRM
Calls run from a script built from each person's own notes, and the outcome lands back on the record. It calls only people who agreed to be contacted, and opt-outs are honoured.
Documents out in one click
Contracts and agreements go out with the right terms already on them, pulled from the record instead of retyped from memory.
One screen for the numbers
Revenue and conversion by channel, read from the system that holds them -- built against your baseline, so the change can be proven.
03 / How it works
Map. Build. Train. Run.
Four stages, in this order, with one team accountable for all four. Each one is built on the measurement the one before it took.
-
01
Map
We write down how the work really moves.
- We sit with the people who do the work -- often the one person who holds it all in their head.
- Every channel, every open deal, every rule run from memory, written down. AI cannot fix what is not written down.
- A baseline, a KPI dictionary and a process map.
- The opportunity in dollars, and a plain go or no-go.
Operating Diagnostic: $12,500, 3 weeks, credited in full
-
02
Build
The system it should run on, set up around how your team works.
- CRM and project management, configured to the process you mapped.
- Every conversation in one record, with drafted replies, AI follow-up and AI calling -- only to people who agreed to be contacted, with every opt-out honoured.
- Contracts and agreements out with the right terms on them.
- One screen for revenue and conversion by channel, built against the baseline.
$25,000-$40,000 for one workflow, or $75,000-$150,000 over 8-16 weeks
-
03
Train
Your people learn it on their own work.
- Training on live work, not on a demo account.
- Documentation for everyone who works alongside it: what it does, what it does not do, how to pause it, who to tell.
- A named owner with a view, a threshold, an alert and an escalation path.
-
04
Run
Then we run it with you.
- Monitoring and maintenance on every plan.
- On the larger plans: incident handling, agreed improvement hours every month and a monthly operating review.
- Benefits reported in four separate buckets, with our fees subtracted.
From $3,500 a month, rising with scope
04 / What you can hold us to
Commitments, in writing, before you call.
These are not results we are claiming. They are terms we work to, and each one is published on this site where you can check it.
- 01
Prices published before you call.
Every one of them is on the approach page. You can read what this costs without talking to anyone.
- 02
The diagnostic is credited in full.
$12,500 comes off the implementation if you go further.
- 03
If it does not clear 3-to-1, we say so and stop.
The work has to be worth about three times what it costs. If the diagnostic says it is not, we do not sell you the build.
- 04
Four buckets, fees subtracted.
Contribution profit, cash costs removed, capacity in hours, cash timing in days. Never one blended headline number.
- 05
The five deliverables are yours to keep.
Baseline, KPI dictionary, process map, quantified opportunity and the go or no-go -- whether or not you continue.
- 06
Senior-led, and capped.
We limit how many engagements run at once, so the people who map your process are the people who build it.
- 07
Your name stays private.
We publish no client identity or result without that client's written permission.
05 / Pricing
Three prices, published before you call.
Map Start here
Operating Diagnostic
$12,500
- A baseline
- A KPI dictionary
- A process map
- A quantified opportunity
- A plain go or no-go
Yours to keep, whether or not you continue.
Request a 25-minute callBuild
Implementation
- Single-Workflow Implementation
- $25,000-$40,000 One workflow, end to end
- Foundation & Deployment
- $75,000-$150,000 8-16 weeks, one or two workflow families
Built against the baseline from the diagnostic, so the change can be proven.
Run
Managed operations
From$3,500/mo
| Lite | $3,500-$6,000/mo |
|---|---|
| Essential | $10,000/mo |
| Growth | $20,000/mo |
| Transformation | $30,000/mo+ |
06 / Fit
Who this is for, and who it isn't.
Built for
- 15 to 20 or more people in process roles, or leakage of about the same size. Count the work, not the revenue: repetition is what pays for this.
- A core range of $15M to $40M and up, with heavy transaction volume.
- Under that? There is a smaller ladder, and we will tell you on the first call, using your numbers, which one fits -- or that neither does.
Not for
- Work that is bespoke every time. The value comes from repetition and volume.
- A small team doing repeat process work. The arithmetic does not clear.
- A chatbot demo by Friday. The first month is reconciliation. We say so early; it costs you one call instead of one quarter.
07 / Published work
The method is on this site, in full.
How we grade the evidence we cite
Every external claim on this site is graded before we use it. The strongest external support for sequencing foundations before automation is McKinsey's 2025 state-of-AI survey, which found workflow redesign had the strongest association with reported generative-AI EBIT impact among the 25 organisational attributes it studied.
It is observational and self-reported. It is not causal, and it is not a study of the US mid-market. It is consistent with the argument; it is not proof of it. We write the grade next to the citation rather than let the source do work it cannot do. Every other external claim we make is graded the same way on the claims register.
Guides
- Why AI Can't Fix a Process Nobody Owns The arithmetic we run before anyone builds anything, worked end to end with numbers you can re-run on your own business -- and why the answer is sometimes no.
- The Operating Baseline: financial, customer and workflow visibility What a baseline actually contains, why three kinds of visibility are needed rather than one, and how to test the baseline you already have in an afternoon.
08 / Questions
Four questions we hear first.
How long does it take?
The Operating Diagnostic takes 3 weeks. Foundation and Deployment runs 8 to 16 weeks; a single workflow is a smaller piece of work. Running it is monthly, for as long as it is useful to you.
What if the numbers say no?
Then we say so and we stop. An implementation has to clear a 3-to-1 return before we will propose it. If it does not, you keep the five deliverables and we do not sell you the build.
Do you record my staff?
No continuous recording, and no background microphones. We start with the timestamps your systems already write. Watching the work in person is optional, and scoped with you in advance.
What does it cost?
The diagnostic is $12,500, credited in full. Implementation is $25,000 to $40,000 for one workflow, or $75,000 to $150,000 for Foundation and Deployment. Running it starts at $3,500 a month. Every price is on the approach page.
Start with the bottleneck, not the tool
Pick the thing your team does most often by hand. We will ask six questions about it on the phone -- starting with how many, how long each, and who does them -- and do the arithmetic out loud. Twenty-five minutes. It is a small multiplication, and almost nobody sits down and does it. Sometimes it says don't bother, and we will tell you that too.