Architects who learn your business
On-site immersion, a map of the process as it really runs, your words on the screens. Scoping happens at your place, not over video calls.
Four kinds of expertise work on your project: solution architecture, AI integration, support for your teams, security of your data. Here's who does what, when, and what you get out of it.
WHAT YOU ARE ACTUALLY BUYING
On-site immersion, a map of the process as it really runs, your words on the screens. Scoping happens at your place, not over video calls.
Data entry, extraction, drafting, alerts, follow-ups: AI takes on the repetitive work. Never your calculations.
One person from day one to go-live: they deliver, they train, they hand the skills over to your teams.
Role-based access, an access log, tested backups. Every spreadsheet that disappears is one fewer copy of your data out in the wild.
WHO WORKS ON YOUR PROJECT
You speak to a single person: your dedicated expert. Three other specialists work behind them, at precise moments in the project.
Software solution architect
They spend a day on your site and follow your teams workstation by workstation. They note what nobody says in a meeting: the shadow spreadsheet, the follow-up done from memory, the quote redone twice. From that they draw the map of your real process — not the one in the manual — then settle with you what goes into the first version and what waits.
What it changes for you
Your screens carry your words: your statuses, your stages, your names for things. Nobody has to learn a foreign vocabulary.
AI integration expert
They look at where your teams' time goes: re-keying a delivery note, re-reading an email to pull out a date, writing the same follow-up every week. They put AI exactly there, with an exit rule for every doubtful case, and leave the rest to the engine.
What it changes for you
Repetitive work leaves your teams' day. Your figures stay calculated by the software — never by the AI.
Dedicated expert
The same person from day one to go-live. They ship every two weeks, sit next to the people using the tool, fix what gets in the way and train the teams on their own screen, with their own records.
What it changes for you
Your teams don't discover the tool on switchover day: they watched it grow, and two or three of them can already train the others.
Cybersecurity expert
Role-based access, data separation, an access log, tested backups, a full review before go-live. They also look at what the software makes disappear: a shared file with no password, an export travelling by email, a spreadsheet living on five USB sticks.
What it changes for you
Building your software with us shrinks your attack surface instead of growing it. That is a commitment we put in the contract, not an option.
What AI will never do at your company It does not calculate your totals, your margins, your stock or your payroll. Those values come out of the engine, deterministically and reproducibly. AI captures, extracts, drafts and alerts — the arithmetic is not its job.
See how AI is kept in checkTHE METHOD, STEP BY STEP
Nothing gets built before you have signed off on what will be built.
A day with your teams, at their workstations. We watch, we listen, we note the double entries and the shadow files.
Who leadsSolution architect
Your process written down in plain words — your words — and reviewed by the people who live it. That document becomes the software.
Who leadsSolution architect
What we build first, what waits, what we will not do. Scope, screens, data, metrics and price: signed on both sides.
Who leadsArchitect and dedicated expert
A release every two weeks on your real data, followed by a short session with the teams concerned.
Who leadsDedicated expert
Access rights, logs, backups, a full export of your data and of the manifest. The reversibility clause and the third-party source code escrow are written into the contract.
Who leadsCybersecurity expert
WHAT EACH SIDE BRINGS
Already running an ERP? Keep it. We don't touch your accounting. We replace the fourteen spreadsheets around it, and plug the rest into it.
WHAT WE HEAR FIRST
Satisfaction drops six months after an ERP change because teams get a foreign tool imposed on them, with a vocabulary that isn't theirs. Here it is the other way round: the software takes your process and your words, and your dedicated expert trains the teams on their own records across the three months — not in a single day at the end.
In practice — The screens come out of workshops run with your teams, and two or three people trained in-house become the tool's champions.
This is not custom code. It is a declarative configuration on a single engine, the one every one of our clients keeps alive. Your screens, your rules and your fields are yours; the engine that runs them is shared, tested and improved for everyone.
In practice — Your changes are included in the subscription, and the engine improves for you without you funding a rebuild.
The mockup is generated in minutes, with sample data from your industry. No commitment.