Pricing

How we
price.

No surprises. Fixed scope for audits and sprints; a weekly retainer plus agreed scope for builds; a monthly retainer for research. Final scope and cost are confirmed after a discovery call.

Engagement models

Four ways to work together.

Most work starts with an audit or a two-week sprint. We'll tell you plainly which model your problem needs.

Fixed scope01

Audit

Find what's slow, risky, or rotting before you spend on the wrong fix.

What's included
  • Architecture diagram
  • Code-quality + security report
  • Prioritised remediation plan
  • Live walk-through
Timeline
1–4 weeks
Fixed scope02

Sprint

A focused two-week push to ship one well-defined thing: a feature, a prototype, a fix.

What's included
  • Discovery + scope doc
  • Working feature or prototype
  • Tests + code review
  • Deploy + handover notes
Timeline
2 weeks
Weekly retainer + agreed scope03

Build

Custom platforms (ERP, CRM, LMS, SaaS) and agentic AI, built to grow with you.

What's included
  • Discovery + scope doc
  • Production deployment
  • Handover + documentation
  • 30-day support window
Timeline
4–12 weeks
Monthly retainer04

Research / R&D

Proof-of-concepts, applied research, and university partnerships at the AI/SE intersection.

What's included
  • Quarterly report
  • Working prototypes
  • Co-authored papers (optional)
  • Tooling + infra
Timeline
Ongoing
How pricing works
Fixed

Fixed where it counts

Audits and sprints are fixed scope. You know exactly what you get, and what it costs, before we start.

Retainer

Flexible where it flexes

Builds run on a weekly retainer against agreed scope; research runs monthly. You pay for the time, not for surprises.

Discovery

Confirmed after a call

Every engagement is confirmed after a short discovery call, with final scope and cost in writing. No obligation, no lock-in.

What actually moves the number.

Why there’s no price list

We don’t publish a rate card because the same job can differ tenfold depending on what we find. What we will promise: a written figure before anything starts, and no surprises after it.

01

How much of the system we touch

A single feature in a healthy codebase is a different job from the same feature in one nobody has maintained for three years.

02

Whether the data is ready

Most AI work is really data work. If the data needs cleaning, labelling, or validating first, that is the bulk of the estimate.

03

Prototype or production

Something to show a board next month, versus something that holds up under real traffic with monitoring and on-call, are different engagements.

04

How long we stay on

Every build includes a support window. Extending it past that is a separate, smaller number.

Every number is
confirmed on a call.

Every number is confirmed after a discovery call, with no obligation. Tell us the problem and we'll come back with the right model, the scope, and the cost in writing.

Book a call