Business management (ERP)
Sales, purchasing, stock, invoicing and HR on a single database, built module by module.
Country and language
Other markets: these available language versions show the same page.
Business software
A tool built around the way you work, not the other way round. We have developed and maintained business software in Paris since 2008, and the code is yours.
The need
Business software is the tool that carries the way your company really works: how an order becomes an invoice, how stock is updated, how a team knows what to do tomorrow morning. As long as a product on the market comes close, take it — it is cheaper and faster.
Custom work starts where that product forces you to work differently from the way you actually do. The signs are specific: Excel files duplicating the software, the same data re-entered in two places, an export reworked by hand every month, or a business rule the settings cannot express.
We do not replace everything at once. We start with the process that costs the most time, deal with it, and extend only once the first piece is running in production.
What we develop
Each family has its own page, with the modules, the method and a budget range. Most projects combine two or three of them.
Sales, purchasing, stock, invoicing and HR on a single database, built module by module.
Pipeline, quotes, scheduled follow-ups and reporting, built around your sales process.
Quotes, invoices, reminders, bank reconciliation and exports in the format your accountant expects.
Every sale decrements real stock, with an offline mode so service keeps running.
Working hours, absences and time worked, available from your teams' phones.
Phone, website and platforms in a single schedule, with capacity and confirmations under control.
How we work
Four stages, in this order. You sign off each one before the next starts.
We spend time with the people who will use the tool, to map the real process — not the one in the manual. Deliverable: a priced, prioritised scope.
1 to 2 weeksClickable screens for each path through the tool. You correct the mockup, where changing your mind costs nothing.
2 to 3 weeksThe first batch is the one that saves the most time. It goes into production while the next one is being built.
8 to 16 weeksExisting data is migrated, teams are trained, then a settling-in period before the code is delivered to you.
2 to 4 weeksIntegrations
Data is entered only once. What we link most often — during scoping we check what each tool actually exposes.
Example project
A services company ran its jobs, its spare parts stock and its invoicing across seven shared workbooks. Every month-end took two days of cross-checking, and stock discrepancies were found too late. We delivered a first batch centred on jobs and invoicing, then added stock three months later.
Budget
The figure depends on the number of modules and on the integrations. Here is the usual starting point.
Indicative figure for a first scope in production. Every quote is issued as a fixed price after scoping, with no per-seat fee.
FAQ
The tool that carries the core of your activity, as opposed to generic tools like email or office software. An ERP, a CRM, a till, a schedule: as soon as software encodes your own rules, it is business software.
Look at the market first. If a product covers 80% of your need and the remaining 20% is negotiable, take it. Custom is justified when those 20% are exactly what sets you apart, or when the per-seat cost becomes heavier than a development project.
A first usable version normally lands 8 to 10 weeks after scoping. It does not cover everything: it covers the process that costs you the most, and your teams work on it while the rest is being developed.
You do. The source code is delivered to you at go-live. You are tied to IDEALOGY only if you want maintenance and new work — never by the tool itself.
That is planned for: development runs in batches, and the architecture is designed so a module can be added without rewriting the rest. After go-live, changes are handled continuously or under a maintenance contract.
Yes. Scoping is better done on site and we travel for it; the rest of the project runs well remotely. The team itself is in Paris 8e.
Family by family
Let's talk
Describe the process that costs you the most time. We will tell you frankly whether a product on the market is enough, or whether a development project is justified.