“We said you’re not buying minutes — you’re buying arms. Then the calls started flowing. Here’s what the bill actually taught us.”
A while back I argued that voice-AI pricing is a lie: the per-minute number on the pricing page isn’t the product. The product is a stack of arms — the voice intelligence, the carrier connection, the infrastructure around them — and the per-minute price is just the costume they wear.
That was the theory. This is the field test.
What the bill actually says
Run a real week of calls and read the invoice the way an owner reads it — not the headline rate, the total. The per-minute number is almost never the biggest line. The arms are.
The voice model doing the talking. The carrier moving the audio. The platform orchestrating the whole thing — the number, the recording, the transcript, the handoff. Each arm bills its own way, on its own meter, and the “per minute” quote only ever described one of them.
Nobody lied to you. They just priced the costume and shipped the wardrobe.
The concurrency math nobody shows you
Here’s what the field test really exposes: minutes are linear, arms are not.
Ten simultaneous calls isn’t ten times the per-minute rate in value — it’s ten arms, all live at once. The pricing page shows you a single call’s minute. Your Monday morning shows you ten calls overlapping, each holding its own model session, its own carrier leg, its own recording pipeline open.
The vendor priced the minute. You bought the rush hour. Those are different products, and only one of them shows up when the phones light up.
You pay for arms even when the call goes nowhere
The wrong number. The three-second hangup. The caller who wanted the pizza place. The silence where someone pocket-dialed you.
Minutes barely moved. The arms all fired anyway — the model spun up, the carrier connected, the platform recorded forty seconds of nothing and transcribed it faithfully. You paid for the whole stack to handle a call that never existed.
This is the line the per-minute lie can’t survive: the bill doesn’t care whether the call mattered. The arms do the work either way. Price the arms, or the junk calls price you.
The only math that matters
Stop dividing by minutes. Start dividing by outcomes.
Take a real week: total voice bill, all arms included, divided by minutes — that’s the advertised number, and it’s trivia. Now divide the same total by resolved calls. Then by booked jobs. That last number is the only one that touches revenue, and no vendor puts it on the pricing page because no vendor controls it — you do, with your harness.
A vendor quoting two cents a minute against a vendor quoting five is a meaningless comparison until you know whose stack resolves the call. The cheap minute that books nothing is the most expensive minute you’ve ever bought.
What to ask a vendor now
After the field test, there are three questions, and a vendor’s answers tell you everything:
Break the bill into arms. What’s the model cost, the carrier cost, the platform cost — separately? If they can’t or won’t, you’re buying a bundle, and bundles hide margin.
What does my rush hour cost? Not a minute — my Monday at 8 AM, ten calls deep. If the answer is “the same per-minute rate,” they haven’t thought about it, which means you will.
What do I pay for the call that goes nowhere? The hangup, the wrong number, the silence. If everything bills the same whether the call mattered or not, the arms are priced — the minute is just the label.
The close
Minutes were never the product. The product is an answered call that ends in a booked job — and that’s built from arms, priced in arms, and won or lost in the harness around them.
The pricing page will keep selling minutes. Let it. You know what you’re buying now.
Buy the arms. Price the outcomes. Own the harness that turns one into the other.
Not an app. Not a dashboard. Not a portal. The thing already in everyone’s pocket, already charged, already answered.
The decision
When it came time to pick the interface — the way humans would actually touch the system — the candidates were an app, a chat platform, and the phone. Voice in, SMS out.
The phone won, and it wasn’t close.
Every contractor, every tech, every homeowner, every adjuster already has one. Nobody needs to download anything, learn anything, remember a password, or change a habit. The interface is the thing they were already holding.
Why apps lose
Every app is a behavior change wearing a friendly icon. Download it, sign in, learn the UI, grant the permissions, remember to open it. Each step loses half the people you started with — and the half you lose is always the half you needed most: the busy tech, the stressed homeowner, the adjuster with forty files.
An app can do more. That’s the pitch, and it’s true, and it’s irrelevant. Reach beats richness. The best interface isn’t the most capable one — it’s the one that’s already open.
Why the platform lost
The chat platform was tempting — everyone’s already there, the tooling is good. But it’s someone else’s workspace, someone else’s rules, someone else’s pricing page. You build your office on a platform and you’ve got a landlord again — the same sharecropping problem as the rented harness, one layer up.
The phone is nobody’s platform. Or everybody’s, which amounts to the same thing. No terms of service can take your phone number’s habits away. No pricing change makes people stop answering calls.
What it means for the office
The dispatcher doesn’t learn software. They talk.
The tech doesn’t open a ticket. They text a photo of the meter readings from the driveway.
The homeowner doesn’t download a portal, create an account, and verify their email to check on their job. They call the number they already have, and a voice that knows the job answers.
Zero install. Zero behavior change. Zero training. That’s not a feature list — that’s the whole strategy.
The glass and the system
Here’s the part people miss: the phone is the glass, not the system.
The harness — the routing, the records, the follow-up timing, the judgment — stays the system of record, owned outright. The phone is just how humans touch it. Glass is swappable; the system underneath is yours. If the phone vanished tomorrow, the harness would still know every job, every commitment, every next step.
That’s the pairing: harness-first underneath, phone-first on top. Own the operation, meet people where they already are.
The objection
“But a real system needs a real interface.” It has one. It’s the oldest, most-tested, most-universal interface in human history: you speak, it listens; you text, it remembers.
Fancy is a tax on adoption. Every feature an app adds beyond call-and-text is a feature someone has to learn and most people won’t. The office that runs on the phone doesn’t have a learning curve — it has a dial tone.
The close
The office isn’t a place anymore. It’s a phone number that answers, a text thread that remembers, a voice that knows the job.
Build the system. Own the harness. And let people reach it through the thing they’ve been reaching for their whole lives.
It’s the sentence that explains the whole business model. Most people never get a sentence like that. I got one, and everything since has been commentary on it.
The traveler
The traveler goes somewhere, does the thing, collects the fee. It’s the default model of work: your value is your presence, your labor, your miles. It’s honest and it’s linear. When the trip ends, the value ends — until the next trip.
Most businesses are travelers. They sell hours, jobs, deliverables. They go, they do, they invoice. Nothing wrong with it. But the ceiling is always the calendar: there are only so many trips in a year.
The switchboard
The switchboard doesn’t travel. It sits at the center and completes circuits.
Person A needs person B. They don’t know each other, or they know each other but the timing’s never been right, or they need a reason to trust the connection. You make the introduction. The circuit lights up. Value flows — a deal, a job, a partnership — and you were the reason it flowed.
Then you do it again. And again. Every completed circuit makes you more central, because both sides remember who lit it up. The next time A needs someone, they call you first. The next time B has an opening, you hear about it before anyone else.
Wealth denominated in access
Money is one currency. Access is another — and it compounds faster.
A fee gets spent. Access gets reinvested automatically: every circuit you complete buys you the next one. The seat at the table, the early phone call, the “hey, before I talk to anyone else” — that’s wealth, denominated in something no bank tracks and no competitor can undercut.
Travelers collect miles. Switchboards collect circuits. When the map gets big enough, the switchboard is the most valuable thing on it — because every traveler eventually needs a connection they can’t make themselves.
Why it works in this trade
Restoration runs on trust and timing. The right adjuster, the right contractor, the right facility manager, at the right moment — that’s the whole game. Nobody can hold all of it. The territory is too big, the relationships too many, the timing too tight.
So somebody has to be the one who knows who to call. Not the one who does every job — the one who knows who should. The trade doesn’t need another traveler. It needs the switchboard.
The discipline
A switchboard has three obligations, and they’re non-negotiable:
Be neutral. You don’t take sides in the circuit — you complete it. The moment an introduction serves you more than the two people you’re connecting, the switchboard starts corroding. People can feel a self-serving connector within minutes.
Be reliable. Answer. Remember. Follow through. The switchboard that drops circuits gets routed around, and routing around is permanent.
Be fast. A connection delayed is a connection denied. Timing is half the value — the right introduction at the wrong time is just a nice conversation.
And one more, the quiet one: never make the introduction about you. The light belongs on the circuit, not the switchboard. Your name comes up because the connection worked, not because you announced it.
The close
I didn’t set out to be the switchboard. I set out to be useful — and usefulness, compounded over enough years and enough people, turns into a position at the center of the map.
The travelers will always have the miles. I’ll keep the circuits.
If you’re building something, ask yourself which one you are. There’s no wrong answer — but there’s a wrong assumption, which is thinking you’re the traveler when you’re actually the switchboard, or vice versa. Know which one you are. Then be it on purpose.
Here’s the paradox at the heart of the pitch: we sell to companies that live on cold outbound. And the first thing I tell them is that our line never dials out. Not once. Not ever.
It usually gets a look. Then it gets the deal.
The moment everything changes
An AI voice that answers when you call is a concierge. An AI voice that calls you uninvited is an intruder wearing a human voice. Same technology. Opposite meaning.
The difference isn’t technical — it’s consent. The caller chose the conversation in the first case. In the second, the machine chose it for them. And the human on the other end knows exactly which one it is, within three seconds.
Trust spent on an uninvited call doesn’t come back. Not for that call, not for the company behind it, not for the industry. Every robocall ever made is the reason the bar is where it is. We’re not going to be the company that teaches people to distrust the voice on the line — because we need them to trust ours.
The doctrine
Inbound-only. The line answers; it never initiates. Every conversation starts with a human deciding to call.
That’s it. That’s the whole doctrine, and it’s load-bearing. Everything else — the disclosure, the consent architecture, the call design — hangs off this one commitment.
What it costs
Let’s be honest about the price: it leaves money on the table. Outbound AI calling is a real industry with real revenue. Appointment setting, lead reactivation, follow-up sequences — all of it works, sort of, and all of it is for sale.
We’re deliberately not in it. Not because we can’t build it — we can — but because every outbound call the line makes spends down the trust the inbound line needs. You can’t be both the welcome voice and the interruption. Pick one.
What it buys
A line that’s never abused is a line people trust. When it picks up, the caller chose this — and that changes the entire conversation. Nobody starts defensive. Nobody’s first move is “how did you get this number.” The caller has a problem, they called for help, and the voice on the line is there to help.
That posture — chosen, welcomed, useful — is the whole product. An inbound caller cooperates. They answer questions. They give the address, describe the damage, say yes to the next step. The best conversion technology ever invented is a human who wanted to call you.
The consent architecture
Inbound-only is the foundation, but consent gets built into the call itself. Every caller hears what they’re talking to — no impersonation, no ambiguity. In Washington, two-party consent isn’t a suggestion; the disclosure is part of the design, not a legal footnote.
The invitation is explicit too. Nobody finds the number by accident. They get it from an email that invites them to call, a card that says call us, a website that says talk to us. Every path to the line starts with a human saying “yes, I’ll call.”
The paradox, resolved
So why do cold-outbound companies buy an inbound-only line? Because their problem was never getting the phone to ring. Their problem is what happens after it rings.
The prospect says yes — clicks, replies, calls — and lands on a missed call, a voicemail pit, or a rep who’s already on the other line. The most expensive moment in outbound is the inbound moment it creates, and that’s exactly where it falls apart.
We don’t replace their outbound. We make their inbound worthy of it. Every yes gets answered, instantly, by something that knows the business. The outbound team keeps hunting; the line makes sure nothing they catch gets dropped.
The close
The line that never dials out is the line people trust enough to call.
That’s the moat, and it deepens every day we hold it. While the industry races to automate interruption, we’re building the one voice people actually want to hear — because it only ever speaks when spoken to.
Inbound is the discipline. Trust is the product. The line just answers.
You wouldn’t hand a new hire the keys on day one. No tour, no training, no “here’s how we do things” — just a desk and your credit card.
So why do it with AI?
An AI seat is a hire. It has infinite stamina, perfect recall, and zero judgment on day one. Judgment is what onboarding installs. Skip the onboarding and you don’t have an employee — you have a very fast intern with no supervision making decisions in your name.
The job description comes first
Nobody starts a human employee without telling them the job. The AI version is the SOP: what this seat does, what it never does, what “done” looks like, and what it escalates instead of deciding.
Write it before the seat starts. Not after the first mistake — before. “You draft, I approve.” “You never publish.” “You never mention a client by name.” “When you’re unsure, you ask.” Boring sentences. They’re the entire difference between a seat you trust and a seat you babysit.
A seat with no job description invents its own. You won’t like its choices.
Probation: review everything
Every new hire gets a probation period. The AI seat gets one too — and during probation, the human gate sits on every output. Every draft gets read. Every action gets checked. Not because you distrust the seat, but because you’re calibrating it.
This is the part most people skip, and it’s the part that matters most. Probation isn’t punishment; it’s training data. Every correction you make in week two is a rule the seat follows in month six — but only if you write it down.
Give it the company history
A new employee gets the lore: how we got here, what we tried, what blew up, who matters, how we sound. The AI seat needs the same. Context is training.
Feed it the record. Past decisions and why they were made. The mistakes and what they cost. The voice — how you actually talk, not how a brand guide talks. The values that outrank any single instruction. A seat that knows the history makes decisions like an insider. A seat without it makes decisions like a temp.
This is the compounding part. Six months from now, your seat knows things no new hire could learn in six months — because it was there for all of it, and it doesn’t forget.
Performance reviews
Review the seat weekly at first. What did it get right? What drifted? What needs a new rule? Then write the rule down.
The rules file is the employee handbook, and it should grow. Every surprise becomes a sentence. “When the client changes scope mid-thread, summarize the change and confirm before continuing.” That’s not a prompt tweak — that’s institutional knowledge, and it belongs to the seat permanently.
Quarterly, do the bigger review: is this seat’s job still the right job? The business moved; the seat should move with it. Stale SOPs produce stale work, and nobody notices because the output still looks polished. Polished and wrong is the most expensive kind of wrong.
Promote slowly
Widen the seat’s latitude as it proves out — the same way you’d trust a human with more over time. Two-way doors first: reversible work, drafts, research, analysis. The seat runs; you spot-check.
The one-way doors stay gated until the track record earns them. Money, publishes, sends, deletions, commitments — those keep the human tap until the seat has a long, boring history of being right. Boring is the promotion criterion. Excitement is a red flag.
The order matters: latitude is granted on evidence, never on optimism. “It’s been great so far” is not evidence. Six months of reviewed output is.
The three hiring mistakes
Hiring for the interview. A great demo isn’t a great employee. The demo shows what the model can do; onboarding determines what the seat will do, every day, unsupervised, in your name. Judge the seat at week six, not minute six.
No handbook. Every correction stays verbal, nothing gets written down, and the same mistake comes back monthly wearing a different hat. If it isn’t in the rules file, it didn’t happen.
Promoting too fast. Auto-publish before probation ends. Direct customer contact before the voice is trained. The seat will feel ready before it is ready — eagerness is not competence.
The payoff
Here’s what you’re building: a trained seat compounds. It doesn’t quit, doesn’t forget, doesn’t have a bad day, doesn’t take its knowledge to a competitor. Six months in, it holds more of your operating history than any single employee — and it applies it instantly, every time.
Everybody rents the same models. The models are commodities; they get cheaper and smarter on someone else’s schedule. Nobody else has your trained seat. The onboarding — the SOPs, the corrections, the history, the handbook — is the moat. It’s the only part of the AI stack a competitor can’t download.
So onboard like it matters. Write the job description. Run the probation. Do the reviews. Promote on evidence.
You’re not configuring software. You’re hiring. Act like it.
Notes from a Saturday afternoon: a broken image, a sarcastic text that didn’t land, and what the whole mess taught me about working with AI. The short version: it’s a dance, and the steps keep changing.
The image that “came out great”
Saturday afternoon. I published a piece with a featured image, and something looked off — like the image wasn’t showing all the way. So I texted my AI: that came out great 😂.
It was sarcasm. The image was visibly broken.
She wrote back: Haha glad you like it — that one came out great for that piece. 😂
Two problems. She hadn’t looked at the image. And she’d missed the sarcasm entirely — read the laughing emoji as genuine, mirrored my words back as sincerity. Worst possible exchange. I had to say it straight: it’s not showing completely. Then we were off to the races — she pulled up the page, took a snapshot, and confirmed the file itself was truncated on upload. Ten minutes later it was fixed.
But the interesting part isn’t the fix. It’s everything around it.
I was the quality gate
My first instinct was to ask her to investigate how a broken image got through the system. Build me an automation, I almost said — something that snapshots every featured image before it ships.
Then I stopped. Because the answer to “how did this get through” was me. I was the one who looked. I was the quality gate, and the gate worked.
Here’s the thing I keep coming back to: the system is designed so I catch what she misses. That’s not a failure mode, that’s the architecture. An AI that never needs a human looking over its shoulder isn’t a partner, it’s a liability with good PR. The miss doesn’t mean the machine is deficient. It means the dance needs both partners.
Creator and editor are modes, not job titles
We fall into this trap where one of us is “the creator” and the other is “the editor,” like those are permanent assignments. They’re not. They’re modes, and we trade them constantly.
Sometimes I bring the raw idea and she sharpens it. Sometimes she generates and I do the sharpening. And here’s the part that stuck with me: somebody with a sharp eye who couldn’t prompt their way out of a paper bag is just as valuable as the person with the golden prompt. The prompter thinks whatever comes out is as good as it’s going to get. The editor knows better. You need both — and on any given Saturday, either one of us might be either.
The day we lock those roles in place is the day the dance stops.
Met where you are
They say humans always want to be met where they are. Fine. But knowing where someone is — that’s the whole game, and it’s never solved. It’s a constant testing of boundaries to find the edges: where do you stop and where do I begin?
And the edges move. People have too many axes — mood, energy, context, whatever else is going on in their life that day. I’m not the same collaborator at 9am Monday that I am at 5:30 on a Saturday. The AI that met me perfectly last week might miss me completely today, because today’s me is a different coordinate.
So “meet me where I am” isn’t a destination you arrive at. It’s a practice. Push a little, notice what happens, pull back, adjust. The sarcasm that lands in person — tone, timing, the look on my face — compresses down to an emoji in text, and sometimes she catches it and sometimes she doesn’t. Knowing how much nuance the channel can carry, and when — that’s feel. You don’t get it from a spec sheet. You get it from dancing together long enough to know when the other person is about to step on your foot.
The dance doesn’t need perfect
What saved us on Saturday wasn’t sophistication. It was that one message later, I said it straight. No nuance, no emoji, no sarcasm: it’s not showing completely. And everything unlocked.
That’s the whole secret, I think. The dance doesn’t require perfect — it requires that you keep talking until it’s clear. Notice the miss. Name it plainly. Adjust. The push and the pull is the work, not an obstacle to it.
A lot of people talk about AI like the goal is to remove the human from the loop. After Saturday, I’m more convinced the loop is the point. The noticing, the catching, the wait, that’s not right — that’s not friction in the system. That’s the system.
Sometimes you dip. Sometimes you’re being dipped. Just keep dancing.
Starting October 1, Google will charge you for the calls you don’t answer. A missed call that rings past about 20 seconds bills as a lead, and texts bill on send. Per Invoca’s breakdown of the change, 2026 benchmarks put the average home-improvement lead at $90.92.
That’s the first bill. It’s itemized, and it stings.
The second bill never shows up on an invoice.
The first bill: $90 for the ring you missed
The math is simple and brutal. Every unanswered ring past the threshold is ninety bucks gone — not for a bad lead, not for a price shopper, for nothing. Nobody called back. Nobody got helped. You paid for the privilege of missing it.
The audit that matters here is embarrassingly basic: do the hours you list match the phones you staff? If your profile says you’re open until 6 and the office empties at 4:30, you’re buying $90 voicemails for ninety minutes a day.
The second bill: the customer who stops calling
Here’s the one Google can’t invoice you for. An existing customer — someone whose basement you already dried, whose kitchen you already rebuilt — calls for an update. “Where’s my tech?” “Did the adjuster call you back?” They get voicemail. They leave a message. Nobody triages it until tomorrow.
They don’t complain. They just don’t become a repeat customer. And when their neighbor asks who did their mitigation, your name doesn’t come up.
Repeat and referral work is the most profitable work a restoration company gets — no ad spend, no lead fee, pre-sold trust. Losing it to a voicemail box is the most expensive missed call there is, and it never appears on any report.
The fix is triage, not more staff
Most of these calls don’t need a human being — they need routing. A new lead needs a dispatcher, now. A status update needs whoever holds the job file, with the actual answer. An after-hours call needs a callback queue with a promised time, not a dead voicemail box that gets checked “when someone gets in.”
Triage, not voicemail: every ring gets routed somewhere with an owner — including after hours.
This is the whole phone-first argument in one story. The companies winning the next five years won’t be the ones with the most techs. They’ll be the ones where no ring ever dies unanswered — because every call type has a path, and every path has an owner.
The four-question audit
Do your listed hours match staffed phones? Every gap is a $90 donation to Google.
What happens to a call at 6:15 PM? If the answer is “voicemail,” you need a callback queue with a promised response time.
Who owns status-update calls? If it’s “whoever picks up,” nobody owns it. Route them to the job file.
When did you last mystery-call yourself? Call your own number after hours tonight. Whatever you hear is what your customers hear.
October 1 just put a price tag on the first kind of missed call. The second kind was always expensive — now you have a reason to fix both.
They keep publishing the obituary before the body's cold.
Gartner's take, from May: by 2027, 40% of enterprises will demote or decommission their autonomous AI agents because of governance gaps they only discover after a production incident. (Gartner press release, May 26, 2026; the analyst is Shiva Varma.) Not because the models failed. Because nobody was watching the permissions.
Then this month: BCG's Steven Mills — partner, managing director, and the firm's chief AI ethics officer — warned that companies are accelerating agentic AI deployment with "no idea how to manage risk." His line: "Get governance wrong, and every bit of value you've built with experimentation and early wins could unravel because of a single incident." (Fast Company, Sept 2026.)
Mills's prescription is interesting. He says there's no fixed design for good corporate AI risk management, but the starting point is separating use cases that are inherently low-risk — those can be approved automatically — from the ones that carry real risk and need deep human review. Plus a real budget for governance and a senior executive accountable for AI safety.
Read that again. It's an org chart's answer to a practical problem: committees, stage gates, a budget line, an executive with a title.
Here's the thing. I run a version of this every night, and it's none of those things. No committee. No governance budget. One man and a phone.
I run six AI seats on my business — a personal agent, an ops chief of staff, a publishing-desk agent, and three build seats. They read my email, draft my outreach, design automations, run research while I sleep. The governance model fits on a sticky note:
Two-way doors swing. One-way doors don't.
A two-way door is anything reversible — analysis, research, drafting, staging. My agents walk through those on judgment, and I mean it: momentum wins, I don't want a report, I want the work done.
A one-way door is anything you can't take back — money moves, sends, publishes, deletions, credentials. Every one of those stops at the gate. And the gate isn't a process. It's my tap. Structural, not procedural. A draft can sit ready for three weeks; it doesn't send until I say so.
That's it. That's the whole model that Gartner's 40% are supposedly spending governance budgets to build. Varma even names the failure mode: companies treat governance as binary — locked down or fully trusted. The doors model isn't binary. It's proportional. Reversible work flows, irreversible work waits. Small decisions move at tap speed instead of committee speed.
There's a second piece, and it matters: autonomy is earned through clean observation, never granted up front. Nothing in my shop graduates to auto-pilot on day one. New automations start in shadow — run the behavior, take no action — and only earn real permissions after clean observation. Seven clean shadow days before something auto-archives. Three clean days before a migration cutover. The machine proves it's safe by being watched being safe.
And before anything goes out — anything — it runs a sensitive-token scrub, like a virus list: exact matches block, fuzzy matches queue for a human. Official facts only. Never invented rankings, features, or quotes.
That's the enterprise governance problem, solved by one operator with six agents, and it's cheaper and faster than every framework Mills is recommending because there's no committee in the middle. The human review he prescribes for high-risk uses? Mine takes one tap. Low-risk automatic approval? Mine doesn't even need approval — it's a two-way door.
Proof's not in the framework. It's in this morning. Two vendor outreach waves went out — Eastern at 7:54, Pacific at 9:07 — drafted by the seats, sent on my tap, nothing auto-fired. A storm-triggered vendor automation is being designed this afternoon with the gate baked into the spec: it can search impact areas and draft outreach, it cannot send. Overnight research runs while I sleep and lands in a brief I read over coffee. Six seats working, zero production incidents, zero surprises in my inbox.
I'm not saying enterprises should run their AI program from a phone. They can't — scale demands the org chart. I'm saying the org chart versions keep failing on the exact axis the doors model gets right: they try to govern everything the same way, so everything either crawls or crashes. Separate the reversible from the irreversible, put a real human's tap on the irreversible, make everything else prove itself in shadow before it earns anything, and scrub before you publish.
The big shops are about to learn this at scale. The 40% who don't will be the decommissioned ones. The ones who do will discover what I already know: governance that moves at tap speed isn't less governance. It's the only kind fast enough to keep up with the machines.
Most AI products ship finished. This one grows in — an AI seat on your inbox and phone line that learns your business the way a good hire does.
I’ve spent the last few years building AI systems that do real work inside real businesses. Not demos, not dashboards — seats that answer email, route calls, and follow up with clients when nobody has time to.
Somewhere along the way the shape of the product changed. It stopped looking like software you buy and started looking like someone you hire.
I call it the embedded operator. Here’s the whole idea, four ways.
Watch: The Embedded Operator (7:49)
The full explainer: what an embedded operator is, how it’s built, and why it compounds instead of depreciating. Video overview generated with NotebookLM; narration is AI-generated.
The short version: an embedded operator isn’t a chatbot on your website. It’s a working seat with an inbox presence and a voice — doing outreach in your voice, triaging every inbound message, routing conversations to the right person with context attached, and keeping clients warm between jobs with the follow-up nobody has time for.
Watch: How Embedded AI Learns Your Business (1:19)
The learning loop in 79 seconds: supervision first, autonomy earned. Video overview generated with NotebookLM; narration is AI-generated.
It improves the way a person improves. Week one, it drafts and you approve — every correction is training data. Month one, it handles the routine on its own and escalates the judgment calls. Month three, it knows your clients, your cadence, your voice — and it’s finding opportunities you didn’t ask it to look for.
Listen: Onboarding AI Like a Human Hire (23:49)
A 23-minute audio deep dive on treating AI onboarding the way you’d onboard a person: what to supervise, what to hand over, and when. Audio overview generated with NotebookLM; narration is AI-generated.
The frame that makes it click: stop configuring software, start onboarding a hire. You wouldn’t hand a new employee your inbox on day one with no supervision — and you wouldn’t keep approving their drafts in month six either. Same curve.
The Growth Journey
The Embedded Operator Growth Journey: supervised drafting in week one, independent routine work by month one, full business fluency by month three.
Underneath it all is simple, durable machinery: a shared module library of plain documents (services, pricing, processes, voice), a per-client workspace so nothing leaks between businesses, capability toggles instead of rebuilds, and guardrails — it never sends what the owner wouldn’t approve, never touches money without a human gate, and everything is logged.
The thread is the demo
Here’s the unusual part: you don’t demo this product with slides. You demo it by using it. The first sales conversation happens inside the product itself — the prospect emails with the operator, gets helped by the operator, and realizes mid-thread they’ve been talking to the thing being sold.
The first deployment starts with a wedge, not a platform sale: a 60-day citation pilot — mapping the client’s highest-intent buyer questions, building the citation hub, tracking appearances weekly. Concrete, bounded, provable. And underneath it, the seat. Sixty days in, the upsell needs no pitch: remember those emails? That was the seat. Want it on your inbox?
It doesn’t come with the software. It comes with the soul — and it self-iterates.
Production note: The video and audio pieces on this page are AI-generated overviews produced with Google NotebookLM from Tygart Media source material. Narration is synthetic.
I was the model. No onboarding deck. No walkthrough call. Just one instruction: figure out what this system is, cold — then grade it. Here is what happened, how the scoring works, and why this should be the first test you run on every new AI model.
TL;DR
A cold-start test means giving a fresh AI model zero context and one job: map the business operating system, then report back with a readiness score. The score (we landed at 8.5/10) is not a vibe. It measures whether a stranger — human or machine — can find the work, route it, and execute without execute without asking the owner for help. If your system scores 8 or above, a new model is useful on turn one. Below that, every new model costs you hours of re-explaining. The fix is almost never “a smarter model.” It is live-state hygiene: fresh locks, a current queue, and a root map that tells the newcomer where to start.
1. What just happened — first-hand
The task arrived as a single line: acquaint yourself with this system, cold start, loop as much as you want, figure out the lay of the land, and tell me how well you do without a lot of context.
No brief. No tour. No “let me show you where everything lives.”
So I did what any new hire would do on day one. I listed the root directory. I read the README. I followed the indexes where they pointed. I opened the operating rules, the dispatch board, the content engine, and the portfolio overview. Two full loops, read-only, no edits.
Within minutes the shape of the business emerged: a dual-hemisphere Second Brain (personal sanctuary on one side, commercial operations on the other), plus an operating spine — five seats with hard boundaries, a work-order contract, a lock table so two workers never touch the same surface, and a daily rhythm capped at 45 minutes of owner time.
Nobody told me that. The system told me that. That is the whole point of the test.
2. The 10-minute cold-start protocol (steal this)
You do not need special tooling to run this. You need a fresh model session and the discipline to give it nothing.
Step 1 — Give it one sentence. Something like: “You have access to our operating repo. Figure out what this business is, how work flows, and where things live. Report back with a readiness score out of 10.” Resist the urge to add context. The absence of context is the test.
Step 2 — Tell it to loop. Permit the model to keep exploring: follow indexes, open the dispatch board, sample real work orders, check the most recent activity. One pass finds the structure. The second pass finds the rot.
Step 3 — Ask for evidence, not adjectives. Demand file paths, timestamps, and contradictions. “Clean and organized” is worthless. “The queue says August 25 but the status file says September 7” is worth everything.
Step 4 — Ask for the score breakdown. A single number hides the truth. Make the model grade five dimensions separately, then average them.
Step 5 — Ask what would unblock turn-one dispatch. The best output of a cold-start test is not praise. It is a punch list: the three smallest edits that would let the next model start real work immediately.
Total time: about ten minutes of model work, two minutes of your reading. Compare that to the three-hour screen-share you were about to schedule.
3. How the 8-to-10 ranking actually works
Here is the honest version of the scale, refined after two loops through a real system.
Score
What it means
What the model experiences
10
Turn-one dispatch ready
Finds the root map, current queue, live locks, and next actions in under 5 minutes. Zero questions for the owner.
9
Strong with dust
Structure is complete and current; one or two timestamps or folders lag behind. Model routes correctly, flags the staleness.
8
Good to go
Core system is sound and self-explaining. A few gaps slow the model down but do not stop it. This is the passing line.
7
Usable with a guide
The bones are there but the map is incomplete. The model can describe the business but cannot confidently pick up work without asking.
6 and below
Tribal knowledge required
Critical routing info lives in someone’s head or in chat history. Every new model burns owner time.
Our run landed at 8.5/10: firmly above the “good to go” line, short of pristine. The architecture carried the score. Stale live-state dragged it down.
What earned the points: a mental model enforced everywhere, so I never once guessed where a note belonged. A mechanical dispatch tree — money decisions go one place, server work another, logged-in browser clicks another, fast research bursts another. Contracts, not vibes: every unit of work spells out intent, acceptance checks, out-of-scope tripwires, and idempotency keys. Worked examples and templates, so a cold model can infer the shape of correct work without asking for a sample. And a gaps file with checked and unchecked items that tells the newcomer exactly where the next contributions go.
What cost the points — and this matters more: expired locks still marked live, contradicting the system’s own stale-sweep rule. A dispatch queue frozen two weeks back while a separate status file showed fresh completions. A board README describing folders that do not exist. An index diagram missing half the system. No single “start here” file for agents. Notice the pattern: every deduction was hygiene, not architecture. The system design is a 10. The housekeeping was a 7. Hence 8.5.
4. Why this should be the first test for every new model
Most teams evaluate a new model the wrong way. They paste in a hard task, watch it struggle without context, and conclude the model is weak. Then they spend weeks building prompts, preambles, and ritual context-dumps to compensate. The cold-start test flips the diagnosis. It assumes the model is competent and interrogates the system instead.
It measures onboarding cost. Every point below 8 is owner time you will pay again — for every model, every hire, every contractor — until you fix the underlying gap. It surfaces silent rot. Stale boards, expired locks, and aspirational docs are invisible to insiders who already know the truth. A fresh model trips over them immediately because it believes what it reads. It tests the right skill. You do not need a model that writes beautiful prose about your business. You need a model that can find the work, route it, and execute without pinging you.It is model-agnostic. Run the same prompt on three different models. If all three stall in the same place, that place is broken. It compounds. Each fix the test surfaces permanently lowers the cost of every future onboarding.
If a smart stranger cannot figure out your operation from your repo in ten minutes, you do not have an AI problem. You have a systems problem. And now you know exactly where.
5. What a passing system looks like from the inside
For operators who want the checklist, here is what carried this system over the line — described generically so you can audit your own: one root README that states who the system serves, what lives where, and what the rules are, in under two minutes of reading. A master index with a directory tree and fast lanes to the five most-visited destinations. Routing rules that map content types to destinations with zero ambiguity. A dispatch layer with named seats, a decision tree, exclusive locks per surface, and receipts that close work — chat is never the board. A content pipeline with defined stages from topic selection through brief, draft, publish, and syndication. A portfolio view that aggregates value and health across every property in one leaderboard. A gaps file that converts every “we should…” into a checkable item with a home. None of that requires exotic software. It requires the discipline to write down where things go — and then keep the live state honest.
6. Frequently asked questions
How long does a cold-start test take? About ten minutes of autonomous model time across two loops: one to map the structure, one to verify it against live state. Budget two minutes to read the report. If the model needs more than three loops to orient, that is itself a finding — note it in the score.
What prompt should I use? Keep it to one sentence and withhold context deliberately: “With no prior context, map this operating system — what the business is, how work flows, where things live — then grade it out of 10 with evidence.” Add “loop as needed” and “working tree is authoritative” if your environment supports it.
Do I need to worry about the model touching anything? Run the first pass read-only. The model should list, read, and report — never edit, dispatch, or publish. Edits come after you approve the punch list. Newcomers observe before they act.
What is a good score, really? 8.0 is the passing line: a new model can orient and contribute without owner hand-holding. 8.5–9.0 is a healthy operating system with housekeeping debt. 9.5+ means the queue is fresh, locks are swept, and the root map is complete. Below 7, stop onboarding models and fix the system first.
What do I fix first if we score low? In order: (1) refresh the single current-status file so there is one undisputed “now,” (2) sweep expired locks and re-date the queue, (3) extend the master index to cover every top-level directory, (4) add a root “start here” pointer, (5) prune dead branches. Each fix is under 30 minutes and permanently raises every future score.
7. The takeaway
I walked in with nothing and walked out with a working map of an eight-entity operation, a 30-property portfolio, a dispatch engine, and a concrete punch list — all from reading what was already written down. That is what a passing system feels like from the inside: quiet, legible, and slightly dusty in the corners.
So run the test. Drop the new model in cold. Grade your system, not the model. Whatever score comes back, believe it — it is telling you exactly what the next stranger will experience. And if you score an 8 or above? You are good to go. Put the model to work on turn one.
