Choose the guide for your next software decision

OutsourcingVN is operated by Netbase JSC. Netbase sells the services discussed here, so this is a supplier's editorial library. It does not claim independent ranking or commercial neutrality. A useful guide should still help you prepare a brief, compare approaches and ask another provider for evidence.

Contents

• Choose a starting point
• Outsourcing to Vietnam
• Project engineering and delivery economics
• Audit, maintenance and legacy modernization
• Business workflows and industry decisions
• AI workflow automation
• Choosing a supplier and governing remote delivery
• Market-specific delivery questions
• Emerging technology assessment
• Read the evidence before choosing the service
• Common questions
• Bring the decision and its constraints

Choose a starting point

A pillar explains a broad decision; a supporting guide examines one part in detail. Several groups reuse the same supporting guide because security, ownership and handover affect more than one buyer journey. The index lists each buyer guide once, while the pages themselves connect the relevant journeys.

Use global delivery for the operating model, project delivery for scope and acceptance, and engagement models for how work is contracted, with managed outcomes and specialist sprints covering the two models beside a project. These five delivery pages are entry points alongside the 88 guides below. Reading every page is unnecessary: choose the unresolved decision, collect the suggested evidence and record who can accept the next step.

Outsourcing to Vietnam

This group addresses provider selection and the working agreement. Country choice does not replace checking the actual team, delivery controls or project dependencies.

• Vietnam outsourcing frames the provider-selection decision and the evidence a buyer should request before committing.
• Comparing software outsourcing companies explains documented criteria and how to compare providers without inventing an independent ranking.
• Vietnam software outsourcing cost separates scope, assumptions and responsibilities when two proposals appear difficult to compare.
• Outsourcing due diligence identifies what to request, what to verify and what remains uncertain after a supplier conversation.
• Vietnam vs India compares the two sourcing locations on time-zone overlap, language, talent depth, data rules and how to check a supplier.
• Vietnam vs the Philippines compares engineering-led and support-led delivery, language, time zone and data rules before you shortlist.
• Vietnam vs Poland sets offshore delivery beside European nearshore for buyers in Europe: overlap hours, GDPR footing, contract law and governance.
• Vietnam vs Latin America weighs offshore delivery against nearshore teams for North American buyers on handover rhythm, language and legal footing.
• Time-zone collaboration connects overlap windows, written handoffs, decision owners and escalation to the project agreement.

Project engineering and delivery economics

Start here when you need to define a new product, repair a stalled project or decide what the buyer must contribute. The supporting guides now connect to the project and global delivery entry points; they are not an unconnected list.

• Total software delivery cost provides a worksheet for discovery, build, integrations, governance, security, handover and support.
• Software project brief turns an outcome into users, systems, constraints, dependencies and acceptance evidence that providers can respond to.
• IP ownership separates transferred custom work from licensed dependencies and identifies questions to settle in the agreement.
• Data security and compliance sets out access, review, data-handling and incident questions for the buyer's responsible owners.
• Handover and exit specifies the access, artefacts, documentation and operating knowledge needed when responsibility changes.
• Software project rescue assessment establishes the facts, access and immediate risks before anyone promises a replacement plan.
• Scope boundaries records what is in, what is out and which dependencies the buyer owns before any proposal is written against them.
• Acceptance criteria shows the buyer how to write criteria that a test can pass or fail, so acceptance is not a matter of opinion.
• Change control sets how a change request is raised, sized, approved or declined without losing budget or schedule control.
• Project risk register lists delivery risks, owners and triggers before the project starts rather than after one fires.
• Fixed-scope or milestone contracts compares contract shapes by how much of the scope is known when the agreement is signed.
• Custom build or SaaS weighs building a capability against subscribing to one, including exit and data ownership.
• Low-code vs custom development compares app-builder platforms with writing code for the application.
• SaaS product discovery questions prepares the tenancy, billing, role and release questions a SaaS discovery must answer.
• AI-assisted software delivery explains what changes in review, ownership and delivery evidence when engineers work with AI assistance under human review.

Platform questions such as Magento, Laravel, WooCommerce, Odoo or Next.js have their own technologies hub. The relevant build route is Custom Product Engineering. Where the immediate need is understanding a system before committing, inspect the Technical Audit Sprint definition instead of assuming that discovery includes implementation.

Audit, maintenance and legacy modernization

These guides cover systems that must keep working while responsibility or architecture changes. A passed deployment and an accepted operating handover are different events; make both visible in the plan.

• Software takeover and maintenance connects inherited access, reliability, debt, incident ownership and the continuing support boundary.
• Legacy system modernization frames the decision to change an existing system without treating a rewrite as the default.
• Replace, refactor, wrap or retain compares options against constraints, evidence and the cost of leaving a dependency in place.
• Incremental modernization explains bounded changes, coexistence, parity and the conditions for retiring the previous path.
• Legacy data migration covers profiling, mapping, reconciliation, exceptions and the evidence needed to accept transferred data.
• Legacy system risk assessment identifies the technical and operating uncertainties to resolve before accepting a larger commitment.
• Software technical due diligence scopes a code, architecture and operating-risk review before an acquisition, investment or supplier decision.
• Technical debt assessment ranks debt by business consequence so that remediation can be weighed against new features on the same terms.
• Managed software operations scope defines the systems, coverage hours, service levels and exit terms that a continuing operations agreement must state.
• Reliability and incident readiness checks monitoring, runbooks, escalation and recovery before the next incident tests them.
• Release readiness checklist sets the quality, security and rollback evidence required before a release is approved.
• E-commerce modernization checklist covers catalogue, checkout, extensions, data and search continuity when a commerce platform must change.
• Headless vs traditional e-commerce compares an API-first architecture with a coupled storefront.
• Magento vs WooCommerce weighs the two commerce platforms against catalogue, store count and team.
• WordPress to headless CMS migration plans a move from WordPress to an API-first CMS and a separate front end: content model, URL mapping, redirects, editor workflow and a phased cutover.
• Magento to WooCommerce migration plans the move once WooCommerce is chosen: data mapping, extension equivalents, URL and search parity, checkout set-up and a rehearsed cutover.

Use Legacy Application Modernization for a scoped change and Managed Operations for an agreed continuing operating boundary. Neither link implies that an unknown system is automatically supportable.

Business workflows and industry decisions

Begin with the process and its exceptions. The industry guides add a specific operating context to existing Industry and Solution pages; they do not turn every taxonomy combination into a new service.

• Business workflow transformation helps choose between process changes, configured software, deterministic automation and a bounded AI step.
• Print order and fulfilment follows specification, artwork approval, order acceptance and the handoff to fulfilment.
• Marketplace matching and quotation examines discovery, supplier responses, quote comparison and the boundary between a request and a commitment.
• ERP procurement and inventory follows purchasing, goods receipt, stock movements and reconciliation across responsible teams.
• Odoo vs custom ERP compares configuring Odoo, extending it and building your own.
• Data platform readiness checks data ownership, quality, access and integration before a reporting, data or AI platform commitment.
• Local business directory launch plans listing sources, claim and verification, categories and a mobile-first launch for a local directory.
• Loyalty and rewards platforms plans reward shops, points-plus-cash checkout, catalogue feeds and the integrations a rewards programme depends on.

The Solutions hub holds the workflow pages, and Industries provides sector context. Use them to examine exceptions and evidence limits before asking for a scope. The AI Workflow Blueprint is an assessment route where its defined scope fits; an AI build is not assumed.

AI workflow automation

This group asks whether a model belongs in the workflow, how it should be evaluated and where a person remains accountable. It is useful before choosing a model vendor or an agent framework.

• AI workflow automation guide connects candidate selection, system shape, model choice, evaluation and human review into one buying decision.
• AI automation use cases helps assess repeatability, data readiness, error consequences and whether simpler rules would be sufficient.
• AI agents versus workflows distinguishes fixed steps from delegated choices and the controls each arrangement requires.
• AI model selection defines the task, constraints and evaluation before selecting an implementation dependency.
• AI workflow evaluation turns real examples and failure cases into acceptance evidence and a repeatable regression check.
• RAG vs fine-tuning decides whether retrieval, tuning or both fit your data.
• AI proof of concept to production turns a working pilot into a supported service.
• LLM observability and monitoring plans traces, quality signals and alerts after release.
• MCP server integration plans how agents reach your systems through MCP.
• AI transformation roadmap builds the leadership team's portfolio-level AI plan.
• Human review in AI workflows examines review thresholds, routing, escalation and the capacity needed to handle exceptions.
• AI workflow governance questions lists what an approver should settle on ownership, data, accountability and audit before an AI workflow is signed off.

AI Workflow Automation describes the commercial build route. Its scope and acceptance criteria must be agreed for the buyer's actual process; a guide does not establish an accuracy or business-result guarantee.

Choosing a supplier and governing remote delivery

These guides apply to any supplier in any country, including Netbase. Use them before a shortlist and again once the work is running.

• Vendor evaluation criteria sets documented criteria for comparing software suppliers and states the operator's conflict of interest.
• Project outsourcing or staff augmentation compares who owns the outcome, the team and the risk under each arrangement.
• In-house vs outsourced development decides whether to build an internal team, outsource the project or combine both.
• Fractional or full-time CTO compares leadership models by company stage, pending decisions and handover.
• Remote delivery governance covers cadence, reporting, escalation and supplier onboarding for a running remote engagement.
• White-label development for agencies plans a partner build delivered under an agency's own brand.
• Offshore development centre sets up a dedicated, long-running team, from governance to exit.

Market-specific delivery questions

Each market guide identifies questions for the buyer's own advisers and integration owners. Official references inform the questions, but the guides do not decide which law applies to a particular business or establish local delivery presence.

• Software delivery by market compares the first questions each market raises and routes you to its guide.
• Nigeria focuses on data flows, payment-provider roles and the evidence needed to accept local integrations.
• UAE distinguishes jurisdiction, identity-service prerequisites, language requirements and project-specific acceptance.
• Singapore examines identity onboarding, data handoffs and the responsibilities behind a production integration.
• UK separates public-sector and private-buyer questions, accessibility acceptance and supplier handover responsibilities.
• Mauritius frames data and payment roles alongside continuity, ownership and acceptance of the operating process.
• Saudi Arabia covers bilingual Arabic and English acceptance, e-invoicing integration and data-protection questions before a Saudi project is scoped.
• United States covers contract terms, state privacy obligations and overlap hours for a project delivered remotely.
• Australia covers privacy obligations, handover windows and acceptance for a project delivered from another time zone.
• South Africa prepares personal-information, payment and acceptance questions for a project serving South African users.
• Kenya covers data-protection registration, mobile-money integration and acceptance for a Kenya-facing project.
• Canada covers federal and provincial privacy questions, English and French content and acceptance.
• Indonesia frames personal-data, local payment and language questions before an Indonesia-facing project is scoped.
• Philippines covers data-privacy obligations, payment integrations and support overlap for a Philippine project.
• Netherlands covers GDPR as applied by the Dutch authority, e-invoicing and payment habits.
• Germany covers data protection, works-council consultation, accessibility and e-invoicing formats.
• France covers CNIL guidance, accessibility, the e-invoicing reform and French-language requirements.
• Sweden covers GDPR as applied by the Swedish authority, accessibility, public-sector e-invoicing and BankID.
• Cyprus covers EU data protection under the Cypriot commissioner, bilingual delivery and small-market sourcing.
• Ghana covers the Data Protection Act, mobile money, Ghana Card identity checks and connectivity constraints.
• Malaysia covers the amended data protection act, the MyInvois e-invoicing mandate and local payment rails.

Emerging technology assessment

These pages support feasibility decisions. They separate approved delivery evidence from related Work records and from capabilities offered through a scoped assessment. A technology name in a guide is not a vendor partnership or a promise to implement it.

• Emerging technology adoption establishes the buyer's decision, experiment boundary, agent/tool permissions and assurance requirements.
• Production AI inference examines operating constraints, representative workloads, failure handling and evidence for a deployment decision.
• RAG and context engineering connects retrieval permissions, source provenance, freshness and answer evaluation.
• Multimodal document AI examines document inputs, extraction errors, review and evidence that survives the processing chain.
• Edge AI considers devices, offline behaviour, updates and field acceptance before a rollout commitment.
• Speech interfaces defines real-audio evaluation, consent, accessible alternatives and recovery when recognition fails.
• Robotics software feasibility limits the initial decision to software interfaces, simulation and qualified review before physical deployment.
• AI assurance and red teaming plans adversarial and misuse testing, and the release evidence it must produce, before an AI workflow goes live.
• AI agent tool permissions decides which tools an agent may call, with what consent and which controls against prompt injection.
• Embeddings and semantic search decides whether meaning-based search, matching or deduplication belongs in a product and how relevance is judged before release.

Read the evidence before choosing the service

A Work record may be named or anonymised and may contain an approved result or only a bounded scope. Read the individual record's permission, period and limitations. A related example can help you ask better questions; what it supports is the approved scope stated in that record.

The methodology explains how claims and conflicts are handled. Each guide should identify its sources and meaningful update date. Recheck time-sensitive official documentation before making a legal, security or integration decision, and request a correction when a source no longer supports the published wording.

Bring the decision and its constraints

Submit a project with the outcome, systems, unresolved decision and accountable owner. OutsourcingVN is Netbase's own outsourcing-services platform. The next step is to establish fit and scope, including the possibility that more evidence or a different approach is needed.

Related services and solutions