PRICING
A clear scope.
A clear cost.
A useful proposal explains what you’re buying, what it costs to run, and what success means.
We have not published package prices yet. The framework below explains how a project should be scoped; it is not a quote.
ASSESS
Understand the opportunity.
Workflow mapping, baseline measurement, feasibility, options and a defined pilot scope.
BUILD
Prove one workflow.
Agreed inputs and integrations, implementation, evaluation, approval steps and handover.
RUN
Keep it useful.
Model usage, hosting, messaging where needed, monitoring and an agreed maintenance arrangement.
What changes the cost?
The number of workflows, integration complexity, data quality, transaction volume, security requirements and the amount of human review. A reliable estimate needs these inputs.
What about ownership?
A proposal should state who owns the code, data, infrastructure accounts and documentation, and identify any third-party licensing or reusable components. Our final commercial terms are still being prepared.
START WITH ONE GOOD QUESTION
What would you love
to stop doing manually?
Build your project briefA practical starting point. No technical knowledge needed.