CRM with invoicing
The quote accepted in HubSpot, Zoho or Salesforce becomes a customer and an invoice in Sage, Odoo, Holded or A3, without anyone copying it. And the payment goes back to the CRM so sales know what is going on.
Home / Systems integration
Systems integration · ERP, CRM and the restGetting the ERP, the CRM and the usual programs to pass data between themselves.
The customer is created in the CRM, typed again in invoicing and once more in the delivery program. Three places, three versions of the same misspelt surname. It connects on top of what is there, without replacing what is already paid for and working.
3places where the same data is typed, on average, in the companies I see
0core systems that need changing, almost always
2 to 6weeks per integration, depending on the systems
1 monthof support after delivery
What gets connected
The connections people ask for most, and why.
Online shop or bookings with the ERP
The order from the website, the booking engine or the PMS goes into the ERP with the right stock, price and customer. No more orders typed in on Monday.
The spreadsheet only one person understands
There is almost always one: the customs cost split, the commissions, the hours per job. It comes out of the spreadsheet and into the system, with the same rules, so it doesn't depend on that person never being off sick.
Microsoft 365 or Google Workspace with everything else
The incoming email creates the task, the form someone fills in creates the record, the calendar lines up with the appointments. It is what you already pay for, put to work.
How I do it
On top of what is there, not instead of it.
There are two ways to integrate: replace every system with one that does everything, or connect the ones you have. The first costs a year and a headache, and in the end the new one doesn't do everything either. The second costs weeks and leaves each program doing what it does well.
I use the programs' own APIs when they have them, n8n or Make when it pays not to write code, and code when it has to be exact. The choice follows what is there, not what is in fashion, and it is explained in the working session document so you can change it or have someone else maintain it.
And every connection has its own error tray: when a piece of data doesn't match, it isn't lost; it gets flagged and a person looks at it.
1 timeeach piece of data gets typed. The guest registration form, the owner statement and the commission all come out of the same booking.
One piece of data, one place, and from there to everywhere else.
At a holiday rental management company, guest details were typed into the PMS and again for the guest registration form, and the owner statement was put together in a spreadsheet. Now the booking goes in once and the form, the statement and the commission come out of it. Four hours a month that should never have existed.
It is the holiday rentals case, and it is pure integration: no new system, three connected.
Questions
Before you book.
What if my program has no API?
Almost all of them have some way in: scheduled exports, an accessible
database, a mailbox it reads. And if there really is none, the screen gets automated the
way a person would use it, which is what they call RPA. It is the last option, but it
works.
Does it break when they update the program?
It can happen, and that is why every connection warns you when something stops
matching instead of failing silently. For the first month after delivery I stay
available, and after that there is a maintenance fee if you want it, or I leave you the
documentation so whoever you choose can look after it.
Do I have to give you access to everything?
To what is needed and with the minimum permissions, through dedicated users
that can be revoked. What access exists and what it is for gets written down, and it is
reviewed at the end.
Get started
Tell me what gets typed in two places.
Fifteen free minutes to see what can be connected and what isn't worth it.