What a discovery actually finds.
Gate one of every engagement is an assessment that stands on its own. This is what it looks at, what it produces, and what you are left holding if you decide to stop there.
Four things, in the order that matters.
The process as it actually runs
Not the documented version. Who touches the work, in what order, how many times it changes hands, and where it waits. Most of the cost is in the waiting and the rework, and neither appears on a process map drawn from memory.
The systems and where they disagree
An inventory of what holds the record, what holds a copy, and which copy people actually trust. Integration points, manual bridges, and the spreadsheets doing load-bearing work between two platforms.
What it costs you today
Hours by role, cycle time, error and rework rates, and the revenue or working capital consequence where there is one. This is the number your internal business case gets built on, so it is estimated conservatively and the method is shown.
What is worth doing, ranked
Every candidate scored on effort against impact, with the dependencies named. Including the ones we would not do, and why. A ranked list is only useful if it is honest about the bottom of it.
A findings report, and it is yours.
Whether or not you engage us to build anything.
Current-state map. The process end to end, with the handoffs, wait states, and manual bridges marked. Usable in front of your own executive team without translation.
Systems inventory. What runs where, what talks to what, and which connections are fragile.
Ranked opportunity list. Each item with an effort estimate, an impact estimate, and the operating metric it would move.
A recommended first move. One thing, with the reasoning. Sequencing matters more than ambition, and the first build should be the one that de-risks the rest.
Bounded, and light on your team.
A scoping conversation
30 minutes. What hurts, what you have tried, and whether an assessment is even the right next step. Roughly half the time the answer is that a narrower conversation would serve you better, and we say so.
Stakeholder sessions
The people who run the process, not only the people who own it. Usually a handful of sessions across operations, finance, and technology.
Systems and data review
Read access where it is straightforward, walkthroughs where it is not. No changes to anything in production.
Findings, presented
The report, walked through with your team, with the ranked list open to challenge. If we have the priorities wrong, that session is where it gets fixed.
Start with the process that costs you most.
A conversation first. A structured assessment when it earns one.