[1–2 wks]
Audit
You get
Operations map, UX audit, a priority list
We need
Access to the current system and time with a few of the people who use it daily
How we work
GMT+4
This is the rhythm every project runs on: the phases, who is in the room, what we need from you, and when you will hear from us. No guesswork about what happens next.
The thinking behind it: our methodologyFour phases
How we work
Floréal, Mauritius — GMT+4
01 — Your working day
Mauritius, GMT+4 · Winter times · Europe gains an hour of overlap in summer
02 — Phases
Typically 6–16 weeks from kickoff to launch. The bars show a 16-week project.
[1–2 wks]
You get
Operations map, UX audit, a priority list
We need
Access to the current system and time with a few of the people who use it daily
[2–3 wks]
You get
A clickable prototype on your real data, tested with users
We need
A sample data export and the weekly review slot
[6–10 wks]
You get
Figma design system, developer-ready specs, build QA
We need
A developer contact and written sign-off at each milestone
[support window]
You get
Launch support, training notes, fixes
We need
A named owner on your side after go-live
03 — Every week
Review
In your morning, in the calendar for the whole project. We show working screens, not slides.
Update
What was done, what is next, and the decisions we need from you — with dates.
Decisions log
The Figma file and a running log of every decision, readable by your team at any time.
04 — After launch
Software meets real users on launch day. That is when most of the useful fixes appear.
Included
[X weeks] of fixes and adjustments after launch, at no extra cost.
Optional
Monthly monitoring, small changes and automation upkeep.
Ongoing
A standing team for the next range, the next portal, the next pipeline.