They know slightly more about their customers than you do. Nothing visible. Nothing you'd act on.
Vancouver · 3 open Q3
Fractional AI Team · Service Businesses
Self-learning AI systems that get smarter with every interaction.
Creating a simple product (platform, catalog, ordering app) is pointless: they'll code a copy in a month.
Only a service built from a million small solutions, which take a long time to accumulate and are impossible to replicate, can protect you.
50+
Clients
762
Workflows redesigned & automated
1.5M
Hours of manual work saved
Straight to the founder
Learn more about self-learning AI systems in your business
A working session with the founder to review how self-learning AI systems can grow your business — where they would fit, what they would learn first, and which number should move.
You're probably one of two people
02 / 14Diagnosis
The problem has a name.
Your process forgets.
Every day your business makes thousands of small decisions. Which client to call. What to offer them. What tone to use. When to push and when to wait.
Almost none of them are written anywhere. They live in people. When the person leaves, the decision leaves with them. When the person is busy, the decision gets made badly. And next year the company repeats this year's mistake, because nothing recorded that it was a mistake.
You don't have a technology problem. You have a memory problem.
And no — the pilot didn't fail because you picked wrong.
Bolt an assistant onto a process that forgets and you get a process that forgets faster. IT has a name for that: paving the cowpath. Smoother road. Same swamp.
70%
of what makes AI work is people and process. 10% is the algorithm
BCG · 10-20-70 rule · 2024
74%
of companies have yet to show tangible value from AI
BCG · AI Adoption · 2024
95%
of enterprise GenAI pilots produced no measurable P&L impact
MIT NANDA · 2025
Illustrative scenario · a composite mid-market firm / HVAC Service
The eight years that walked out in March
Without the system
Marisa ran the Harbor Point account for eight years. She knew Ray never approved anything on a Friday. She knew Building 4's chiller wanted a look two weeks before the first heat wave, not after. She knew Ray hated being upsold and would say yes to a quote he had asked for himself.
In March she left. Tyler inherited her inbox and a folder of notes, and sent Harbor Point the spring maintenance promo. Ray read it and didn't reply.
Six weeks later Harbor Point was trialling another mechanical contractor.
With the system
Marisa leaves and nothing resets.
Two weeks before the heat wave Ray gets a message in the thread he already uses: "Building 4 chiller — same pre-season check as the last two Mays? Tuesday or Thursday." He replies with one word. He may not even know Marisa is gone.
Three things made that message possible: the account's rhythm, the rules for this type of customer, and the tone that works with Ray. None of them lived in Marisa's head any more.
30 min · with the founder · no pitch
03 / 14What it costs
Here's the part that doesn't show up until it's too late.
A competitor who rebuilt their process isn't beating you by 15%. They're beating you by an amount that grows.
Month 01
Month 12
They know which of your customers are about to leave — before your account manager notices.
Month 24
You can't hire your way back. There is no person to hire who has sat inside four hundred customer relationships at once.
Price can be matched in a week. Two years of accumulated decisions can't be matched at all.
Which is the good news. Build the thing that accumulates, and you become the one nobody catches.
Illustrative scenario · a composite mid-market firm / Freight & 3PL
The brokerage that quoted six points under you
Without the system
A new brokerage opens across town, hires two of your agents, and quotes six points under your rates. Same TMS. Same load boards. Same carrier network — literally the same carriers.
Your shippers start splitting freight "just to compare."
On paper you have nothing they don't have.
With the system
You have three years of decisions they cannot buy.
Which carriers actually show up on the Laredo lane in July. Which shippers accept a rate increase in Q1 and which one cancels over it. Which loads go bad in the first four hours, and what to do in hour two instead of hour nine.
They can quote under you this month. They cannot quote under three years of knowing which carrier will strand a load on I-40. And every month you run, the gap widens.
30 min · with the founder · no pitch
04 / 14The mechanism
Not faster.
Smarter.
Faster is what software has been selling you for thirty years. Smarter is new, and it fits in two loops.
Loop one runs in seconds
The system acts, the customer reacts, the reaction is captured as signal. The next contact is better aimed than the last one.
Loop two runs in days
One person — the owner of the process — sees what worked across every customer at once, changes the rule, and ships it.
Loop one makes it better with one customer. Loop two makes it better with all of them.
Most AI projects build the first loop and stop there. The second one is where the compounding lives.
Illustrative scenario · a composite mid-market firm / Lead Generation
The opener that stopped being sent on Thursdays
Loop one · seconds
A message goes to an operations director at a regional carrier. Opened twice. No reply.
Signal recorded: for this profile, a value-proposition opener doesn't land.
The next attempt at the same profile opens with one concrete detail about their own operation instead. Reply in fifty minutes.
Loop two · days
Friday review across 340 sends. Generic openers: 3% replies. Openers naming one specific operational fact: 11%.
And a second pattern nobody had looked for — replies triple when the message lands Tuesday between 7 and 9am local, and collapse Thursday afternoon.
Two rules change. Next month: 4% to 12% — and the meetings that book are better qualified, because a specific opener filters out the people who were never going to buy.
30 min · with the founder · no pitch
05 / 14The obvious question
"Why not just buy an agent that already learns?"
Buy one. For the box it covers, a good product will beat anything we'd build for you — and we'll tell you so on the call.
But look at what it learns, and where that learning lives. It learns inside its own box: support conversations, or scheduling, or intake. It doesn't learn how your quoting connects to your dispatch, or why one account renews and its twin doesn't.
A bought flywheel isn't a moat. It's a subscription — and so is theirs.Every competitor buying the same product gets the same learning
We build the loop that runs across the process you actually compete on, and it belongs to you. Usually alongside the products, not instead of them.
Illustrative scenario · a composite mid-market firm / Healthcare
The booking agent that filled every slot
Without the system
Nine clinics buy a scheduling agent. It answers calls, offers slots, books them. Booking rate climbs immediately and the report looks excellent.
Then no-shows climb too. One provider's Thursday block runs forty minutes over every week and the agent keeps filling it. Patients who need pre-authorization get booked and turned away at the desk. Same-day urgent has nowhere to go, because every slot is already full.
With the system
The product was good at booking. It could not learn what the front desk knows.
Which provider runs long and by how much. Which payer needs pre-auth before a slot is offered. Which patients come only after a second reminder. How many same-day slots to hold back on a Monday in February.
Keep the scheduler. Then build the loop that learns your clinics — otherwise you've automated the booking and kept the no-shows.
30 min · with the founder · no pitch
06 / 14For whoever gets blamed when it breaks
You know the pattern. This time you get the machine room.
An outside team promises your CEO something, you inherit an unaccountable black box, and you own the incident review. Here's what we hand you instead.
Gear 01
Knowledge base
Facts, rules, examples. Versioned. A knowledge base nobody has touched in three months is more dangerous than none — it manufactures confidence.
Gear 02
Autonomy ladder
L1 to L5, assigned per decision type, not per process. Rules in three layers: red lines, guardrails, guidance.
Gear 03
Decision memory
Input, alternatives, decision, rationale, confidence, outcome. Skip the outcome field and your log is an archive, not a flywheel.
Gear 04
Eval gate
Accuracy, safety and regression suites run before any rule or knowledge change ships. Nothing reaches a customer untested.
Gear 05
Metrics + counter-metrics
Every metric carries its counterweight. Intervention rate against decision quality. Order value against churn.
Why the counterweight
Klarna reported $40M saved on automated support, every dashboard green, then brought people back: nothing measured quality on the hard cases.
A metric without a counterweight lies.Level
The system
Your people
L1 · Assistant
Suggests options
Decide everything
L2 · Advisor
Prepares the decision with its reasoning
Approve each one
L3 · Co-pilot
Handles the standard cases
Review in batches, take the exceptions
L4 · Supervised
Acts alone inside normal conditions
Watch metrics, step in on anomalies
L5 · Autonomous
Acts alone, including the odd cases
Design the rules and the red lines
Illustrative scenario · a composite mid-market firm / Auto Dealership
The upsell rule that cost two loyal customers
Without the system
The service BDC adds one rule: recommend the premium maintenance package on every visit. Reasonable — the margin is good and the pitch is scripted.
Two weeks later the customers who have come every 5,000 miles for six years and want exactly the oil change start getting pitched. One stops responding. One leaves a two-star review saying they feel like a target.
Nobody connects either one to the rule change.
With the system
Every rule change runs the suite before it ships. Twenty scenarios, ten of them hard.
One is "loyal customer, six years, same service, never bought an add-on," and the correct answer is "confirm the usual, offer the earliest slot."
The change fails that test. It doesn't ship until the rule reads: pitch premium only where there's a history of accepting add-ons, or a real inspection finding. The two-star review never gets written.
30 min · with the founder · no pitch
07 / 14How it reaches production
Every stage has its stop signal defined before it starts.
Stage 01 · 2 weeks
Shadow
The system works in parallel and sends nothing. We measure agreement with your people — a clean read, because nobody is anchored to a suggestion.
Stop if agreement < 80%
Stage 02 · 2 weeks
Canary
Five to ten percent of volume runs at the new level. Small enough to be safe, large enough to be real.
Stop if canary trails control
Stage 03 · 4–8 weeks
Gradual
Ten, twenty-five, fifty, one hundred percent. Metrics checked at every step before the next one opens.
Stop on any metric out of band
Stage 04 · 2 weeks
Full
Everything at the new level, with heightened monitoring and a daily read instead of a weekly one.
Stop on anomaly in the daily summary
Rollback is a routine operation, not an incident
Roll back the segment, not the process. Record the cause — "something went wrong" is not a cause. Set a retry date, because a rollback without one quietly becomes a permanent downgrade.
Teams that are afraid to roll back get stuck at low autonomy. Teams that roll back easily move faster.
Illustrative scenario · a composite mid-market firm / Insurance
The nine days that saved the renewal book
Without the system
Month five. Autonomy is raised across the book — renewal packets now go out without a producer approving each one.
Two weeks later, three of the largest accounts have gone silent. It surfaces at the quarterly review.
The room concludes that AI doesn't work in a regulated business. The project is shelved and the budget moves somewhere safer.
With the system
Same decision, caught in nine days by intervention rate and response rate — not by a lost account.
Cause written down, not guessed: accounts above $250K premium expect the producer's own framing and a coverage-change summary up front. The system was sending the standard packet, because the knowledge base didn't carry that distinction.
Large accounts drop one level. Mid and small stay where they are. Three weeks to add the rules, re-run the tests, raise again. Metrics hold. Nothing was shelved.
30 min · with the founder · no pitch
08 / 14Deploy or reshape
Three questions.
Answer them honestly.
Nobody sees your answers. They stay in this browser.
Question 01 · Roles
Six months after your last AI project, did anyone's job description actually change?
If your people do the same work faster, nothing was rebuilt.
Question 02 · Data
Does the process now produce data that didn't exist before?
Decisions with reasons attached, outcomes, rules learned from experience. If not, nothing is accumulating.
Question 03 · Route
Can the system carry a customer through without a human at every step?
If a person is a mandatory relay, you bought an assistant, not a system.
Illustrative scenario · a composite mid-market firm / Accounting
The firm that bought a faster pen
Without the system
Licenses bought. A lunch-and-learn delivered. The partners are told AI is adopted.
Six months later, open any job description — unchanged. Ask what data the process produces that it didn't before — none, the same fields. Ask whether a client can be carried through document chase without a person at every step — no, every email still waits on someone to press send.
Staff use it to polish emails. Realization rate flat. Same March, same all-nighters.
With the system
Six months in, the senior associate's description reads differently: they design the rules for intake and document chase, they don't write each chase email.
The process produces something new — a log of what was requested, why this client got that wording, and whether the documents actually arrived.
Routine chase runs without a person; associates take the exceptions. Three yeses. Realization moves because the chase stopped depending on who remembered.
30 min · with the founder · no pitch
09 / 14What we talk you out of
Most of your processes should be left alone.
Roughly 15–20% of the processes in a company are worth rebuilding this way: the ones that run often, touch revenue or the customer, and hand work between people or systems. The rest need basic automation and no ceremony.
Gate 01
Tied to a number
Not "will get more efficient" — which metric moves, and by how much. If you can't name it, the process isn't ready.
Gate 02
Data to start from
Not clean. Not complete. Existing. If there is no history anywhere and none can be captured, it's too early.
Gate 03
You can act on the output
If the system recommends and nobody downstream can execute, it's theatre. This is the gate most pilots quietly fail.
We'll tell you which of yours clear them — including when the honest answer is "none of them, not yet." We've said it before. It costs us a project and saves you a year.
Illustrative scenario · a composite mid-market firm / B2B SaaS
Three candidates. Two got a no in week one.
The two we turned down
QA regression triage. Clean data, obvious candidate, engineering wants it. But it moves no number the board tracks. Fails gate one — tied to a metric. Basic automation, no ceremony.
Roadmap prioritization from customer feedback. Sounds smart in a strategy deck. Then ask what happens when it surfaces a priority: product decides by conviction and quarterly politics, not by a queue. The recommendation has nowhere to land. Fails gate three.
The one we built
Renewal and expansion across 900 accounts. High volume, direct line to net revenue retention, real turnover among CSMs, usage and ticket history already exist, and CSMs contact accounts weekly — so a recommendation has somewhere to go.
Three gates cleared. This one gets built.
The honest part: two of three got a no in week one, and that's why the third one shipped.
30 min · with the founder · no pitch
10 / 14What changes for your team
Someone has to own the loop.
The process owner doesn't write the messages. They design the rules the system works by, set the red lines, read the weekly summary, and answer for the metrics. Architect, not bricklayer. It's usually your best operator, and it's a promotion.
Most of the team moves to working inside the rebuilt process: handling what the system escalates, judging the edge cases that need judgement.
And the knowledge stops leaving with people. When your next best operator resigns, their judgement is already in the system — as rules, as examples, as a decision log with reasons attached.
Not a knowledge-management project. A by-product of the loop running.
Living SOPs, not an SOP written once for the audit.
Illustrative scenario · a composite mid-market firm / Distribution
The manager who blocked it for three months
Without the system
Gus has run the warehouse for twelve years. Asked to pilot there, he agrees in principle — the data needs cleaning first, Q3 is peak season, let's revisit after the new year, and we'd need to align with suppliers.
Every objection is reasonable. Together they are an infinite runway.
Gus isn't against AI. He's against losing the three things his standing rests on: he knows how the warehouse really runs, he assigns the work, and he controls quality by being there.
With the system
Nobody argues with him. He gets four guarantees instead. While it runs in trial, dips in warehouse metrics don't count against him. It works beside his people, not instead of them. The stop button is his, no approval needed. And a bad call is a knowledge-base problem to fix together, not his mistake.
Then one small task inside his own territory: the two hours his team burns every Monday guessing next week's demand.
Month two, Gus comes back with his own idea. "What if it watched stock levels too? I know the rules it would need." By month four he owns the process. Same person. Different seat.
30 min · with the founder · no pitch
11 / 14How we work
First we draw the plan.
Then we build to it.
01 · 1–2 weeks · fixed fee
Diagnose
Which processes clear the three gates, what the loop would look like, what number moves and by when. You own the output whether or not we build it.
02 · 8–12 weeks · time & materials
Build
Knowledge base, autonomy ladder, decision memory, eval suite, metrics. Shadow to canary to gradual to full. First loop turning inside the first month.
03 · ongoing
Run
Someone has to turn the slow loop every week. Either we train your process owner to do it, or we do it with them until they can.
Build runs on time & materials, not a fixed price. A process that learns doesn't have a fixed scope — pretending otherwise means one of us is guessing, and it's usually you who pays for the guess.
12 / 14Who you'd be working with
I've been on your side of this table.
I'm Den. I built a services company from a handful of people to about 65, roughly doubling it every year for four years.
I know precisely what it feels like when the business only works because four people remember things — and what it costs the week one of them leaves.
762
Workflows redesigned & automated
50+
Clients across service businesses
1.5M
Hours of manual work saved
That's our own million small decisions — and the reason we can look at one of your processes and tell you in 45 minutes where the memory is leaking.
13 / 14Where this goes next
Pick one process.
We'll take it apart with you.
Bring the process that breaks when the wrong person is away. Thirty minutes, with the founder, not a salesperson.
You leave with
01
Where the decisions inside that process actually live today
02
What it would take for the process to remember them
03
The number that should move, and roughly by when
04
An honest read on whether it's worth rebuilding at all
No deck. No proposal unless you ask for one. If it isn't a fit, I'll say so in the same thirty minutes.
Straight to the founder
Learn more about self-learning AI systems in your business
A working session with the founder to review how self-learning AI systems can grow your business — where they would fit, what they would learn first, and which number should move.