Knowledge base

Which systems can you connect.

Almost every small business runs on the same layers. A register, an accounting package, a schedule, a mailbox. They all work, but separately, and you're the link that retypes everything. This article lists those layers and what an integration solves for each pair, in concrete terms.

The layers almost every business already has.

Connecting starts with looking at what's already there. Buying new software isn't the first step. Go through this list for your own business. Most owners recognize five or more, and they're almost always disconnected from each other.

  • Register or invoicing: where the money comes in
  • Accounting: where the money gets accounted for
  • Planning or schedule: who works when
  • Mailbox: where customers and suppliers come in
  • Forms on the site: sign-ups, requests, quote requests
  • Reviews: what customers say about you in public
  • Calendar: appointments, reservations, occupancy times

Each of those systems does its own job just fine. The manual work happens between them. Retyping numbers from one into the other, comparing lists side by side, moving a sign-up from a form into the real system. That in-between work is exactly what an integration takes over.

What an integration solves per pair.

An integration isn't an abstract project. It's always a pair. From now on, this system talks to that system. For each pair you can say very concretely what it delivers.

  • Register to accountingNo more retyping. Every transaction goes into the books automatically with the right VAT rate, and the typos disappear along with the typing.
  • Schedule next to clocked hoursDiscrepancies show up on their own. Whoever started later or worked longer lands at the top of the pile, instead of someone comparing two lists side by side every period.
  • Site form to follow-upNo more lost leads. Every request goes straight into the system where follow-up happens, with a confirmation to the customer, instead of waiting in a mailbox.
  • Reviews to an approval listNo review sits for days. New reviews arrive in one place, with a draft reply ready for approval.

The honest condition is that there has to be a door.

Not every system can be connected. The condition is that the system has an export or an API, a way to get data out or put data in without a person having to click. Modern packages almost always have one. Older registers and niche packages sometimes don't.

That's why you check this up front, not halfway through the build. It's one of the things I do in the free process review. I look at each system to see whether there's a door, and what fits through it. If there's no door, you hear it right away, before anything gets built or paid for.

After that, start with one pair, not everything at once. The integration that saves the most manual work goes first, and each next pair builds on what's already there.

How far this can go if you keep building.

At Inge de Bruijn Zwembad, 12+ systems are now connected into one whole: register, schedule and hours, accounting, building management, energy, reviews and more. That didn't start as a master plan. It grew one pair at a time. You can read the result in the pool case study.

It doesn't have to go that far for you to benefit. The first pair usually pays for itself already. What connecting costs and what a project like this looks like is on the automation page.

Which pair delivers the most for you?

In the free process review I go through your systems, check each one for a door, and point out the pair where you should start.

No newsletter spam. One email a month at most, and you unsubscribe by replying.

Walk me through one process