AI-Ready ODC
Three ways to work together
The right model depends on whether you are buying capacity, a capability, or an outcome.
Dedicated team
A team that works only on your product, directed by you. Suits organisations that need a capability they do not have internally and expect the work to continue for quarters rather than weeks.
Best when: the roadmap is longer than the current team can absorb, and you want continuity of context rather than a rotating cast.
Team extension
One or more engineers inside your existing team, working to your process, your standards and your stand-ups. The lowest-friction way to start, and the easiest to judge honestly after a month.
Best when: you have engineering leadership already and need capacity in a specific stack.
Fixed-scope project
A defined outcome, delivered and handed over. Suits well-understood problems — a migration, an integration, an MVP with a clear boundary.
Best when: the outcome is describable in advance and you do not want to manage a team to get there.
Choosing between them
- Buying capacity for a team you already run → team extension
- Buying a capability you do not have → dedicated team
- Buying an outcome with a clear edge → project
If it is genuinely unclear, extension is the cheapest way to find out, because it is the easiest to stop.
Frequently asked questions
Which engagement model should we start with?
If you have an engineering team and need capacity, start with team extension. If you need a whole capability you do not have, a dedicated team fits better. If the outcome is well defined and finite, take it as a project.
Can we move between models?
Yes, and it is common. Several engagements start as one or two engineers inside an existing team and grow into a dedicated team once the working relationship is proven.
What is the minimum commitment?
Dedicated teams are quarterly because ramp-up cost makes anything shorter bad value for both sides. Project work is scoped to the outcome rather than a period.
How is pricing structured?
Dedicated teams and extension are priced per engineer per month. Project work is priced to the scope. We do not price by hours logged, because that rewards the wrong behaviour.