Diagnostic: five days to know what you are building
Before talking about development, you need to know who uses what, what must connect to what, and which regulatory constraints apply. That is what the diagnostic does.
12,000 – 30,000 DH depending on scope (≈ $1,290 – 3,300)
What you receive
A map of roles and permissions: who sees what, who approves what, and where the conflicts nobody had written down are.
An inventory of integrations: your existing tools, the bodies you submit to, and what will have to be reworked or replaced.
The regulatory constraints applying to your data — law 09-08 and sector obligations — and what they impose on the system.
A prioritised backlog with an effort estimate per block, so you can decide what ships first.
A costed scope: what the first version costs, and what can wait for the second.
The document is yours. If you decide to have the project built elsewhere, you leave with a usable specification — that is the point.
How it runs
- 1
A one-hour kickoff: your context, your irritants, what you have already tried.
- 2
Two or three interviews with the people who will actually operate the tool. Not only management — the manager and the field agent know things that never reach the top.
- 3
A technical review of what exists: data, tools, integration points, hosting constraints.
- 4
A ninety-minute readout, with the document and the costing. You ask your questions there, not three weeks later.
Why it is paid
Because a free assessment mostly attracts people who were not going to buy, and consumes the time needed by those who were. A modest fee filters the former without costing the latter anything.
And it is credited in full against the framing sprint if you continue. In practice, if you go the whole way, the diagnostic cost you nothing.
Book a diagnostic
Tell us in two lines what you are trying to solve. We will come back with a slot and a proposed scope.