Dedicated team
A stable, embedded team for continuous product work with predictable monthly cost.
ENGAGEMENT MODELS
Four ways to work together, and how to pick one.
The commercial shape of an engagement changes what it is like to deliver. These are the four we offer, what each is genuinely good at, and where each one starts to strain.
01 / THE MODELS
What each model is
Fixed scope
A defined deliverable with an agreed price, suited to well-understood problems.
Staff augmentation
Specific skills added to your existing team for a defined period.
Discovery sprint
A short, fixed engagement that produces a plan and an estimate you can act on.
02 / CHOOSING
Which one fits the work
The wrong model makes good delivery expensive. These are the conditions under which each one is the right answer.
Choose a dedicated team when the roadmap is open-ended
Product work rarely finishes. If the backlog keeps refilling and continuity matters more than a fixed end date, a standing team costs less over a year than repeatedly rebuilding context.
Choose fixed scope when the problem is genuinely understood
A fixed price needs a fixed specification. That works well for a defined integration or a migration with known endpoints, and works badly for anything still being discovered.
Choose staff augmentation when you have the plan but not the hands
If your team knows what to build and simply lacks a skill or the capacity, adding people to your existing process is cheaper and faster than handing the work to a separate team.
Choose a discovery sprint when the estimate matters more than the build
A short fixed engagement that produces a plan, an architecture, and a costed roadmap. It is the least expensive way to find out that a project should be scoped differently.
03 / COMMERCIAL TERMS
What holds across all four
These terms do not vary by model. They are the parts buyers are most often surprised by, so they are stated here rather than buried in a schedule.
Ownership
The repository, the infrastructure, and the documentation are yours from the first commit, under every model.
Notice periods
Thirty days on a dedicated team or augmentation. Fixed-scope work ends when the deliverable is accepted.
Change handling
Scope changes are priced and agreed before work starts on them, never absorbed silently and invoiced later.
Rate transparency
One blended rate per role, published in the contract. No separate charges for project management.
Reporting
Progress, spend, and risks shared on an agreed cadence, including in the months that go badly.
Exit
Handover documentation and a walkthrough are part of the engagement, not a separate purchase.
04 / QUESTIONS
Common questions
Can we change models partway through?
Yes, and it is common. Discovery sprints frequently become dedicated teams, and dedicated teams sometimes reduce to augmentation once your own hiring catches up. We would rather change the model than keep an arrangement that has stopped fitting.
What is the minimum engagement?
A discovery sprint is the smallest sensible unit of work. Below that there is not enough time to understand the problem properly, and an answer produced without understanding it is not worth paying for.
How is a fixed price protected against scope creep?
By writing the scope down in enough detail that both sides can tell whether something is inside it. When a request falls outside, we price it separately rather than absorbing it and losing interest in the quality of the original work.
Do you work with our existing suppliers?
Regularly. Most systems have more than one party touching them. We agree interfaces and ownership boundaries at the start so integration problems have an owner rather than a debate.
05 / RELATED
Related reading
Have a complex technology challenge?
Start a conversation Bring us the problem.
Share the goal, the challenge, or the idea. We will help turn it into a clear digital path.