The six steps at a glance
-
Discovery and strategic alignment
Goals, users, constraints and success measures are agreed
- Netbase owner
- Account manager, business analyst, solution architect
- What you get
- A shared scope, priorities and the KPIs the project will be judged on
-
Team assembly and architecture planning
The right team is formed and the technical design is set
- Netbase owner
- Project manager, solution architect
- What you get
- A named team of 3 to 30 people and an architecture plan
-
Agile execution with outcome-based milestones
The product is built in short increments tied to outcomes
- Netbase owner
- Project manager, developers, QA, UI/UX
- What you get
- Working software at each milestone, reviewed every week
-
Modular and productized components
Proven modules are reused where they fit, custom code where they do not
- Netbase owner
- Solution architect, developers
- What you get
- Less rebuilt plumbing and more time on what makes your product different
-
Training, rollout and optimization
Your users are trained, the release goes live and early results are tuned
- Netbase owner
- Project manager, QA, business analyst
- What you get
- A launched system your team knows how to run
-
Ongoing support and co-building
The platform keeps improving with the same accountable team
- Netbase owner
- Account manager, project manager
- What you get
- A long-term partner rather than a handover and goodbye
Step 1: Discovery and strategic alignment
Discovery asks the hard questions early: which workflow is broken, who uses the system, what it must connect to and what "done" means in numbers.
Your part a decision-maker who can set priorities, access to the people who do the work today, and honest answers about budget, deadlines and existing systems.
Step 2: Team assembly and architecture planning
With the scope agreed, Netbase assembles a team sized to the job: from 3 to 30 people, from business analysts and architects to developers, QA engineers and UI/UX designers. Work typically starts within 1–2 weeks after discovery, with the architecture plan set in parallel.
Your part confirm the team shape, name your own product owner and approve the architecture direction.
Step 3: Agile execution with outcome-based milestones
Each milestone is defined by an outcome, a workflow that now runs or a journey that now converts, not by hours burned. This follows the agile value of working software over comprehensive documentation (Agile Manifesto, 2001). QA works inside each increment.
Your part join the weekly review, test what is delivered and decide quickly when trade-offs appear.
Step 4: Modular and productized components
Netbase builds with modular, productized components: parts that have already run in production. Where a module fits, reuse removes risk and time; where it does not, the team writes custom code and keeps the seams clean. The SaaS product accelerator shows how that reuse is packaged for new products.
Your part decide where standard behavior is good enough and where your differentiation lives.
Step 5: Training, rollout and optimization
Netbase trains your users and administrators, rolls the release out and watches the KPIs agreed in discovery, then tunes what real usage reveals.
Your part schedule your people for training, own internal communication and share the business data the KPIs depend on.
Step 6: Ongoing support and co-building
After launch, the same accountable team can keep supporting and extending the platform, with new features going through the same weekly review.
Your part keep a product owner engaged and bring new priorities to the review rather than to a ticket queue.
Agile delivery: sprints and weekly demos
Work is planned in short sprints against the outcome-based milestones of step 3. Every week the team demos working software in the review, you accept or redirect it, and the backlog is re-ranked. Progress is visible between reviews in the project tracker (Jira, Redmine, Trello or GitHub).
Lean: discovery first, then the smallest release that proves value
Lean delivery removes work that does not move a measure. Discovery tests the riskiest assumption before the build budget is spent, the first release is a minimum viable product or pilot measured against a baseline, and features that do not earn their keep are cut rather than polished.
Remote-first, distributed delivery
Netbase delivers remote-first from its Hanoi head office, in English, Monday to Saturday from 9:00 to 18:15 Vietnam time (UTC+7). It overlaps Asia-Pacific hours and the European morning; with the Americas, work runs asynchronously, with calls at the edges of both days. Day-to-day channels are Slack, Zoom, Skype or Chatwork, and source code lives in GitHub.
Security by design and DevSecOps
Security is part of each increment, not a final audit: secure code review on every change, vulnerability scanning, role-based access and MFA for admin dashboards, and encryption in transit and at rest. The full controls are on security and compliance.
API-first architecture
Architecture planning (step 2) defines the APIs before the screens. Web and mobile apps, partner systems, IoT devices and AI features then use the same documented interfaces, so a new channel or model can be added without rebuilding the core.
AI-augmented delivery
AI enters the process twice. For your product, step 1 asks where AI would change the workflow, and the answer is scoped, built and measured in the same milestones as everything else; company-wide change runs as AI transformation. In our own delivery, AI-assisted tools chosen per project help draft user stories and test cases, review code and triage logs; an engineer reviews every output before it merges or ships. Each item below states how mature it is at Netbase.
-
In delivered work
Product recommendation engine
Built for 4over4 from browsing and purchase history.
-
Available capability
Machine learning, NLP, computer vision, generative AI and AI with IoT
AI capability areas Netbase offers; beyond the 4over4 features they are not yet tied to a published case.
Governance that keeps you in control
Netbase governance is built on three habits:
-
Weekly reviews
Progress, risks and decisions are reviewed with you every week.
-
Named accountability
A dedicated account manager owns the relationship and a project manager owns delivery.
-
Open channels
Client dashboards show status between reviews.
Who the process is for
The six steps fit companies building or modernizing a business-critical platform. If you need capacity inside your own roadmap rather than a full project, the same governance applies to our dedicated development teams. Where the process is heading is set out in our vision.
See the process in delivered work
The 4over4 e-commerce conversion case study and the Geo-Tek IT e-commerce platform case study show engagements Netbase delivered, with measured outcomes. Browse all of them in our work, or read the rest of the trust record under Why Netbase.
Start with a delivery review
Review your delivery plan with Netbase: we will show how the six steps apply to your scope, who would be on the team and when work could start.
Frequently asked questions
Both. Discovery fixes the scope and price, then the build runs in Agile increments, so priorities can move inside the agreed change process.
Only tools you approve, under your data and security rules. AI suggestions are reviewed like any other change, and you can switch AI assistance off for sensitive repositories.
Not without your agreement. Model and hosting choices are made per project in discovery, and data handling can be written into an NDA and DPA.
Discuss a project
Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.+84 937 869 689
91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam
Get in touch
Tell us what you want to build, modernize, or operate.