Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Marketing Technology › MarTech Tool Categories

Reviewing Marketing Tool Licences and Seats

How to review what each marketing tool licence pays for: paid seats against active users, tiers against real usage, duplicate subscriptions and the fixes.
Tutorialbeginner10 min readUpdated

Where licence spend leaks

The marketing technology hub asks of every tool what job it does, who owns it and whether another tool already does the same thing. A licence review asks the cost version of those questions. Spend rarely leaks through one big mistake; it leaks through small drifts in each billing basis, each reasonable when it happened.

LeakHow it usually happensWhere the review catches it
Seats nobody usesA leaver's seat is never released; a seat bought for a project outlives itCompare paid seats with users
Seats on the wrong typeEveryone given the full seat when some only read reportsCompare paid seats with users
Contact counts above needImports, old leads and contacts with no purpose kept indefinitelyCompare contact and usage counts
Usage beyond the tierVolumes grew, or a tier was chosen for a peak that passedCompare contact and usage counts
Add-ons nobody usesA module bought for one campaign and never switched offFind unused modules
Duplicate subscriptionsTwo teams buy the same kind of tool on company cardsFind duplicates
Separate AI seatsAn assistant bought per person when the stack already has AI built inFind unused modules; find duplicates

The choosing and evaluating tools guide defines total cost to include the data costs a tool adds, such as events ingested, contacts held and usage beyond a tier, and a licence review is where those costs are checked after purchase. The marketing tool onboarding SOP asks its adoption review whether any user access can be removed; this tutorial asks the same of every tool at once, and of every billing basis, not only seats.

Before you start

Gather the spend first. From finance, the software lines for the period: invoices, company card statements and expense claims. The guide to building a marketing budget treats annual software contracts as fixed costs and asks for notice periods to be recorded against them; if that was done, the budget is the starting list. The guide to tracking spend against budget notes that annual subscriptions may be booked as prepayments and that software is sometimes booked to a central technology cost centre rather than marketing, so ask finance to search beyond marketing's own lines.

Then gather the use. Administrator access to each tool, or someone who has it, to read user lists, contact counts, usage figures and which modules are switched on. The order forms or terms accepted for each tool, showing what it bills on and when it renews. The stack record or inventory, if the business keeps one. And the team's time: the review ends with conversations about who needs what.

Agree two things before starting. Who decides each change: the tool's owner for their tool, with the budget holder signing off anything that changes a contract. And who owns data protection, because the contact-count step touches Personal Data and the decisions on what to remove are theirs.

The steps

  1. List every paid tool from invoices, card statements and expense claims

    Build one list of every tool the business pays for, however it is paid. Invoices show the contracted tools. Card statements and expense claims show the tools bought by individuals, which are the most likely to be duplicates or forgotten. Include free tiers that carry paid add-ons, and tools paid for by an agency and recharged. For each, note the owner, the amount, how often it is billed and who pays it. Where the business has a stack record, add anything it lacks; the tutorial on running a marketing stack audit covers the wider inventory.

  2. Record what each licence bills on: seats, contacts, usage or modules

    For each tool, write down what the bill depends on, from the order form, the terms or the invoice lines. The common bases are seats (named users, sometimes of different types), contacts or records held, usage (sends, events, sessions or similar volumes), modules and add-ons switched on, and the tier that bundles some of these together. Many tools bill on more than one. Record the renewal date, the date by which notice must be given and whatever the terms say about changing quantities during the term. If the terms are unclear, note it as a question for the supplier rather than guessing.

  3. Compare paid seats with the people who actually use each tool

    Set the number of paid seats against the tool's user list, then against the people who use it in practice. Look for seats held by leavers, seats assigned to nobody, seats held by people who no longer use the tool, and people on a full seat whose work needs only a lighter one. Use the tool's own last-activity information where it shows it, and ask the seat holders where it does not. Hand account removals to the access review, so that removing a seat and removing access happen once, in order, and are recorded; a leaver's records and integrations are handed over before the account goes.

  4. Compare contact and usage counts with what the programme needs

    Where a tool bills on contacts held, compare the count with the contacts the programme actually needs: people who can be contacted for a live purpose. The gap is usually old imports, leads with no consent record, duplicates and contacts with no purpose. Removing contacts that serve no purpose is consistent with the data minimisation and storage limitation principles the GDPR glossary entry describes, and the decision, including whether records are deleted or archived, belongs to whoever owns data protection. Keep every suppression entry: a suppression list exists so that people who opted out are recognised and blocked if their address arrives again, as the ICO's direct marketing guidance cited there expects opt-outs to be honoured. For usage-based billing, compare the volumes in the bill with the volumes the use cases need, and look for usage nobody intended, such as a test sending to the full list.

  5. Find modules and add-ons nobody uses

    List the modules and add-ons each tool bills for and set each against a use case someone can name. Add-ons bought for one campaign, a trial that converted to paid, and features bundled into a higher tier that nobody uses are the usual finds. For AI add-ons and separately bought AI seats, check what AI the stack's existing tools already include; the comparison of standalone AI assistants and built-in AI features sets out how to decide which route a task needs, and a paid seat for a task the built-in route already covers is a candidate for removal.

  6. Find duplicate subscriptions for the same job

    Group the tools by the job they do. Two survey tools, two social schedulers or two design tools bought by different teams are the classic finding, often on separate cards so that neither team knew. The MarTech categories guide helps place tools that describe themselves differently but do the same job, and the tool categories hub describes consolidation as a project, not a cancellation. For each duplicate, note which tool better serves the use case and which contract ends first.

  7. Rank the fixes by saving and effort

    Turn every finding into a candidate fix with an estimated saving, from the business's own invoices, and an estimate of the effort: releasing an unused seat is minutes; merging two subscriptions means moving people, data and habits. Sort them on the impact-effort matrix. Quick wins go first. Larger moves, such as consolidating duplicates or changing tier, need a plan and usually wait for a contract date. Fixes with little saving and real effort can be dropped and recorded as such. Read small savings with care: the matrix is a first sort, and a fix that removes a risk can matter more than its saving.

  8. Make the changes at the right contract dates and record them

    Make each change when the contract allows it. Some changes, such as releasing seats, may be possible at once under the terms; others, such as reducing a committed quantity, cancelling an add-on or merging subscriptions, may only take effect at renewal, and the notice date governs whether that renewal is still open. Put each timed change in the calendar with its notice date and owner, and carry it into the review of the tool before it renews, which turns unused seats and add-ons into its negotiation list. The guide to cutting the marketing budget makes the same point for commitments: give notice where a contract allows it rather than breaking it. Record every change in the stack record and tell finance, so the budget and forecast reflect the new amounts.

What to compare for each billing basis

Each basis has its own comparison and its own trap. The table is a reminder for each row of the review.

Billing basisCompareWhere the figures come fromUsual fixWatch out for
SeatsPaid seats against people who use the tool, by seat typeInvoice; the tool's user list and activity; the teamRelease unused seats; move readers to a lighter seat or a shared reportRemoving a leaver's account before their records are handed over
Contacts or records heldThe count billed against contacts needed for a live purposeInvoice; the tool's contact count; the data protection ownerRemove or archive contacts with no purpose, as data protection decidesDeleting suppression entries to lower the count
Usage or volumeVolumes billed against volumes the use cases needInvoice; the tool's usage figuresStop unintended usage; match the tier to real volumesChoosing a tier for an average when the use case peaks
Modules and add-onsEach add-on against a named use caseOrder form; the tool's settingsSwitch off unused add-ons at the date the terms allowAn add-on that another tool quietly depends on
TierThe tier's bundle against what is used from itOrder form; the tool's settings and usageMove to the tier that matches real useLosing a feature a live use case needs
Duplicate subscriptionsTools doing the same job for different teamsCard statements and expense claims; the teamConsolidate onto one tool at the earlier contract endCancelling before the move is done

An engineering consultancy right-sizes its licences (illustrative)

Illustrative example — not a real result

Kinnoculm Engineering right-sizes its marketing licences

Kinnoculm Engineering, an invented engineering consultancy, reviews the licences behind its marketing. Finance's search of invoices, card statements and expense claims finds 13 paid tools, 2 more than the marketing team's own list, both bought on company cards.

The seat comparison finds 14 paid seats in the design tool, 3 of them still assigned to former staff, against 9 people who used it in the previous quarter, and 6 seats in the social scheduling tool against 3 users. The two card purchases turn out to be the same survey tool, bought separately by the graduate recruitment team and the events team for £35 and £42 a month. The email platform bills on contacts held and shows 21,400 contacts. Of these, 6,800 have no consent record and no live purpose anyone can name, and a further 1,150 are suppression entries.

Ranked on the impact-effort matrix, the seat releases are quick wins. The access review removes the former staff accounts first, and 5 design seats and 3 scheduling seats are released at once, which the terms allow. The survey subscriptions are merged onto the events team's account when the other renews, with notice given before its deadline. The data protection lead decides that the 6,800 contacts with no purpose are archived out of the email platform rather than kept, and that every suppression entry stays, so the count falls to 14,600. Each change is recorded in the stack record and finance updates the forecast.

Common mistakes

  • Starting from the tool list instead of the spend. Tools bought on cards and expense claims are the ones the list misses, and often the duplicates.
  • Counting users, not use. A user list shows who can sign in; whether they need the seat is a conversation.
  • Deleting suppression entries to cut a contact count. People who opted out become reachable again the next time their address is imported. Suppressions stay.
  • Removing contacts without the data protection owner. What is removed, archived or kept is their decision, not a billing one.
  • Releasing seats before handing over. A leaver's records and integrations go to someone else before the account and the seat go.
  • Cancelling at the renewal date. The notice date comes first; changes that miss it wait for another term.
  • Not telling finance. A saving that never reaches the forecast is spent twice.

Frequently asked questions

Is a licence review the same as an access review?

No, though they read the same user lists. An access review asks whether each account should exist and at what level, for security and control. A licence review asks whether the business is paying for what it uses. A former employee's account is a finding for both; an active user on a more expensive seat type than their work needs is mainly a licence finding. Run them together where you can, and let the access review make the removals so they are recorded once.

Can we delete contacts to bring the bill down?

Some, with care. Contacts the business holds with no purpose are worth removing anyway, because the GDPR's data minimisation and storage limitation principles argue against keeping personal data that is no longer needed; that decision belongs to whoever owns data protection. Suppression entries are different: they are kept so that people who opted out stay suppressed if their address arrives again. Deleting them to lower a count saves money by making the next mistake more likely.

How do we tell whether someone actually uses their seat?

Ask the tool first, then the person. Many tools show a last sign-in or last activity date in their user list; where one does not, ask each seat holder what they did in the tool recently and what would stop if they lost it. A seat used once a quarter for one report may be better served by a read-only role, a shared dashboard or a request to a colleague. The answer is a judgement about the work, not a usage threshold.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. Regulation (EU) 2016/679 (GDPR) — EUR-Lex
  2. Direct marketing guidance — Information Commissioner's Office (UK)

Related