Three engagement models
Most outsourcing deals follow one of three models. The right one depends on how well you can describe the work today.
- Start fixed-scope work with a short paid discovery phase that turns ideas into a written scope
- For time and materials, agree a monthly cap and a weekly report of what was done
- For a dedicated team, decide who manages priorities day to day
Engagement models compared| Model | How it works | Fits when |
|---|
| Fixed scope | Agreed features, price and acceptance criteria | The scope is clear and unlikely to change |
|---|
| Time and materials | You pay for hours or days worked, with a monthly report | The scope will evolve, or you are still learning what users need |
|---|
| Dedicated team | Engineers work on your product full time under your lead | You have a product owner and a long roadmap |
|---|
Communication and time zones
Vietnam is on UTC+7, which overlaps well with the rest of Asia and Australia, partly with Europe in the morning, and little with the Americas. Agree fixed hours for calls and a channel for urgent issues.
Ask who you will talk to. A project manager who relays messages adds a step; an engineer who reads your message and changes the code removes one. Insist on written summaries after calls, in English, so decisions do not live only in someone's memory.
For a product used by Vietnamese customers, a bilingual team helps twice: you work in English, and the interface, messages and support texts are written by people who use Vietnamese daily.
What the contract should cover
Bring this list to your lawyer. It covers the points that cause most disputes later.
- Who owns the source code, designs and documentation, and from which moment
- Which open-source licenses may be used
- Confidentiality, and how your data and your customers' data are handled
- Acceptance: how a feature is checked and approved
- Payment schedule tied to delivered work, not to dates alone
- Warranty period for bugs after launch
- How either side can end the contract and what is handed over
Rules on contracts, personal data and cross-border data transfers apply to both sides and change over time. Check them with a lawyer who knows Vietnamese law and the law of your home country.
Keep the keys in your name
The simplest protection costs nothing: create the accounts yourself and invite the vendor. Code repository, cloud hosting, domain, app store accounts, Zalo Official Account, analytics and payment provider should all belong to your company.
If the relationship ends, you remove access and keep everything. If a vendor insists on hosting your product in its own account, ask why and how the hand-over would work.
Invoices and payments
How you are invoiced depends on where your company is registered and where the vendor is registered. A company inside Vietnam usually needs a Vietnamese e-invoice (hóa đơn điện tử) for its accounting; a company abroad may pay against a commercial invoice instead.
Agree the currency, who pays bank fees and which taxes appear on the invoice before the first payment. Ask your accountant which document your company needs; we agree the invoice format in writing before the first payment.
How to check a vendor before you sign
References and portfolios help, but a short test tells you more.
- Meet the engineers who will write the code, not only sales
- Ask for a small paid task first: one feature, one integration or a technical review
- Read the code or ask someone you trust to read it
- Check how they write: a clear proposal usually means clear work
- Ask what they will not do, and who they would send you to instead
The first four weeks
A good start looks the same in most projects: accounts and access first, then a written scope and a first working piece within the first weeks, then weekly demos. If you cannot see working software on your own server early on, raise it.
Plan for hand-over from the first day: documentation in the repository, a short guide to deploy and run the system, and credentials stored in your password manager, not in a chat.