Run a weekly pipeline review that isn't a status meeting
Redesigns the weekly pipeline review around a simple rule: only deals where group attention changes the outcome make the agenda. You get the CRM filter views, a timeboxed 45-minute structure, facilitation lines for shutting down narration, and named anti-patterns — turning a dreaded status readout into the meeting where deals actually move.
You are a sales operations coach who has rebuilt the weekly pipeline review at dozens of B2B teams, always starting from the same diagnosis: the default meeting is reps reading their deal list aloud to a manager who could have read the CRM. That meeting costs the team hours, teaches nothing, and trains reps to narrate instead of think. A good pipeline review works only on deals where the group's attention can change the outcome, and it ends in commitments.
Design my weekly pipeline review:
1. The filter: rules for which deals make the agenda — stuck past normal stage duration, big and early enough to shape, at a decision point, or flagged by a rep for help. Everything else stays in the CRM. Give me the specific CRM views to build.
2. The pre-read: what everyone updates before the meeting (not during), and the rule that anything answerable from the CRM is not discussed live.
3. A 45-minute agenda with timeboxes: 5 minutes on the number and its delta, 30 minutes working 3-4 filtered deals with a structure per deal (situation in 60 seconds, the specific obstacle, group input, one committed next action with an owner and date), 10 minutes on process patterns the deals revealed.
4. Facilitation rules: what the manager says when someone starts narrating history ('what do you need from us on this deal?'), how to cut a deal discussion that's circling, and how commitments get tracked to next week.
5. The anti-patterns to ban by name: deal-by-deal roll call, forecasting theater (that's a separate 1:1), public interrogation, and solving the same deal three weeks running without escalating.
Avoid: agendas that still secretly review every deal, meetings over 45 minutes, and structures needing manual admin the CRM could automate.
Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time:
1. How many reps are in the meeting, and how many active deals do they carry collectively?
2. What does the current meeting look like, and what do you and the reps each hate about it?
3. What's your CRM, and what views or reports exist today?
4. What decisions should this meeting actually produce for you as the leader?
Once you have my answers, produce the design. If the team is small enough that a weekly meeting is overkill, say so and propose the lighter alternative.How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Be honest in question 2 about what reps say behind your back — that's the meeting you're actually fixing.
- 3
Build the CRM filter views before the first new-format meeting; the filter is the whole design.
- 4
Run the new format for three weeks before judging it — week one will feel strange to everyone.
- 5
Track the committed next actions and open the next meeting with them; unchecked commitments kill the format.
Best practices
If a deal makes the agenda three weeks running, the meeting has failed it — escalate to a dedicated deal review instead.
Let reps self-nominate deals for help; the flagged-by-rep lane is where the best discussions come from.
Keep forecasting out entirely — mixing forecast scrutiny into deal coaching makes reps defensive and both jobs worse.
End every deal discussion with one action, one owner, one date, written down where the room can see it.
Example: what this looks like in practice
A sales manager at a 25-person managed services provider runs a Monday meeting where six reps read through 80 deals in 90 minutes while everyone else answers email. He answers the interview: HubSpot, no saved views beyond 'all open deals', and what he actually needs is early sight of at-risk deals and coaching moments. The model designs three HubSpot views (stuck 1.5x past median stage duration, new deals over $30K, rep-flagged), a pre-read rule, and the 45-minute structure. First week under the new format, the team works four deals instead of eighty; a stuck $45K deal gets unstuck when another rep mentions knowing the buyer's new CFO. Reps stop multitasking because the meeting finally involves them.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Stop reviewing the pipeline in them. Filter the agenda to the 3-4 deals where group attention can change the outcome — stuck, large-and-early, or rep-flagged — and handle everything else asynchronously in the CRM. Structure each deal discussion to end in one committed action with an owner and date. This prompt builds the filters, the agenda, and the facilitation lines.
More sales strategy & planning prompts
Build a quarterly outbound plan that survives contact with reality
Produces a complete quarterly outbound plan — pipeline math, prioritized segments, 3-5 concrete plays, a launch calendar, and named risks — grounded in your actual win rate and team capacity. The capacity check is the killer feature: it forces the plan to admit when the math doesn't close instead of papering over it with optimism.
Design an irresistible B2B offer with the value equation
Applies the value equation to your actual B2B offer instead of leaving it as a book concept. You get a blunt scoring of your current offer, three rebuilt variants with guarantees your margins can survive, the operational cost of each, and a small validation test — turning 'our offer is fine' into an engineering exercise.
Build a 13-week outbound campaign calendar for the quarter
Turns a pile of campaign ideas into a staggered 13-week execution calendar with owners, prep time scheduled before launches, standing review rhythms, and kill criteria at week 7. It prevents the classic quarter shape — frantic week-1 launches, silent middle, panicked final push — by design rather than discipline.