Most founders have never seen their own operation written down in one place. This is that document — built from what's actually in your systems, not from a single conversation about how things are supposed to work.
- What you get: a data inventory, an observed-reality report, a gap map, and the recorded review session — see below.
- How long it takes: 10 business days from when we have your credentials and the elicitation sessions are complete.
- What it costs: a flat fee for the whole engagement, agreed before we start — not an hourly meter, and no change orders inside the fixed scope below.
- What happens next: you talk to us, we agree the three systems in scope, then we get to work — see "What happens next," below.
What you get
Four deliverables, built in this order because each one depends on the last:
Structured data inventory
Every one of the three in-scope systems, catalogued — not read once and summarized, but inventoried as source material you can check against your own records.
Observed-reality report
What's actually happening, derived from system records rather than from the interviews. The same four-source method behind the Mochlos methodology, applied to your business specifically.
Gap map
Where what the team says diverges from what the systems show, and where your own systems contradict each other. Usually the single most valuable page in the package.
Session recording + notes
The deliverable review session with you, recorded and annotated, so nothing said in the room gets lost once the call ends.
How it runs
Read-only access to up to three of your systems — Monday, SharePoint, QuickBooks, whatever stack you already run; you specify which. One structured elicitation session with the founder, 90 minutes. Up to two further sessions with key operators, 60 minutes each. From there we build the inventory, the report, and the gap map, and deliver the whole package within 10 business days of credentials and sessions being complete.
What's explicitly out of scope
This is a diagnostic, not a build. It stays that way on purpose — a fixed scope is what makes the fixed fee and the 10-day SLA possible.
- No system configuration changes of any kind.
- No document drafting — no runbooks, SOPs, or role descriptions. (That's a different engagement.)
- No integration builds.
- No access to any system not named in scope.
You approve the export before we deliver it
The package we hand you is redaction-safe by process, not by promise: before delivery, you review and approve the export yourself. Nothing goes out that you haven't already seen and cleared.
How you'll know it worked
You should be able to name your top three operational gaps within 30 minutes of reading the deliverable. That's the bar we test the package against, together, in the review session — not a claim we make about it beforehand.
What happens next
Talk to us, and we'll agree which three systems belong in scope and get the sessions on the calendar. From credentials and sessions complete, the clock is 10 business days. You get the four deliverables in a review session, with time to work through what they mean for your business — and if what turns up is worth building on, this is the entry point into the full methodology, not a dead end.