Perspectives
Field notes from building Runbook — essays on operations, AI, and the difference between authored and inferred systems.
March 2, 2026 · Jeff Rogers
You Don't Have Procedures. You Have Habits.
Every service operation runs on six things. The question is whether they were authored — or inferred from the habits of whoever is still around.
#perspectives#procedures#habits
April 12, 2026 · Jeff Rogers
The Six Primitives, Composed
An authored system is made of six things. Here is what they are and how they compose into a business that runs.
#perspectives#primitives#framework
April 13, 2026 · Runbook
How Sabir Homes Runs Without the Owner
A Tuesday at a residential services company where the admin doesn't chase anyone. The policies do.
#customer-story#policies#case-study
April 14, 2026 · Jeff Rogers
Write Your First Rule in 60 Seconds
One frustration, one sentence, one enforced rule. What authoring a policy actually feels like.
#product#policies#walkthrough
April 14, 2026 · Jeff Rogers
Why We Don't Call Runbook an Agent
Every AI product is pitched as an agent. Runbook isn't. Here's why the word hides what matters — and what we built instead.
#positioning#authored-systems#ai
April 15, 2026 · Runbook
The First Five Rules Every Gym Should Write
Waivers, open checks, kid capacity, equipment inspections, late close — the five policies that take a gym from 'held together by memory' to 'runs when the owner is out.'
#vertical-gyms#policies#playbook
April 15, 2026 · Runbook
What Happens When You Have 50 Policies
A tour of how the Runbook dashboard keeps a growing policy layer legible: grouping, conflict warnings, never-triggered rules, and the signals that keep the system honest.
#product#policies#dashboard
April 18, 2026 · Jeff Rogers
Architect Mode Needs a Substrate
There's a popular essay arguing the founder's job is shifting from Founder Mode to Architect Mode. The frame is correct. The architecture it assumes is not.
#positioning#authored-systems#founder
April 18, 2026 · Runbook
The First Five Rules Every Realtor Should Write
Lead response, pre-approval gates, seller disclosures, closing runbooks, and the 90-day follow-up — the five policies that turn a solo realtor's chaos into something that runs when they're in a showing.
#vertical-real-estate#policies#playbook
April 18, 2026 · Jeff Rogers
Most AI Transformations Are Speeding Up the Wrong Thing
Bolting AI onto processes you already have just makes yesterday's constraints run faster. The real opportunity is to ask which of those processes should exist at all.
#perspectives#ai#process
April 18, 2026 · Jeff Rogers
The Economics of Authored vs Inferred
Agent-first products pay to re-derive the same logic on every event. Substrate products pay once when the rule is authored. The cost gap is 15-20x at steady state and widens as the business grows.
#perspectives#economics#ai#architecture
April 18, 2026 · Jeff Rogers
Why Runbook Policies Aren't Claude Skills
Skills and policies both let you write intent in plain English. But one is a prompt an LLM executes, and the other is a rule an engine executes. The difference decides which one you want for your business.
#positioning#policies#skills#ai
April 18, 2026 · Jeff Rogers
Don't Automate the Trainer. Automate Around Them.
An economist's take on what becomes scarce in an AI-abundant world has a sharp implication for service SMBs: the relationship is the product. The wrong AI strategy is the one customers can see.
#perspectives#ai#positioning#relational
Runbook perspectives are grounded in the authored.systems framework — ten principles for building operational systems where humans author the rules and machines enforce them.