$25k – $60k
A focused tool
A single workflow done properly — a custom internal tool, a dashboard, an integration between two systems, or automating one repetitive process. Narrow scope, one or two user types.
Pricing
Plan your next step with confidence.
Indicative investment ranges, what shapes the scope, and how we agree the work before it begins. Enough to size your next step with confidence and start a useful conversation.
Indicative price ranges
$60k – $180k
A mid-sized system
A system several people rely on daily — multiple workflows, real data modelling, a few integrations, more than one kind of user. The operational backend behind a growing operation.
$180k+
A platform
Infrastructure-level work — connected field systems, monitoring platforms, LIMS-style data systems, or a platform built for the next few years of growth. Multiple subsystems, hardware, and integrations.
Indicative ranges for planning, not quotes. Source, documentation and runbooks are included. Ongoing operations support is usually a separate, optional retainer.
What shapes the investment
The work determines the scope.
These six factors help us understand what your system needs.
Read the full breakdownHow clear the scope is
A well-understood problem costs less than a vague one. Uncertainty is the most expensive line item — which is why we resolve it before quoting a build.
How many kinds of user
One user type is straightforward. An admin, an operator, a field tech, and a manager — each with different needs and permissions — is four problems, not one.
How much it integrates
A system that stands alone is cheaper than one that has to talk to hardware, legacy databases, or third-party tools that don't share an API.
The state of your data
Clean, structured data is a head start. Data trapped in spreadsheets, inconsistent formats, or one person's head has to be understood and reshaped first.
Compliance & reliability needs
Audit trails, traceability, security, and systems that can't afford downtime all raise the bar — appropriately. Consequential systems cost more because they have to be right.
Depth of understanding required
Some problems can be specified in a conversation. Others need us in the field, watching how the work actually happens, before anyone can say what should be built.
Start a conversation
Understand the work before pricing the build.
A fixed-fee Discovery Sprint maps the work and gives you a grounded plan, including an honest assessment of whether to build at all.