Skip to main content

What are you looking for?

Explore our services and discover how we can help you achieve your goals

Global delivery: remote-first from Hanoi

OutsourcingVN projects are operated by Netbase JSC, headquartered in Hanoi, Vietnam, and delivered remote-first to clients in other countries. The team is built for the project, not by nationality, with one accountable delivery owner however it is composed. This page explains where the work happens, how teams are put together and how location affects security, intellectual property and communication.

Submit a project View our work

Reviewed by Huy Nguyen (David), CEO · Updated 3 Nov 2026

star

Hanoi headquarters, remote-first delivery

Netbase JSC's head office is in Hanoi, and it is the company's only office. Netbase serves clients in the United States, Europe and Asia-Pacific from there. Those markets are a delivery footprint rather than a map of offices: Netbase has built web-to-print stores with online design tools for print businesses in Singapore, France, the Netherlands and South Korea, and Magento stores with companion Android and iOS apps for fashion retailers in the Netherlands and Nigeria and for a parts and equipment seller, all delivered from Hanoi for clients that are not named. Netbase's Clutch profile carries client reviews from businesses in Romania, Spain, Sweden, France, Denmark, the Netherlands and Belgium. Remote delivery is the default because it gives access to the right specialists, avoids unnecessary travel and produces a written record of decisions and evidence.

Being remote-first does not mean remote-only, an office, employees or round-the-clock coverage in your country: local presence is scoped as its own activity.

How is a project team composed?

A team can combine several kinds of contributor, all under Netbase management:

Contributor type What they do Best for
Netbase core delivery Netbase employees and core delivery capability based in Vietnam The steady core of the team
Netbase-managed specialists Specialists working from other locations when the scope needs a skill Filling one specific skill gap
Approved partners Subcontractors or delivery partners, disclosed as your contract, security or procurement rules require Scopes needing a disclosed partner
Your own people Your product owners, engineers and subject-matter experts, with responsibilities written into the plan Keeping product decisions in-house

Contributors are selected for role fit, delivery evidence, language, time-zone overlap, availability, continuity, data and security requirements, and project economics. Whoever contributes, Netbase keeps responsibility for the plan, role assignment, access control, quality, milestone verification, reporting and handover.

When does hybrid or onsite work make sense?

  1. Discovery and workshops

    Process mapping, stakeholder alignment or architecture workshops where being in the room shortens the path to decisions.

  2. Restricted access and cutover

    Facility-restricted systems, migration or launch cutover, and incident response that need physical presence.

  3. Acceptance and adoption

    User acceptance sessions, training and handover where the people receiving the system need hands-on support.

Onsite work is available on request and scoped as a project decision. The statement of work records its purpose, location, dates, roles, travel and local compliance responsibilities, expenses, security and workplace-access rules, and the return to remote operation. It is not a promise of immediate local staffing in every country.

Time zones and working hours

The Hanoi office works Monday to Saturday, 9:00 to 18:15 Vietnam time (UTC+7), and support coverage follows those days. To make that work across regions:

  • each project agrees its overlap window, the hours when both sides are available for calls and decisions;
  • written, asynchronous updates carry routine status, so work continues outside the overlap;
  • meetings are kept for decisions, discovery, demonstrations, incidents and unresolved risks;
  • response and acceptance windows are agreed per project, and escalation contacts are set before any production access.

Round-the-clock coverage is not offered by default. Where a project needs extended hours, they are defined and agreed in the contract before they are relied on.

Language and communication

Project communication, documentation and deliverables are in English unless the contract says otherwise. Written decisions and status updates reduce the risk of misunderstanding across languages and time zones, and important agreements are confirmed in writing after any call. If your users or stakeholders need another language, for example for user acceptance or training, that requirement is scoped with the activity.

Security and data across borders

Cross-border work changes who can access data, from where, and under which rules. These points are settled in discovery and the contract, not assumed:

  • where data is stored and processed, and which contributors may access it;
  • role-based access control and MFA for admin dashboards, with access to your environments granted per role, following NIST's standard definitions of each control;
  • secure code review and version control as standard practice;
  • contributors working under NDA, with NDAs and DPAs available on request.

The privacy policy explains how this site handles information you send us.

Where does AI help across a distributed team?

Netbase delivery uses AI-assisted engineering under human review, wherever the contributor sits. Any restriction you place on AI tool use for your code or data is written into the project, the same as any other cross-border data rule.

Intellectual property

For custom development, the intellectual property created for you belongs to you. Netbase's productized modules and products, where a project uses them, are licensed rather than transferred, and the proposal identifies them before you accept it. Contributors from any location work under the same terms.

One accountable delivery path

However many locations are involved, the project has one delivery owner, one milestone plan and one route for risk, change and acceptance. Distributed sourcing does not dilute accountability. The project delivery page explains how milestones, reviews and handover work, and the engagement models page explains how this compares with other ways of buying outsourced work. For the reporting, escalation and evidence rules to request from any distributed supplier, see remote delivery governance.

What distributed delivery means in practice

Most day-to-day work happens in shared, access-controlled tools: your repositories, a project workspace for scope and decisions, and agreed chat and call channels. Work passes between contributors through written handoffs, code review and documented decisions, not hallway conversations. That keeps progress visible at any hour, lets a specialist join one milestone without disrupting the team, and leaves a record that survives role changes.

If you are choosing Vietnam specifically

Some buyers start from the country question. The Vietnam outsourcing guide covers what to check when outsourcing software work to Vietnam, the vendor evaluation criteria apply to any shortlist wherever the supplier sits, and the about page explains who operates OutsourcingVN.

Common questions

Yes. The roles on the project, and any subcontractor or partner involved, are disclosed at the level your contract, security or procurement rules require.

Yes, when an activity justifies it. The visit is scoped with its purpose, dates and roles, and agreed before it is relied on.

Often, yes. Contributors can work inside your environments with access granted per role, and the data rules are set in discovery and written into the contract.

Not when the overlap window, response times and decision owners are agreed up front. Written updates let you review progress on your own schedule, and urgent issues follow the project's escalation path.

Talk to Huy Nguyen (David), Founder and CEO of Netbase JSC: message him on WhatsApp at +84 937 869 689 or email project@netbasejsc.com. You can also send your brief through the project request form. Say which workflow or system the project concerns and what has to stay unchanged; the first step is a discovery conversation, and scope and milestones are agreed after it.

Plan the distributed delivery decision

Choose the engagement model before staffing a plan: project outsourcing or staff augmentation, in-house against outsourced delivery, managed outcomes for a system already in production, or specialist sprints for one bounded skill gap, and see white-label development for agencies if you are reselling the work. Then define the overlap and handoff window, the data and access boundary and the total delivery worksheet. Those are separate decisions; location alone settles neither ownership nor security. The commercial route is Custom Product Engineering.

The multi-vendor marketplace mobile app record is adjacent delivery evidence for engineering scope; ask for a project-specific plan first.

Scope delivery for a specific market

The market delivery index compares all sixteen guides side by side and routes you to the right one; use the Nigeria, UAE, Singapore, UK, Mauritius, Saudi Arabia, United States, Australia, South Africa, Kenya, Canada, Indonesia, Philippines, Netherlands, Germany and France buyer guides to identify local questions for your own advisers and integration owners.

Tell us where your team and users are

We will plan around it: submit a project. OutsourcingVN is operated by Netbase JSC and is Netbase's own outsourcing-services platform.

Tell us what you want to build or automate.

Submit a project