A renewal reminder arrives for a tool you didn't buy. The contract renews in two months, cancelling requires notice before then, and the person who signed it has moved to another team. Now the marketing team has to find out who uses the software, what depends on it and whether the current contract still fits.
That search is a martech stack audit. Your martech stack is the collection of technology your marketing team uses to do its work, and it tends to grow by accumulation: a subscription added for one campaign, a tool inherited with a team, another bought by a different department. Some tools overlap, some are underused, and some support important work that no usage report shows.
Budget pressure makes the questions harder to put off. In Gartner’s 2026 CMO Spend Survey, 56% of CMOs said their marketing organization lacks the budget required to deliver its 2026 strategy. The survey ran from January through March 2026 among 401 CMOs and other marketing leaders in North America, the UK and Europe, and the vast majority represented organizations with annual revenue above $1 billion. Your company may be smaller, but a finance team under similar pressure will still ask what each renewal is for.
The approach below treats the audit as a series of renewal decisions, not one large inventory project. It ends with a one-page brief you can take to finance, IT and the people who use the tool.
Start with the renewals that have deadlines
For each tool up for renewal, collect five facts:
The renewal date
The cancellation or change-notice deadline
The contract owner, who manages the agreement
The business owner, who is accountable for the work the tool supports
The time needed to make a change, including approvals, migration and training
The date that matters is usually earlier than the renewal date. If a contract requires 60 days’ notice, the decision is due two months before it renews, and your internal approvals and any transition work have to fit inside that window. A platform connected to your CRM, your reporting and your campaign sends needs more lead time than a standalone subscription, because more things can break when it changes.
You don’t need to audit everything at once. Begin with the renewals that are close, expensive, unowned or unresolved: the approaching deadlines, the largest spend, the tools nobody clearly owns, and the ones with a question nobody has answered. A short list of those is enough to start.
Connect each tool to the work that depends on it
For each tool on your short list, write down the task or outcome it supports, who uses it directly, who relies on its outputs and which systems connect to it. Keep it to a line or two per tool so the inventory stays small enough to use.
The fastest way to get this is a short conversation with the tool’s owner and someone who uses it regularly. Three questions surface most of what you need:
What would become harder or stop happening if this tool disappeared?
Which outputs do other teams rely on?
Where does someone still have to export, reconcile or re-enter information?
The third question often finds work that never appears in a contract or a usage report, such as a weekly spreadsheet that exists because two systems don’t talk to each other.
Fluence’s work for PepsiCo shows why a connected view matters at scale. In the Marketing Application Contract Repository engagement, Fluence organized approximately 70 marketing applications into a connected view of ownership, integrations, commercial relationships and dependencies, and established the information architecture and renewal preparation guidance around it. The PepsiCo case study describes that work. The lesson carries over to a portfolio of any size: renewal decisions become easier when each application’s owner, agreement and dependencies sit in one place.
Read usage in context
Usage data tells you who logged in. It doesn’t tell you who depends on the results. A tool with two regular users may produce reports the entire department reads. A seasonal tool may be essential during one campaign each year. An integration may keep important work running in the background with almost no logins.
So treat low usage as a question, not a verdict. When adoption is weak, the cause might be a poor fit, a confusing workflow, too little training, a duplicate of something you already own, or a business need that has changed. Each points to a different action. Our article on why an unused tool is a design problem looks at low adoption through workflow, trust and support. Decide which explanation applies before you recommend anything, because cancelling a tool nobody was trained to use can simply move the problem to its replacement.
Compare the options on the same terms
Most renewals come down to six choices. The graphic shows when each one fits and what to check before choosing it.

Consolidation is where audits most often go wrong, because two tools can share a feature name and still not do the same job. To test it, look at the specific task, the data it needs, the integrations, the permissions and the people involved. A reporting feature that can’t read the same data for the same viewers hasn’t shown it can absorb the work.
Compare the options over the same period, and include what each one costs beyond the license: implementation, migration, training, a stretch of running old and new systems side by side, and the ongoing work of administering whatever you choose. Count a saving only when you can point to the spending that will actually change, and state your assumptions, such as how long a change will take or when a new price applies, so finance can challenge them. For more on assumptions and defensible value estimates, see Your ROI Calculator Should Survive the CFO, which focuses on designing a calculator. This article is about evaluating the technology you already own.
Put the decision on one page
A renewal decision brief gives finance, IT and the tool’s users the same facts in one place. It covers six things:
The tool and the business need
The decision deadline and the responsible owner
Evidence of use and important dependencies
Options considered and what each would mean
The recommendation and its reasoning
What information is still needed, who will get it and the next action
Here is a completed brief for a reporting platform. The tool, teams and details are invented to show how the pieces fit together.
Tool and need: Reporting platform. It produces the weekly channel report and the monthly summary for the CMO.
Deadline and owner: Cancellation notice is due in 45 days. The marketing operations manager owns the decision, and procurement manages the contract.
Evidence and dependencies: Two analysts use it daily, and the usage report shows no one else logging in. Interviews showed that the demand generation, brand and regional teams all rely on the weekly report, and two ad-platform connections feed it data.
Options: Cancel and rebuild the reports in the CRM. Cut seats, which saves little with only two users. Renew for one year while testing the CRM.
Recommendation: Renew for one year. Usage alone points toward cancelling, but three teams rely on the reports, and the CRM hasn’t been shown to read the ad-platform data. Run that test during the term.
Still needed: Whether the CRM can take in the ad-platform data (marketing operations, within a month) and the vendor’s price for a one-year term (procurement). Next action: schedule the test.
Without the dependency review, this brief would have recommended cancelling a tool that two people use. With it, the recommendation protects work three teams rely on and still sets up a real test of consolidation, with the evidence sitting next to the decision.
Pick the renewal with the nearest notice deadline and write its brief first. The next one will have a template to follow.
If your team needs help organizing costs, evidence, dependencies and competing options into a decision, Fluence’s Cost-to-Value & Decision Support work produces decision briefs, cost views, value analysis, comparison guides and executive summaries.
Fluence Takeaway
A useful martech stack audit starts with the next renewal decision, not a perfect inventory. Identify the owner, deadline, users, dependencies, and real alternatives, then put the recommendation and unanswered questions on one page before the notice window closes.

Nick Katsarelas
Business Development



