Four steps from discovery to go-live, with a deliverable at every one
Each step has an output you keep, a decision point before the next one starts, and a clear ask of your team. You know where the project stands without having to ask.
01The four steps
How a project runs
The same four steps for a digital-transformation or a software project. Each step scales with the work; the order does not change.
- 01
Discovery & consulting
We sit with the people doing the work and reconstruct the real process: where data lives, which actions repeat, where the same number gets typed twice. You end the step with a map of current operations and a list of bottlenecks ranked by the time they cost.
- 02
Solution design
From those bottlenecks we draft the new workflow, what is in scope and what is explicitly out, the systems to integrate with, and the order of rollout by phase. You approve the plan before any code is written.
- 03
Build & integrate
We build in phases, each one running and in your hands. Integration with your POS, accounting and existing sales channels; legacy data migrated and reconciled. Before go-live, a parallel run with a small group.
- 04
Training & support
Training per role, handover of documentation and admin access. After go-live we stay close through the early period, resolve what surfaces, and keep tuning based on how your team actually uses it.
02Outputs and your part
What you receive, what we need from you
No step ends in a meeting. Each one leaves behind a document or a working system that is yours.
After discovery
You receive: a written picture of current operations, a prioritized list of bottlenecks, and a recommendation on where to start. We need: time with the people who own the process, and access to the workflows, forms and data in use.
After design
You receive: scope, workflows, the integration list, a phased plan and a cost estimate. We need: one decision-maker to approve scope — scope settled late is the most common cause of delay.
During build
You receive: a working build at the end of each phase, a test environment, test results and a visible record of defects fixed. We need: someone to accept each phase and give feedback within the agreed window.
At handover
You receive: the live system, admin accounts, role-based documentation, and source code and data as agreed in the contract. We need: a named internal administrator for the team to hand over to directly.
What gets handed over — documentation, source code, data — is written into the contract before work starts.
03Day to day
What happens between the milestones
How the work runs week to week — the same for project-based work and lab-type teams.
One owner, one channel
Every project has one person at DXS accountable for answering you. Day-to-day conversation runs in a shared channel; on Japanese projects, BrSE and comtor work directly in Japanese so requirements are never translated twice.
Weekly progress sharing
Each week you get what shipped, what is in progress, what slipped and why. Blockers are raised when they appear, not saved for the end of a phase.
Quality has a process
Code is reviewed against the team's standards and tested before it reaches you for acceptance. Defects are tracked on one list that you can see.
Handover does not depend on one person
Documentation and source code live in the shared repository, not on someone's laptop. When a team member changes, the next one picks it up from there; your information is handled under NDA.
04Get started
Start at step one
The first consultation is discovery in miniature: you walk us through how you run today, we point at what is worth doing first. Free, no strings attached.
- Review the process costing you the most time
- Define what belongs in a first phase
- Sketch a roadmap and rough estimate
Request a consultation
Leave your details and the DXS team will get back to you shortly.