Engagement models

Three ways to work with us.

Most of this page is about when each model is the wrong choice, because that is the part nobody tells you and the part that costs money later.

Fixed price
Agreed scope, agreed number, milestone billing.
Suits
- The scope is genuinely clear and unlikely to move
- A defined phase — a migration, a redesign, an MVP
- You need a number to take to a budget holder
Don't pick it if
You expect to change direction as you learn. Fixed price makes every change a negotiation, which is slow and sours the relationship.
Dedicated team
A team allocated to you, billed monthly.
Suits
- The product will keep evolving and priorities will change
- You want to redirect work without renegotiating
- You need continuity — the same people, month after month
Don't pick it if
The work is a one-off with a hard edge. You would be paying for availability you do not need.
Staff augmentation
Our engineers inside your team and your process.
Suits
- You already have a team, a backlog, and a way of working
- You need a specific skill — Flutter, AWS — for a period
- You want to keep architectural ownership in-house
Don't pick it if
You have nobody to own the work. Augmentation needs a technical lead on your side; without one it quietly becomes an unmanaged project.

Side by side

Billing, commitment, and who carries the risk

Attribute	Fixed price	Dedicated team	Staff augmentation
Billing	Per milestone, against agreed deliverables.	Monthly, per allocated person.	Monthly, per person.
Commitment	The project. No ongoing obligation after handover.	Usually a minimum term, then rolling.	Usually a minimum term, then rolling.
Who carries the risk	We carry the estimate risk, so the price includes a buffer for it. That is the honest trade: certainty costs a margin.	You carry the scope risk and get the flexibility in return. Cheaper than fixed price when the scope really does move.	You own delivery and direction. We supply capability, not management.

We have deliberately left rates and timelines off this page. Both depend on what you are building, and a number here that changes in the first call is worse than no number.

FAQ

Yes, and it is common — a fixed-price MVP that becomes a dedicated team once the product is live. We would rather change the arrangement than pretend the original one still fits.

Dedicated team, honestly — it fits how we work, and it is the model where running the infrastructure afterwards makes sense. But we will say if fixed price is genuinely better for your situation.

You do, under every model. The repository sits in your organisation and the infrastructure in your cloud account, so you are never locked in.

Not sure which one fits?

Tell us what you are building and what has gone wrong before. We will say which model we would pick and why.

Let's talk

Billing, commitment, and who carries the risk

Attribute	Fixed price	Dedicated team	Staff augmentation
Billing	Per milestone, against agreed deliverables.	Monthly, per allocated person.	Monthly, per person.
Commitment	The project. No ongoing obligation after handover.	Usually a minimum term, then rolling.	Usually a minimum term, then rolling.
Who carries the risk	We carry the estimate risk, so the price includes a buffer for it. That is the honest trade: certainty costs a margin.	You carry the scope risk and get the flexibility in return. Cheaper than fixed price when the scope really does move.	You own delivery and direction. We supply capability, not management.

We have deliberately left rates and timelines off this page. Both depend on what you are building, and a number here that changes in the first call is worse than no number.

Three ways to work with us.

Fixed price

Dedicated team

Staff augmentation

Billing, commitment, and who carries the risk

Not sure which one fits?

Three ways to work with us.

Fixed price

Dedicated team

Staff augmentation

Billing, commitment, and who carries the risk

Not sure which one fits?