The question

Everyone on the leadership team looks at a different dashboard. What should I be looking at?

When each leader brings their own numbers to the meeting, the meeting turns into reconciling them. The fix isn’t one dashboard for everyone, and it isn’t a separate one each.

Where it sits on the loop

The whole loop, seen from where you sit. Sales leaders mostly work Pipeline and Won. Customer success owns Onboarding through Renewed. Whoever owns go-to-market looks after Imported through Replied. A CRO and RevOps answer for the whole thing.

Every recurring meeting inspects one part of that loop: the commit call looks at Pipeline to Won, the renewal review at the customer side, the pipeline review at the acquisition side.

How to think about it

One map, different lenses.

Everyone reads the same loop. The stages, the conversion rates between them and the first constraint are the same for the whole team, so there’s one version of the truth to argue about.
Each role starts from the stages it can change. A CRO needs to know which reps are behind ramp. A customer success leader needs to know which renewals are at risk. Same loop; different first question.
Keep the first constraint shared. Lenses decide what each person works on today. They shouldn’t produce different answers to “what is holding us back?”
A pulse first, detail on request. Four numbers you read in five seconds, with the detail one click away, beat a wall of charts nobody opens.

Common mistakes

Every leader builds their own dashboard. The numbers disagree at the edges, and the meeting spends its time on which one is right.
One dashboard for everyone. It has to show everything, so nobody can find their own first question on it.
Reading someone else’s lens as your own. Previewing another role is useful, but the headline numbers you see are still scoped to what you are allowed to see.

In Summit53

The Revenue Engine is the home for leaders, at / and always at /revenue-engine. The masthead, canvas and first constraint are the same for everyone. The Action Brief, the persona chip strip and the operational cards change with your persona.

Where `/` takes you

If your role is Individual Contributor, / opens My Engine. You can still open /revenue-engine.
If your workspace is brand new (no deals and no leads yet), / opens Build your engine.
Otherwise / opens the Revenue Engine. While it decides, the page reads Loading your workspace...

How your persona is chosen

Your persona comes from your functional role, set in Teams, roles & invites:

Chief Revenue Officer → Chief Revenue Officer
VP of Sales → VP Sales
Sales Manager → Sales Leader
RevOps Leader → Revenue Operations
Customer Success Leader → Customer Success
GTM Owner → GTM Owner
Sales Enablement Leader → Sales Leader
Individual Contributor, which is also the default for a new sales profile → Account Executive

If you have no sales profile at all, you see the Sales Leader view. There is no persona picker on the page. To preview another persona, add ?persona= to the address, for example /revenue-engine?persona=cro. Accepted values are cro, vp_sales, sales_leader, revops_leader, cs_leader, gtm_owner and account_executive; anything else shows Sales Leader.

The active persona is named in three places: the Action Brief eyebrow beside the canvas (for example CRO BRIEF — AS OF TODAY), the chip strip (CHIEF REVENUE OFFICER · CARDS) and the card drawer’s header.

The page, top to bottom

Masthead: the forecast call, pacing, KPI tiles and the period selector, with the Engine | Blueprint switch and the Field guide, Diagnostics, Glossary and Refresh buttons. See Masthead & KPIs.
Build your engine card, while setup is unfinished. See Build your engine.
Where your next deals come from, in workspaces that are still building up activity. See Action plans & tasks.
Canvas, with the Action Brief docked to its right (below it on narrower screens). See Revenue flow canvas and Diagnostics.
Did our advice work?, once something is being tracked. See Signals & the Loop.
Persona chip strip, which opens the card drawer (below).
Operating View by segment, sales region or market. See Operating view by region.
Annual planning scenario, when it applies (see below).
A three-column row: the Forecast Rail, the Stage Inspector, and Quota pacing with Forecast gap diagnosis. On a phone the side columns stack at the bottom.
Capacity Planning, when it applies (see below).

Switching the masthead to Blueprint replaces everything below the masthead with your Blueprint. See Blueprint & Knowledge.

The persona chip strip

Below the Loop band, a strip shows a few numbers for your persona, after a tag such as CHIEF REVENUE OFFICER · CARDS. Click the strip or Open cards to open the drawer.

Sales Leader: stalled deals, high-risk deals, reps behind ramp, at-risk value.
Chief Revenue Officer: hunter / farmer / hybrid, reps behind ramp, revenue at risk, avg waste score.
VP Sales: reps need coaching, reps behind ramp, at-risk deals to touch, hunter / farmer / hybrid.
Revenue Operations: avg waste score, high-risk deals, at-risk value, data quality, Salesforce sync.
Customer Success: retention signals, NRR, GRR, accounts at risk.
Account Executive: my stalled deals, my revenue at risk, meetings missing notes, my next renewal.

A chip with no value is hidden; if none has a value, the strip doesn’t appear. The GTM Owner persona has no chip strip.

The operational card drawer

The drawer slides in from the right, headed for example CHIEF REVENUE OFFICER · OPERATIONAL CARDS and Chief Revenue Officer cards, with Must-have layer · routed by ?persona=cro underneath. Close it with Close, the × button, Esc or a click on the dimmed page. The cards load each time you open it.

Sales Leader, and personas without their own set (Account Executive, GTM Owner): Deal Drag, Ramp Cohort.
Chief Revenue Officer: Team Deal-Mix, Ramp Cohort, Deal Drag.
VP Sales: Coaching Priorities, Ramp Cohort.
Revenue Operations: Deal Drag, Data Quality, CRM Sync Health.
Customer Success: Renewal Forecast, CS Movers.

Team Deal-Mix: reps classed as Hunters, Farmers, Hybrid or Unknown by the deals they closed over the last few quarters. Show reps (N classified) opens the table. With nobody classed yet: No classified reps yet — reps need ≥3 closed-won deals in the window to classify.
Ramp Cohort: reps in ramp by cohort, with Month, Actual / Expected, Progress and a Status of On track, Ahead, Behind or No quota. View lowest-attainment rep → opens that rep. Empty: No reps currently in ramp.
Deal Drag: Average Waste Score, High Risk Deals, At Risk Value and Stalled Deals, with View full Deal Drag →. See the Risk Signals guide.
Coaching Priorities: this week’s reps needing attention, their coaching layer (On target, Effort, Knowledge, Skills or Other) and their at-risk deals. Empty: No coaching priorities this week — team coaching layers and deal execution are within tolerance.
Data Quality: the overall score and status, then the largest issue after TOP ISSUE, with View full DQ dashboard →. Empty: No data quality issues detected.
CRM Sync Health: one row per Salesforce, HubSpot or JobAdder connection with Health (Healthy, Degraded, Failing or Not synced), Last sync, 7d errors and Avg latency.
Renewal Forecast: the renewal book for the next 90 days in four tiles (Renewal book, At risk · N accts, Commit, Best case) and up to three at-risk accounts. Empty: No renewals land in the next 90 days.
CS Movers: health-score movement in Movers down and Movers up, plus At risk in 30 days, a directional projection. With no history: No health-score movement yet — accounts need a prior V/I snapshot to show a delta.

Capacity Planning and the Annual planning scenario

Capacity Planning appears only when the address names the CRO or Sales Leader persona (?persona=cro or ?persona=sales_leader); a matching role alone isn’t enough. The Annual planning scenario appears for the same personas, and also when a Learning Hub step links to it. Both are covered in the Capacity planning workspace guide.

The welcome window

Until you start onboarding, Summit53 may open Welcome to Summit53!, which asks you to Select your role (Account Executive, Sales Leader, Founder or RevOps) and shows your route through the Learning Hub. Start Onboarding begins it (Sales Leaders and founders with a leader role land on Build your engine); Skip for now or the × hides it for the rest of your browser session. It stays out of the way while a Fix playbook is open.

Preview a persona

Open /revenue-engine?persona=vp_sales (or another value from the list above).
Check the Action Brief eyebrow, for example VP SALES BRIEF — AS OF TODAY.
Click the chip strip or Open cards.
Review the cards, then close the drawer.
Remove ?persona= to return to your own view.

When the data is thin

Whose data. The masthead’s numbers follow what you’re allowed to see, not your persona: owners, admins, CROs and VPs of Sales see the whole organisation; a manager sees their team; everyone else sees their own book. Nothing on the page labels which, and ?persona= doesn’t change it.
What a preview changes. ?persona= changes the Action Brief, the canvas’s rings, the chip strip and the cards. The first constraint stays the same for every persona with an organisation-wide view; the Account Executive persona has none.
Missing values are hidden, not zero. A chip without a value doesn’t show. Cards say when there’s nothing to report, for example No reps currently in ramp.
Manager-only cards. Some cards show an access message instead of numbers: Hunter/Farmer mix is only available to managers., Ramp cohort is only available to managers., Coaching priorities are only available to managers., Renewal forecast is only available to CS leaders and managers. and CS Movers is only available to CS leaders and managers.
Directional, not predictive. At risk in 30 days on CS Movers extends a recent trend; treat it as a prompt to look, not a forecast.

Do it this week

List your recurring meetings: commit call, deal review, pipeline review, 1:1s, renewal review, board.
For each one, write the stage or stages of the loop it actually inspects.
Mark any stage that no meeting looks at. That gap is often where the first constraint hides.
For each attendee, write the first question they should answer before the meeting, and where they’ll find it.
Agree one shared number everyone quotes the same way: the first constraint.

Troubleshooting

Going to the home page takes me to My Engine. Your role is Individual Contributor. Use /revenue-engine for the organisation view.
Going to the home page opens Build your engine. Your workspace has no deals or leads yet. Bring some in and / opens the Revenue Engine.
I’m a team lead but I see the Account Executive view. Your sales profile’s role is still Individual Contributor, the default. Ask an admin to change it on the Roles page.
The masthead numbers didn’t change when I previewed another persona. That’s expected: the masthead follows your own access, not the persona.
No chip strip appears. The brief may still be loading, none of the chips has a value yet, or you’re viewing the GTM Owner persona.
I’m a CRO but I don’t see Capacity Planning. Add ?persona=cro (or ?persona=sales_leader) to the address.
A card shows an access message. It’s limited to managers or CS leaders; see “When the data is thin”.

Revenue Engine home: one loop, a view for each role