Blueprints
Your way of running a company, made installable.
OTP is the Organization Transport Protocol. A Blueprint is what it transports: the shared organizational knowledge of a company that already runs well, captured as a payload and applied to any other in one click. Nothing about how you work has to change. What you already built becomes portable.
You spent years shaping how a company should run: the words you use, the meeting you run, the numbers you watch, the seats on the chart, the processes behind them. That knowledge works. It also lives in exactly one place, the company where you built it, and every new company starts the climb from zero.
A Blueprint ends the rebuild. It captures all of it from a real working account, not a template you drafted from memory, and applies it to any other organization in one click. Not a document about your method. The method itself, installed.
A Blueprint carries the configuration of a company, category by category. You choose what goes in; every asset is listed by name before anything is applied.
Section names, values, vocabulary. The words your companies run on.
Formats, agendas, cadence. Your Delta Meeting, shaped the way you run it.
KPIs, groups, and the dependencies between the numbers.
Teams, the chart, and what every seat is responsible for.
The intelligence layer's configuration, so every company gets the voice you shaped.
Priority templates. The shape of a quarter, ready to fill in.
Operating plans. The documented way the work actually gets done.
Configuration travels. Data never does. And people become roles: a Blueprint carries the seat, never the person sitting in it.
Your method is not frozen, so a Blueprint is not either. Improve the source once, capture a new version, and push it to every linked organization. Before anything lands, the update preview tells the truth per asset: new, unchanged, a safe update, or something the client changed themselves.
Safe updates land. Local edits are kept. And every apply can be undone, so pushing your latest thinking is never a leap.
This is the part that changes the economics. A published Blueprint becomes a template any organization can start from. A new client does not sign up to an empty tool and then spend a quarter learning your method. They are born into it: your language on day one, your meeting on the calendar, your scorecard already watching.
Your methodology stops being a service delivered one room at a time. It becomes a product every client starts from, and every improvement reaches all of them.
Every acquisition starts on your operating model. Day one at the newest company looks like year three at the first.
Anyone who runs more than one company knows the rebuild. Build it once. Never rebuild it.
Create a Blueprint from a working account. Pick the account that runs your method best; the Blueprint reads its configuration and packages it, category by category.
Point it at any organization. Preview every asset, choose what to bring, apply in one click. If anything lands wrong, undo it.
When your method improves, refresh a new version from the source and push it to every linked organization at once. The preview keeps every apply honest.
Hand anyone a permanent link, or publish to the template gallery. Recipients can import it, or create a brand-new organization from it, born running your way.
You are not changing how you run companies. You are keeping it, and carrying it with you to every company you touch next.
Blueprints is in Labs today, an early-access beta. Once you are signed in, turn it on under Settings, then Labs.