⌁ Synthetic fixture · no real company, person or peer index What's mocked?
Operational design
For the role you keep almost-hiring

Tell me what the role
would have done.
I'll tell you what it costs you.

Connect the systems that role would have used. In about a minute you get a Role Design built from your own data. What runs, what it's worth, and what it isn't yet allowed to do.

Start with one line
No sales call, no card. The six questions are anonymous.
Don't install another tool. Add the role that's missing.

Your inbox, phone, calendar, spreadsheets and field-service software already contain the job description. TOD reads the work, identifies what is repeatable, what needs judgment, and what is falling through the cracks.

Observe→ Design→ Shadow→ Work→ Prove
A person owns the Role

AI does the repeatable work. A real person stays accountable for the Role: handles the exceptions, improves it, and reviews the numbers with you.

It tells you which is which

Some work can run automatically. Some needs approval. Some should always stay with a person. TOD doesn't guess its way through your business.

Keep it only if it earns its place

See what was completed, what still needs a person, how much time the Role returned, and where every number comes from.

Hire the role before you hire the person.

⌁ Prototype running on a synthetic fixture · See everything that's mocked
Step 1 of 3 · drift
Demo 1 · property management Demo 2 · event décor

Six things, then one ask.

Finish the sentences. Nothing here is a lead form, and nothing here is a credential. It goes straight into the design.

Step 3 of 3 · the ask

Where does the
work arrive?

We ask where work arrives, not which software you bought. Read-only, every one of them. You may not be the person who does this work. A CEO can be here about someone else's role, so what matters is connecting the systems the role works in, not your own. One of them is required: the mailbox. Response times and thread evidence live there, and a design without it would be a guess. Where a source belongs to a person, that person authorizes it, never you over their head.

What the company runs on

⌁ Mocked: OAuth. Buttons set a connected flag and load fixture data. No credentials are requested, stored or transmitted.

Reading your systems
0.0s
Step 2 of 3 · account

Before we read anything,
we need to know who is asking.

Still no sales call and no card. But the next screen asks for read access to your inbox and your property system, and a connection like that is a credential. It has to belong to someone who can revoke it.

Work email
Your name
Your role

No password. The link is the login. ⌁ Mocked: no email is sent. The link resolves immediately.

One named person on the record, one place to revoke, one counterparty who can sign. That is all an account is for here. Why this comes first →