A first conversation
Tell us about the process, the problem, and the tools involved. We talk through whether custom software or a simpler change makes sense.
Pricing & project scope
Every engagement is different. You should still know what you’re paying for, what happens next, and who is responsible for the work.
Your process. Your tools. Connected.
01 / How an engagement works
The first conversation is free. The project is scoped before development begins.
Tell us about the process, the problem, and the tools involved. We talk through whether custom software or a simpler change makes sense.
We map the relevant workflow and technical requirements. Any deeper discovery work is agreed before it starts.
You receive the work, price, timeline, and responsibilities in writing. Integrations, dependencies, and support are discussed as part of that scope.
Review working software, prepare the team, and agree on the launch. Changes outside the original scope are discussed before additional work proceeds.
02 / What shapes the price
The number of workflows, roles, screens, and exceptions affects the work involved.
Existing data quality, migration work, and third-party integration constraints shape the technical scope.
A clean handoff and ongoing support are different needs. We agree on the level of help your team wants.
Sessions are scoped by audience, format, preparation, and travel. You receive the price before booking.
A few useful answers
We do not publish a universal starting price because the work varies. The first consultation helps establish what needs scoping.
Custom projects are scoped around the work and support you need. Any recurring hosting, third-party services, or maintenance costs should be identified in the proposal.
We discuss the effect on price and timeline before proceeding with a change outside the agreed scope.
Keep exploring
Bring the process, the problem, or the idea. The first conversation is free.