The Integration You Didn't Pay For Can Still Cost You

A fitness tracker company recently told its users that syncing to Apple Health, something that used to just work, now needs a paid subscription. People who'd bought the hardware years ago, on the understanding their data would flow where they wanted, suddenly found a $99 a year charge standing between them and a feature they already thought they owned.

It's an easy story to read and move on from if you don't own a smart scale. But the pattern underneath it shows up constantly in business software, and it's worth sitting with for a minute if any part of your business runs on a free integration someone else controls.

The integration was never really yours

When you connect two pieces of software, whether that's your booking system syncing to a calendar, your CRM pulling in accounting data, or a platform pushing orders into a spreadsheet, you tend to think of that connection as a fixed part of how your business works. It's been running for two years. It's in your process documents. Staff rely on it without thinking about it.

But if that connection runs through a vendor's free tier, you don't own it. You're borrowing it. The vendor built it, decided to offer it for free, and can just as easily decide to charge for it, restrict it, or drop it when it stops serving their business model. Nothing about "it's always been free" obliges them to keep it that way.

This isn't a hypothetical. It's the normal lifecycle of a free integration:

• A vendor offers a feature free to win customers or compete with a rival.
• Usage grows, and so does the cost of supporting it.
• The vendor reclassifies it as "premium" once enough people depend on it to tolerate the charge.

The people paying the new fee aren't being punished for doing anything wrong. They're paying because they built a habit, or a workflow, around something that was free by choice, not by right.

Where this actually bites a business

The Apple Health example is consumer-facing, but the same thing happens in B2B software all the time:

• A CRM's free plan includes webhook events, then a pricing update moves webhooks to the "Growth" tier.
• An accounting platform's API is open to all customers, then API access becomes a paid add-on once enough third-party tools start relying on it.
• A booking or payments provider offers a free sync with your website, then restricts it to accounts above a certain transaction volume.

None of this is malicious. It's a vendor adjusting their business model as their product matures. But if that integration is quietly doing something important, feeding your invoicing, triggering your fulfilment, keeping two systems in sync, you find out how important it was at the exact moment it's taken away or re-priced.

What's actually worth checking

You don't need to distrust every free feature you use. You need to know which ones your business actually depends on, and treat those differently. A few questions worth asking about any integration you rely on:

• Who built it? If it's a feature of the vendor's own platform (like a native API), it's more stable than a free add-on bolted on later to compete with someone else.
• Is it in their free tier for strategic reasons, or because it costs them almost nothing? Features that are free because they're cheap to run tend to stay free. Features that are free to drive adoption tend to get monetised once adoption succeeds.
• Do you have a fallback if it disappears tomorrow? Not a plan to build one eventually, an actual fallback you could switch to within a week.
• Is the data flowing through it something you could export and hold yourself? If the integration is the only place that data lives, you're more exposed than if you've also got a copy of it in your own system.

Where owning the integration changes things

This is the actual difference between relying on a vendor's free connector and having a custom integration built for your business. A custom integration, one you've paid for and that writes data into your own database rather than just passing it through someone else's dashboard, doesn't disappear because a vendor changed its pricing page. You might still need to adjust it if an API changes, but you're not at the mercy of a product decision that has nothing to do with you.

It also means the data itself sits somewhere you control. If a CRM decides tomorrow that webhook events are a paid feature, that's a cost to weigh up and negotiate, not a crisis, because the integration and the data it produces belong to your system, not theirs.

I do a fair amount of this kind of work, connecting CRMs, payment providers, accounting tools and internal systems so a business isn't stuck depending entirely on a vendor's goodwill for something core to how they operate. If you want to see what that looks like in practice, I've written about it on the systems integration page.

None of this means every free integration is a trap. Most aren't worth worrying about. But if you've got one sitting quietly underneath something that actually matters to your business, it's worth two minutes asking what you'd do the day it stops being free.