Six steps. Everything a machine can observe is observed; everything it cannot is asked once, plainly.
Prefer it read aloud, with a simulator? Take the narrated walkthrough — same content, six minutes, no jargon.
The single most important page on this site, so it is spelled out rather than summarised.
| Signal | Kept | Why |
|---|---|---|
| Application | The name — Salesforce, QuickBooks, a spreadsheet | Which systems a process crosses is what makes it automatable or not. |
| Action | One of: navigate, click, type, submit, copy, paste, upload, download, search, wait, switch_app, scroll | A fixed list. An unrecognised verb becomes other — "whatever the client called it" is a text field by another name. |
| Element | Its role: button, field, link, table | Never its label. "Approve invoice 4471" would leak both a process and a record. |
| Address | Site name, plus a path with identifiers masked: /orders/:id/edit | Query strings are dropped whole, never shortened — that is where search terms and tokens live. |
| Duration | Milliseconds on each step | The measurement the entire cost model is built from. |
| Who | A hash of whatever reference you supply, salted per company | The module counts how many people do a piece of work. It never learns who they are, and two companies hashing the same person get different pseudonyms. |
Runs with the same shape are grouped. From a group we measure: how many runs, over how many days, by how many distinct people, and the median duration. Hours per week, per person, follows from those.
The grouping is a machine guess about where one piece of work ends and the next begins. It stays proposed until a person confirms it, and only confirmed processes enter the roadmap.
A browser can watch how long work takes. It cannot know what the person doing it is paid.
So there is no industry average anywhere in this product. A process with no hourly rate contributes zero dollars to every figure in your roadmap and is listed as uncosted. Enter a rate and those hours become dollars. That is the only path by which a dollar figure can appear here.
Which concern is the real blocker · what you could spend once without losing sleep · which risks keep you up · whether you would trust a report pulled today · how hard data is to get out · whether the work touches personal, health or payment data.
The full readiness interview asks about forty things. Better than thirty of them are now measured, which is what this module is for. The evaluation refuses to run while one of the six is missing, and names which — a confident document built on absent inputs is precisely the artifact most executives have already been sold once.
The same AI Readiness Department that runs consultant-led engagements, called through the same code: Data Readiness, then Cost Comfort, then Risk Comfort, then the Roadmap Builder, coordinated by the Readiness Director.
The order is load-bearing. Data runs first because its count of blocking gaps becomes remediation hours in the cost model; cost runs second because its Phase 1 scope is what risk writes guardrails around. Run concurrently, the three lanes quietly disagree about which processes are in the pilot.
ingest pushes observed work in — this is the key that sits on many laptops, and it can read nothing back. read lets your own AI query the roadmap over MCP at /discovery/mcp.
The read surface will not confirm a process, set a rate, or answer a posture question. Those are the human judgements every figure rests on, and an agent that could supply them could manufacture a roadmap end to end with nobody in the loop.
The assessment and the roadmap are free and stay yours. A build is quoted to its scope.