This guide is for founders, product owners and COOs who must decide who runs a new platform after launch. It sits next to the agentic AI automation service, because products with AI agents inside need a running owner from the first day in production. If you are moving a running engagement from one vendor to another, the transition and knowledge-transfer plan covers that path.
In this guide
- What does build-operate-transfer mean for a software product?
- When should a partner run your platform before handing it over?
- Which engagement shape fits your product?
- How do you know the platform is ready to transfer?
- What goes into a build-operate-transfer contract?
- When should you not use build-operate-transfer?
- Where AI fits
- What delivery record exists, and what does not
- Alternatives: other ways to get a platform running without an operations team
- Limits of this guide
- Frequently asked questions
- Next step
What does build-operate-transfer mean for a software product?
Build-operate-transfer (BOT) started as a project-finance model in which a private company builds and runs an asset under a concession before handing it to the public owner, as the Wikipedia entry on build-operate-transfer describes. Software vendors use the name for offshore teams that move to the client.
For a software product, the object of the transfer is different. What moves is the running platform: production environments, cloud and third-party accounts, release pipelines, monitoring, on-call duty, runbooks and the product backlog. People may or may not move with it. If your question is who should employ an offshore team, the comparison of an offshore development center, a captive center and staff augmentation answers it.
A product BOT has three phases. In the build phase the partner ships the first release. In the operate phase the partner runs production while your team joins step by step. In the transfer phase your team takes over each duty once it passes a written test, and the partner steps back to an agreed support role or leaves.
When should a partner run your platform before handing it over?
Choose an operate phase when three conditions are true at the same time. You do not yet have people who can deploy, monitor and recover the platform. The product cannot wait for that team, because customers, partners or staff will use it from launch. And you want to own and run the platform yourself in the long term.
An operate phase also helps because usage patterns, data volumes and integration failures show up only under real traffic. The team that built the system fixes them quickly and writes the runbook from real incidents rather than guesses.
It is harder to justify when the platform is simple, rarely changed and already hosted on a managed service. In that case a clean code drop with documentation and a short support window costs less and leaves fewer dependencies.
Which engagement shape fits your product?
| Option | Who runs production | Main risk | Choose it when |
|---|---|---|---|
| Build and hand over | Your team from launch | Your team learns on live incidents | You already have an operations team and a simple platform |
| Build-operate-transfer | The partner, then your team after written tests | The operate phase drags on without exit criteria | You will own the platform but have no operations team yet |
| Build-operate (no transfer) | The partner, long term, under a support scope | Dependency on one partner | Running software is not where you want to build skills |
| In-house from day one | Your own hires | Slow start while you recruit | Engineering is your core business and you can hire now |
The deciding question is not cost but where you want the operating skill to live in two or three years. If the answer is inside your company, plan the transfer from the start. If the answer is with a partner, a build-operate arrangement with clear exit rights is more honest than a transfer you never intend to trigger. If the platform runs AI agents, measure their cost per accepted task during the operate phase.
How do you know the platform is ready to transfer?
Handover should be a test your team passes, not a meeting. The Google SRE book describes a production readiness review that checks architecture and dependencies, instrumentation and monitoring, emergency response, capacity planning, change management and performance before a team accepts a service. A product BOT can use the same areas as transfer gates.
-
Ownership gate
Every domain, cloud account, code repository, app store listing, payment and messaging account and API key is registered to your company, with the partner as a named user you can remove. Pass when your administrator can list every account and its owner without asking the partner.
-
Change gate
One of your engineers ships a small production change using only the written release runbook and the pipeline, while the partner watches and does not touch it. Pass when the change goes live and can be rolled back the same way.
-
Recovery gate
Your team restores the platform or a full copy of it from backup into a clean environment, following the restore runbook. Pass when the restored copy works and the time it took is written down.
-
Incident gate
Run a planned incident drill during your team's on-call shift: a failed dependency, a full disk or a broken integration. Pass when your team detects it from monitoring, follows the runbook and writes the incident note.
-
Exit gate
Revoke the partner's production access for an agreed period while your team runs the platform alone. Pass when nothing breaks and nobody needs to ask for access back.
Track the gates with delivery measures that outlive the transfer. DORA's software delivery performance metrics include change lead time, deployment frequency, failed deployment recovery time and change fail rate. Recording them during the operate phase gives both sides the same evidence.
What goes into a build-operate-transfer contract?
Write the transfer into the first contract, not into a later change request. A clear agreement names the phases, the gates above, who decides that each gate is passed, and what support the partner gives after transfer. Luxoft's guide to the BOT model splits BOT into pre-build, build, operate, transfer preparation and transfer, and warns that transfer only works when the team can operate without the partner.
Four clauses matter most. Intellectual property: what is created for you is yours from the start, not at transfer. Accounts: production accounts are opened in your name on day one. Knowledge: runbooks, architecture notes and incident records are deliverables with acceptance criteria. Exit: you can trigger transfer early.
On the Netbase side, the client owns the IP created for it in custom development; Netbase productized modules are licensed, not transferred. Most Netbase projects are delivered on fixed-price contracts, with milestone-based, monthly team retainer and KPI-linked models also offered. Build-operate(-transfer) terms are agreed deal by deal with the CEO and never published.
When should you not use build-operate-transfer?
Do not choose BOT if you cannot name who will run the platform after transfer. Without a hiring plan, the operate phase simply becomes permanent outsourcing with a transfer clause nobody uses. In that case, choose a build-operate arrangement openly and keep the exit rights.
Do not choose it for a short-lived product, a campaign site or a prototype that will be rebuilt; transfer tests and runbooks pay off only for a platform you will run for years.
Be careful when regulation makes you the accountable operator from day one, for example for payments or health data. You can still use a partner in the operate phase, but your own staff must hold the approvals and see the audit trail throughout, not only after transfer.
Where AI fits
AI tools help most in the operate phase: summarising logs and alerts, drafting incident notes, proposing patches with regression tests, and turning recorded fixes into runbook steps your team can follow. Engineers still review every patch, production change and runbook page, because a fluent summary can describe the wrong failure. Netbase works with the major commercial and open-source AI tools and models, chosen per project, under human control.
- In delivered work
Recommendation engine
A recommendation engine delivered for 4over4's online printing store, suggesting products from browsing history and previous purchases; it is not an operations tool.
- In delivered work
WhatsApp AI chatbot with CRM integration
An AI chatbot for WhatsApp Business connected to the client's CRM; the client is not named.
- Available capability
AI-assisted operations runbooks
Log summaries, draft incident notes and patch proposals reviewed by engineers before anything reaches production; not yet tied to a published case.
What delivery record exists, and what does not
Netbase runs, maintains and upgrades what it builds, remotely and alongside the client's in-house team, under an agreed support scope; response targets are set per contract. The managed operations and support page describes that run scope, and the engagement models page lists dedicated teams, project-based development, on-demand support and fully managed delivery. Ongoing support is the sixth step of the Netbase delivery lifecycle, after training, rollout and optimization.
The longest published operating record is a multi-tenant cloud ERP delivered as SaaS for a US software company that is not named, where Netbase works remotely as its offshore development partner. Clients can follow their project's milestones and tasks in a shared Cloodo workspace, which keeps the operate-phase backlog visible to the team that will take it over.
What does not exist: Netbase has not published a case in which a running product was transferred to a client's own operations team under a BOT contract, and no transfer duration, gate result or cost figure is published. Co-build, build-operate(-transfer) and revenue-share models are described on the partnerships page; their terms are agreed deal by deal and stay private.
Alternatives: other ways to get a platform running without an operations team
A managed cloud platform with a light support contract. The provider carries most infrastructure work. Choose it when the product is simple and the main risk is the application code.
Application maintenance and support only. A partner fixes defects and applies updates, while you keep hosting and on-call duty. Choose it when you already run infrastructure but lack developers; application maintenance and support covers that scope.
Exit planning without an operate phase. If you mainly fear lock-in, write exit rights and data portability into a normal build contract. The vendor lock-in and exit planning guide shows how for AI agent platforms.
Limits of this guide
- It describes product operation and its transfer, not the legal transfer of employees or a company; employment and entity questions belong with your own advisers.
- The gates are a working checklist, not a standard; adapt them to your platform's risk and regulation.
Plan the next step with a Netbase consultant
Frequently asked questions
A maintenance contract keeps the partner responsible indefinitely and does not build your own team's skills. Build-operate-transfer has a planned end: your team joins during the operate phase and takes over each duty after passing a written test, so the partner's role shrinks by design.
You should own them from the first day. The code, data and documentation created for you, and every production account, belong to your company throughout; the partner works as a named user whose access you can remove at the exit gate.
Yes, if the first contract keeps both options open. Write the transfer gates and the exit right into it, and review them at each milestone; if you decide to keep the partner, move to a support scope with response targets rather than leaving an unused transfer clause.
Yes. Prompts, evaluation sets, model settings, vendor accounts and human approval steps become transfer items, and your team should run at least one evaluation and one rollback of an AI change before the exit gate.
Next step
If you are commissioning a platform and want to agree who runs it after launch, tell us about your product and team and we will reply with a proposal covering the build, the operate phase and the transfer gates.
Related services and solutions
AI automation and agents that keep people in charge Netbase provides AI automation and agent development for operations teams that want repetitive, multi-step work done by software while people keep approval over decisions that matter. We combine rule-based automation with AI where it adds value, build in human approval, and measure return against a baseline.
Learn More
Application maintenance and support for live web, mobile and business software Netbase maintains and supports software that is already live: web platforms, online stores, mobile apps, ERP and CRM systems and internal tools, including software another vendor built. We take it over after a code and environment review, then fix defects, keep frameworks current, monitor it, make small changes and report monthly, under service levels agreed in your contract.
Learn More
SaaS product accelerator: launch an AI-ready SaaS on proven Netbase modules A SaaS product accelerator is a set of reusable Netbase modules for accounts, billing, roles and integrations that helps founders and product teams launch subscription software faster, with room for in-product AI from the first release. Reusing these modules can shorten development time, and the approach is proven on Printcart, Netbase's own web-to-print SaaS.
Learn More
Custom cloud ERP with AI forecasting and document capture: projects, finance, HR and CRM in one system A custom cloud ERP from Netbase is one browser-based system where a growing company runs its projects, finance, HR and customer relationships on shared data, with AI that reads invoices and forecasts demand and cash. It suits SMEs that have outgrown spreadsheets but not their own way of working, on the foundation of Cloodo Workspace, which Netbase built and runs.
Learn More
Work with Netbase remotely
Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.
Discuss a project
Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.project@netbasejsc.com
+84 937 869 689
91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam
Get in touch
Tell us what you want to build, modernize, or operate.