The integration you need is probably already paid for, check what your existing tools can do before buying a third

A gap opens up between two systems. Orders live in one place, invoices in another, and somebody spends part of every week moving information from the first to the second. The obvious next step is to find a product that sits in the middle and closes the gap.

Sometimes that is the right answer. More often the capability is already paid for, switched off, or exposed through an interface that nobody in the building has ever opened.

The person is the integration

It is worth naming the current arrangement accurately. When two systems do not talk and a person moves data between them, that person is the integration layer. They are an unusually expensive one, they only run during office hours, they make occasional errors that nobody catches for weeks, and they are entitled to annual leave.

Describing it that way changes the maths. The question is no longer whether to spend money on a connection. Money is already being spent on the connection. The question is whether the current form of it is the one you would choose.

What is usually already there

Most business software sold in the last decade can send and receive data. It is rarely advertised on the pricing page, because it is not what wins a demo, but it is almost always present.

• Features included in your tier. Plenty of platforms ship with an export schedule, a webhook, or a native connection to the other product you already run, sitting unenabled because nobody looked.
• The interface behind the interface. The screen a user sees is one way into a system. Nearly all of them have another, designed for machines, and it usually does more than the screen does.
• A connection that already runs in one direction. Often one system is already pushing something somewhere. Extending an arrangement that works costs less than inventing a new one.

Why the third tool is tempting

Buying is easier than connecting. It has a price, a vendor, a contract, and a demo where everything works. Connecting has none of that. It needs somebody to look at two systems in detail and make a judgement, which feels like a project even when it is a week of work.

The trouble with the third tool is that it is a third thing. It has its own login, its own renewal, its own release notes, and its own edges that do not quite line up with either of the systems it was bought to join. In eighteen months it is part of the estate rather than a fix to it, and the original two systems still do not talk to each other directly.

What to check, in order

None of this needs a supplier to start.

1. Write down the fact being moved. Not the process, the fact. An order number and its status. A contact and their address. Being precise about what actually travels makes everything after it simpler.
2. Search both platforms for that fact. Look up the field name in each set of documentation. If both systems can read and write it programmatically, the gap is a connection problem rather than a product problem.
3. Check the plan you are on. Some capability is gated behind a tier. Occasionally the upgrade is the cheapest option on the table, and occasionally you are already on the tier that includes it.
4. Count the current cost honestly. How many minutes, how many times a week, and what happens downstream when it is late or wrong. Without that number there is nothing to judge any option against.

When buying is right

This is not an argument that new software is always the wrong answer. If a genuine capability is missing, if volume has outgrown what the current tools were built for, or if the existing platform is being retired, then replacing it is sensible and connecting it is throwing good money after bad.

The distinction is worth making out loud before anyone books a demo. Missing capability is a buying problem. Present but disconnected capability is a plumbing problem. They look identical from a distance and they cost very different amounts to solve.

The duller question

Before pricing up a platform to close a gap, it is worth asking what the software already on the invoice can actually do, and what it would cost to connect it properly.

The answer is often that the licence renewed in March already includes most of it.