Skip to content

Contract

The contract terms, in writing, before you sign

Every project is governed by a written contract with annexes. This page summarises what you would be signing and — just as deliberately — what you would not be signing, so you can check it now rather than discover a clause later.

we trade as a registered household business (a hộ kinh doanh), not a company. That is a legal form in its own right in Vietnam: it can sign contracts and it can issue an invoice. It does not issue VAT invoices — software products and software services are a không chịu thuế object, so no VAT is calculated and your side cannot deduct input VAT from this spend. The invoice you receive carries the same name as our business registration — open the registration and compare it letter by letter, including the diacritics, before you sign.

Three payments, 30 / 40 / 30

The money follows something that is running, not a date on a calendar. The middle payment falls due only once you have seen the system running on your own infrastructure.

  1. 0130%

    Deposit

    On signature, before we write the first line of code.

  2. 0240%

    Second tranche

    When you have run the first working build on your own infrastructure and confirmed it in writing. We cannot call this tranche due because a date arrived while you had not yet looked.

  3. 0330%

    Final tranche

    On handover of the source code and the documentation.

The clauses worth reading twice

The source is yours from the start
Not on handover, not when the final payment is settled. We do not hold your source as leverage to collect the last payment, and we cannot demand it back if you pay late.
Defect warranty: 30 days for short work, 90 for multi-week builds
The software package runs 6–10 weeks and carries 90 days. On a build that long, a 30-day window is not proportionate to what you have just bought. A code audit or an AI assessment hands over a report, not a running system: what protects you there is our obligation to correct the report if it is wrong, not a countdown. The period runs from handover and only for defects inside the delivered scope. Hosting, licences and third-party services are outside it.
Scope changes are quoted first
Anything outside the agreed scope gets a separate written quote and waits for your written agreement before work starts. It is never folded into the original package and charged for afterwards, and nothing is charged that you did not agree to.
No hard price before there is a scope
Without a signed scope document there is no price in the contract. We do not give a number for work whose scope is undefined.
Third-party costs are yours to contract
Hosting, domains, paid library licences, SMS providers, e-invoice vendors — you contract and pay them directly. We do not collect on your behalf and we do not act as your representative.
Your data goes nowhere
Your data is never used to train somebody else's model, including mine. That is a clause in the contract, not a verbal assurance.
After the warranty
The contract sets out a post-handover support window. There is no monthly recurring package — if you need one, we will tell you it does not exist here rather than sell you an empty one. The system and the source stay yours, and you can hand the fixes to somebody else.
The contract names who receives it on your side
“The system stays yours” only holds if your side has someone who receives it — who uses it daily and can ask us things. So the contract has a clause that names that person. If you do not have one yet, we say so up front and propose a separately-priced site survey, rather than hand over a system nobody opens. This is the only clause where the buyer may have nobody to fill in — and if you cannot fill it in, that is the thing to say before signing.
The size of work we decline
We do not take software projects below VND 200,000,000. Not because we are pricing high, but because at that level there is no honest way to write a scope, quote it and contract it.

What is in the contract pack

Four parts. Three exist as reusable documents; the fourth is written per project and is the part that decides the price.

  1. Software development services contract

    The main document: who the parties are, what is delivered, how progress and acceptance work, how payment runs, what the warranty covers, who is responsible when, and what this contract does not include.

  2. Annex 1 — Price schedule and payment structure

    The price ladder published on this site, so both sides are looking at the same number, plus the 30/40/30 table and the out-of-scope items. This project's actual price lives in this annex, not on the web page.

  3. Annex 2 — Scope of work and acceptance criteria

    Written per project, because no two projects are alike. It carries the feature list, the completion condition for each milestone, the shared components, and the data migration script. Without this annex there is no price.

  4. Annex 3 — Confidentiality and personal-data terms

    This system stores your staff's names, roles and login history, so this annex is not optional. It states where data is stored, who may access it, which third parties process it, and how quickly an incident must be reported.

What this contract does not cover

Written down so the two of us can check before signing rather than argue afterwards. If you need any of the following, we will say so in the first conversation.

  • 24/7 cover, or a one-hour response commitment

    The system has one maintainer. Both promises would have to become lies at exactly the moment you needed them.

  • A team

    No staff augmentation, no team of our own. If a project needs three or more people working at once, it belongs with a larger company.

  • Cybersecurity services

    No ISO, SOC 2 or CMMI certification or audit. We do not do security work.

  • A pre-trained AI model

    The AI work we sell is integration, measurement and operation on your own data — not an off-the-shelf model, and not an AI strategy deck with no build attached.

  • Integrating with a platform that has no public documentation

    Unless a paid feasibility spike is done first and you agree to it in writing. We have never delivered a Zalo OA, KiotViet or TikTok Shop project for a client.

Common questions

Am we locked into a contract?
For a system build, yes — and without a signed contract and scope document there is no price at all, because we do not put a number on work whose scope is undefined. If it turns out we are not the right fit, you do not pay.
Will you hold the source code until we pay in full?
No. Ownership passes to you on the project start date and the repository sits in your account from that point. We do not hold your source hostage to the final payment.
What happens after the project is delivered?
The contract ends at handover. You then have three options and no lock-in: stop entirely, use the support window already written into the contract, or hand the fixes to somebody else.

Read the contract, or start with a quote

Send us a few lines about the problem you are facing. If it is not a fit we will tell you plainly, and if it is, the next step is a written scope and a written quote.