Falnor / Solutions
ERP integration automation for systems that do not talk to each other
Most mid-market operations run an ERP, a CRM, an accounting tool and a lot of email, and none of them quite agree. People fill the gap by re-typing. Nobody wants to buy another piece of software for that. Falnor builds the layer in the middle: one system that reads everything you already run, moves the data, and asks a person only when a decision is needed.
Book a discovery callWhy re-typing never goes away
Connecting two tools is easy for the clean cases. The work that remains is the cases that do not fit: a field that means two things, a record that exists in one tool and not the other, an approval that happens in a message. See how this compares with Zapier, Make or n8n.
- The same customer or order is entered in two or three systems, and they drift apart.
- Exceptions are handled by whoever knows the history, so one person becomes the integration.
- Nobody can say which system is right when two disagree.
What the layer in the middle does
It reads from and writes to the tools you already run, under permissions you set, and keeps a record of every change. It works with NetSuite, Salesforce, HubSpot, Xero and others.
Maps where each fact lives
We write down which system holds the truth for each detail and where it has to appear. You keep the map whether or not we build.
Reads before it writes
Every connection is read-only first. It shows the changes it would make and you check them against reality.
Moves and reconciles
Matching records are updated under your rules. Conflicts are listed for a person with both versions beside them.
Keeps the history
Each change is logged with what it read, the rule it followed and who approved it, so you can answer why.
Permissions you control
The system starts read-only, showing what it would do on your real cases before it does anything. It takes over one task at a time, once it is right at least 9 times in 10. Anything unusual, large or hard to undo waits for a named person, and every step is recorded. Read, write and delete rights are set per tool and per action, so an error in one place cannot spread to another.
Works with the software you already use
We build on your own tools instead of asking you to move. Common starting points:
- NetSuite
- SAP
- Salesforce
- HubSpot
- Microsoft Dynamics
- Xero
- Zendesk
We work with businesses in the US, the UK and Europe.
Questions people ask
What is ERP integration automation?
It is using software to keep your ERP and the tools around it in step: moving data between them, reconciling differences and routing exceptions to a person, so nobody re-types.
Do we need to replace any of our systems?
No. The system sits in the middle of what you already run.
How is this different from an integration platform?
Integration platforms connect fields. We also handle the exceptions, the approvals and the record, which is where most of the manual work remains.
Can it stop one system overwriting another by mistake?
Yes. Permissions are set per tool and per action, it starts read-only, and conflicts go to a person instead of being overwritten.
How is it priced?
A named process is scoped first, then built at a fixed price agreed in writing before any build starts. The guide to how automation projects are priced explains the parts.
Which countries do you work in?
We work with businesses in the US, the UK and Europe. The system runs on your own software, so your data stays where it is.