Business

Plugins and add-ons: counting the small recurring extras

Websites, online shops and design tools attract small paid add-ons. Individually modest, together they form a recurring cost that deserves its own line.

Editorial illustration for Plugins and add-ons: counting the small recurring extras

Small purchases, large pile

A website might use a plugin for forms, another for speed, another for security and another for bookings. A design tool may have paid extensions. An online shop may rely on paid apps. Each costs a modest amount, billed monthly or yearly, and the total often exceeds the base platform’s fee.

List them all

Open each platform’s billing or add-on page. Record the add-on name, cost, billing period and purpose.

Add-onPurposeCost per month
Form pluginenquiries199
Speed pluginfaster pages149
Booking appappointments349
Security pluginprotection125

The total is 822 a month, or 9,864 a year, on top of the platform plan.

Ask what each does

For each, ask whether the function is essential, whether the platform now includes it or a cheaper alternative exists. Platforms often add features over time that make old add-ons redundant.

Check for overlap

Two add-ons may do the same job. A security plugin and a host with built-in protection may duplicate. Compare feature lists and remove duplicates.

Consider the risks of removal

Before removing an add-on, check what depends on it. Some plugins store data you need. Test changes on a copy of the site if possible, or ask whoever maintains it.

Prefer fewer, better tools

Every add-on adds cost and complexity. A smaller set, kept up to date, is usually safer and cheaper than a large pile.

Track in Spendix

Create a Website and shop add-ons category. File each charge. At the quarterly review, compare the total with the revenue the site produces.

Beware of auto-renewals

Many add-ons renew yearly. Note the renewal dates. An add-on you stopped using may renew without notice.

A worked trimming

Of the four add-ons above, the speed plugin duplicates a feature the host now offers, and the security plugin overlaps with the host’s protection. Removing both saves 274 a month, or 3,288 a year. You test the site afterwards, check page speed and run a security scan with the host’s tool, and find no drop in quality. The booking app stays, because it drives income, and the form plugin stays, because it is cheap and reliable.

Keeping updates in view

Add-ons need updates, and old ones can become risky. Paying for an add-on that is no longer maintained is a double loss. Check the last update date on each. If a tool has not been updated in a long time, plan to replace it.

Set a quarterly reminder to visit the add-on pages, review the list, and compare the monthly total with the site’s income. A site that earns little may not justify many paid extras, and a site that earns well may justify more. The comparison keeps the spending proportionate.

Free options and built-in features

Before paying for an add-on, search for a free or built-in feature that does the job. Platforms evolve, and what needed a paid add-on last year may now be standard. Ask the platform’s help pages, and read the feature list for your plan. A few minutes of reading can avoid a recurring cost.

Keeping a list of what you removed

When you remove an add-on, note the date and the reason. If a problem appears later, the list helps you work out whether the removal caused it. It also helps when you consider returning to a tool, because you remember why you left.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports