One morning your company website throws an error on the checkout page. Customers are calling to complain, orders are stuck, and the one person who knows how the system is configured is on holiday and not picking up. In that moment the question becomes very clear: should you have your own dedicated tech team, or hire an outside firm to handle operations?

This is a familiar dilemma for small and medium enterprises (SMEs) that have moved past the startup phase and now genuinely depend on their software. There is no single right answer, but there is a clear way to think it through.

The real cost of an in-house team

When people imagine a dedicated tech team, they usually only tally salaries. But the real cost is far bigger than the number on the employment contract.

  • Salary and benefits: An experienced operations developer in Vietnam typically runs 20, 35 million VND per month. Add insurance, bonuses, equipment, desk space and licensed software, and the actual cost climbs 30, 40% above gross salary.
  • Recruitment: Posting, screening and multiple interview rounds take months. Through a headhunter, fees often equal one to two months of the candidate's salary.
  • Retention: Technical staff change jobs often. Every departure costs you time to re-hire and, more dangerously. The knowledge they take with them.
  • The "one person knows everything" risk: SMEs can usually afford only one or two technical people. All system knowledge lives in their heads. Sick leave, vacation or resignation turns the whole system into a black box.
  • Paying for idle time: Website operations aren't busy every day. Many months the system just runs smoothly, yet you still pay a full salary to someone waiting for incidents.

Altogether, a minimum two-person in-house team can cost 600, 900 million VND per year, before the hidden costs of hiring and retention.

When in-house is the sensible choice

In-house is not a bad option. In the right context, it's superior.

  • Software is the core business: If your product *is* the software (an e-commerce marketplace, a fintech app, a SaaS), technical capability is a strategic asset you shouldn't hand outside.
  • Constant daily change: When the system needs edits and new features every day, an in-house team beside you reacts faster than any external contract.
  • Deep domain knowledge: Some complex operations need people steeped in your internal culture and processes. Hard to transfer in the short term.
  • Security and control: With highly sensitive data, an in-house team means direct control and fewer third parties touching it.

The common thread: in-house makes sense when engineering creates competitive advantage, not just when you need to "keep the system from crashing."

Outsourcing operations. The gains and losses

Fixed-subscription outsourcing is popular with SMEs precisely because it reverses the weaknesses above. But it has its own price.

Gains:

  • Fixed, predictable cost: A steady monthly fee, usually far below the cost of a full team. Because you share resources with other clients.
  • No hiring or retention worry: Staff turnover is the provider's problem, not yours.
  • Knowledge doesn't sit with one person: A professional firm documents processes and spreads knowledge across a team. Reducing black-box risk.
  • Broad experience: They run many different systems, so they spot and fix incidents faster.

Losses:

  • Less direct control: You can't hand off small ad-hoc tasks the way you would to someone in the next room.
  • Vendor dependence: Picking the wrong partner, or getting locked in, is a real risk. You need clear contracts and handover commitments.
  • Poor fit for high-intensity change: If you need new features daily, the subscription model can become a bottleneck.
  • Ramp-up time: An outside partner needs an initial phase to learn your system.

A decision framework for owners

Instead of asking "which is better," look through three lenses:

By size. Under ~50 staff with only one or two core systems: outsourcing is almost always more cost-effective. Above a few hundred staff with many systems: you have enough volume to justify your own team.

By stage. In a stable phase, when the system runs steadily and mostly needs *keeping healthy*, outsourcing is ideal. In a hot-growth, constantly-innovating phase, lean toward in-house. Or a hybrid (a small core team plus outsourced baseline operations).

By system type. Systems that are a *competitive advantage* (the reason customers choose you), keep in-house. *Supporting* systems (website, internal infrastructure, back-office tools). Outsource, so your team focuses on creating value.

Many businesses end up doing both: keeping the core in-house and outsourcing baseline operations.

Conclusion

There is no absolute winner. Only the option that fits your size, stage and the nature of your systems. An in-house team gives you control and speed when engineering is the core business; outsourcing gives you predictable costs and peace of mind when the system mainly needs to be kept running reliably.

For most SMEs that *own* a website or supporting software, rather than making software their core business. Subscription-based operations outsourcing is usually the more sensible math. If that's exactly where you're hesitating, Siri9 operates websites and software for businesses at a fixed monthly cost, so you can pour your energy into the business and leave the technical side to a dedicated team.