Engagement models for outsourced project outcomes
An engagement model decides who owns what: the scope, the day-to-day decisions, the quality of the result and the exit. Choosing it before choosing a vendor avoids the most common outsourcing failure, where a buyer expects an outcome but has bought hours. OutsourcingVN leads with one model, milestone project delivery, and offers others only where they fit a defined need.
Submit a project View our workReviewed by David Nguyen (CEO) · Updated 5 Oct 2026
The default: milestone project delivery
Use this model when you can define an outcome and want a provider to own a planned body of work. Scope, dependencies, acceptance criteria and the exit are agreed before build work starts, and the project advances one accepted milestone at a time.
-
You own
The business outcome, product and priority decisions, access to your systems and people, and milestone acceptance.
-
Netbase owns
The delivery plan, team composition, technical quality, reporting against the plan, change impact analysis and the handover.
-
Commercially
Most Netbase projects are agreed as fixed-scope contracts with an agreed total after discovery, with milestone-based arrangements also available. Terms are set per project in the proposal; none are published here.
This is the model used for both Phase 1 services, Custom Product Engineering and AI Workflow Automation. The project delivery page explains how it runs from proposal to exit.
Engagement models compared
-
Milestone project delivery (default)
- Best fit
- An outcome you can define, delivered as a planned body of work
- Who steers scope
- Shared: you own the outcome and acceptance, Netbase owns the delivery plan
-
Discovery or audit first
- Best fit
- The main risk is missing information; the project produces a decision such as a scope, an architecture assessment or an audit report
- Who steers scope
- A short, bounded project agreed with you
-
Managed operations after handover
- Best fit
- Maintenance, monitoring and continuous improvement of a system that has already been delivered and assessed
- Who steers scope
- A separately scoped service
-
Dedicated capacity under Netbase management
- Best fit
- A backlog you prioritize, managed and reported on by Netbase; a secondary option, not the default
- Who steers scope
- You, through the backlog
Where dedicated capacity needs to stand for years rather than one project, the offshore development centre guide covers how to set it up, govern it and plan its transfer.
Netbase also offers dedicated development teams, on-demand support and fully managed delivery. On OutsourcingVN these sit behind the project model: they are proposed when a project's shape calls for them, and each one still needs a defined responsibility split, reporting and exit.
How to choose
Answer four questions:
-
Can you describe the result you will accept?
If yes, milestone project delivery fits. If not yet, start with discovery.
-
Who will make day-to-day product decisions?
If you want to direct the backlog yourself every week, dedicated capacity may suit you better, but you then carry more of the delivery risk.
-
Is the system already built and stable?
If the need is to keep it running and improving, a managed operations scope is the right frame, starting with an assessment; managed outcomes explains how objectives and review periods replace bought hours.
-
How will the engagement end?
Every model here has a planned exit. If you cannot describe one, the scope is not ready.
Moving between models
Models can follow each other. A common sequence is a discovery milestone, then milestone project delivery for the first release, then a separately scoped managed operations service once the system is live and has been assessed. Each step has its own scope, acceptance and exit, so you can stop after any of them without losing what has been delivered. When the gap is one skill rather than a release, such as an architecture review or a platform migration, a specialist sprint with a fixed timebox and exit condition can sit between those steps.
When the gap is leadership rather than delivery capacity, fractional CTO and AI transformation advisory sits alongside these models rather than replacing them: a retained advisor can set the roadmap that later becomes a project, a sprint or a managed operations scope. The fractional CTO versus full-time CTO comparison helps decide whether that seat is now right for your stage, and the AI transformation roadmap guide sets out what it should tackle first. Where the question is whether to buy an outcome or add people under your own direction, the project outsourcing versus staff augmentation comparison works through that choice in more depth, and where the question is whether to outsource at all rather than hire, the in-house versus outsourced development guide compares both against building the capability internally.
What stays the same in every model
-
One accountable operator
Netbase JSC contracts and manages the work, including any specialist or disclosed partner who contributes.
-
Written scope and change control
Changes to cost, time or scope are visible decisions.
-
Security practices
Secure code review, role-based access and NDAs for contributors.
-
Intellectual property
For custom development, intellectual property created for you belongs to you.
-
AI-assisted engineering under human review
Any restriction you set is written into the plan.
Questions to ask any provider
Whichever provider you choose, these questions show quickly whether an engagement model will protect the outcome you are paying for:
- Who is accountable if a milestone is late or fails acceptance, and what happens next?
- How are changes classified, approved and reflected in the plan?
- Which people, locations and subcontractors will touch our code and data?
- What exactly is handed over at the end, and can we run the system without you?
- How do we leave the engagement early, and what does that cost in time and access?
The comparison of software outsourcing companies uses criteria like these; note that it is published by OutsourcingVN, which is operated by Netbase JSC.
What we do not offer
We do not sell anonymous seats, CV volume or indefinite staffing with no defined deliverable, and we do not act as a marketplace where you hire individual freelancers. We also do not promise a business result that depends on factors outside delivery control, such as sales or user adoption. Where an engagement needs people onsite, that is scoped as a specific activity; see global delivery.
Evidence
The Work records show delivered project scope under this model, labelled with their evidence level and limitations. The methodology page explains how those records and every other claim on this site are reviewed.
Check the model against the operating plan
Use global delivery to assign accountability across contributors. Work through time-zone collaboration, security and data boundaries and total delivery cost before comparing capacity with a fixed scope. These worksheets clarify buyer responsibilities without promising a universal saving. Custom Product Engineering is the commercial route for a bounded build; the multi-vendor marketplace record provides scope evidence, not evidence that every engagement model fits the same project.
Not sure which model fits?
Send the outcome and we will recommend one: submit a project. OutsourcingVN is operated by Netbase JSC and is Netbase's own outsourcing-services platform.