Software development engagement models that fit your work
There are three software development engagement models to choose from: a fixed price project, a dedicated team, or care and support for software that's already live. Whichever you pick, your code gets the same reviews and testing, and you get regular written updates on progress.
Pick the model that fits your work
The model you choose decides what's locked in from the start, what can change along the way and how we bill you.
Fixed project
We build a clearly defined product for a price and timeline agreed up front.
Best when
- Your requirements are clear
- You need a fixed budget to plan around
- The work has a clear end point
Dedicated team
Engineers, designers and testers who work on your product and nothing else.
Best when
- Your product will keep growing
- Priorities change often
- You want to add skills quickly
Care and support
Regular, planned maintenance so your live software stays secure and keeps working.
Best when
- Your software is already live
- You need fast help with bugs
- You want updates done on a schedule
How each engagement model works
Here's how the three models compare on the things people ask us about most when they're choosing.
A set scope at an agreed price
After discovery, we write down every feature, screen and connection to other systems, along with what "done" will mean. You agree the price before any work begins, so you know the number you're planning around.
- Budget predictabilityHigh
- FlexibilityLow
- Speed to startMedium
- Your involvementLow
- Billing. Usually by milestone.
- Changes. We price any change separately and only add it once you approve.
A full time team of your own
You get a team with the skills your product needs, working on it full time. They follow your priorities from one sprint to the next, and the team can grow or shrink as your plans change.
- Budget predictabilityMedium
- FlexibilityHigh
- Speed to startFast
- Your involvementHigh
- Billing. Time and materials, explained below.
- More. See our dedicated development team service.
Steady care for live software
A small team gets to know your system, keeps watch over it, fixes bugs and keeps it up to date. Any time left over in the plan goes on improvements you choose.
- Budget predictabilityHigh
- FlexibilityMedium
- Speed to startFast
- Your involvementLow
- Billing. An agreed monthly plan.
- More. See our software maintenance and support service.
What does time and materials mean?
With time and materials, you pay for the work that actually gets done. That means the team's time at rates we agree in advance, plus any costs you've agreed to, such as software licences or cloud hosting. It's the natural fit for a dedicated team, because their work changes from one sprint to the next.
You still won't get a surprise bill. We agree the team size and a budget for each period up front, then log time against the items in your backlog and report it to you in plain terms.
Fixed price or time and materials?
- Already live?Choose care and support.
- Clear, stable scope?Choose a fixed price project.
- Priorities keep changing?Choose a dedicated team on time and materials.
- Not sure?We'll suggest one and tell you why.
You can mix them too. For example, you could build the first version as a fixed project and then carry on with a team or a support plan.
How the three models compare
| Feature | Fixed project | Dedicated team | Care and support |
|---|---|---|---|
| Best for | A defined product with a clear end point | Ongoing work on a growing product | Software that is already live |
| How it is billed | Fixed price, usually by milestone | Time and materials at agreed rates | An agreed monthly plan |
| Scope | Fixed once agreed | Set sprint by sprint | Fixes, updates and small improvements |
| Team | Sized to the plan | Chosen with you, only on your product | A small group who know your system |
| How long | The length of the project | As long as you need | Ongoing, reviewed regularly |
| Reporting | Progress against milestones | Sprint demos and time reports | Monthly summary |
| Code and designs | Yours | Yours | Yours |
What affects the cost?
We won't give you a fixed price until we understand the work. When we do, it depends mostly on:
- How many features and screens you need, and how many types of user
- Which other systems it connects to, such as a payment provider or your own databases
- Platforms: web, iOS, Android, or all three
- How sensitive the data is, for example health records or card payments
- Team size and how long the work runs
For a rough idea now, try the project estimator below. You'll have a written estimate to agree before any work begins. Our guide on how much custom software costs explains each factor. Whatever model you choose, the work follows our software development process.
Switching between models
- Fixed projectWe build the first version.
- Care and supportWe look after it once it's live.
- Key stepDedicated teamA team grows it as your plans get bigger.
The same people and documentation come with you when you switch. Just tell your delivery lead, and we'll make the change at a sensible point, such as the end of a sprint.
Estimate your project in a minute
Answer three questions to see a likely budget band and how long this kind of work usually takes. It's a starting point for a conversation, not a quote.
A medium web application
- Likely budget
- 5,000 to 15,000 USD
- Typical length
- 4 to 6 months
- Work can start
- Within one to two weeks
- How it's priced
- One fixed price, agreed first
A rough guide, not a quote. You get a fixed estimate in writing after a free discovery call, and the figures depend on the details we learn there.
Questions about engagement models
If you know exactly what you need and when it should be finished, a fixed project usually works best. If the work will keep going and your priorities shift, a dedicated team makes more sense. And if your software is already live and just needs looking after, go for a support plan. We'll help you decide in the first conversation.
Yes, and lots of clients do. A common pattern is a fixed project to build the first version, followed by care and support once it's launched.
Yes. Whichever model you choose, a second engineer reviews the code, automated tests run on every change, and new work is tried on a staging copy before it goes live. You also get documentation and regular written updates.
A fixed project lasts as long as the work does. Teams and support plans carry on for as long as you need them, and we review them together regularly, so you aren't tied into a long contract.
Usually within one to two weeks of agreeing the plan. It depends on which skills you need and how big the team is.
Not sure which model fits?
Tell us about your project, and we'll suggest the model that fits, with no commitment.