A weekly marketing meeting should end with decisions: what ships, what stops and who owns each call. The agenda below does that in 45 minutes by moving status updates into async pre-work and spending the live time on three things: metrics against target, experiment results and next week’s bets.
Why most marketing meetings are status theater
The typical marketing meeting is a round of the room. Each person reads out what they worked on, the lead nods, and everyone leaves with the same plan they walked in with. It feels productive because everyone spoke. Nothing changed.
A quick test: if you canceled the meeting and circulated the notes instead, what would the team lose? If the honest answer is nothing, you’re running status theater.
The usual causes are structural, not personal:
- The agenda is a list of people, not a list of decisions. Time goes to whoever talks longest, not to whatever matters most.
- There are no targets on the screen. Without a number to compare against, every metric looks fine or alarming depending on who presents it.
- Experiments have no decision rules. Results get discussed, then discussed again next week.
- Nobody in the room can say yes. If every real call needs the founder, and the founder isn’t there, the meeting can only report.
- Commitments have no owner or date. “We’ll look into it” is a mood, not a commitment.
Fix the structure and the meeting fixes itself.
The 45-minute agenda, block by block
Five blocks, same order every week, with a hard stop.
| Time | Block | Output | Led by |
|---|---|---|---|
| 0-5 | Last week’s commitments | Done, not done or carried, with a reason | Meeting lead |
| 5-15 | Metrics review | Each off-target metric labeled explained, investigate or act | Metric owners |
| 15-30 | Experiment results | Ship, iterate, kill or extend for each concluded test | Experiment owners |
| 30-40 | Next week’s bets | Three to five priorities, each with an owner, a definition of done and a due date | Meeting lead |
| 40-45 | Decisions readback | Decisions, escalations and parking lot confirmed out loud | Note taker |
A few rules keep it inside 45 minutes:
- Start on time, even if someone is missing. Their pre-work speaks for them.
- Anything needing more than five minutes of debate goes to the parking lot and gets its own smaller session with only the people who need to be there.
- The decision maker attends. If that’s a founder or CEO who can’t come every week, they delegate the authority explicitly, in writing.
- No slides. Everyone works from the same scorecard and the same notes doc.
The commitments check is the only block that ties this meeting to last week’s promises. Keep it binary: done, not done, or carried with a one-line reason.
The metrics review: what to look at weekly vs monthly
The weekly scorecard should hold leading indicators the team can move within a week or two. Lagging outcomes like pipeline by source, win rate, payback and cohort LTV move too slowly to act on weekly, and reviewing them every week invites overreaction to noise. Keep the weekly view to roughly eight to twelve numbers.
| Business type | Review weekly | Review monthly |
|---|---|---|
| B2B SaaS | Demo requests or trial signups, lead acceptance by sales, spend and cost per qualified lead, trial activation | Pipeline created by source, win rate, CAC payback, expansion and churn |
| Ecommerce / DTC | Revenue, orders, blended MER, new-customer CAC, site conversion rate | Contribution margin, repeat purchase rate, cohort LTV, channel mix |
| Service business | Inquiries, booked calls, cost per booked call, proposals sent | Close rate, revenue by source, average engagement value |
Each weekly metric should roll up to something the company already committed to for the quarter. If you’ve set marketing OKRs tied to revenue, your weekly metrics are the key results and the inputs behind them.
How to run the ten minutes
Show every metric against its target and its trailing four-week average, then discuss only the rows that sit outside an agreed band. A band of 10-15% off the four-week average is a reasonable starting point; tighten or loosen it once you see how noisy each metric is. Rows inside the band get zero airtime.
Every row outside the band gets exactly one of three labels:
- Explained: a known cause, such as a promotion ending, a holiday or a tracking change. Note it and move on.
- Investigate: cause unknown. One owner, a due date, and a finding at next week’s meeting.
- Act: cause known and fixable now. The decision gets made in the room.
A red number without a label is just anxiety.
Reviewing experiment results and deciding what comes next
This block gets the most time because it’s where the team learns. Only two kinds of tests belong here: tests that concluded, and tests that hit their pre-set decision date. Tests still running don’t get discussed.
Each owner presents in the same format, in about two minutes:
- Hypothesis: what we believed and why
- Primary metric and decision rule: set before launch
- Result: the number, the sample and how confident we are
- Recommendation: ship, iterate, kill or extend
Then the group decides:
| Decision | When to use it | What happens next |
|---|---|---|
| Ship | Clear win on the primary metric, guardrail metrics intact | Roll out and add the follow-up to next week’s bets |
| Iterate | Promising signal, or a loss with a clear reason | New variant with one variable changed goes into the backlog |
| Kill | Clear loss, or flat with no reason to expect a different outcome | Log the learning, free the capacity |
| Extend | The pre-set sample size hasn’t been reached | New decision date, no peeking in between |
The rule that saves the most time: the decision rule was written before the test launched, so the meeting applies it instead of debating it. “Extend” is only for tests that haven’t reached their planned sample, never for a result someone found disappointing.
Inconclusive results are results. Log them with the same care as wins, because the next person with the same idea needs to know it was tried. How tests get into the queue, and how the backlog is scored, belongs in your growth experimentation process. The weekly meeting is where that process gets its decisions.
Priorities, owners and deadlines
The bets block turns the first thirty minutes into next week’s work. Limit it to three to five team-level priorities; anything smaller belongs in individual task lists.
Every bet needs four things before it goes on the list:
- One owner, by name. Not “paid team.” A person.
- A definition of done. “Launch the new pricing page variant to 50% of traffic,” not “work on pricing page.”
- A due date. Usually before next week’s meeting, so it shows up in the commitments check.
- The metric it’s meant to move. If it doesn’t connect to a number on the scorecard, ask why it’s a priority.
Then do a capacity check. Compare the list against what the team actually completed last week. If people committed to eight things and shipped four, commit to five, not eight again. Over time, the share of commitments completed becomes a useful signal of its own: consistently low means the team overcommits or gets pulled into unplanned work; always perfect usually means the bets are too safe.
Async pre-work that keeps the meeting short
The meeting only fits in 45 minutes if the reporting happens beforehand, in writing. Set a deadline, such as the end of the day before, and hold it.
- Scorecard updated with this week’s numbers, targets and four-week averages
- A one-line note from the owner on every metric outside the band
- Experiment readouts written in the standard four-part format
- Each person posts a three-line update: shipped, slipped, blocked
- Decisions needed listed, each with a recommendation from whoever raised it
- Meeting lead reads everything and orders the agenda so decisions come first
One rule makes the whole system work: no pre-read, no airtime. If an update wasn’t posted, it doesn’t get presented live.
The tool doesn’t matter; a shared doc or a pinned Slack thread works. What matters is that the scorecard pulls from the same sources every week, so nobody argues about whose number is right.
Agenda template and meeting notes format
Copy this into your notes doc and reuse it every week:
WEEKLY MARKETING MEETING — [date]
Lead: [name] · Notes: [name] · 45 min, hard stop
Pre-read due: [day, time] · Scorecard: [link]
1. LAST WEEK'S COMMITMENTS (5 min)
[Owner] — [commitment] — Done / Not done / Carried: [reason]
2. METRICS REVIEW (10 min) — only rows outside the band
[Metric]: [actual] vs [target] (4-wk avg [x])
→ Explained / Investigate ([owner], [date]) / Act ([decision])
3. EXPERIMENT RESULTS (15 min)
[Test]: [hypothesis] · [result, sample] · Decision: Ship / Iterate / Kill / Extend
4. NEXT WEEK'S BETS (10 min)
[Bet] · Owner: [name] · Done means: [...] · Due: [date] · Moves: [metric]
5. DECISIONS READBACK (5 min)
Decisions · Escalations · Parking lot (session owner + date)The notes that matter most are the decisions, not the discussion. Keep a running decision log in the same doc with five fields: the decision, the owner, the date, the reason, and when to revisit it. Post the notes within an hour of the meeting. Months later, that log is how you explain why the plan changed.
When I come in as a fractional CMO, this meeting is usually one of the first things I install. It’s low cost, it shows within a few weeks whether the team is shipping and learning, and it makes every other change easier to run.
Get it built
If your marketing meetings end with updates instead of decisions, I can set up the scorecard, the experiment log and the weekly rhythm, then run it with your team until it runs without me. Start with a Growth Audit, $1,500 fixed and credited if we continue. See pricing or get in touch.