How we work
You see working software every week
Fixed scope, fixed price, written milestones. Most software projects fail in the gap between what was agreed and what was assumed, so we close that gap in writing before anyone starts.
The shape of an engagement
- Step 01
A call Thirty minutes. You describe the problem. We say whether we are the right people, and sometimes we are not.
- Step 02
A written scope What is included, what is not, what it costs and when it lands. You approve it before anything is built.
- Step 03
Weekly builds A demo every week on real software, not a status report. You redirect early, while it is still cheap.
- Step 04
Launch Into production, with the monitoring and the handover documents written while we still remember why.
- Step 05
The month after Included. The first weeks of real traffic are when you find what testing missed, and we are still there.
We agree the number the system is meant to move before we build it, and we report against that number rather than against a task list. More bookings, fewer missed enquiries, faster collection, whichever one your business actually needs.
After launch
Run
A monthly price. Optional, and most clients take it, because the systems we build are the ones a business cannot have down.
We build and run these systems. Running yours is a real offer with a real price, not a favour we do between projects.
We operate it
Monitoring, updates, and the operator failures that are nobody’s fault and still have to be fixed by somebody.
We watch the spend
Messaging and AI usage bill per use and grow with your success. We review the wallet monthly and tell you before it surprises you.
We report the number
The one we agreed before the build. If it is not moving, that is the conversation, not the uptime percentage.
What we will tell you
Including the parts you would rather not hear
When not to build it
Sometimes the answer is a spreadsheet, a tool you already own, or nothing at all. A supplier paid by the hour has no reason to say so. We run our own systems, so we know what a bad build costs for years afterwards.
What the running costs will be
Messaging, hosting, payment fees and AI usage all scale with your success. They appear in the proposal as numbers, with allowances, not as a line saying unlimited.
Where the regulation sits
If your design touches payments or personal data in CEMAC, we will say so at scoping. Finding out after launch is the expensive version.
Two languages
We write, meet and ship in French and English. Documentation comes in whichever one your team actually reads.
One timezone
Central Africa Time overlaps the whole European working day. No handover notes written for somebody asleep.
Your code
You own everything we write for you, in your repository, from the first commit. That is in the contract.
Start with the thirty minutes
You leave with a view on scope, cost and timeline, whether or not you work with us.