The Quarterly Martech Review: Agenda, Scorecard and What to Cancel

By Antonio Caruso, Caruso Martech

Published Nov 12, 2026 · Updated Nov 12, 2026 · Automation & Intelligence

A stack you cleaned up last year will grow back unless someone checks it on a schedule. Here is a 90-minute quarterly review with a scorecard and a clear rule for what to cancel.

Most marketing teams review their stack once, during a painful audit, and then never again. A year later the same problems are back: tools nobody owns, overlapping features, and renewals that went through because nobody looked at them in time.

The renewal problem is measurable. Vertice, which processes software spend for its customers, found that 70 percent of low-value tail-spend contracts renewed without any review in Q3 2026. Those are exactly the small marketing tools that add up, and a short review every quarter is how you catch them before they renew.

Quick answer: how do you run a quarterly martech review?

  • Book 90 minutes every quarter with the stack owner, a finance contact and each tool owner on call.
  • Score every tool on the same five questions, using data pulled before the meeting.
  • Check every renewal and notice date falling in the next six months.
  • Decide keep, fix or cancel for each tool, and record the reason.
  • Leave with owners, deadlines and a figure for what the decisions save.

Why a quarterly review works better than an annual audit

A quarterly review catches problems while they are still cheap to fix. An annual audit finds them all at once, often after several have renewed for another year. Ninety minutes every quarter keeps the stack in a known state, and it spreads renewal decisions evenly across the year.

The audit still has its place. If you have never built a full inventory, start with a one-day stack audit and use its output as the first quarterly baseline.

After that, the quarterly review only checks what changed: new tools approved through your request process, changed usage, upcoming renewals. That keeps the meeting short enough that people keep turning up to it.

Who should be in the room

Three people make the decisions every quarter: the person who owns the marketing stack, someone from finance, and the head of marketing or whoever signs off the budget. Tool owners join for their item only. Keeping the core group small is what lets the review finish in 90 minutes and still end with decisions.

Finance brings the renewal dates and contract terms, which marketing rarely has in one place, along with any spend that went through expenses. The stack owner brings usage and integration data, and the budget holder makes the calls that need a trade-off.

Tool owners matter because they know what a tool actually does day to day. Five minutes each is usually enough to confirm usage and flag anything the data misses, such as a workflow that only runs at month end.

The review agenda, step by step

The review follows the same five steps every quarter, and most of the work happens before the meeting. The stack owner updates the inventory, the group scores each tool, checks renewals, makes decisions, and records actions. A fixed agenda keeps the meeting short and makes each quarter comparable with the last.

  1. The stack owner updates the inventory a week before, with cost, seats, last-login data and renewal date for every tool.
  2. The group scores each tool on the five scorecard questions, spending most of the time on tools that score poorly.
  3. Finance walks through every renewal and notice date falling in the next six months.
  4. The group decides keep, fix or cancel for each flagged tool and records the reason in one line.
  5. The stack owner logs each action with an owner and a deadline, plus the saving each decision produces.

Step 3 is the one teams skip, and it decides whether the review saves money this year or next. Anything with a notice date before the following review needs a decision in this meeting.

The five-question scorecard

Every tool gets scored on the same five questions: does someone own it, do people use it, does it overlap with another tool, does it connect cleanly to the rest of the stack, and does it earn its cost. Three or more weak answers puts the tool on the cancel shortlist for discussion.

Ownership comes first. A tool with no named owner has nobody to defend it and nobody to fix it, and that is usually where the other problems start.

Usage and overlap need real data. Pull seat counts and last-login dates from each admin panel before the meeting, and list any two tools that do the same job side by side.

Integration and cost are where the hidden expense sits. Writing in CIO, Pawan Deep Singh advises mapping ownership, usage and dependency before touching contracts. The same order works for scoring: know what depends on a tool before you judge whether it is worth the money.

How to decide what to cancel

Cancel a tool when it fails the scorecard and nothing important depends on it. Fix it when it fails on ownership or adoption but does a job you need. Keep it when it scores well. The decision only becomes real once someone checks the notice date, because a cancellation that misses the window waits another year.

Notice windows deserve their own column in the inventory. Vertice's renewal data shows 56.8 percent of marketing software contracts carried auto-renewal clauses in Q3 2026, so many cancellations need written notice well before the renewal date.

A fix decision needs an owner and a deadline too, whether that is training, a configuration change or a cheaper tier. If the tool still scores poorly at the next review, it moves to the cancel list.

Cancelling also needs a plan for the data. Export anything you still need for reporting or attribution before access ends, and tell the people who used the tool what replaces it.

What the review produces

Each review should leave three outputs: an updated inventory, a decision log with owners and deadlines, and a savings figure finance can track. Over a year, those four logs show which decisions stuck, how much the stack cost each quarter, and whether new tools are arriving faster than old ones leave.

That trend matters. Zylo's 2026 SaaS Management Index puts the average company portfolio at 305 applications, and marketing stacks grow the same way when nobody checks them.

Use the quarterly numbers when you ask for budget changes or push back on a new tool request. A year of logged decisions makes a stronger case to finance than any one-off proposal, which is the approach we laid out for presenting a CFO case.

If you want help setting up the inventory, scorecard and first review, see our services or contact us before your next renewal comes round.

Caruso Martech

We write about marketing systems, attribution, and growth operations because these are the problems we work on every day. If something in this post is relevant to what you're building, we're happy to talk through it.

Related insights