The CRM subscription is the visible cost. Around it, a second layer grows: the dialler someone installed for a campaign, the document-signing add-on, the enrichment tool on a free trial that quietly converted, the scheduling widget, the dashboard extension. Each solved a real problem for someone. Together they become a tangle of recurring charges, data permissions and dependencies that nobody has the full picture of.

This is the CRM-specific version of SaaS sprawl, and it has a particular twist: these tools sit directly on your customer data.

Why Add-Ons Accumulate

CRM marketplaces make installation easy, often one click and an approval prompt. That convenience is the reason they are useful and the reason they multiply. Individual teams solve their own problems quickly, without any single person owning the total. Trials roll into paid plans. Someone leaves and takes the knowledge of why a tool exists with them.

None of that is a character flaw in your organisation. It is the default outcome when installation is easier than governance. The fix is to make governance light enough to survive contact with real work.

Build a Single Inventory

Start with a list of everything installed in or connected to the CRM, plus everything paid for separately that touches it. Sources to check: the CRM’s installed-apps or connected-apps page, the billing and expense records for software subscriptions, and a quick message to team leads asking what they use.

For each item capture the following:

• What it does and which team uses it.
• Who owns it, by name, with a backup.
• What it costs and when it renews.
• Which CRM data it can read or write, and whether it can export.
• Who is licensed and how many actually use it.
• What would break if it vanished.

An inventory with those columns answers most later questions. Even a shared spreadsheet is enough if it is maintained.

Create a Lightweight Approval Path

You do not need a committee. You need three questions answered before something new is connected:

1. Does something we already own do this? Many CRMs have native features that overlap with add-ons, and it is worth checking the vendor’s current documentation before buying.
2. What data does it access, and is that acceptable? Read the permissions requested at installation. An app that wants write access to every object to display a calendar is asking for too much.
3. Who will own it, and what happens if they leave?

For low-risk, low-cost tools, a short form reviewed by the CRM administrator within a couple of days is enough. For anything touching sensitive data, involve security and privacy colleagues, and check that the supplier’s terms and data handling fit your obligations, which vary by region and sector.

Watch for the Hidden Dependencies

Add-ons create coupling. A custom field might exist only because a plug-in writes to it. A report might depend on data an enrichment tool fills. An automation might call an add-on action.

Before retiring any app, search for references in fields, layouts, automations and reports, and ask the owner what relies on it. Removing a tool that quietly populates a required field can break record creation for a whole team.

Also consider vendor risk. If a small add-on vendor disappears or discontinues a product, how painful is that? Where an add-on is critical, know the exit path: how data is exported and what the alternatives are.

Decide Between Keep, Consolidate and Retire

Situation	Typical decision	Check first
Used daily, clear owner, fair cost	Keep	Permissions still minimal
Overlaps a native CRM feature	Consolidate or retire	Does the native feature meet the real need?
Few users, many licences	Reduce licences	Renewal date and notice terms
No owner, no recent use	Retire	Dependencies and data to export first
Critical but vendor looks fragile	Keep with an exit plan	Export route and alternatives
Free trial running	Decide before it converts	Conversion date and billing terms

Put renewal dates in a calendar with a reminder well before the notice window. The expensive mistakes are the ones where the notice period quietly passes.

A Hypothetical Example

A mid-sized sales team’s inventory turns up nine add-ons. Two overlap: a meeting scheduler and a built-in scheduling feature that came with the CRM plan. One enrichment tool has twenty licences but only six people who logged in during the last quarter. A document-signing add-on has no owner, but the finance team turns out to use it monthly for contracts.

The administrator proposes three changes: move scheduling to the native feature after a two-week trial with the sales team, cut the enrichment tool to the active users at its next renewal, and assign the signing tool formally to finance operations with a named backup. Nothing is cancelled in a panic, and each decision traces to a fact in the inventory.

Offboard Apps as Carefully as People

When you retire an app, revoke its connection in the CRM, rotate any credentials it held, export whatever data you need, and confirm the vendor deletes data held on your behalf according to its terms. Update the inventory and tell the users. Many teams uninstall the add-on but forget the separate subscription, so confirm the billing stops too.

Keep It Alive

Review the inventory in your regular admin review. Ask new hires’ managers to check the list before requesting something new. And make the approval path visible, since people bypass processes they do not know exist.

Frequently Asked Questions

Should we block all marketplace installs? Usually not. Restrict installation to administrators or an approval workflow, so teams can still ask quickly while someone checks permissions.

How do we find add-ons nobody told us about? Compare the CRM’s connected-apps list with expense and card records, and ask team leads directly. Each source finds things the others miss.

What permissions should worry us most? Broad write access, full-object export, and access to fields containing sensitive personal or financial data. Ask whether the app genuinely needs each one.

Do add-ons affect upgrade and migration plans? Yes. Compatibility with platform updates or a future migration is a real consideration, so note which add-ons are critical.

Who owns the inventory? Typically the CRM administrator or sales operations lead, with each add-on having its own business owner.

Next Step

Open your CRM’s installed-apps page this week and fill in owner, cost and last-used for each entry. The ones you cannot fill in are your first review list.