Skip to content

Quote

A quote is a document, not a number on the phone

we do not give a hard price for work whose scope is undefined. Every quote we issue comes with a scope document, and it only becomes a fixed figure once that document is signed by both of us. This page describes the quote before you ask for one.

The seller is our household business, not a company. A household business can sign contracts and can issue an invoice. What it cannot do is issue a VAT invoice: software services are a không chịu thuế object, so no VAT is calculated on the invoice and there is no input deduction for your accountant. The seller name on the quote is the name on our business registration — compare it against that registration itself, letter by letter.

What is in every quote

Seven parts, in the order a reader needs them. The price table is the third part, not the first — deliberately.

  1. 01

    Your problem, written in your words

    we write the problem back in your language rather than translating it into technical terms. If we have misunderstood, you see it in the first section, before you reach a single number.

  2. 02

    A scope document, signed alongside the quote

    Feature list, data model, role permissions, screen descriptions you approved before we wrote any code, and a test plan. This quote is only valid once that document is signed.

  3. 03

    The indicative price table

    Labelled indicative, and it becomes a fixed price when the scope document is signed. The published bands for each package live on the pricing page, together with the arithmetic behind the smallest one.

  4. 04

    The 30 / 40 / 30 payment schedule

    Deposit on signature, second tranche when you have run the first working build on your own infrastructure, final tranche on handover of the source and documentation. Ownership of the source is yours from the project start and does not depend on the final tranche.

  5. 05

    Adoption and rollout, priced as its own line

    Deployment plan · a named internal owner with decision rights · staged rollout to a first user group · a check-in after week two. It is a separate line with its own hours and its own price, not folded into the build — because a system that runs is not the same as a system staff use.

  6. 06

    What this price does not cover

    Third-party fees, 24/7 cover, a team, ISO / SOC 2 / CMMI certification. Written so you can check before signing rather than read it later.

  7. 07

    A signature block, and a covering email

    A quote is never sent naked. The covering email says why this price, and proposes a specific call rather than restating the number.

Indicative pricing and validity

Every figure in a quote is indicative. A quote is valid for 14 days from the date it is issued; after that the figures have to be re-quoted, because the costs and the risks have moved. Anything outside the agreed scope is quoted separately in writing and waits for your written agreement before work starts.

When we will not quote at all yet

There is one case where we give no figure whatsoever, and we say so up front so you are not kept waiting: when nobody yet knows whether the job is possible.

  • The target platform has no public documentation

    we can only integrate against something that has public documentation. We have never delivered a Zalo OA, KiotViet or TikTok Shop project for a client, and we say so immediately rather than letting you find out later. In that case the work starts with a separate paid feasibility spike.

  • The spike concludes — or it does not

    You receive a written conclusion backed by something that actually ran, together with the alternative route if it is not viable. If the conclusion is that it cannot be done, the spike ends there — you do not pay for a project that cannot happen.

  • The scope is not yet defined enough to price

    Then we say so plainly: the scope has to be written first, and priced after. There is no figure before there is a scope.

What no quote of mine promises

None of the following appears in any quote we issue. They are listed here so you do not have to work out whether paying more would buy them.

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

    This is one person. Both promises would have to become lies at exactly the moment you needed them.

  • A team

    No staff augmentation, no team. If a project needs three or more people at once, go with a larger company.

  • Cybersecurity services, ISO / SOC 2 / CMMI

    Not something we do.

  • A pre-trained AI model

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

  • Software work below VND 200,000,000

    we do not take it. There is no honest way to write a scope, quote it and contract it at that size; an audit or a template may fit.

One thing stated plainly: there is no monthly subscription

After handover, the contract sets out a support window. Beyond that there is no recurring package here — if you need a monthly one, we will tell you it does not exist rather than sell you an empty one. The system and the source stay yours afterwards, and you can hand the fixes to somebody else.

Send a few lines and we will ask specific questions back

You do not need to write a technical brief. A description in your own words is enough. We reply within 1 business day.