A data model that fits
Your objects, your statuses, your rules. No field forced into a box it was not made for.
Country and language
Other markets: these available language versions show the same page.
Business software
Business software built around your process instead of the other way round. Designed, developed and maintained in Paris, with the source code delivered to you.
The problem
It starts as one file to track jobs. Three years later it has eleven tabs, four people editing copies of it, a macro nobody dares to touch, and a monthly figure that takes two days to rebuild. Off-the-shelf software did not fix it, because your process does not look like the one the software was written for, and the workaround became the process.
We develop the tool your work actually needs: quotes, jobs, planning, stock, invoicing, approvals, whatever the sequence happens to be in your business. We start from the real process, including the exceptions people handle by hand, and we build only what you ask for, in the order that helps you first. There is no per-seat subscription growing with every person you hire, and no module you pay for twice.
The software connects to what you already run, so figures are entered once and reconciled nowhere. You get a first usable version in weeks rather than at the end, then modules in your order of priority. At production you receive the source code, the database and the documentation, and you stay with us only for maintenance and new work.
What we build
Every project starts with a core, then grows module by module in your order of priority.
Your objects, your statuses, your rules. No field forced into a box it was not made for.
Quotes, orders, invoices and reports in your own layout, plus CSV, Excel and PDF exports that accountants accept.
Scheduled jobs, reminders, escalations and status changes that fire on rules instead of on someone remembering.
Accounting, payroll, e-commerce, telephony or machines on the shop floor, linked through APIs, files or webhooks.
The figures you rebuild by hand today, live: margin, load, delays, activity per team and per period.
Each person sees their scope and nothing else, and every change is logged with who, when and what.
How we work
Four stages, in this order. You sign off each one before the next starts.
A day with the people who do the work, to map the real process rather than the manual. Deliverable: a priced, prioritised scope.
1 to 3 weeksClickable screens for each path through the tool. You correct the mockup, where correcting is free.
2 to 3 weeksA testable delivery every two weeks, in your order of priority. You use the core while we build the rest.
8 to 16 weeksExisting data imported, teams trained, then maintenance and new modules. The source code is yours.
OngoingTechnology
Boring, well-documented tools that another developer can pick up in five years:
Example project
The same job was entered three times: once on a paper ticket, once in a planning spreadsheet, once in the invoicing software. We built a single job record from the call to the invoice, with the schedule and the accounting export attached to it.
Budget
The figure depends on the number of modules and on the integrations. Here is the usual starting point.
Indicative figure for a standard scope. Every quote is issued as a fixed price after the scoping phase, with no per-seat fee.
How it is priced
Two companies in the same trade never quite run the same process. We look at yours first — including the exceptions your team handles by hand — and then we put a fixed price on what actually has to be built.
After delivery
Business software keeps living: regulations change, your other tools change, your team asks for adjustments. The contract is drawn up alongside the quote, and it can be cancelled.
FAQ
It costs more on day one and less over five years, because there is no per-seat fee growing with the team. The honest test is simple: if a standard product fits your process without workarounds, buy it. We will tell you when that is the case rather than sell you a project.
A first usable version normally lands eight to ten weeks in. Your team works on the core while we build the remaining modules, which also means the feedback that changes the design arrives early, when changing it is still cheap rather than after everything has been written.
Often that is the better plan. We frequently keep the accounting or payroll software in place and build only the missing layer around it, connected through an API or a scheduled export. Replacing everything at once is rarely worth the risk when one weak link is the actual problem.
You keep the source code, the database and the documentation, and the software goes on running. Any competent development team can take it over, which is exactly why we write it with standard tools instead of a framework only we know. We help with the handover if you ask.
See also
Let's talk
Thirty minutes is enough to say whether custom software is the right answer for you, and to give you an honest range.