This guide is for anyone holding a proposal or statement of work (SOW) from a Vietnam-based vendor and deciding whether to sign it, and for anyone writing their own RFP terms before a shortlist comes back. It checks the document in front of you, not the vendor behind it; for picking the contract type before a proposal exists, see dedicated team vs fixed price, and for the Vietnam outsourcing decision as a whole, see the outsourcing guide.
In this guide
- What makes a proposal checkable for scope creep?
- Which signals in a proposal predict scope creep?
- How do you read a proposal before signing it?
- When is this checklist the wrong tool?
- Where AI fits in reading a proposal
- What delivery record exists, and what does not
- Who checks the proposal for you?
- Limits of this guide
- Frequently asked questions
- Next step
What makes a proposal checkable for scope creep?
A proposal is checkable, not just readable, when four of its parts each answer a specific question: what is explicitly excluded from scope, not only what is included; whether each deliverable is specific enough that both sides can test it against the finished document; whether a change-control step exists in writing for anything not in that list; and whether acceptance has a stated test, not a general promise of quality. Wikipedia's definition of scope creep describes the failure this checks for directly: uncontrolled changes or continuous growth in a project's scope after it starts, usually because the boundary was never written down. A statement of work exists specifically to draw that boundary; if a proposal reads like a sales pitch instead of a SOW, that absence is the first red flag, before any clause is read in detail.
Which signals in a proposal predict scope creep?
| Signal | Vague wording that hides it | What it costs you | Ask for this instead |
|---|---|---|---|
| No named exclusions | A scope section that lists only what is included, with no "not included" or "phase 2" line | Anything not explicitly out is treated as a negotiation, not a fact, once work starts | A scope section with its own exclusions list, the way Netbase's own delivered proposals separate a phase 1 build from phase 2 and phase 3 items named and left out (see below) |
| A deliverables list that reads like a feature summary | "A modern, scalable admin dashboard" instead of named screens, roles and actions | Both sides can claim the delivered build matches their own reading of the sentence | Deliverables specific enough that a third party could check them off against the finished product without asking either side what was meant |
| No change-control mechanism | Silence on what happens when a new request arrives, or only "changes may incur additional cost" | A verbal "sure, we'll add that" becomes the de facto process, with no record of cost or schedule impact | A written step: who can request a change, how its cost and schedule impact is estimated, and that work pauses on it only if either side says so |
| No testable acceptance clause | "Delivered to a high standard" or "subject to client approval" with no test named | Acceptance becomes a mood, not a gate, so a disputed feature has no written test to settle it | An acceptance clause that names the test (a checklist, a staging walkthrough, a defined bug-severity threshold) before work starts, not after |
How do you read a proposal before signing it?
-
Read the scope section before the price
If it has no exclusions, phases or a "not included" line, that is the single highest-risk signal on this list; ask for one before reading further.
-
Check every deliverable against the "could a stranger verify this?" test
A deliverable only a vendor's own team could confirm as "done" is not specific enough to protect either side.
-
Find the change-control clause, or ask why there is none
A fixed-price contract without one is not actually fixed; a dedicated-team or retainer proposal does not need one in the same way (see below).
-
Find the acceptance clause and the test it names
If acceptance is "subject to approval" with no stated method, ask what method the vendor actually uses internally and have it written in.
-
Check the proposal's own internal consistency
Do the phases, dates and totals in the narrative match the numbers in any table or appendix? A mismatch is often where a missing exclusion hides.
-
Put every answer in writing before signing
, in the contract or SOW itself, not in a follow-up email. A verbal clarification is not enforceable once work is under way.
When is this checklist the wrong tool?
This checklist assumes a scope that is meant to be fixed at signature, which is the normal shape of a fixed-price engagement. A dedicated development team or a monthly retainer is built around the opposite assumption: scope is expected to move sprint to sprint, and it is governed by backlog priority and reporting, not by a change-control clause written once. If the proposal in front of you is for a dedicated team, the right check is dedicated team vs fixed price's governance comparison, not this one; running a scope-creep audit against an engagement that was never meant to have fixed scope answers the wrong question.
Where AI fits in reading a proposal
AI is useful for a first pass over a long proposal, never as the only check before signing a contract. Netbase works with the major commercial and open-source AI models, chosen per project, for any assistance work it recommends. Each item below states how mature it is at Netbase.
- In delivered work
Product recommendation engine
Built for 4over4's online printing store from browsing and purchase history; it is not a contract-review tool, and this guide names it only as Netbase's one published, named AI feature.
- Available capability
AI-assisted proposal and SOW review
Flagging vague scope wording, a missing exclusions list, or an acceptance clause with no stated test in a draft proposal is a natural-language pattern-matching task for a large language model; not yet tied to a published client engagement, so treat its output as a prompt for a human legal or technical review, not a verdict.
What delivery record exists, and what does not
Netbase's own six-step delivery lifecycle sets outcome-based milestones in its planning stage before execution starts, and its four-step project workflow sets the delivery-milestone and payment plan in its own planning stage before coding begins — the same boundary-writing habit this guide recommends to a buyer, applied to Netbase's own proposals:
- ACT Printing. The delivered scope was a named phase 1 apparel-ordering build; B2B accounts and reorders were named as phase 2, and AI and third-party integrations as phase 3 — both explicitly out of the signed scope, not an open-ended roadmap (ACT Printing record).
- A Dubai-based loyalty and rewards company (not named). The proposal structured a headless reward-shop platform into four named phases delivered over 3.5-4.5 months, rather than one undivided build (loyalty platform record).
- Deyar Printing & Advertising. The bilingual web-to-print platform's AI design suite, ERP integration and e-invoicing were named as a planned third phase, separate from the delivered discovery-to-production-operations scope (Deyar record).
What does not exist. No published Netbase record describes reviewing or scoring a third-party vendor's proposal for scope-creep risk; the examples above show Netbase's own proposals naming their boundaries, used here only to illustrate what a checked box looks like in a real document, not as a claim about any other vendor's practice or a result for a future buyer.
Who checks the proposal for you?
| Route | Strength | Choose it when |
|---|---|---|
| Your own team | Knows the project's real requirements best | Someone on your side already has contract or delivery experience and the time to do this checklist properly |
| A contracts lawyer or procurement specialist | Catches legal and commercial gaps this guide does not cover (liability, IP, termination) | The deal size or risk justifies a paid review, especially for first-time outsourcing |
| An independent technical advisor | Reads the technical deliverables and acceptance criteria with delivery experience, not just contract language | You want a second technical opinion before signing, for example a fractional CTO or CIO engaged separately from the delivery vendor |
| The vendor's own account manager | Fastest explanation of what a clause means | Only for clarifying intent, never as your only check: the same party who wrote the proposal cannot be your independent reviewer |
In Netbase custom development, the client owns the IP created for it, delivery communication runs in English, and most projects are delivered on fixed-price contracts agreed after discovery, with milestone-based, retainer and KPI-linked terms also offered. Teams of 3 to 30 combine business analysts, architects, developers, QA and UI/UX, typically starting 1-2 weeks after discovery, with weekly reviews, KPI dashboards and a named account and project manager. See how Netbase structures dedicated development teams, or the related SaaS product accelerator for a product-shaped engagement.
Limits of this guide
- This checklist reads a document; it cannot tell you whether a vendor will honour what the document says. Reference checks and a small paid pilot remain the way to test that.
- No scope-creep statistic is published here: the publicly available figures on how often outsourced projects see scope creep carry no primary citation this guide could verify, so none is used.
- Every proposal format differs; some vendors put exclusions in an appendix, a separate SOW, or an email thread instead of the main document. Check all of them, not just the page headed "Scope".
Plan the next step with a Netbase consultant
Frequently asked questions
No. Only what is written into the signed proposal or SOW is enforceable once a dispute starts; ask for every verbal clarification to be added to the document before you sign, not sent separately by email.
No. A fixed-price contract only prevents it if the scope section itself is specific and the change-control clause is written; a vague fixed-price proposal is exactly as exposed to scope creep as a vague proposal under any other model.
Treat that refusal itself as the signal. A vendor confident in its own estimate has no reason to avoid writing down what is out of scope or how a change is priced.
Only proposals meant to have fixed scope at signature. A dedicated-team or retainer proposal is built to let scope move, so the comparison in dedicated team vs fixed price is the more useful check for that document instead.
Next step
Send us the proposal you are evaluating and we will book a solution review to walk through its scope, deliverables and acceptance clauses with you. You can also read protecting IP when outsourcing for the clauses this guide does not cover, or see the software outsourcing transition and knowledge-transfer plan for what to plan once the engagement ends.
Related services and solutions
An AI-augmented dedicated development team in Vietnam that answers for results Netbase provides dedicated development teams from Vietnam for product companies and enterprises that need engineering capacity. Teams of 3 to 30 people work only on your product, use AI-assisted engineering under review, report to a named account manager and project manager, typically start within one to two weeks after discovery, and the IP they create is yours.
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
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.