Knowledge base, for pools and sports businesses

Standard package, or connect it yourself?

Sooner or later every pool and sports business faces the same choice. Put everything in one big package like ReCreateX or Vintia, or connect the systems you already have. It isn't a question of good or bad. It's about when a package fits, and when connecting your systems gets you more. This article puts both side by side, honestly.

What a standard package does well.

An all-in-one package for the leisure industry takes a lot off your plate. Point of sale, access control, memberships, bookings and reporting come as one coherent whole, from a single vendor, with support and updates. For a pool that's starting from scratch or wants to replace outdated standalone systems, that's a logical and safe choice. You're buying a proven product, not a build project.

ReCreateX and Vintia are mature packages that run well at many pools. If your processes are close to the standard of a package like that, and you don't need heavy customization, going along with the package is often faster and cheaper than having something built. If that's you, start there.

Where it starts to pinch.

A package gets difficult the moment your way of working differs from the standard. Then there are two outcomes, and neither is pleasant. You adapt your process to the package, or you pay for custom work inside a system that wasn't built for it.

  • You're tied to one vendor, and someone else decides the rates, the pace and the roadmap
  • Connecting to what you already have, like your accounting, building management or your own website, can be painful or expensive
  • You pay per module or per user, even for parts you barely use
  • Your data lives in the package, and getting it out is rarely as easy as putting it in
  • An idea of your own, like a daily briefing or an AI assistant trained on your own knowledge, doesn't simply fit in

None of this makes a package wrong. These are the costs you accept in exchange for convenience. The question is whether you want to pay those costs, or whether your situation calls for something else.

The other route, connecting what you have.

Instead of replacing everything, you keep the systems that work fine and build the layer in between that makes them work together. Your POS stays your POS, your scheduling software stays your scheduling software, but the data flows between them and the reporting, the briefing and the customer contact sit on top.

  • You keep what worksNo big migration and no six months of getting used to it. What runs well stays, and only the manual work in between disappears.
  • You pay step by stepYou connect the process that costs the most first, measure the result, and only then expand. No package price for modules gathering dust.
  • The code is yoursWhatever gets built is your property. You're not tied to a vendor to make changes to it.
  • Room for your own ideasA daily briefing at 07:00, an AI assistant that knows your rates, review handling. Things that don't fit in a standard package do fit here.

The price of this route is that someone has to build and maintain the integration layer. That's exactly the work I do, and it's why maintenance and monitoring are part of the service instead of a separate ticket system.

How Inge de Bruijn chose.

Inge de Bruijn Zwembad in Barendrecht faced exactly this choice. There was a proposal for a standard package on the table. The pool deliberately turned it down and went the other way, connecting its existing systems and having the missing layer built. Not because the package was bad, but because its way of working and its own ideas didn't fit the mold, and because the pool wanted to stay the owner of its own data and processes.

What runs there now: more than twelve systems working as one whole, a daily briefing at 07:00, an AI assistant for customer questions, automatic review handling and monitoring that keeps running through the night. You can read how it's built in the full case study, and what each part delivers in automation for swimming pools.

How to decide what fits you.

No dogma, just a few honest questions. If you mostly answer with the left side, a package is probably fine. If you land on the right side, connecting your systems is worth considering.

  • Do you mostly work the standard way, or do you have processes that really depend on your own approach?
  • Are you starting from scratch, or do you have systems that work fine on their own and that you'd rather keep?
  • Do you want the convenience of one vendor, or do you want to stay the owner of your data and code?
  • Is what the package offers enough, or do you have ideas of your own that don't fit in it?

Not sure where you stand? That's exactly what we figure out in half an hour. I won't sell you an integration if a package is better for you. That's the deal.

Package or integration, which is smarter for your pool?

In the free process review I look at the systems you have now and tell you honestly which way to go, even if that means telling you to keep your package. Half an hour, and you leave with three concrete opportunities on paper.

At most one email a month. To unsubscribe, just reply. Your address stays with me.

Walk me through one process