A training provider runs its sessions from a shared spreadsheet: enrolments arrive by email, invitations are retyped one at a time, signed attendance sheets are scanned into a network folder, certificates are produced by hand and invoices are keyed again into the accounting package. Nothing is broken, yet three people spend their days copying what already exists somewhere else. That is the usual starting point for bespoke software: a genuine need, nothing written down, and a well-founded fear of opening a project with no end in sight. So we check first that writing code is warranted, then move in short stages you are free to stop.
Every stage carries its own scope, its own price and its own acceptance record. Decide to stop between two of them and whatever was delivered and accepted stays with you, on the terms the contract sets out.
We question the people who actually run the process, not only the management, and write down how it works today. Sometimes a different setting in Odoo or a revised procedure settles the matter, and we say so before proposing any development.
Module layout, technology choices, hosting with OVHcloud, Scaleway or Clever Cloud, and the list of exchanges with your existing tools. These are the decisions that are expensive to undo later.
A prototype your staff can try before anything is built. Moving a button on a wireframe takes a quarter of an hour; in delivered code the same change can fill a week.
Every fortnight a build lands on a test environment your colleagues open in their own browser. You watch the product grow rather than read progress reports about it.
Scenarios written with your key users, automated checks in the continuous integration pipeline and functional acceptance run by your own team before any stage is signed off.
Data loading, training over video calls, close attention during the first weeks, then fixes, dependency updates and new features under a maintenance agreement.
How long discovery and the first release take depends on the number of business rules, users and connections to your other software. The schedule comes out of discovery: that is the figure to plan against, not a guess offered before anyone had looked.
We describe the process as it actually runs, put a number on the hours it swallows each month and say plainly whether development will pay for itself. Billed in its own right, with nothing committed afterwards.
The main screens, tried out by the people who will live with them daily. Corrections made here are the cheapest of the whole project.
The narrowest scope that settles the main difficulty, demonstrated every fortnight and handed to a small group of willing users.
Switch to production, a watching period, then handover of the repository, documentation, credentials and the paperwork covering rights, as the contract provides.
Writing the code is hardly ever the heaviest line in the budget. The weight sits in what already exists: duplicate records, gaps in the history, calculation rules nobody can explain any more. Set aside time to clean your data and to walk the teams through the change. A sound tool used the wrong way produces wrong numbers with great confidence.
Discovery and the first release often suit a fixed price, because the scope is known once discovery ends. Later changes, where priorities shift from month to month, run better on time and materials at EUR 95 per hour excl. VAT, with a monthly ceiling in the contract so spending stays predictable.
The aim is always a first release genuinely in service, however small, rather than a complete product delivered late. We open the minimum scope that settles the main difficulty, hand it to a few willing users, then widen it. The timing depends on how many business rules apply and is stated at the end of discovery.
Yes, and it is designed that way. Discovery is billed in its own right and you leave with the written requirements, the diagram of exchanges, the schedule and the cost estimate. The file belongs to you: pass it to another supplier, or keep it until the subject becomes urgent again.
Test environments run on anonymised sets hosted inside the European Union. Where access to live data becomes unavoidable, it is named, logged, time-limited and covered by a processing agreement under GDPR. If the nature of the processing calls for it, we help your data protection officer prepare the impact assessment.
Companies do draw on Bpifrance schemes or France 2030 calls for projects for work of this sort. We neither prepare applications nor promise funding: we supply the technical description, the schedule and the cost breakdown in the format usually requested, and your adviser handles the submission.
Tell us what your teams still do by hand and how many people spend time on it. We start with discovery, and if a product off the shelf will do, you will hear it from us.
Message received
An answer follows inside one working day. Report an outage that is stopping people working and it moves ahead of everything else.
Nothing here under that name. Check the spelling, or simply choose the nearest large city instead. Since every engagement runs remotely, whichever you pick changes nothing about what we do for you.
