Skip to main content

What are you looking for?

Explore our services and discover how we can help you achieve your goals

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 work

Reviewed by Huy Nguyen (David), CEO · Updated 14 Nov 2026

star

Which engagement model fits your project?

Each of these three models has its own page. Terms are agreed per project in the proposal.

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 after discovery, with milestone-based arrangements also available. A contract of this kind places the risk and responsibility for cost on the provider once scope is agreed, not the buyer. Terms are set per project in the proposal, the engagement's statement of work; none are published here.

On payment methods, Netbase JSC is paid by bank transfer to the company account of Netbase JSC or through PayPal Business, PayPal's own product for businesses to accept and send payments.

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

Model Best fit Who steers scope
Milestone project delivery (default) An outcome you can define, delivered as a planned body of work Shared: you own the outcome and acceptance, Netbase owns the delivery plan
Discovery or audit first The main risk is missing information; the project produces a decision such as a scope, an architecture assessment or an audit report A short, bounded project agreed with you
Managed operations after handover Maintenance, monitoring and continuous improvement of a system that has already been delivered and assessed A separately scoped service
Dedicated capacity under Netbase management A backlog you prioritize, managed and reported on by Netbase; a secondary option, not the default 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:

  1. Can you describe the result you will accept?

    If yes, milestone project delivery fits. If not yet, start with discovery.

  2. 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.

  3. 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.

  4. 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 leadership rather than delivery capacity, fractional CTO and AI transformation advisory sits alongside these models: a retained advisor sets 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 right for your stage, and the AI transformation roadmap guide sets out what it should tackle first. To add people under your own direction instead, see staff augmentation and the project outsourcing versus staff augmentation comparison; to decide whether to outsource at all, the in-house versus outsourced development guide compares both.

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

    Every change request affecting cost, time or scope is a visible decision.

  • 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.

Where does AI help, whichever model you choose?

Every model carries the same practice: AI-assisted engineering under human review, inside Netbase's own delivery team. AI tools help draft code and tests, summarise changes and prepare documentation; a named engineer reviews and owns every change, and any restriction you set on AI tool use is written into the plan. The project delivery page explains where this fits against milestones and acceptance.

Questions to ask any provider

These questions show 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. 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.

Common questions

Milestone project delivery: scope, acceptance criteria and the exit are agreed before build work starts, and the project advances one accepted milestone at a time.

Yes. A common sequence moves from a discovery milestone to milestone project delivery, then to a separately scoped managed operations service once the system is live and assessed.

One accountable operator, written scope and change control, security practices, intellectual property ownership for custom development, and AI-assisted engineering under human review.

Talk to Huy Nguyen (David), Founder and CEO of Netbase JSC: message him on WhatsApp at +84 937 869 689 or email project@netbasejsc.com. You can also send your brief through the project request form. Say which workflow or system the project concerns and what has to stay unchanged; the first step is a discovery conversation, and scope and milestones are agreed after it.

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.

Tell us what you want to build or automate.

Submit a project