The X isn't a logo. It's how we work.
Four phases to take an idea to production, no gaps and no surprises. Each has deliverables, duration and owners; none gets skipped.
The four phases on the arms of the X
The logo turned into an infographic: each arm is a phase, and the center is where we decide whether to move on.
- Phase 01
Assessment
We step into the real operation. We map processes, bottlenecks and the cost of manual work.
- Phase 02
Design
Solution architecture, scope, roadmap and estimate. All in writing before the first line of code.
- Phase 03
Engineering
Sprint-based build with visible releases. Reviewed code, automated tests, continuous deployment.
- Phase 04
Adoption
Training, measurement and iteration. A system nobody uses solved nothing.
01 Assessment
Understand before building
We join your team on a real day. We don't ask how the process should work: we watch how it does.
- Deliverable · Operations map
- Duration · 1 to 3 weeks
- Who joins · Operations and leadership
- Decision · Go or stop
02 Design
Everything in writing before the code
Architecture, scope, roadmap and estimate. And what's left out, too: half of a project's conflicts start with “I thought it included…”.
- Deliverable · Scope document
- Duration · 2 to 4 weeks
- Who joins · Architecture and client
- Decision · Sign or adjust
# Scope · phase 02 ## Includes - solution architecture - data model - per-milestone estimate ## Not included - historical data migration 03 Engineering
Visible releases, not promises
Sprints with a demo. Every two weeks you see something that works, not a progress percentage in a spreadsheet.
- Deliverable · Software in production
- Duration · By milestone
- Who joins · Engineering team
- Decision · Demo every 2 weeks
04 Adoption
Until they run it on their own
Training, documentation and measurement against the goals set in phase 01. If nobody uses it, nothing was solved.
- Deliverable · Self-sufficient team
- Duration · 4 to 8 weeks
- Who joins · Real users
- Decision · Impact gets measured
What you get in each phase
The same table we use internally to close one phase before opening the next.
| Phase | Deliverable | Typical duration | How it closes |
|---|---|---|---|
| 01 | Operations map, cost of manual work and prioritized findings | 1–3 weeks | Presentation to leadership and a go decision |
| 02 | Architecture, written scope, roadmap and per-milestone estimate | 2–4 weeks | Scope sign-off, including what's left out |
| 03 | Software in production, automated tests and technical documentation | By milestone | A working demo on real data |
| 04 | A trained team, usage dashboards and measurement against the baseline | 4–8 weeks | Impact report against the phase 01 goals |
Why we don't skip phases
We're often asked: “we already know what we need, start coding”. This is what happens when we agree.
-
Without phase 01, the wrong process gets built
A workflow nobody follows gets automated, and the system is born obsolete.
-
Without phase 02, scope gets argued mid-build
It's the source of almost every relationship that ends badly.
-
Without phase 04, the system goes unused
The full investment gets paid and the operation stays the same. The worst of the three outcomes.
It all starts with phase 01.
A 15-minute meeting, no strings attached, to get to know your operation and what you need. The assessment comes after — and we tell you even if the answer is that technology isn't it.