The Biweekly · 2026-07-12 Eric + Adam

One big decision, then four small ones.

What I heard

'we need to clearly clarify what it really is going to deliver for them.'

Every name explains itself the first time it's said.

Flat fee plus equity, never performance fees.

Every guarantee covers our delivery, never their outcomes.

'we'd have more work than we could handle — that's not what we want.'

A hard cap at eight clients and a tripwire on hours. The bridge stays a bridge.

The precedent engagement: two ten-hour days, fifteen grand, and the real value in the gaps the team didn't know they had.

The founding price for the Rewire: $15K bought the manual version a decade ago.

The old way, built honestly

The first build was the obvious pack: process audit, SOP playbook, monthly operating system. Priced, guaranteed, finished, and honestly good. Its opening line: 'your processes aren't documented.'

Not a wrong pitch. A common one.

Who already opens that way

A market-rate EOS implementer

$5,000 a month

The precedent engagement

$15,000, a decade ago

Every EOS implementer and fractional COO in your network

the buyer's comparison set

A recent prospect had already heard several process-style pitches. What won the proposal request was the one they hadn't heard: AI built into its bones instead of sprinkled on top.

Your sentence, completed

'the same discovery — but AI compiles the playbook, and an agent layer stacks on top.'

If a machine can compile the playbook and carry the follow-through, AI isn't a topping on a process audit. It changes what the product is. The thing eating these companies was never missing documentation. It's the traffic: every job, question, and status update routing person-to-person because that's the default nobody chose. Documentation organizes the work and leaves the traffic untouched. A machine that carries the traffic is a product nobody in this market is selling.

The disease is the hyperactive hive mind (work coordinated by unscheduled, ad-hoc messages). We can't document their way out of a workflow problem.

The new way

The dream isn't quiet for its own sake. Owners want a company that runs itself: chaos conquered, their time back. Freedom. Working name: the Self-Running Company (alternates: "The Quiet Company," "Runs"; every name here is open in Decision 2). Three steps, working names:

The Interruption Audit

Two weeks, read-only on the systems they already have. The first honest picture of where the company's attention goes.

The Rewire

Rules for the recurring traffic, then the machine layer that carries it. The playbook they'd pay thirty grand for elsewhere falls out as a byproduct.

Run Quiet

The monthly board, the owner's packet, your review. The enforcement layer that keeps chaos from growing back.

The machine carries the traffic and keeps the score. Their people keep every decision. The owner gets their time back.

The case for it

The comparison set goes from five firms to zero.

They feel it hourly: the binder is an abstraction, the phone is their life.

The beta trap closes: AI stops being what makes us faster and becomes the thing they're buying.

The readout, pictured · Illustrative numbers, not claims. Nothing client-facing until we have our own data

Picture Client 01's readout in week three. Four numbers on the table: sixty-one messages a day through his phone. Eleven of the last fourteen callbacks born at the dispatch-to-tech handoff, not on a job site. Decisions bouncing four times before they close. His best tech's longest uninterrupted stretch: twenty-four minutes. Then one question: 'which of these did you already know?' The silence after that question is the product.

Fourteen texts by nine a.m.: the company has one nervous system, and it's him. Being needed is the most seductive failure mode. Every owner we pitch is flattered by being the operating system, right up until they want a vacation, or a valuation.

Side by side

	The old wayv0.1 · Process!-anchored	The new wayv0.2 · traffic-anchored
Opening line	"Your processes aren't documented."	"How many texts had you gotten by 9 a.m. today?"
Problem named	Missing systemization	The traffic about the work eating the work
Felt by the owner	As a lecture they've heard for 20 years	As their actual morning
Who else says it	EOS implementers, fractional COOs, process optimizers, including Adam's own reference set	Nobody in this market
What AI is	A faster way to make the binder	The product: the machine that carries the traffic
Buyer compares us to	$3–5K/mo implementers	Nothing local. A category of one
Where Process! lives	The headline	The stick layer: why it holds after month three
The hire-more trap	Unaddressed	The teach: every person added multiplies the traffic
One word	"Organized."	"Freedom."

The five decisions

What do we lead with?

When a prospect hears this for the first time, do they hear paperwork, or their own phone? This is the big one; everything downstream is drafted either way.

Why it matters

The opening line picks our competition. Documentation puts us beside five firms and a price anchor that belongs to someone else. Traffic puts us in a lane of one, with the machine as the product.

Proposed

Lead with the traffic. The side-by-side above is the argument; the offer sheets below are built on it.

The stick layer closes the credibility gap. When the skeptic says "we tried systems, they died," the second teach lands: systems die because nobody could afford enforcement (an owner per rule, a weekly board, a loop that catches drift) until the machine made enforcement cheap. That's the Process-book material doing its correct job: supporting act, not headline.

Your bridge line: "I ran my company on EOS and process docs. They helped. The thing actually strangling us was the phones, and nobody was selling a fix for that."

What do we call it?

Do these four names explain themselves out loud, the first time they're said?

Why it matters

The names carry the pitch when neither of us is in the room.

Proposed

The Self-Running Company · The Interruption Audit · The Rewire · Run Quiet. Then a three-word test with ten warm contacts.

Alternates. Audit: "The Two-Week Read" (report title: Where the Day Goes). Project: "The Operations Rewire," "The Coordination Rebuild." Recurring: "The Operating Review" (safe/plain), "Mission Control" (vivid; slight overclaim risk). Category alternates: "The Quiet Company," "Runs."

The three-word test: ten warm contacts, three words each; fishing for freedom, quiet, operator. If consultant or software comes back, more Adam in the warmer, less offer.

What does it cost, and what do we promise?

Can we say the price and the guarantee in one breath, without flinching?

Why it matters

The promise is the trust mechanism. We guarantee what we control, our delivery, never their outcomes. Flat fee plus equity, never performance fees.

Proposed

Audit $7,500, fully credited forward. Rewire $30,000 list, $15,000 founding. Run Quiet $7,500 with the review, $5,000 without. And: "If the readout isn't worth the fee, don't pay the fee."

On the Audit and Rewire: "If the readout isn't worth the fee, don't pay the fee." Countable fallback: "If the Audit doesn't surface at least ten fixes you didn't already have written down, it's free."

On Run Quiet: late/incomplete packet = free month · 30 days' notice · keep everything built. No hostages.

All alignment mechanisms, none performance fees. Matches your "if we suck, fire us" posture.

How do we split it, and where does our time stop?

This only works if it stays a product line, not a second job. You're building companies; neither of us is signing up for full-time consulting.

Proposed split

Eric 45% of collected fees; Adam 55%. Client equity accrues to the venture per deal. To paper with counsel before the first client signs; terms here are a sketch, not legal advice.

Proposed timebox

The machine carries delivery. Agents assemble, Eric reviews: steady-state ≤6 hours per client per month. Six clients ≈ one week a month.

Adam's standing commitment is the monthly operating review and the warm introductions. Everything else is machine and Eric. Building companies stays the day job.

The tripwire protects both of us. Any client over 10 hours a month, two months running, means the automation is broken: fix the back end before the next intake.

Who do we prove it with first?

Client 01 is ready to start. Do we green-light, and hold the cap at eight?

Why it matters

We named the trap: 'more work than we could handle.' The cap keeps the beta a beta, and one real before/after gives us the numbers the pitch can't claim yet.

Proposed

Green-light Client 01: read-only access to field-service software + QuickBooks, and the Audit starts. Cohort: 2–8 warm-network founding clients, capped hard at eight.

The first 30 days

Wk 1

Access + baseline pull.

Wk 2

Two on-site days.

Wk 3

Readout: his traffic numbers, the chaos map, ten-plus fixes. Choose Rewire or Pilot in the room; book day-60 before leaving.

Wk 4+

First rules live, board up, first packet ships.

When all five are decided: counsel on the structure · Client 01 outreach owner + date · pitch field-test on two warm contacts.

What the client would see

The three offer sheets, as drafted

The frame · The paragraph everything else hangs on

Your company doesn't have a people problem. It has a traffic problem. Every job, question, and status update routes person-to-person, through your phone, the group texts, the dispatcher's inbox, because that's the default nobody chose on purpose. The traffic about the work now interrupts the work itself: your best tech gets pulled mid-job, decisions bounce four times before they close, and you're answering "quick questions" before 7 a.m. and after 9 p.m. Here's the part that stings: hiring more people makes it worse, because every person you add multiplies the traffic. Documentation doesn't fix it. Another app doesn't fix it. Rewiring how work and information move, and letting a machine carry the traffic, fixes it. Quiet is what a company that runs itself sounds like. Quiet is what profitable sounds like. And a company that runs itself hands you back the thing you started it for: your time.

Step one

The Interruption Audit

2–3 weeks · $7,500 · fully credited forward

Two weeks, read-only access to the systems you already have (field-service software, QuickBooks, calendars) and you get the first honest picture of where your company's attention actually goes.

The readout shows you, in your own numbers:

Your traffic load: messages and calls per day, per person; how many land on you; what arrives before 7 a.m. and after 9 p.m.

Decision bounce: how many rounds the average decision takes before it closes, and which decisions only close through you.

The interruption tax: the longest uninterrupted stretch your best people actually get. (Most owners guess two hours. It's usually under thirty minutes.)

Where the chaos is born: the handoffs and recurring situations that generate the traffic: intake, scheduling, status-chasing, callbacks.

Your team's effort: zero. Nobody changes anything, nobody gets watched, no meetings. Read-only, two weeks, one readout.

Guarantee: at the end of the readout, if you don't believe it was worth the fee, don't pay the fee.

Step two

The Rewire

One-time project · $30,000 list

We redesign how work and information move through your company so it stops routing through people's phones by default, and we install the machine layer that carries the traffic.

What you get:

Coordination rules that stick: a designed rule for every recurring traffic source the Audit found: how jobs come in, how they get scheduled, how status moves without anyone asking, how escalations reach you (and what no longer does). Each rule written in a page, each with one named owner.

The machine layer: AI and automation configured to carry the traffic: intake handled at the gate, schedules set without the six-text volley, status pushed so nobody has to chase it, the paperwork assembled while your people work. Our standing rule: the machine carries the traffic and keeps the score; your people keep every decision. We will never sell you "AI runs your company."

The playbook, included. Once the traffic is rewired, your core processes are already mapped, so you get the full documented playbook, the thing other firms charge this entire fee for on its own, as a built-in deliverable, one to two usable pages per process, one named owner each.

The scoreboard, stood up: the handful of numbers from your Audit, live on a board your crew sees weekly, so "how's it going" stops being an argument.

How it runs: ~4–6 weeks. Two on-site days (leadership plus one key person per department, walked in handoff order); the rest is build. Your team's disruption: two days.

Prefer to start smaller? A 60-day Pilot rewires ONE traffic source end-to-end for $12,500, with success criteria set in writing before we start.

Step three

Run Quiet

Monthly · $7,500 with the operating review · $5,000 without

The monthly system that keeps the company running itself, because chaos grows back, and catching it small is the whole game.

Every month:

The Owner's Packet: financials plus operations in one fifteen-minute read: what moved, what slipped, what's driving it, the one fix we recommend next. Assembled by the machine, reviewed by us.

The Monthly Operating Review: a working session with Adam: walk the packet, pick the fix, name the owner, set the check. (The difference between the two tiers.)

The stick layer: the reason this holds when every past initiative died by month three: every rule and process keeps its named owner, the crew sees the board weekly, and every miss gets traced to the step that caused it, not the person. New traffic sources get caught and converted into rules before they become culture.

Quarterly off-site prep and debrief, generated from your own numbers.

Terms: month to month after the pilot. Any month your packet is late or incomplete, that month is free. Thirty days' notice to leave, and the scoreboard, the rules, and the playbook are yours to keep. No hostages.

Pilot → Run Quiet conversion is decided by rule, not mood: criteria set in writing at the Audit readout (packet on time 2/2 months; at least one of three chosen numbers moved or its root cause fixed-in-progress; owner scores value ≥8/10), decision meeting booked for day 60 before we start.

The economics, between us

Not client-facing

Offer	List	Founding (beta)	The story
Interruption Audit	$7,500	$7,500, never discounted; 100% credits to the Rewire	"You risk two weeks and a fee that comes back."
The Rewire	$30,000	$15,000	The precedent anchor, repositioned: the manual, documentation-only version of this cost $15K a decade ago: Word docs, two long days, no numbers, no machine layer. Founding clients pay that price for the rewire, the AI layer, and the playbook folded in.
Pilot (60 days, one traffic source)	$12,500	$10,000	Written criteria; converts by rule.
Run Quiet	$7,500/mo (with review) · $5,000/mo (without)	$5,000/mo with review, 6-month lock, then $7,500	Full tier at the floor while we tune it: full value visible, discount visible.

Price discipline: the $7,500 tier is load-bearing. The lock has an end date; hold it at renewal.

Eric at 45% of collected fees:

Recurring clients	Monthly gap
3	−$7,875
4	−$4,500
5	−$1,125
6	+$2,250 ✓ gap closes
8 (cap)	+$9,000

Each founding Rewire adds ~$6,750 one-time. Gap closes at six recurring clients, or five plus one Rewire per quarter. Bridge A covers the near term; target six recurring by month 4–6.

"Quick question: how many texts had you gotten by nine this morning? [pause] Right. And I'd bet most were 'quick questions' only you could answer. I know, because when I ran my restoration company, I was the routing system. We had EOS. We had SOPs. They helped, but the thing actually strangling us was the phones, and nobody was selling a fix for that.

Here's what nobody tells you: you don't have a people problem, and you don't really have a process problem. You have a traffic problem. Every job, question, and status update moves person-to-person because that's the default nobody chose. The traffic about the work now interrupts the work itself. And the trap, the one I fell into, is hiring your way out. Every person you add multiplies the traffic. You hired an office manager to get your phone back, and now you text each other about the texts.

It's measurable, and you've never seen it in one place: how many rounds a decision bounces before it closes. How many decisions only close through you. What arrives after nine at night. The longest uninterrupted stretch your best tech actually gets: owners guess two hours; it's usually under thirty minutes.

You know the morning I mean. Fourteen texts by nine. You're the operating system. Feels necessary, right up until you want a vacation. Or a valuation.

The fix isn't better people or another app. Give the recurring traffic rules: how jobs come in, how schedules get set, how status moves without anyone asking. Then let a machine carry the traffic: intake gated, status pushed, paperwork assembled while your people work. The machine carries the traffic and keeps the score. Your people keep every decision. You get a company that runs itself.

And if you're thinking 'we tried systems, they lasted a quarter,' you're right. Here's why: enforcement. A rule holds only if it has an owner, a scoreboard the crew sees weekly, and someone catching drift while it's small. That used to take a manager's full attention forever, which is why it always died. The machine just made enforcement affordable. That's the actual change.

So here's the whole ask: two weeks, read-only, the systems you already have. You change nothing; your team won't notice. You get your numbers and the map of where the day goes. If the readout isn't worth the fee, don't pay it. Every owner thinks they know where the traffic comes from. The data usually surprises them. Want to see yours?"

Lines to test

The words: "Quiet" is the sound; "freedom" is the point. Guard the one risk explicitly: quiet ≠ slow. "Quiet is what profitable sounds like."

The opener: "How many texts had you gotten by 9 a.m. today?" Keep "If you took two weeks off tomorrow, what breaks first?" for the valuation conversation.

The rhyme: "If it lives in the thread, it's already dead."

The one-liner: "Your company doesn't have a people problem. It has a traffic problem. Two-week read of your own messages. See it."

The one visual: the owner's own week as a strip. Before: chopped into confetti by interruptions. After: blocks. Their calendar, not stock art. And stay granular: "14 texts by 9," "4 bounces," "27 minutes," never "a lot."