Insights — Sales Problems & Founder-Led Growth — 6 min read
How Should a Managing Director Review Sales Each Week?
A Managing Director's weekly sales review is not the team's pipeline meeting run one level up — it is a shorter, sharper set of questions aimed at catching problems the team's own routine will not surface on its own.
In short
A Managing Director's weekly sales review should take fifteen to thirty minutes and focus on four things: whether pipeline numbers have moved in a way that matches what was actually reported as happening, whether any deal or account needs an MD-level decision this week, whether activity levels are consistent with the team's own targets, and whether anything in the numbers contradicts what the MD is being told verbally. It is a check on the business's commercial reality, not a repeat of the team's own operational meeting.
Many Managing Directors either sit inside the team's own pipeline meeting, adding little beyond their presence, or skip weekly review altogether and only look closely at sales once a quarter's numbers have already disappointed. Neither gives an MD what they actually need, which is a short, regular check on a small number of things only the MD is positioned to judge: whether the pipeline can be trusted, whether the team is doing enough of the right activity, and whether anything needs deciding this week rather than left to run on.
This is a genuinely different exercise from the team's own weekly rhythm — the recurring check-ins, protected prospecting time and pipeline updates that keep day-to-day selling moving. This article is about what the MD personally asks, checks and decides in their own review, not about running that team meeting again from the top.
Why shouldn't the MD's review just be the team meeting, attended by the MD?
Sitting inside the team's own pipeline meeting tends to do one of two unhelpful things: either the MD's presence changes how honestly the team reports problems, because nobody wants to admit a stalled deal in front of the boss, or the MD ends up managing individual deals in detail, which is the team's job, rather than checking the things only a Managing Director should be checking — pattern, risk and decisions that need to be made above the team's own authority.
A separate, shorter review, using the outputs of the team's rhythm rather than replacing it, keeps both meetings doing what they are actually for.
What numbers should the MD actually look at each week?
Fewer than most MDs initially assume. Total pipeline value, the number of new opportunities opened this week, anything that has moved to a decision stage, and anything that has sat without contact for longer than it should have. Trying to review every deal individually every week is not oversight — it is a way of spending an hour without actually deciding anything, because there is too much detail to draw a conclusion from.
- Pipeline value this week versus last week, and why it changed
- New opportunities opened this week, compared with what the team's own activity target implies
- Any deal that has moved to, or stalled at, a decision stage
- Any account or quote flagged as stuck beyond the normal follow-up window
- Anything reported verbally in the last week that the numbers do not support
What does it mean to check whether the pipeline "can be trusted"?
It means looking for the gap between what is reported and what is actually true — a pipeline can look healthy on paper while containing several deals that have quietly gone cold, been reported optimistically, or simply never had their status updated. The MD's job in the weekly review is not to personally verify every deal, but to spot-check enough of them, and enough of the pattern of movement week to week, to notice if the numbers being reported no longer feel credible.
What decisions actually belong at the MD's desk, rather than the team's?
Pricing flexibility beyond a set threshold, whether to continue pursuing a large but stalling account, whether a resourcing gap needs addressing now rather than next quarter, and anything that affects cash flow or capacity commitments. These are the decisions the weekly review exists to surface promptly, because a decision that waits three weeks for the MD's attention costs more than one made the week it was flagged.
How does the MD tell the difference between an activity problem and a market problem?
This is one of the specific judgements only the MD is well placed to make, because it requires context the team's own weekly rhythm does not surface — comparing this quarter's numbers against a longer run of history, and against what is being heard from customers and the wider market. If new opportunities opened has fallen but the team's activity numbers look consistent, that points to demand softening rather than effort dropping. If activity has clearly dropped and opportunities have followed it down, that is a team management issue, not a market one, and it needs a different response entirely.
| Pattern | Likely meaning | MD's next step |
|---|---|---|
| Activity steady, opportunities falling | Market or proposition issue | Check pricing, competition, and recent lost-deal reasons |
| Activity falling, opportunities falling | Team management issue | Address with the team lead directly, not just the numbers |
| Pipeline value rising, cycle time also rising | Deals inflating without progressing | Spot-check a sample for genuine movement |
| Numbers steady, verbal reports overly positive | Reporting honesty gap | Ask more specific questions, less general ones |
How much time should this actually take?
Fifteen to thirty minutes, once the numbers themselves are already being produced by the team's own weekly rhythm. If the MD's review is taking an hour or more, it has usually drifted into re-running the team's own detailed meeting, which defeats the purpose of having a separate, sharper check at MD level.
What should the MD do differently in a quiet week versus a busy one?
The temptation in a busy week is to skip the review, on the assumption that no news is good news. That is precisely backwards — busy weeks are when reporting quality slips fastest, because everyone is stretched and updates get abbreviated. The MD's review should be the one weekly commitment that does not get pushed, even in a five-minute version, because it is the one check specifically designed to catch problems before they surface on their own three months later.
What is the most common mistake MDs make in this review?
Reviewing only revenue and pipeline value, without looking at the activity that produces them. Revenue and pipeline are lagging indicators — by the time they move, the cause is usually several weeks old already. Activity levels are the only part of the weekly numbers the MD can actually influence in real time, which is exactly why they deserve more attention than the outcome figures that get most of the attention by default.
When does this weekly discipline stop being enough on its own?
A short weekly review is a genuinely good habit, but it is a monitoring tool, not a strategy. If the same issues — stalled deals, falling activity, an over-optimistic pipeline — keep showing up week after week despite being flagged, that is a sign the underlying process or team structure needs proper attention rather than another few weeks of watching the same numbers. That is a reasonable point to bring in fractional commercial leadership, someone experienced enough to fix what the weekly review keeps correctly identifying but the business has not yet resolved on its own.
If you are not yet sure which of these problems you actually have, the Sales Help for Founders & Business Owners hub is a useful place to work out whether the gap is in this weekly review, the team's own operating rhythm, or something further upstream.
Need Sales Director capability without the salary?
Fractional sales leadership: strategy, pipeline, team management and accountability for one or two days a week.
Related services
Written by
By Tom Evans
International Sales & Market Development Director, Evans Sales Consultancy
Published 21 September 2026 — 6 min read