Pricing

Priced around
the risk

We do not publish a price list, because a number that fits one team is wrong for the next. We scope the work, prototype the riskiest flow, then give you a written estimate with the assumptions attached.

Book a scoping callSee delivered work
Engagement models

Three ways to work

The right model depends on how much certainty you have. Most engagements start with a prototype and move into one of the other two.

Start here

Prototype sprint

A fixed-scope working prototype of the core workflow, built in weeks so the riskiest assumptions are tested before a production commitment.

Best for: Teams that need to prove a workflow, integration or AI feature before funding a full build.

  • Discovery and workflow mapping
  • A working prototype of the core flow
  • Architecture and integration notes
  • A written production scope and estimate

Fixed fee, agreed before work starts.

Most common

Fixed-scope milestone

A defined production deliverable broken into milestones, with a written scope, acceptance criteria and a clear handover.

Best for: Teams with a well-understood workflow and a defined outcome.

  • Production design and build
  • QA, security review and deployment
  • Documentation and handover
  • Milestone-based payments

Milestone-based, tied to accepted deliverables.

Evolving product

Dedicated sprint retainer

Continuous delivery with a dedicated team, bi-weekly demos and a roadmap that adapts as you learn.

Best for: Products that will keep evolving after the first release.

  • A dedicated engineering team
  • Bi-weekly working demos
  • Architecture and delivery ownership
  • Ongoing iteration and support

Monthly retainer, reviewed against the roadmap.

Always included

What the number covers

Every engagement is quoted as a complete path to a working system you own — not an estimate that stops at “development”.

  • Discovery, workflow mapping and scope definition
  • Solution and integration architecture
  • Design, build, QA and security review
  • Deployment into your cloud and tenancy
  • Documentation and a working handover
  • Full source code and IP ownership
Cost drivers

What moves the number

Scope and certainty

A well-defined workflow with clear acceptance criteria is easier to fix-price than an open-ended product discovery.

Integration surface

Each external system — ERP, EHR, policy admin, payment, identity provider — adds interface, testing and failure-handling work.

Compliance and evidence

Audit trails, access reviews, data residency and retention requirements add design and verification work that cannot be skipped later.

Data migration

Moving and reconciling existing records is often the least visible and most underestimated part of a replacement project.

Non-functional requirements

Availability targets, throughput, offline support and multi-region resilience change the architecture and the testing regime.

Ongoing ownership

Whether you take the system in-house or need ongoing support changes the handover and run-cost model.

Questions

Pricing, answered

There is no honest single number. Cost is driven by scope, integrations, compliance requirements and non-functional targets. We scope the work, prototype the core flow, then give you a written estimate with assumptions before committing to a production build.

A prototype turns assumptions into something you can test. It reduces the risk of funding a long build around a workflow that does not survive contact with real users, and it gives both sides a shared basis for estimating production work.

Yes, when the scope is clear enough to define acceptance criteria. For evolving products, a dedicated sprint retainer is usually a better fit than pretending the scope is fixed.

Discovery, architecture, design, build, QA, security review, deployment and handover are included in the scope we quote. Third-party licences, infrastructure spend and provider fees are separate and stay in your accounts.

Fixed-scope work is billed against accepted milestones. Retainers are billed monthly against an agreed roadmap. The schedule is written into the agreement before work starts.

Changes go through an explicit change-control step: we describe the impact on scope, sequence and cost, and you decide before the work is added. The goal is no silent scope drift in either direction.

Yes. You own the source code, intellectual property, data and cloud infrastructure. There is no vendor lock-in and no per-seat licensing to us.

Yes. Many engagements begin with a scoping review or a single prototype sprint focused on the highest-risk workflow, then expand once the direction is proven.

SEE THE PROTOTYPE WE'D BUILD

Give us 30 minutes. We'll show you the fix.

Tell us where the work slows you down. We'll come back with a prototype of the custom software, internal tools or automation we'd build to remove it — working in weeks, and you own the code.