Large or boutique Vietnam IT vendor: how to match vendor size to the job

This guide is for founders, product leads, CTOs and procurement leads comparing shortlisted Vietnamese vendors of different sizes for the same project. It assumes you already know why Vietnam is on the list; for the cost drivers, team models, IP terms and a vendor-honesty checklist that applies to any vendor regardless of size, see the Vietnam outsourcing guide. This page answers a narrower question: once Vietnam is the market, how big should the vendor be?

In this guide

• Why "which vendor" and "how big a vendor" are different questions
• The decision matrix: match size to the job
• What each size is actually built to do
• A sequencing plan for the decision
• Where AI fits
• What delivery record exists, and what does not
• Alternatives: other ways to right-size the engagement
• Limits of this guide
• Frequently asked questions
• Next step

Why "which vendor" and "how big a vendor" are different questions

Most public comparisons of Vietnamese IT vendors are rankings: company A, B and C ordered by scale, awards or review count. Second Talent's "Top 10 Software Development Outsourcing Companies in Vietnam" and MOR Software's own outsourcing overview are typical of the genre — useful for building a shortlist, silent on which size fits your project. Neither publishes a decision rule for a buyer who already has three vendors of different sizes on the table and needs to pick one.

Size changes four things a ranking does not show: how many people stand between you and the engineer writing your code, how much process the vendor insists on before work starts, how likely the same people stay on your account for a year, and how well the vendor absorbs a scope that keeps changing. None of those show up in a "top 10" list.

The decision matrix: match size to the job

Score your own project against each row, then read down the column with the most matches.

No row decides alone. A project that scores mostly in one column has a clear answer; a split score usually means a mid-size vendor, sized between the two, is the safer default — large enough to carry a real programme, small enough that the same people stay on it.

What each size is actually built to do

A large vendor carries more people across more accounts, so it spreads fixed costs — security, compliance, account management, bench capacity — over many clients. That is real value on a programme that needs several specialisms at once or must prove a formal process to its own auditors. The trade-off is depth of attention per account: a six-person build rarely gets a large vendor's most senior people, and scope changes often travel through more layers before they reach the engineer doing the work.

A boutique or mid-size vendor carries fewer accounts per senior person, so the same architect or lead engineer who scoped the work is often still the one reviewing it months later. That continuity and shorter decision chain suit a project whose scope is still being discovered, or where the client wants to reach a named engineer directly rather than an account manager. The trade-off is ceiling: a boutique vendor can struggle once a programme needs five specialisms at once, a formal audit trail, or more bench than it carries.

Treat "boutique" and "large" as a spectrum, not two boxes: a vendor with 30 to 80 people can sit in the middle, carrying more bench than a true boutique while keeping fewer layers than an enterprise-scale firm.

What delivery record exists, and what does not

Netbase is itself a Vietnamese vendor in the middle of the spectrum this guide describes, so we show our own record rather than ask you to take the framework on faith.

• Team shape. Netbase delivery teams run from 3 to 30 people, combining business analysts, project managers, solution architects, developers, QA and UI/UX, with work typically starting one to two weeks after discovery — closer to the boutique or mid-size end than to an enterprise-scale bench.
• Continuity on a long programme. Since 2020, Netbase has worked as offshore development and managing partner on a multi-tenant cloud ERP for a US client (not named), through a first phase covering CRM, messaging, HR, a knowledge base and API integrations, with a retail extension planned for a second phase. The engagement record is in the cloud ERP portfolio record; see also how a comparable programme is set up in the AI-first offshore development center guide.
• A named commerce case. For 4over4's online printing store, Netbase delivered conversion and checkout work, search and a recommendation engine; revenue grew 82% within six months, as reported in the published 4over4 case study. The figures reflect the whole engagement, not a single feature, and depend on that client's baseline.
• Positioning and terms. Netbase leads with consulting, solutions and custom development; most projects run on fixed-price contracts after discovery, with dedicated teams, project-based development, on-demand support and fully managed delivery offered as engagement models. The client owns the IP created in custom development. Delivery communication runs in English, with weekly reviews, a KPI dashboard and a dedicated account manager and project manager. Security practice covers code review, TLS in transit, role-based access, MFA and vulnerability scanning, with NDAs and DPAs on request.
• Scale context. Founded in 2012, Netbase has served 500+ clients; the 2023 company profiles put the share of projects from clients outside Vietnam at 85%.

What does not exist. Netbase publishes no comparison of its own delivery against a named large competitor, no vendor-size benchmark, no switching-cost study and no figure for how often a continuity clause has been invoked. The cloud ERP programme's second phase is planned, not completed, and no duration or headcount is published for it.

Alternatives: other ways to right-size the engagement

Netbase runs the boutique-to-mid-size end of this table through dedicated development teams or a scoped offshore development center for a longer-lived programme; either model stays consulting-first, with a fixed-price default agreed after discovery rather than open-ended staffing. Whichever size you pick, the commercial model is a separate decision: see dedicated team vs fixed price.

Limits of this guide

• Vendor size is one input, not the whole decision; the Vietnam outsourcing guide's checklist still has to pass regardless of size.
• "Boutique", "mid-size" and "large" are not registered headcount bands; treat the matrix as a scoring method, not a classification you can look up.
• No duration, cost, success rate or switching-cost figure is claimed for any vendor size; none is published anywhere Netbase can source.

Next step

Score your own project against the matrix above, then book a solution review and we will size the engagement model to it, boutique-style or scaled. See how Netbase runs a longer-lived programme in the offshore development center model.

Related services and solutions