Free · self-serve · no call

Find out what your work actually costs
before anyone sells you software.

Install a recorder, work normally for a week, and get back a costed AI readiness roadmap built from what was measured — not from what somebody remembered in a meeting.

The assessment and the roadmap are free and stay yours. Building anything is quoted separately, and quoted to scope.

The problem with asking

Every AI readiness assessment starts by asking an executive to describe their processes and estimate the hours. Both answers are guesses, and every dollar downstream inherits them.

Nobody remembers the swivel chair

Carrying the same number between two systems by hand is the most automatable thing in an office. It is also never described as a process — it is remembered as part of one.

Estimates round to the story

"About four hours a week" is a feeling. A measurement is 6.2 hours across 12 observed runs by 2 people over 14 days, and it either supports a business case or it does not.

The systems list is always short

Executives list the CRM and the ERP. The work usually lives in a spreadsheet nobody mentions. Observation finds it; a questionnaire cannot.

What it records — and what it refuses to

This is the whole reason it can be installed at a company that has a compliance officer.

Kept

  • Which application — Salesforce, QuickBooks, a spreadsheet
  • What kind of action — click, type, copy, paste, upload, submit
  • The element's role — "a button", "a field"
  • How long each step took
  • A URL's site name, and a path with ids masked: /orders/:id/edit

Never

  • Anything you type. Not the value, not one character of it
  • Page contents, element labels, document text
  • Query strings — dropped whole, never shortened
  • Clipboard contents on copy or paste
  • Screenshots, of any kind, at any point
  • Who performed the work — the reference is hashed with your own salt
The recorder redacts before anything leaves the laptop, and the server redacts again on arrival and counts what it removed — those counts appear in your dashboard. An extension can be modified by whoever installs it, so the server is the half that actually holds. There is no column in the database that could store a value you typed.

Read the full boundary

What you get back

A Red / Yellow / Green scorecard

Across three lanes: what it would cost, what could go wrong, and whether your data is good enough to start. Each colour carries the one line that matters under it and what would move it.

A three-phase roadmap, drawn

Phase 1 proves it on one thing. A gate. Phase 2 expands what worked. A gate. Phase 3 is deliberately unpriced — costing a transformation against unknowns produces a fabricated number.

A next step small enough to say yes to

Sized to sit under the exposure ceiling you state. A red scorecard produces a smaller step, never "come back later".

A provenance ledger

For every input the roadmap rests on: measured, stated by you, derived, or absent. You have been oversold before. You should be able to check, not be reassured.

Time is measured. Money is stated.

A browser can watch how long work takes. It cannot know what the person doing it is paid — so it never guesses.

A process with no hourly rate contributes zero dollars to every figure in your roadmap, and is listed as uncosted rather than filled in with an industry average. Type a rate and those hours become dollars. That is the only way a number in this document can appear.

Your key works both ways

One credential, two directions, separately scoped.

ingest

Your recorder and any system you already run push observed work in. This is the key that sits on fifty laptops, and it cannot read anything back.

read

Your own AI queries the roadmap over MCP — the scorecard, the phases, the findings, the provenance. A roadmap your assistant can answer questions about is one that gets consulted rather than filed.

Measure a week. Decide from evidence.

Free, no card, no call. The roadmap is yours whether or not anything is ever built.

Create your account