About Nexlab

A new company,
built by an
experienced team.

We’re an independent software engineering company in Ho Chi Minh City. Our team brings hands-on experience from products in insurance, education, finance and enterprise operations.

01Why we started Nexlab

Your engineers should understand your business.

That idea is the reason we started Nexlab. It shapes how we ask questions, plan the work and make technical decisions.

Our team has worked on insurance platforms, school administration, financial applications and enterprise workflows. We bring that experience, then learn the details that are specific to your organisation.

You’ll know who is working on the product, what has been completed and what needs a decision from your team.

02The experience we bring

People who understand
the work behind the software.

Our portfolio brings together project experience from the people at Nexlab. Each case study explains the application, the integration work and the business process involved.

Who you work with

Before an engagement starts, we agree the people responsible for delivery, technical decisions and acceptance on both sides. Your team should know who to speak to about a question, a change or a risk.

03Evidence you can review

Start with the work,
not a sales claim.

We use published project examples and a clear delivery scope to explain what our team has done. Where a capability has no public case study, we say so.

12

published project examples

Each case study names the business process, delivery scope and technologies involved.

07

business areas represented

Insurance, education, enterprise operations, financial applications, healthcare, community systems and security product engineering.

04

client and partner markets

Dubai, Switzerland, Singapore and Taipei, supported from our delivery base in Vietnam.

04Clear responsibilities

Know who owns
the next decision.

We keep individual profiles private. At the start of an engagement, we still make the working roles and decision paths clear.

Role 01

Business owner

Explains the workflow, priorities and business rules, then accepts the result against the agreed criteria.

Role 02

Delivery owner

Keeps the plan, decisions, dependencies and communication clear across both teams.

Role 03

Technical owner

Guides architecture, code review, integration choices and the technical path to release.

Role 04

Engineering & quality

Builds and checks the software, documents the work and prepares it for handover.

05How we work

Simple habits that
keep projects on track.

These are the expectations we set for planning, development and handover. We adapt the details to each client and project.

01

Start with a shared brief

Agree on the scope, what done means and who owns each decision before development starts.

02

Keep the work visible

Review code, run automated checks and show working software regularly.

03

Give people the access they need

Set access by role, keep secrets out of code and separate development from production.

04

Plan the handover early

Write documentation, confirm source ownership and share operational knowledge as we build.

06Based in Vietnam · Working internationally

Ho Chi Minh City is home.
Our clients are worldwide.

We work with clients and partners in Dubai, Switzerland, Singapore and Taipei, with a schedule agreed around each team.

SwitzerlandDubaiTaipeiSingaporeHo Chi Minh CityDelivery base
Four client and partner marketsOne delivery base in Vietnam
  • Home · GMT+7Ho Chi Minh City--:--Delivery base
  • EuropeSwitzerland--:--  from HCMC
  • United Arab EmiratesDubai--:--  from HCMC
  • East AsiaTaipei--:--  from HCMC
  • Southeast AsiaSingapore--:--  from HCMC

Different locations.
A shared way of working.

Dubai, Switzerland, Singapore and Taipei are client and partner markets. Our office and delivery base are in Ho Chi Minh City.

Agree the overlap

Our delivery base is Ho Chi Minh City, GMT+7. We agree meeting times around your team and revisit them when working hours or seasonal clock changes affect the schedule.

Keep decisions easy to follow

Project communication and shared documentation can be in English. We agree the main contact, communication channel and review schedule before development starts.

Keep work moving between meetings

Written updates capture completed work, open questions and decisions needed. Demos and a shared backlog give both teams a common view of what comes next.

07How we work

You’ll always know
what’s happening.

You work directly with the people building your software. We share decisions, progress and risks as the project moves.

  1. 01 / 04

    Listen

    We review the workflow, existing systems and the people using them. Together we agree on the problem, priorities and open questions.

  2. 02 / 04

    Plan

    We agree the scope, responsibilities and acceptance criteria. Dependencies and decisions that affect the schedule are recorded before the build.

  3. 03 / 04

    Build

    We build in short cycles with code review and agreed checks. Demos give you a chance to review the product and make informed decisions about changes.

  4. 04 / 04

    Launch

    We review readiness, prepare deployment instructions and walk your team through the system. Ongoing support responsibilities are agreed as part of handover.

A software team discussing work beside a planning board
08Work with us

Bring your
point of view.

We’re looking for people who take pride in their craft and enjoy working openly with a team.

See open roles
Have a project in mind?

Let’s talk it through.

A short note is enough. Tell us what you’re working on and where you need help.