Running a Weekly Sales Meeting with Real Data, Not Opinions

Most weekly sales meetings follow the same script: each person reports how their week went, the loudest voices get the most time, nobody can verify anything, and the meeting ends with vague promises. Everyone leaves tired and nothing changes. The cure is to bring the data, not stories, and to give every topic a named owner and a deadline. This article is about running the meeting itself. For the analysis loop that feeds it, see the weekly sales and stock review routine. The screens named here are the real ones in gamitrack.

Before the meeting: thirty minutes of preparation

The meeting leader, usually the sales manager, prepares a one-page summary the day before. Open these and note three or four facts from each:

• Targets: achievement and pace per officer, and dealer progress for the fiscal quarter.
• Performers: the ranking of officers for the period.
• Daily reports: calls, productive calls and kg across the week.
• Visits & flags and Alarms: unresolved flags and the integrity score trend.
• Collections: weekly plan versus actual.
• Stock: low-stock list and expiring batches.

Send the summary to attendees beforehand so nobody sees the numbers for the first time in the room. If an officer is going to be discussed, speak to them privately first.

The agenda (60 minutes)

Minutes	Topic	Data
0 to 5	Last week's actions: done or not	Action list
5 to 20	Targets and pace	Targets, Performers
20 to 30	Market: no-order reasons, notes, competitors	Visit outcomes, market notes
30 to 40	Money	Collections, aging
40 to 50	Stock and supply	Stock, low stock, expiry
50 to 60	Actions and owners	Action list

Keep a timer. If a topic overruns, park it as an action: "discuss separately by Thursday".

Segment 1: Last week's actions (5 minutes)

Read the list from the previous meeting. For each item say done, not done or blocked. This first five minutes teaches the team that actions are real. If the list is not reviewed, nobody will do them.

Segment 2: Targets and pace (15 minutes)

Show achievement against target and the daily pace. Look at the spread: who is ahead, who is behind, who delivered most volume in the last three days (late loading). Use the Performers ranking as a starting point, and add context: new outlets, flags, absence, a blocked road.

Rules for the discussion:

1. Praise specifics: "One officer's productive-call rate rose in the east."
2. Ask questions of those behind, before giving advice: "What is the main reason shops say no?"
3. Never humiliate. Coaching conversations that need more time move to a one-to-one.

Include dealers. In via-dealers mode, dealer annual targets by fiscal quarter show who may miss, while schemes show who may earn. See designing dealer schemes that pay for themselves.

Segment 3: The market (10 minutes)

Pull the week's no-order reasons and market notes. Group them. A hypothetical week might show five "has stock", four "price" and three "credit". Each cluster points to an action: "has stock" suggests focusing on shops with low closing stock; "price" suggests checking competitor notes; "credit" suggests a policy discussion with accounts. This is also the right moment for officers to share what is working: a good pitch, a display idea, a SKU that is moving.

Segment 4: Money (10 minutes)

The accountant presents the Collections weekly plan against actual, and the overdue list by age. For each dealer or shop over due, someone is named to follow up and a date set. Link collection to sales: an officer who sells to an overdue account should know. See collecting payments on time for approaches.

Segment 5: Stock and supply (10 minutes)

The stock manager reads the low-stock list and the expiring batches. Sales decides how to handle shortages (substitutes, delayed promises) and expiring stock (focus, scheme, transfer). If you plan production, this is the place to hand sales signals to the production head; see using sales data to plan production.

Segment 6: Actions and owners (10 minutes)

Close by writing the list, live, where all can see it. Each action needs:

• a verb ("Call", "Fix", "Transfer", "Approve"),
• a named person,
• a date,
• how we will know it is done.

Limit the list to what can really be done by next week, typically five to eight items. Send it the same day.

Ground rules

• Start on time. Late people learn to be on time.
• Phones away, except to look up data.
• Data first. "I think" is welcome only after "the numbers show".
• One conversation at a time.
• Disagree with the data by checking it. If a number is disputed, someone opens the orders or payments right then, or takes it as an action.

Coaching spots

Reserve one rotating slot for a short coaching point, such as how a top performer handles a closed shop. Use the day comparison or the officer's visits to show what they did, and let them explain it to peers. Keep it under five minutes. Over a quarter the team gains twelve practical ideas that came from the team itself.

Common failures

Failure	Fix
Meeting becomes storytelling	Start from the screens, not from reports
Data is late or wrong	Make same-day entry a rule; review in the daily routine
The same people talk	Ask each officer one question
Actions vanish	Review them first next week
Fear of the numbers	Praise good data habits, not only high sales

Linking to other routines

The weekly meeting sits between the owner's daily morning routine, which finds problems, and the month-end closing, which settles targets, commissions and collections. The 12 KPIs article gives you a ready list of what to bring.

Next steps

Everything above is read from the same data you already enter during the day, so the better the daily habit, the shorter the meeting. See the plans on the pricing page, and use the Help centre for reports and targets setup.