Start here: what this blog means by ontology, operator, and owner-ready

If you landed on this blog from a search or a link, you probably hit a post mid-argument, full of words like “ontology” and “owner-ready” that we never stopped to explain. This page fixes that. It tells you what the recurring vocabulary means, who we write for, and which posts to read first.

Who we write for

You run a business that depends on you too much. Customers want you on the phone, employees ask you to make every judgment call, and stepping away for a week costs you sleep. You want the company to run as a system, documented and teachable and consistent, the way a franchise runs, without becoming a franchise.

Or: you are the skilled person a company just cut. You fixed the equipment, worked the claims, kept the schedule honest. The role is gone; the skill is not. You are weighing whether that skill can become a small business you own.

Honestly, most of the archive so far is neither of those things. It is research notes: deep readings of insurance manuals and state regulations that we do to build our own tools, labeled as research in the series name. The posts written for you are newer and fewer, which is why this page exists — to route you to them without making you wade through payer-manual close readings first.

The vocabulary, in plain language

Ontology. A research word for a simple thing: the shared map of your business. The named list of things your company deals with (customers, jobs, promises, approvals, deadlines, exceptions) and how they connect. Every business has one. In most small businesses it lives in the owner’s head, which is the problem.

Operator. The person actually running the work day to day. Sometimes the owner, sometimes a manager, sometimes the new hire you hope can take the Friday calls. When we say “the next operator,” we mean whoever inherits the work after you: an employee you promote, a manager you hire, a buyer.

Owner-ready (or owner-operable). Work is owner-ready when another capable person could run it from the records alone, without calling you from a customer’s driveway to ask what to do. A business full of owner-ready work can be delegated, grown, or sold. A business full of private judgment cannot.

The record. Our shorthand for wherever a piece of work keeps its facts: the job ticket, the claim file, the customer note. The recurring argument on this blog is that most records store what happened but drop why: which rule applied, who decided, what remains open. When the “why” drops out, the business runs on memory, and memory doesn’t transfer.

Source. The document a rule actually comes from: the contract, the payer manual, the state regulation, your own price sheet. We keep insisting that records point back to sources because “we’ve always done it that way” is how businesses become hostage to whoever remembers the reason.

Lane. Context that changes which rule applies. The same insurance code pays differently under different plans; the same service call carries a different promise inside and outside your service area. Knowing the lane before applying the rule is half of what experienced staff do without being able to say so.

Business-process franchise. The idea, from Michael Gerber’s The E-Myth Revisited, that you should build your business as if you were going to franchise it: every recurring workflow documented well enough that a competent stranger could run it to your standard, even if you never sell a single franchise. Our E-Myth Notes series works through this idea; our tooling work exists to make it achievable without a year of writing binders nobody reads.

Where to start

If you own a business: start with the E-Myth Notes series; Technical skill is not a business model and The business itself is the product are the spine. Then read How to start making your business run without you, which turns the idea into a first project you can run this month.

If you were laid off and want to build: start with Turning your trade or back-office skill into a business, then Laid off? The tools that replaced you can build the business you own.

If you build software or study knowledge systems: the research notes are for you. The dental series is the deepest thread; a good entry point is The administrator is not the authority.

We would rather you read three posts that change what you do next month than thirty that you nod along to. Start with the path that matches your situation, and if a term shows up that this page doesn’t cover, that’s a defect, and the page will grow as the vocabulary does.