Skip to content

Every engagement is quoted individually.

There is no rate card here, because the work is not a commodity. A quote is built from the problem in front of us — and it is the same for the first conversation as it is for the final invoice. Here is exactly how it is put together.

Get a custom quoteSee what we build

What shapes a quote.

  1. 01

    The scope of the problem

    How much of the process moves onto the system, and how much of the existing work has to keep running alongside it.

  2. 02

    Where it has to work

    Web only, or web and mobile — the system of record is the same, the surfaces are not.

  3. 03

    Integrations and data

    Payment rails, third-party services and existing records that have to come across, cleanly.

  4. 04

    The depth of AI & automation

    A single intelligent workflow or automation across a whole process — the two are priced differently.

  5. 05

    Whether we operate it

    A one-off build handed over, or a product we host, update and watch as a running partnership.

How an engagement can run.

E1

Product build

Per scope

A fixed-scope engagement: frame the problem, design the system, engineer it, test and secure it, then ship. Quoted once, up front, after a scoping conversation.

E2

Build & operate

Per scope

We build the product and stay on it — hosting, updates and monitoring — as a running partnership rather than a handover.

E3

Problem framing

Per scope

Before any code: what the problem really is, what to build first, what to leave out, and a plan for what comes next.

What a quote states — plainly.

No retainer surprises, no invented line items. If something changes the scope, it is quoted before it starts.

Included

  • The scope, the deliverables and the timeline
  • The price for that scope, stated once
  • What is included, and what is itemised separately

Itemised separately

  • Third-party services and payment-rail fees
  • Hosting and infrastructure, when they apply
  • Anything outside the agreed scope — quoted before it starts

How to get a number.

  1. 01

    Tell us the problem

    Email the process that is still on paper, on spreadsheets or in the group chat. A paragraph is enough.

  2. 02

    A scoping conversation

    We map the problem, the users and the constraints, and tell you honestly whether software is the answer.

  3. 03

    A written quote

    Scope, deliverables, timeline and price — stated once, in writing, before anything is built.

Start with an email