How do I run a weekly pipeline review in TactStack?
Short answer
A weekly pipeline review is a standing meeting where the team walks through every open deal by stage, calling out what has stalled and what needs a next step. Pull up the pipeline live, sort by stage and last activity, and assign an action to anything that has not moved in longer than it should.
Before you start
- An up to date sales pipeline with clear stages and owners on every deal.
- A recurring time slot on the calendar for the review itself.
- A rule for how long a deal can sit in a stage before it counts as stalled.
- The ability to filter or sort the pipeline by last activity date.
Step by step
- 1
Set the meeting on a fixed weekly schedule
Put a standing appointment on the calendar for the same day and time every week, ideally early enough to still act on what comes up.
A pipeline review that happens whenever there is time eventually stops happening.
- 2
Open the live pipeline, not a snapshot
Run the review directly from the working pipeline view rather than a report exported earlier in the week.
Deals move daily, and a stale snapshot leads to discussing problems that are already fixed.
- 3
Sort by stage and last activity date
Group deals by stage, then within each stage sort by how long it has been since the last update or contact.
This surfaces the deals actually at risk instead of just the newest or largest ones.
- 4
Set a stall threshold per stage
Agree on how many days a deal can sit in a given stage before it counts as stalled, since early stages tolerate more time than late ones.
Without a defined threshold, every stall discussion turns into an argument about what counts as too long.
- 5
Walk the stalled deals first
Spend the bulk of the meeting time on deals past their threshold, asking the owner what the blocker is and what the next concrete step is.
Healthy deals do not need meeting time; stuck ones do.
- 6
Assign a next action before moving on
Every stalled deal should leave the meeting with a specific next step, a date, and an owner attached, logged directly on the deal.
A stalled deal discussed without an assigned action just gets discussed again next week.
- 7
Spot check the healthy stages briefly
Glance at total count and value in the earlier stages to confirm the top of the pipeline is still being filled.
A pipeline can look fine this week and run dry in a month if new deals stop entering it.
- 8
Review last week's assigned actions first
Before covering new stalls, check whether the actions assigned in the previous review actually got done.
A pipeline review with no accountability for its own action items trains the team to ignore it.
What good looks like
- Stalled deals get caught within a week instead of surfacing at the end of the month.
- Every stuck deal leaves the meeting with an owner and a next step, not just a discussion.
- The team gets a consistent read on how full the pipeline is, not just how big it looks.
- Sales managers can coach on specific deals instead of vague performance concerns.
Common mistakes
The ways this goes wrong in team, and what to do instead.
Reviewing every deal instead of the stalled ones›
Walking through the entire pipeline top to bottom wastes time on deals that are moving fine and pushes the real problems to the end.
Do this instead: Sort by last activity and lead with the deals past the stall threshold.
No defined stall threshold›
Without a clear number of days per stage, the team argues over what counts as stuck instead of fixing it.
Do this instead: Set a specific day threshold for each stage before the first review.
Discussing problems without assigning actions›
A deal flagged as stuck but left without a next step and an owner shows up stuck again the following week.
Do this instead: Require a logged next step and date before moving to the next deal.
Skipping the review when the pipeline looks light›
A quiet pipeline is exactly when the review matters most, since it is the moment to catch a drop in new deals early.
Do this instead: Keep the weekly review on the calendar regardless of how full the pipeline looks.
Frequently asked
6 questions about run a weekly pipeline reviewRelated guides
Pick the next thing to set up, or back up a step if something here assumed work you have not done yet.
Do this next
The natural follow-on tasks once this one is working.
People usually get here from
Guides that lead into this one, in case you skipped a step.
More in Team
Nearby tasks that share the same setup and vocabulary.
Was this guide helpful?
Tell us what worked and what didn't. It shapes what we rewrite next.
You didn't get into business to be in the tech business.
Managed Tech clients hand this to us. We build it, test it, maintain it, and add to it as the business changes, so nobody on your team has to become the person who knows how the system works.