Fits
One core system or module with its full flow, the key integrations, automations, an AI assistant, an online store or an app with the essentials.
Protocol 21
Most software projects fail because the scope is never closed and the date moves every week. We do the opposite: we put in writing what we will build, fix the date and use artificial intelligence to work faster. If something has to change, what we build changes, never the date.
The 5 phases
Day 0
A free diagnosis of the problem.
You get: A diagnosis document, the problem measured, what counts as “done” and the access list. If the project does not fit in 21 days, we tell you here.
Days 1-4
We put in writing what will be built.
You get: A contract with scope and date.
Days 5-14
We build the core.
You get: A first version working end to end.
Days 15-18
Real data, security, integrations and testing.
You get: A system tested with real information.
Days 19-21
We put it live and hand everything over.
You get: Code, passwords, manuals and training.
Scope
One core system or module with its full flow, the key integrations, automations, an AI assistant, an online store or an app with the essentials.
Replacing a full accounting system, projects with dozens of integrations or systems that need prior certifications.
They are split into 21-day cycles, each with a working delivery.
Not everything needs 21 days: a simple website can be ready in 7.
Day 21
Next step
We review it with you in the free 30-minute diagnosis. If it does not fit, we tell you that too.