Blog · How-to guides · Sales teams
A weekly sales meeting agenda built on computed lists rather than verbal updates: five minutes on the numbers that moved, ten on the accounts that need a call this week, ten on the deals that changed or stalled, and five on commitments made and kept. This page gives the agenda minute by minute, the four lists that feed it and where each comes from, what to cut from the usual meeting, the rules that keep it to thirty minutes, and a copyable template.
Most weekly sales meetings are an hour of people describing their week. This one is half the length and consists of decisions about rows on four lists.
| Minutes | Item | Input | Output |
|---|---|---|---|
| 0 to 5 | Numbers that moved | KPI sheet: only lines that changed beyond their threshold | One sentence each on why; no discussion of numbers that did not move |
| 5 to 15 | Accounts | The account list: top twenty by value needing a touch | For each row: owner, action, date |
| 15 to 25 | Deals | The deal list: changed, slipped or stalled | For each row: next step and date, or close it |
| 25 to 30 | Commitments | Last week's actions | Done or not done; not done carries over once |
Four or five KPIs at most: revenue against the same period last year, value coverage at cadence, dormant accounts by prior value, pipeline coverage against required, forecast against target. Show this week, last week, and the threshold. Discuss only the ones that crossed it.
| KPI | Last week | This week | Threshold | Discuss? |
|---|---|---|---|---|
| Value coverage at cadence | 84% | 79% | Below 80 | Yes |
| Dormant accounts, prior value | $1.9m | $2.0m | Rise over 10% | No |
| Pipeline coverage, in-period | 3.8x | 3.7x | Below 3.5x required | No |
Five minutes is enough because most weeks only one line qualifies. The KPI test decides what earns a place on this sheet.
The twenty highest-value existing accounts that are overdue a touch for their tier, or past their own ordering pattern, or sharply down on last year.
| Account | 12-month revenue | Why it is here | Days since touch | Owner | Action, by when |
|---|---|---|---|---|---|
| Halden Group | $610,000 | No touch in 74 days; tier A owes 30 | 74 | J.R. | |
| Marlow Foods | $280,000 | Orders weekly; none for 31 days | 12 | S.P. | |
| Tessel Build | $240,000 | Down 35% on same quarter last year | 20 | J.R. |
The last column is blank on arrival and filled in the meeting. The owner says what and when; nobody explains why the account was neglected. Ten minutes for twenty rows means thirty seconds each, which is right: the decision is nearly always a call this week. The weekly list by industry hub shows what this list contains on twelve different desks.
Not the pipeline. Only deals where something happened or should have.
| Rule | Why |
|---|---|
| Changed stage this week | Progress, or regress, worth thirty seconds |
| Close date moved | Slipped deals are the forecast miss arriving early |
| In stage longer than twice the norm, no activity in 30 days | Stalled: advance it with a dated next step, or close it |
| Closing within 30 days, above a stated value | The forecast depends on it |
A team with eighty open deals usually has ten to fifteen on this list. Stalled deals get one question: what is the next step and its date? No answer closes the deal, which keeps win rate and coverage honest.
Last week's actions from lists 2 and 3, each marked done or not done. No narrative. An action not done carries over once with a new date. Not done twice goes to a one-to-one, not to the group.
This five minutes is what makes the other twenty-five work. People act on a list they know will be read back.
The round-the-table update. Replaced by the lists.
The full pipeline walk. Belongs in one-to-ones; here, exceptions only.
Numbers that did not move. Reading a dashboard aloud.
Problem-solving in the room. A row that needs more than a minute gets an owner and a follow-up with the two people concerned.
Announcements. Send them.
Weekly sales meeting: [date]. 30 minutes.
Actions recorded in the list itself, not in separate minutes.
Lists built by hand. Late, partial, and quietly edited by whoever builds them.
No existing accounts. An hour on twenty deals, nothing on the two hundred accounts that make the revenue.
No read-back. Actions agreed and never checked; the list becomes decoration.
The list is too long. Sixty accounts cannot be covered; people stop preparing. Twenty, ranked by value.
Four lists, thirty minutes, every row leaves with an owner and a date, and last week is read back. The meeting stops being a report and becomes the place where the week's calls are decided. For how the lists differ from dashboards and reports, see dashboard versus report versus list. Covirage produces the four lists from the CRM and ledger exports each week, with the rules stated on each, so the preparation is already done.
It turns a meeting of eight into eight consecutive two-person conversations with six spectators. The content is what each rep chooses to say, which is rarely the account they have been avoiding. A list built from the data raises that account without anyone having to volunteer it.
Nobody, ideally: they are computed from the CRM and ledger exports and arrive the evening before. If someone is building them by hand every Sunday, they will be late, selective and eventually abandoned. Until they are automated, keep them to what one person can produce in twenty minutes, and keep the rules fixed so the list cannot be shaped.
A pipeline review looks only at deals, and usually at all of them. This agenda gives equal time to existing accounts, which is where most B2B revenue comes from and where most meetings spend no time at all, and it looks only at exceptions. Deal-by-deal inspection belongs in one-to-ones.