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

• Where should you start?
• 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
• What evidence should you read before choosing?
• Common questions
• Bring the decision and its constraints

Where should you start?

A pillar explains a broad decision; a supporting guide examines one part in detail. The index lists each guide once; the pages connect the journeys they share.

Use global delivery for the operating model, project delivery for scope and acceptance, and engagement models for contracting, with managed outcomes and specialist sprints beside a project. Choose the unresolved decision, collect the suggested evidence and record who accepts 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 to request before committing.
• Comparing software outsourcing companies explains documented criteria for comparing providers without inventing a 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 stays uncertain.
• Vietnam vs India compares overlap hours, language, talent depth, data rules and supplier checks.
• Vietnam vs the Philippines compares engineering-led and support-led delivery, language, time zone and data rules.
• Vietnam vs Poland sets offshore beside European nearshore on overlap, GDPR, contract law and governance.
• Vietnam vs Latin America weighs offshore and nearshore for North American buyers: handover, language, legal footing.
• Time-zone collaboration ties overlap windows, written handoffs, decision owners and escalation to the 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.

• 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.
• IP ownership separates transferred custom work from licensed dependencies and the terms to settle.
• Data security and compliance sets out access, review, data-handling and incident questions for the buyer's 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 any replacement plan.
• Scope boundaries records what is in, what is out and what the buyer owns.
• Acceptance criteria shows how to write criteria a test can pass or fail.
• Change control sets how a change request is raised, sized, approved or declined.
• Project risk register lists delivery risks, owners and triggers before the project starts.
• Fixed-scope or milestone contracts compares contract shapes by how much scope is known at signing.
• Custom build or SaaS weighs building a capability against subscribing, 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 answers.
• Laravel SaaS development plans tenancy, roles, billing rules, queues and schema migrations on Laravel.
• Laravel mobile app backend plans API versioning, token authentication, push notifications and offline sync on Laravel.
• AI-assisted software delivery shows how review, ownership and evidence change with human-reviewed AI assistance.

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 changing an existing system without treating a rewrite as the default.
• Replace, refactor, wrap or retain compares options against constraints, evidence and the cost of keeping a dependency.
• Incremental modernization explains bounded changes, coexistence, parity and when to retire the previous path.
• Legacy PHP to Laravel migration applies the incremental method to Laravel: behaviour tests, module-by-module moves, staged cutover.
• AngularJS to Vue.js migration moves AngularJS interfaces to Vue.js component by component, with tests pinning behaviour.
• Legacy data migration covers profiling, mapping, reconciliation, exceptions and the evidence to accept transferred data.
• Vtiger CRM to ERP migration maps modules, custom fields and workflows to an ERP and plans cutover.
• QuickBooks to Odoo migration moves accounting, open items and balances into Odoo with a parallel close.
• Redmine to ERP migration moves projects, issues and time entries into ERP project and timesheet modules.
• MySQL to PostgreSQL migration plans schema conversion, SQL and ORM differences, change sync and cutover.
• Legacy system risk assessment identifies the technical and operating uncertainties to resolve before a larger commitment.
• Software technical due diligence scopes a code, architecture and operating-risk review before an acquisition or investment.
• Technical debt assessment ranks debt by business consequence, so remediation competes with features fairly.
• Managed software operations scope defines systems, coverage hours, service levels and exit terms for operations.
• 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 a release needs before approval.
• E-commerce modernization checklist covers catalogue, checkout, extensions, data and search continuity when a platform changes.
• Headless vs traditional e-commerce compares an API-first architecture with a coupled storefront.
• Headless Magento with Next.js plans GraphQL coverage, checkout, caching and multi-store for a decoupled Magento store.
• Magento vs WooCommerce weighs the two commerce platforms against catalogue, store count and team.
• WordPress to headless CMS migration plans the content model, URL mapping, redirects, editor workflow and phased cutover.
• Magento to WooCommerce migration plans data mapping, extension equivalents, URL and search parity and cutover.
• WooCommerce to Magento migration moves a growing store to Magento: mapping, redirects, search parity, rehearsed cutover.
• Magento 1 to Magento 2 migration plans the extension audit, data migration, theme rebuild, delta rehearsal and cutover.
• Magento 2 upgrade plans a 2.4.x upgrade: support window, extensions, a staging rehearsal and rollback.
• Magento malware recovery plans cleaning and hardening a compromised store: triage, cleanup, patches and monitoring.
• Shopify to WooCommerce migration plans the move off Shopify: data mapping, plugins, redirects, payments and cutover.
• Magento for fashion retailers plans size and colour variants, returns, merchandising, multi-store set-up and stock locations.
• Magento for parts and equipment sellers plans part-number search, compatibility data, B2B ordering, quotes and multi-warehouse stock.

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 chooses between process change, configured software, deterministic automation and bounded AI.
• 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 where a commitment begins.
• Laravel marketplace development plans vendor onboarding, order splitting, commissions, payouts and the mobile app API.
• 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.
• Odoo for retail chains plans point of sale, store stock, replenishment, promotions and a store-by-store rollout.
• Odoo for manufacturers plans bills of materials, routings, work centres, costing and a line-by-line rollout.
• Odoo for distributors plans replenishment, multi-warehouse stock, lots, barcode picking and a warehouse-by-warehouse rollout.
• Odoo for food and beverage chains plans restaurant point of sale, recipes, central kitchen production and perishable stock.
• Odoo for energy and engineering projects plans project costing, timesheets, purchasing per project and milestone invoicing.
• Odoo for service and warranty networks plans helpdesk, field service, repairs, warranty checks and service parts stock.
• Odoo for education institutes plans admissions, courses, tuition invoicing, staff and budgets for an institute.
• WooCommerce and Odoo integration sets record ownership, connector or API sync, conflict rules and invoicing.
• Magento and Odoo integration sets record ownership, connector or API sync, multi-source inventory and conflict rules.
• Shopify and Odoo integration sets record ownership and compares an app connector with custom sync.
• Odoo API integration connects custom applications to Odoo's external API with access rights and retries.
• Data platform readiness checks data ownership, quality, access and integration before a platform commitment.
• Local business directory launch plans listing sources, claim and verification, categories and a mobile-first launch.
• Loyalty and rewards platforms plans reward shops, points-plus-cash checkout, catalogue feeds and programme integrations.

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.
• AI automation use cases assesses repeatability, data readiness, error consequences and whether simpler rules suffice.
• 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 regression checks.
• 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 settles on ownership, data, accountability and audit.

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 supplier criteria and states the operator's conflict of interest.
• Project outsourcing or staff augmentation compares who owns the outcome, the team and the risk.
• In-house vs outsourced development decides whether to build an internal team, outsource 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. Regulator references inform the questions; the guides do not decide which law applies to a particular business.

• Software delivery by market compares each market's first questions and routes to all thirty-three country guides.
• Arabic right-to-left commerce plans bilingual Arabic and English stores: direction, fonts, numerals, search and launch.
• Nigeria focuses on data flows, payment-provider roles and accepting 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, continuity, ownership and acceptance of operations.
• Saudi Arabia covers bilingual Arabic and English acceptance, e-invoicing integration and data protection.
• United States covers contract terms, state privacy obligations and overlap hours for remote delivery.
• Australia covers privacy obligations, handover windows and acceptance across time zones.
• South Africa prepares personal-information, payment and acceptance questions for 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 for an Indonesia-facing project.
• 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 under the Swedish authority, accessibility, public-sector e-invoicing and BankID.
• Cyprus covers EU data protection under the Cypriot commissioner and bilingual delivery.
• Ghana covers the Data Protection Act, mobile money, Ghana Card checks and connectivity.
• Malaysia covers the amended data protection act, MyInvois e-invoicing and local payment rails.
• Romania covers GDPR under the Romanian authority, RO e-Factura, accessibility and Romanian-language acceptance.
• Denmark covers GDPR under the Danish authority, MitID, public-sector e-invoicing and bookkeeping rules.
• Thailand covers the Personal Data Protection Act, PromptPay, e-Tax invoicing and Thai interfaces.
• Qatar covers the privacy law, Arabic and English interfaces, digital identity and payments.
• India covers the DPDP Act, UPI, GST e-invoicing, Aadhaar-based checks and Indian languages.
• Colombia covers Law 1581 data protection, DIAN e-invoicing and PSE and Bre-B payments.
• Spain covers GDPR under the Spanish authority, Verifactu, Bizum and co-official languages.
• Poland covers GDPR under the Polish authority, KSeF e-invoicing, BLIK and Polish-language duties.
• Portugal covers GDPR in Portugal, SAF-T and ATCUD invoicing and MB WAY payments.
• South Korea covers the Personal Information Protection Act, identity verification and Korean-language interfaces.

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 deployment evidence.
• RAG and context engineering connects retrieval permissions, source provenance, freshness and answer evaluation.
• Multimodal document AI examines document inputs, extraction errors, review and evidence through 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 first decision to software interfaces, simulation and qualified review.
• AI assurance and red teaming plans adversarial and misuse testing and the release evidence it must produce.
• AI agent tool permissions decides which tools an agent may call, with consent and prompt-injection controls.
• Embeddings and semantic search weighs meaning-based search, matching and deduplication, and how relevance is judged.

What evidence should you read before choosing?

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 FTC's endorsement guidance makes the general version of this point: an exceptional result shown in a case study needs its own disclosure of what a buyer should typically expect, not an assumption that one record generalises.

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

Sources

• FTC, "FTC's Endorsement Guides: What People Are Asking"