For CROs and sales leaders: where to start
Where do I start as a CRO or sales leader? Your view of the Revenue Engine, the playbooks for your week, and the skills that prepare your meetings.
The question
Will we make the number, what’s holding us back, and what does my team do about it this week?
A sales leader’s week is a handful of recurring meetings, each asking a version of that question: the commit call, deal reviews, the pipeline review, 1:1s and, each quarter, the board.
Where it sits on the loop
Mostly Pipeline to Won, with an eye upstream on whether enough replies are becoming pipeline. A CRO answers for the whole loop, renewals and expansion included.
How to think about it
- Start every week from the first constraint. It decides which of your meetings matters most this week.
- Explain movement, not just level. The number on its own is never the question in the room.
- Few actions, each with evidence and an owner. Then check what changed after.
Common mistakes
- Running every meeting from a different report. Use one loop and one first constraint for the whole team.
- Reviewing deals before the stage. A deal-by-deal hour can miss that the whole stage is leaking.
In Summit53
Your view
Your home is the Revenue Engine. With a CRO, VP of Sales or Sales Manager role, the Action Brief, chip strip and cards are tuned to you (for example CRO BRIEF — AS OF TODAY). The masthead shows the whole organisation to CROs and VPs of Sales, and your team to managers. See Revenue Engine home.
Start here
- Read the first constraint and work it: Where is the engine stuck?
- Prepare the commit call: Why is the number different from last week?
- Plan the week: What should I do this week?
Your playbooks
- Is this Commit deal real?
- A competitor just showed up late
- Which region is underperforming, really?
- Board pack and quarterly review
- Can I repeat this AI answer in the room?
Your screens
- Masthead & KPIs and Forecast Command
- Diagnostics and Fix playbooks
- Operating view by region and Capacity planning
- Coaching: manager dashboard
In Claude or Codex
- forecast-delta-brief for the commit call.
- revenue-action-brief-s53 for the week’s priorities.
- deal-review-prep before a deal review.
- territory-review, board-revenue-pack, qbr-generator and rep-coaching-report.
When the data is thin
- Your scope. A manager’s masthead covers their team; check this before quoting a number as the company’s.
- A new team. Until stages have enough volume, there’s no first constraint and conversion steps say Not enough data yet. Start with Build your engine.
Do it this week
- List your recurring meetings and the stage of the loop each one inspects.
- Name this week’s first constraint and the meeting that owns it.
- Pick three actions, each with an owner and the date you’ll check what changed.