Use the second meeting to test the gaps that a polished demonstration leaves out.
We want you to enjoy a good demonstration and then ask us the difficult question. What happens with your files, your missing information and the exception that arrives at the worst possible time? A polished example deserves curiosity. Your operating process deserves a more demanding test.
We would show you the preparation behind the output. Which inputs were supplied? What was mapped beforehand? What remains a human decision? You should be able to tell what you are seeing without guessing how much of the work happened off-screen.
Move beyond the polished example
The most useful second meeting begins with the input. What was supplied? Which fields were required? Who mapped them? What information was missing? These questions reveal whether the proposed workflow fits the data the organisation actually produces. They can also identify a small preparatory step that would make the work much more reliable.
Then introduce an exception. Change a reporting period, remove an expected column or include an ambiguous transaction. The aim is to see how the workflow responds. Does it stop, ask a useful question or proceed with an assumption? A clear request for clarification can be more reassuring than an uninterrupted performance.
We would show you the preparation behind the output.
An illustrative board-pack demonstration might produce an attractive summary from a complete set of management accounts. A harder test would include a missing comparative and an unexplained change in a key measure. The workflow should make those gaps visible. A reader should be able to distinguish the confirmed picture from the interpretation that still needs discussion.
Test the awkward cases
Our preferred second meeting would include someone who knows where the process breaks. Let them remove a column, change a period or challenge an explanation. A workflow that asks a sensible question at that point can tell you more about its usefulness than one that finishes every time.
The human experience deserves its own test. Give a likely user the instructions and observe where they hesitate. They may find a step confusing that seems obvious to the person who built it. That is valuable feedback about the design, especially if the goal is capability transfer.
A demonstration can also help establish the appropriate scope of an engagement. It may show that a file-based workflow is sufficient for the immediate question. It may expose a genuine need for integration. It may reveal that the business first needs to agree a definition. Each outcome can improve the investment decision.
We believe customer-ready demonstrations should show the inputs, the output and the review that connects them. A short video can introduce the possibility. A conversation can explore whether it fits your circumstances. We want the audience to come away with useful questions, not a mistaken impression that every business has the same data or needs the same solution.
Bring the example your team finds awkward. Ask us to explain a failure as carefully as a successful output. We want the conversation to leave you better able to judge what fits your business, including whether a smaller piece of work is the right next step.
Examples in this essay are illustrative, rather than accounts of client engagements.