Shared data core
Customers, products, prices, stock: one single reference, read and written by every module. No double entry, no exports to stitch back together.
Business software
Custom business management software (ERP)
An ERP built module by module, around your real processes. Sales, purchasing, stock, invoicing, HR: one database, developed and maintained in Paris.
One core — six modules, a single database
Paris 8e — team on site
Source code — delivered, it is yours
The need
When every department has its own file
No small company decides to pile up its tools: it happens one piece of software at a time. A spreadsheet for purchasing, an invoicing application, a shared stock file, a calendar for the schedules. Each department ends up working on its own version of the figures, and a simple question — what margin did we actually make on that order? — takes half a day of rework.
Custom management software attacks the problem at the base: one customer reference, one stock, one product catalogue, shared by every module. We do not deploy a full suite in one block. We start with the module that costs you the most today, put it into production, then plug the next ones onto the same core, in your order of priority.
This page is the entry point to the modules we develop: CRM, accounting, point of sale and stock, HR and payroll, booking. Each one works on its own and can be delivered on its own. Assembled, they share the same data and the same access rights: a sale at the till decrements stock, feeds invoicing and reaches the dashboard with no manual re-entry.
Features
The modules and how they fit together
Each module stands alone, but all of them sit on the same data core. You choose the order of deployment.
Sales and customer relations
Pipeline, quotes, orders and history. An accepted quote reserves the stock and prepares the invoice, with no re-entry.
Purchasing and stock
Supplier orders, goods received, stock counts, reorder thresholds. Real stock, not the stock from the last count.
Invoicing and accounting flows
Invoices, credit notes, due dates, payment matching and exports in the format your accountant expects.
Schedules, HR and booking
Working hours, clocking, absences, customer bookings. Approved hours feed payroll preparation directly.
Company-wide reporting
Margin by product, by customer, by site. Revenue, outstanding amounts, cash forecast — all calculated on the same data.
How we work
How an ERP project runs
Four stages, in this order. You sign off each one before the next starts.
- 1
Mapping the flows
We map your processes department by department and decide together which module ships first. Deliverable: a priced, prioritised scope and a diagram of the data to migrate.
2 to 3 weeks - 2
Core and first module
We build the shared database, then the priority module through to production. You use it while the rest is being developed.
6 to 10 weeks - 3
Following modules
One module at a time, testable at every delivery. Each addition plugs onto the existing core without disturbing what already runs in production.
4 to 8 weeks per batch - 4
Migration, training, support
Your historical data is migrated, each department is trained, then maintenance and new work. The source code is yours.
Ongoing
Integrations
Connected to the rest of your system
An ERP is only useful if it talks to what you already run. What we connect most often:
Accounting softwareElectronic invoicingBank statement importsPayment terminalseCommerceCarriers and delivery trackingEmail / calendarElectronic signatureREST APIWebhooksCSV / Excel exportSSO
Example project
A concrete example
Example — to be replaced by a real project
Purchasing, stock and invoicing ERP for a food wholesaler
Supplier orders were handled by email, stock in a spreadsheet updated each evening, and invoicing in a separate application. We delivered the core and the stock module first, then invoicing and purchasing three months later.
1 entry
instead of three
−40%
in stock discrepancies
9 weeks
to the first module in production
Budget
What a custom ERP costs
The figure depends on the number of modules and on the data migration. Here is the usual starting point.
Core + first module — from
15 000 €
Indicative figure. The firm quote is issued as a fixed price after the scoping phase, with no per-seat fee and no extra module forced on you.
- Scoping, data model and mockups
- Hosting and go-live
- Migration of your existing data
- Source code delivered, no lock-in
FAQ
What people ask us most
Do we have to replace all our tools at once?
No, and we advise against it. We deliver the data core and then a single module into production. Your other tools keep running, linked by exports or APIs, and are replaced when their turn comes. Switching everything over in one night is the surest way to bring the company to a halt.
Which module should we start with?
The one that costs you the most in time or in errors. For a shop that is often stock, for a services company invoicing, for a sales team the CRM. Scoping exists precisely to settle that question with figures rather than intuition.
Can we keep our accounting software?
Yes. Many clients keep their accounting tool and their accountant, and we plug the ERP into it: journal entries exported in the expected format, payments fed back, matching. We check during scoping what your software actually accepts, before we commit to anything.
How much does adding a module later cost?
Each module is quoted as a separate fixed price, priced at the moment you launch it. Since the core and the data already exist, a module added later comes out noticeably cheaper than the first. No subscription is triggered simply by adding one.
See also
The modules in the suite
Let's talk
Tell us where it gets stuck today
Thirty minutes is enough to identify the module to deliver first — and to give you an honest range for the whole.