We have seen the deck. Most organisations that come to us have already paid for the deck. It describes a transformation, a roadmap, a set of use cases ranked by impact and feasibility, a reference architecture, and a note about change management. It is usually well-written. It is usually not acted on. Not because the thinking was wrong, but because a deck cannot tell you what you will actually find when you connect to the real data and run the first model against the first workflow.
The alternative is discovery that writes code. Not a blueprint for a future system. A contained, working proof against a real use case, built in a fixed time window, against the actual data, with a defined success criterion that both sides agree on before work starts. The output is not a recommendation. It is a system, or the first piece of one, that the organisation can observe running. The strategy emerges from what you learn.
The alternative to the deck is discovery that writes code.
This matters for risk management as much as it matters for learning. A bounded diagnostic with a fixed fee is a different risk profile than an open-ended transformation engagement. The client knows what they are paying, what they will receive, and what question will be answered. We know what we are accountable for. Neither side is betting on a plan that has not touched reality yet.
What we build in a discovery is explicitly designed to scale into production or to be thrown away, and both outcomes are fine. If the proof works, the next phase has a foundation: real data, real eval results, real edge cases documented. If it does not work, the client has spent a defined budget to learn something true, which is more valuable than spending a larger budget to learn something wrong six months later. The honest version of this conversation is that we cannot always tell you in advance which outcome you will get. We can tell you that you will know sooner, and that knowing sooner is worth paying for.