System integration for people tired of copy and paste

It usually starts with one window at a time. You have the order open in one system and copy the customer’s name, address and line items into another. Then you send a confirmation and add the same thing to a spreadsheet, just in case. Each step takes a minute. Together it adds up to hours every week, and a constant chance of something ending up wrong.

System integration means letting the systems do that for you.

What is system integration?

System integration means two or more systems send information to each other automatically. When something happens in one, like a customer placing an order, the other finds out right away and does its part. Nobody has to copy, paste or retype anything.

It can be as simple as the form on your website adding a new contact to your CRM. Or as involved as an order going from the online store to the warehouse, on to the shipping company and finally into the books as a finished invoice.

Signs you need it

You don’t need to know anything about APIs to recognize the need. It usually shows up like this:

• The same details get typed into two or more places.
• Part of someone’s job is moving data between systems.
• A spreadsheet acts as the bridge between two programs.
• Mistakes happen in the handover: wrong quantity, old address, a forgotten invoice.
• Nobody is quite sure which system has the right number.

If two of those sound familiar, there’s almost certainly time to save.

Three ways to connect systems

There’s no single right way. It depends on how many systems are involved, how often the flow runs and how much can go wrong along the way.

Approach	Fits when	Downside
Built-in integrations	The systems already have a ready-made connection	Only does what the vendor planned for
Tools like Zapier or Make	The flow is simple and doesn’t run that often	Gets expensive and hard to follow as it grows
A custom connection	The flow is important, unusual or runs often	Costs more to build up front

Built-in integrations are always worth checking first. Many systems have ready-made connections to the most common tools, and they cost little or nothing. If they fit how you work, use them.

Tools like Zapier or Make let you build flows without writing code. They’re great for getting started and for simpler things. But they typically charge per task or operation, and as the flows multiply and get more involved it gets hard to see what’s happening and why something failed.

A custom connection is built for your specific flow. It does exactly what you need, handles the exceptions and tells you when something didn’t go through. It costs more to build, but you own it, and it doesn’t get more expensive because you sell more.

Common connections in small businesses

Most connections I build come down to the same handful of flows:

• Online store and accounting. Orders, customers and products stay in sync.
• CRM and invoicing. A won deal becomes an invoice without anyone retyping it.
• Website and CRM. Inquiries land straight where the sales team works.
• Booking and invoicing. A completed booking becomes an invoice draft.
• Inventory and online store. Stock levels match wherever the item was sold.

You can see one of those in practice in the Profilbutiken case study.

What does it cost?

A simple connection between two systems, with data going one way, starts at $4,500. Two-way sync, where records stay identical in both systems, starts at $10,000. Bigger flows with several systems get a fixed price after a call, so you know the cost before I start.

Some systems also charge for their side of the connection, like an API or integration fee. We go through that on the call, so nothing comes as a surprise.

Updated 29 September 2026