Why rebuilding the system landscape is almost never necessary, and what gets built in between instead.
01 In short
Most businesses in real estate and construction do not have bad systems. They have systems that do not talk to each other. The ERP knows the invoice, the CRM the customer, the document store the file and the inbox the enquiry — but nobody carries the information from one to the next except a person. We do not replace these systems. We connect them and automate the steps in between. That turns existing systems into one continuous process.
02 Where the time goes today
Time is rarely lost in the core business. It is lost in coordination: searching for documents, sorting e-mails, checking invoices, transferring information from one system to another, chasing open cases. None of these tasks calls for a new ERP. They call for the systems already in place to keep each other informed.
What that looks like per industry is set out in the entries on time sinks, for example The five time sinks at construction companies or at estate agents.
03 Why a new system rarely solves the problem
Switching systems feels like a clean cut. In practice it brings three problems:
- It takes time. Migrating data, setting up processes again, training staff. Meanwhile two systems run in parallel.
- It moves the gap. The new system is not everything either. Inbox, document store, accounting and specialist software stay alongside it, and between them data is still transferred by hand.
- It costs knowledge. An ERP that has been running for years holds charts of accounts, master data, reports and habits that nobody has ever fully written down.
There are good reasons to switch, for example when a system is no longer maintained. Missing automation is rarely one of them.
04 What gets built in between instead
A connecting layer goes between the existing systems: workflows that react to an event in one system and do the right thing in another.
| Your systems | What happens in between | Result |
|---|---|---|
| E-mail and calendar | Enquiries and invoices are recognised and assigned | Captured |
| CRM | Customers, prospects and properties are matched | Assigned |
| Accounting and ERP | Documents are checked against orders and budgets | Checked |
| Document storage and DMS | Documents end up in the right place, with the right data | In sync |
| All of them together | Open cases are watched and followed up | Followed up |
The systems remain the source of truth. The ERP keeps booking, the CRM keeps managing contacts. The workflow only carries the information between them, at the point where a person does it today.
05 An example: the report from five systems
A property developer wants to know every Monday where the projects stand. Today someone copies costs from the ERP, dates from the project schedule, open items from minutes and the marketing status from the CRM into a template. A new system holding all of that would be a large project.
The workflow reads the same sources through their interfaces, assembles the figures, flags deviations and puts the report forward as a draft. Project management checks it and sends it. No system was replaced, and the report still comes together without anyone retyping it. Which workflows we build for developers is on AI for property developers.
06 What a connection requires
A system can be connected if it has an interface, an export, or at least a mailbox through which it sends data. The ERP and accounting systems we connect have one: Abacus, Bexio, SAP and SAP Business One. Bexio through its REST interface, SAP Business One through the Service Layer; invoices, documents and receivables can be read and prepared there without replacing the system. Which systems we typically connect and what that needs is covered in Which systems we connect. What we build the connection with is covered in What is n8n.
07 When switching systems is the right call after all
We say so when we see it. Signs are:
- The vendor no longer develops the system, or it has neither an interface nor an export.
- The same data is maintained in two systems that do the same job.
- The system does not cover a core process at all, and the gap is filled with spreadsheets today.
Even then the order stays the same: describe the workflows first, then choose the system that carries them. The company analysis settles that before anything is built — see What the company analysis delivers.
08 What stays with you
Your systems, your data, your access rights and your decisions. The workflow prepares and carries information; approval comes from the people who are responsible today.
09 Frequently asked questions
Do we have to change our ERP to automate?
No. We connect the ERP you have with the systems around it. The precondition is an interface or an export.
Who is right when two systems hold different data?
We settle that in advance: for every piece of information there is a leading system. The workflow syncs in that direction, not both.
What happens to the workflow if we do switch a system later?
The connection to the old system is replaced by one to the new system. The workflow itself — steps, rules and approvals — stays.