A WordPress agency can accumulate paid plugins faster than it accumulates reliable records about them. One licence belongs to the client, another sits in a former employee’s account, a third renews for sites that no longer use it, and a fourth is essential but has no named owner.
An invoice list will not reveal those problems. A useful WordPress plugin subscription audit must connect payments to installations, responsibilities and operational consequences.
This guide provides a repeatable audit process for agencies managing multiple client sites.
Define what the audit must answer
The audit should make five decisions possible:
- Which paid tools are installed and active?
- Who owns each licence and renewal account?
- Which client or agency service pays for it?
- Is the tool still needed, supported and correctly licensed?
- What happens if the agency renews, replaces or cancels it?
Do not begin by asking what can be cancelled. Begin by establishing the truth.
Create a subscription inventory
Use one row per product and licence relationship, not merely one row per invoice.
Recommended fields include:
| Field | Purpose |
|---|---|
| Product and vendor | Identifies the software |
| Licence owner | Shows which account controls access |
| Billing owner | Identifies who pays |
| Renewal date and term | Prevents surprise renewals |
| Currency and tax basis | Makes totals comparable |
| Site allowance | Records the contractual limit |
| Sites currently using it | Connects cost to real installations |
| Operational purpose | Explains why the tool exists |
| Update entitlement | Shows what continues after expiry |
| Support entitlement | Clarifies the effect of non-renewal |
| Replacement difficulty | Exposes migration and training cost |
| Decision and owner | Turns inventory into action |
Record evidence for the important fields: vendor account, invoice, licence terms, WordPress installation and internal owner.
Run the audit in seven steps
1. Collect financial records
Export card transactions, invoices, accounting entries and vendor renewal notices for at least one full renewal cycle. Search for trading names as well as product names.
2. Inspect every managed WordPress site
Export or record active and inactive plugins, including version and update status. WordPress’s plugin-management documentation explains that the Plugins screen covers activation, deactivation, deletion and updating, but agencies still need a portfolio-level record across separate sites.
3. Match installations to paid accounts
Connect each commercial plugin to the vendor account and licence key owner. Flag installations where the agency cannot confirm update entitlement.
4. Confirm ownership and client allocation
Label the licence as agency-owned, client-owned or third-party-owned. Record whether the cost is included in a care plan, recharged separately or absorbed by the agency.
5. Review utilisation and overlap
Identify licences that exceed current site needs, multiple products serving the same purpose, and tools retained only because nobody wants to decide.
6. Assess cancellation risk
Check what happens to updates, support, stored data, front-end output and administration if the subscription ends. Never assume expiry simply disables billing without operational effect.
7. Approve and record the decision
Choose renew, resize, replace, transfer, consolidate or cancel. Assign an owner and a completion date, then verify that the financial and technical actions both happened.
Separate cost from value
Annual price alone is a poor decision rule. Compare each tool against:
- time saved during delivery and maintenance;
- revenue or service capability it supports;
- training and documentation already invested;
- reliability and quality of updates;
- security and compatibility risk;
- replacement and migration cost;
- effect on client agreements;
- availability of a realistic alternative.
A £300 tool used safely across many profitable care plans may be excellent value. A £30 licence attached to an abandoned site may be pure waste.
Calculate the real annual cost
Convert monthly, annual and multi-year payments into one annual view. Keep currencies explicit and record whether tax is included.
Then add operational cost:
- administration of renewals and licence keys;
- staff time learning different interfaces;
- support time caused by inconsistent configurations;
- migration effort when a tool changes terms;
- emergency purchases when ownership is unclear.
This explains why consolidating several small subscriptions can matter even when the invoice saving appears modest.
Check site limits and licence terms
Do not infer rights from the number of installations that currently activate successfully. Read the vendor’s current terms.
Confirm:
- production, staging and local-development allowances;
- agency or client-use restrictions;
- transfer rules when a client leaves;
- whether updates continue after licence expiry;
- whether support and cloud services are separate;
- whether a “lifetime” or one-time licence has stated limits;
- what happens to data if a hosted service is cancelled.
WpAgencyKit publishes its current scope on the licence terms page. Use the same evidence-based review for every vendor in the stack.
Identify dangerous ownership patterns
Flag these situations immediately:
- licences controlled by a former employee;
- recovery email belonging to a supplier rather than the agency or client;
- one personal account shared across the team;
- client-owned licences paid from an agency card without a written arrangement;
- agency licences installed on departed client sites;
- production sites using unlicensed or abandoned software;
- renewals with no technical owner;
- critical plugins whose expiry effect has never been tested.
Correcting ownership can be more valuable than cancelling a subscription.
Decide whether to consolidate
Consolidation is useful when it reduces overlapping administration without removing necessary controls.
Compare candidates by capability, data ownership, update route, site allowance, privacy, support and exit path. Test the replacement on a representative site before committing the portfolio.
The WpAgencyKit Bundle combines deployment, cookies, menu conditions, SEO and translation tools under one licensing model. It may reduce overlap for agencies that need those functions, but the audit should first confirm which capabilities each client site genuinely requires.
Build renewal control into normal operations
After the first audit:
- review renewals at least 60 days before payment;
- reconcile the inventory after client onboarding and offboarding;
- require an owner for every new subscription;
- record the business purpose before purchase;
- prohibit untracked personal accounts for agency-critical tools;
- sample installations against licence allowances quarterly;
- keep cancellation and migration evidence.
Finish with decisions, not a spreadsheet
A completed audit produces an approved action list:
- renew essential licences;
- reduce unused site tiers;
- transfer client-owned subscriptions;
- consolidate proven overlap;
- replace unsupported products through a tested migration;
- cancel only after dependencies and rollback are understood.
The objective is not the lowest possible software bill. It is a controlled stack whose cost, ownership and operational value the agency can explain.