How we work together
No jargon, no pressure, and no assumption that the answer is software.
We begin with your people, workflows, economics, and available alternatives. The right first step may be training, a focused working session, workflow and adoption support, an existing product, or a custom system built for you.
Most engagements are bounded pieces of work that stand on their own. Some lead somewhere else afterward; plenty do not, and that is a perfectly good outcome.
A brief conversation to understand the problem, who it affects, what you have already considered, and whether there is a useful next step.
What you get: An honest initial perspective, and a recommended next conversation or engagement.
This is a fork, not a queue. Where we go depends on what the first conversation surfaced.
Worth saying plainly: recommending a product you can buy elsewhere, or nothing at all, are both legitimate results of this step.
Build capability, improve a repeatable workflow, create useful adoption resources, resolve a decision, or define a custom system worth building.
The standard: every paid first engagement should create value that stands on its own, whether or not anything follows it.
Review what people actually used, what behaviour changed, what value it created, and what still needs attention.
What follows: follow-up training, adoption support, a custom system built for you, or stopping. All four are legitimate.
When a specific workflow is already causing real friction, a focused working session is often a better starting point than training. We take one priority workflow, map how it runs today, and work out what is actually worth doing about it.
What you get: a mapped workflow, a problem-value estimate, a review of existing products and other alternatives, the implementation constraints we would face, and a recommendation for the smallest worthwhile next step.
The output is designed to be useful whether or not I do any further work. If the right answer turns out to be software you can buy, you will have that in writing.
$2,000 | one priority workflow
If discovery supports a tailored implementation, we agree on the outcome, responsibilities, acceptance criteria, timeline, and firm price before work begins.
Pricing follows scope, so I do not publish a range here. A consequential workflow with clear economics and a system that has to be right the first time are different projects, and quoting them from the same band would not help either of us.
Where a solution creates a genuine ongoing operational need, we define monitoring, response expectations, included support, scheduled value reviews, and how new features are priced — all before launch.
Not every engagement requires ongoing support, and I would rather say so than attach a retainer to something that does not need one.
Tell me what your team is trying to improve.
No formal preparation is required. A real example of the workflow is helpful if you have one.