Engagement Models & Pricing

There are three ways to pay for software work, and the right one depends entirely on how well the scope is known. Fixed price suits work that can be fully specified in advance. Time and materials suits work that will change as you learn. Dedicated capacity suits ongoing work with no defined end. Choosing wrong is the most common reason outsourcing relationships turn adversarial.

Fixed price

You agree a scope, a price, and a date. It works when the requirements genuinely can be pinned down, and it fails badly when they cannot — because every change becomes a negotiation instead of a decision.

  • Best for: well-understood scope, a migration, a defined integration, a rebuild of something that already exists.
  • You get: budget certainty and a clear definition of done.
  • The trade-off: change costs more, because the price already priced in the risk of it.
  • Requires: discovery first. We do not quote fixed price on a brief alone.

Time and materials

You pay for the effort actually spent, at agreed rates, with a cap and regular review. It is the honest model for anything genuinely new, because it does not force either side to pretend the scope is knowable.

  • Best for: new products, evolving requirements, and work where discovery continues as you build.
  • You get: the ability to change direction without renegotiating a contract.
  • The trade-off: you carry the scope risk, so forecasting and reporting matter more.
  • We include: an agreed cap and a regular review point, so it never runs unbounded.

Dedicated capacity

You pay monthly for an agreed team, and direct their work yourself. It is the simplest model to reason about, and the most economical over a long horizon because ramp-up is paid once rather than at every project boundary.

  • Best for: ongoing product development with no defined end date.
  • You get: predictable monthly cost and a team that accumulates context.
  • The trade-off: it only pays off over months, so it is a poor fit for short needs.
  • Notice periods for scaling down are agreed at the start.

How we actually decide

We propose the model that fits the work, not the one that maximises the contract. If you ask for a fixed price on something that cannot be specified, we will say so and explain what it would take to get there — usually a short discovery phase, which you can then take to any vendor.

Choosing a model
If...ChooseBecause
The scope is fully known and stableFixed priceBudget certainty is worth the change-control overhead
You are still learning what to buildTime and materialsYou can change direction without a contract amendment
The work is continuous with no end dateDedicated capacityRamp-up is paid once instead of every project
You need one specific skill brieflyTime and materialsNo ongoing commitment to unwind afterwards

Frequently asked questions

What are your rates?
Rates depend on role, seniority, and engagement length, so a single published number would be misleading. Tell us the roles you need and the duration, and we will send a rate card that reflects your actual situation.
Do you charge for discovery?
Yes, and deliberately. A paid discovery produces a real plan — architecture, scope, and estimate — that belongs to you and that you can take to another vendor. Free discovery produces a sales document.
Are there minimum contract terms?
They vary by model. Dedicated capacity has a minimum because ramp-up is a real cost; time and materials generally does not. Notice periods are always mutual.
How do you handle scope changes on a fixed-price project?
Through a written change request with its own estimate, agreed before the work happens. The point is that nobody discovers a cost after the fact.

Tell us what you are building

Send a short description of the system and the constraint you are hitting. We reply within one business day.

Book a consultation