The short answer
- First, write down what the team copies by hand between systems, from where and to where.
- Structured data, such as client details or an order number, moves through an automatic integration. Unstructured data / Free text, such as an email or a document, needs processing first: AI prepares the update and the team approves it.
- Replace a system only when it does not fit the work itself, not just because it is not connected to the rest.
When systems are not connected, people connect them
Most small and medium-sized businesses run several systems: a CRM for clients, accounting software or an ERP, a project management tool, and an Excel file or two on the side. Each system does its own job, and what connects them is the people.
- Client message
- Copy
- CRM
- Retype
- Order
- Update by hand
- Project status
Each copy takes a few minutes, so it is easy to miss. But this double data entry repeats with every client and every order.
What copy-paste costs your team
Time lost every day
Time not spent on clients and projects.
Small mistakes that snowball
A wrong phone digit, or an invoice amount that never made it to the CRM.
Everything depends on who remembers
It is unclear which copy is up to date, and the client waits until someone is free.
Step 1: Write down what gets copied, and where
Go through the processes where information is copied by hand, and ask five questions about each copy:
- What information
- From
- To
- Who moves it, and when
- What happens when it is late
Build the list with the people who actually move the information, not only with the manager. They know where the extra side file lives, and which update only happens when someone asks.
This list is a process map, and it also gives your workflows a structure: what lived in a few people's heads is now written in one place that the whole team can see and improve. For example:
| What is copied | From and to | Who and when |
|---|---|---|
| New client details | A WhatsApp messagetoExcel and the CRM | Who and when: Whoever got the message, when they are free |
| Order details | EmailtoAccounting | Who and when: Bookkeeping, at the end of the day |
| Delivery status | Project management tooltoA message to the client | Who and when: The project manager, when the client asks |
Step 2: Match a solution to each copy
Looking at the list, most copies fall into one of three types, and each type has its own solution:
Structured data: an automatic integration
When the same data, such as client details or an order number, moves from system to system unchanged, the systems can be connected. Many systems have ready-made integrations (APIs), and services such as Make and Zapier connect different systems too. For example, a new client in the CRM is created automatically in the accounting software.
Unstructured data / Free text: AI prepares, the team approves
An email with an order, a supplier document or an update written in words needs processing first. An AI (artificial intelligence) tool can read them, find the important details and prepare a draft update, task or order. The team checks and approves, and the decisions stay with them.
For this to work well, the AI needs context: what each system holds, how the systems connect and what matters in each process. You build that context from the list in step 1.
Information kept in several places: decide where it lives
When the same detail sits in the CRM, in Excel and in email, nobody knows which copy is right. Decide on one system where each piece of information is stored and updated, and let the other systems take it from there, so everything stays in sync. Sometimes this alone shows that a whole file is no longer needed.
So when is it worth replacing a system?
- It does not fit a core part of the work, even after it was set up properly.
- It cannot be connected and its data cannot be exported, and it sits at the heart of the process.
- The team does not use it, for a reason training will not fix.
And if there is no central system at all and everything is spread across files, setting up one system is not a replacement. It is order.
Step 3: Connect one process, then expand
Pick one process
The one that repeats most, or where a mistake costs the most.
Connect and test
Test the connection in real work, together with the team.
Roll out and expand
Once it works, hand it to the team and move on to the next process.
This is how Brain Ops works, in two services: AI in everyday workflows and monday implementation. See the full method.
FAQ
Do you need a new system to connect your systems?
Not necessarily. Most of the time you connect what you already have. A new system, such as monday, fits when there is no single place where the team manages tasks and status.
Can AI update the systems on its own?
Technically, often yes. But where clients and money are involved, it is better for the team to approve each update, at least until you see it works well.
What is the difference between automation and AI?
Automation moves structured data by a rule set in advance, for example a new client in the CRM who is also created in the accounting software. AI is needed when something has to be understood or reasoned about: processing free text, such as an email or a document, or finding insights in a large amount of data.