Scoping the exchanges
Which data flows, in which direction, how often, and what happens when the two sides disagree. Written down before anything is built.
Your application ignores your ERP and your CRM. We connect them.
An application that does not talk to your business tools forces someone to re-enter data by hand. This is where we are rarest: we speak the language of generated applications and the language of enterprise systems.
Does this sound familiar?
- The same data is entered twice: in the application and in the ERP.
- Your prices or stock levels are never up to date on one side or the other.
- Your ERP sits on an internal server, with no opening to the outside.
- Nobody can say what the application is supposed to send, or when.
- A manual file export has been standing in for a connection for months.
What we do
ERP and CRM connectors
We build connectors to Sage 100, Sage X3, Cegid, EBP, Divalto, Odoo, to a CRM such as HubSpot or Salesforce, to an email system or a business API, depending on what you run.
Agent on your network
When the ERP is internal and must not be exposed to the internet, an agent installed on your network carries the exchanges. It opens nothing outward.
Recovery from failure
A connection that drops must not lose data. Exchanges can be replayed, and failures are visible instead of silent.
The ERPs and CRMs we connect
The route depends on the software, its version and the way it is installed at your site. These are the families of tools we work on.
ERP and business management software
Sage 100 is the case we meet most often in French SMEs, followed by Sage X3 in larger organisations. We also work on Cegid and its XRP Flex range, on EBP, on Divalto, on Odoo and on SAP. From one ERP to the next, the underlying work is the same: deciding what flows, in which direction and how often.
CRM and sales tools
HubSpot, Salesforce, Pipedrive, Sellsy, Axonaut: all of these expose an API, that is a way in designed for another piece of software to read and write. The link is therefore shorter than with an ERP installed on your own premises, and most of the work goes into matching records, so the same customer is not created twice.
Accounting and invoicing
Pennylane and the other online accounting tools connect without particular difficulty. The question that matters is not technical: it is what your application is allowed to write into your accounts, and who signs that off.
Internal software and tools with no API
An ERP sitting on a server in your offices does not have to be exposed to the internet: an agent installed on your network carries the exchanges to the application. And when the software exposes nothing at all, there are still routes: reading the database, dropped files, a scheduled export.
How it works
- 01
You describe your tools
Which ERP, which version, hosted where, and what you want flowing. We tell you plainly whether it is feasible.
- 02
We check the prerequisites
Access, licences, modules, network openings: whatever depends on you and your vendor is listed before the quote, not discovered halfway through.
- 03
We build the exchange
On test data first, with you, to confirm that what flows is correct.
- 04
We connect for real
Supported go-live, with a simple way to see what went through and what failed.
Budget and timeline
A connector starts at 2,500 € excl. VAT, on a scope written down before anything begins. A first read-only step, on the data costing you the most time today, is delivered within a few weeks. Writing into the ERP takes longer: it commits your accounts and is signed off with the person who keeps them. The quote is free and comes back within 48 working hours.
See services and pricingReal engagement, client anonymised
A concrete case
A distribution SME had built a field application for its sales team with Lovable. The items, the customers and the sales documents stayed in Sage 100.
We scoped the exchanges with the IT provider running the server, then installed an agent that reads the Sage database locally and pushes the data to the application twice a day.
OutcomeThe sales team works on the ERP's data, with no manual import, and the state of each synchronisation is visible.
Read the full caseQuestions about ERP and CRM connections
My ERP is not on your list. Is that a problem?
No. What matters is not the name of the software but what it exposes: an API, a database that can be read, or failing that file exports. Give us the exact name of the software and its version, and we will tell you plainly what is feasible and by which route.
Do we have to open our server to the internet?
No. When the ERP is installed on your premises, a program placed on your network reads the data locally and sends it to the application. No inbound access is opened and your firewall stays as it is.
How long does a connection take?
A first read-only step, on a narrow scope, is delivered within a few weeks. Writing into the ERP takes longer, because it commits your accounts and needs accounting sign-off. The timeline is written on the quote, along with the scope.
How much does a connector cost?
From 2,500 € excl. VAT for a common scope. The exact price depends on the number of flows, their direction and the state of your installation. The quote is free, comes back within 48 working hours, and the price is fixed.
Do we need our integrator or software vendor to agree?
Their help is often needed: they know your configuration, your licences and your access. We bring them in at the scoping stage rather than discovering them halfway through. We do not administer your servers or your ERP: we build the link and support its go-live.
What happens if the connection drops?
Exchanges can be replayed and failures are visible instead of silent. That is the most common flaw in links put together quickly: nobody is told, and the gap between the two systems widens for weeks.
Let's talk about your project
Tell us about your situation. We come back within 48 business hours with a fixed-price quote, free and with no commitment.