Book a call
Thirty minutes. No deck, no demo.
You describe the operation and where it gets stuck. I ask the questions I would ask in the first hour of an engagement. It is a conversation between two people who run things, not a sales call with a discovery script.
October 2026
Loading times
Pick a day to see the times.
Would rather write it down? .
What to bring
Nothing prepared. Not a specification, not a requirements document, not a budget. The problem as you would describe it to a colleague is exactly the right level of detail.
What you get out of it
- A read on whether the problem you named is the real one, or a symptom of something one step upstream.
- A rough sense of what changing it would involve — process, structure, systems, or some combination of the three.
- A straight answer about whether this is work I should be doing, including when it is not.
What happens after
If there is something worth doing, the usual next step is a short discovery engagement — time inside the operation, ending in a written map of how it actually runs and a costed plan of what to change and in what order. That document stands on its own: if you took it and built with somebody else, it would still have done its job.
What it asks of you
Time with the people who do the work, not only the people who describe it. One person inside the business who can answer a question and make a call — things slow down without them. And a decision when the options are on the table; options are only useful to someone willing to choose between them.