The question

Something’s off with the number and everyone has a theory. Where are we actually stuck, and did what we did about it help?

This is the question under most leadership meetings. It usually gets three answers, one per department, and a list of initiatives. A month later nobody can say which of them worked.

Where it sits on the loop

The whole loop, from Imported to Renewed and back. It’s the first job of a weekly revenue review, and it sets the agenda for every other playbook: once you know which stage is holding things back, you know whether this week is about the forecast, a deal, a competitor, a region or renewals.

How to think about it

Three moves, in a loop: find, fix, check.

Find the first constraint. The earliest stage that’s clearly failing, judged on stage-wide evidence: conversion against a benchmark, on enough volume to trust. One bad deal is a deal problem, not a stage problem.
Fix it with one ordered plan. Look first, then change the likely cause, then put the change to work. Write down the rate you’re trying to move and the date, and decide how long you’ll wait before judging.
Check what changed after. When the window ends, compare the rate with where it started. Say “it moved after the fix”, not “the fix moved it”. If you can’t tell, say so; it doesn’t count for or against you.
Then look again. Fixing one constraint usually reveals the next. The loop is the method.

Common mistakes

Starting with the loudest problem. The deal the CEO asked about gets the week, and the stage that’s actually broken keeps leaking.
Five fixes at once. Something improves and nobody can say which change it followed, so nothing is learned.
Never checking. The fix is declared done when the steps are done. Whether the rate moved is never asked.

In Summit53

The three moves run across three surfaces on the Revenue Engine, and you can ask the same questions from Claude or Codex.

1. Find it: the first constraint

Open the Revenue Engine. The first slot of the Action Brief reads First constraint · <stage> with a Critical or At risk pill, and that stage pulses on the canvas.
The Stage Inspector opens on that stage. Read its LIKELY CAUSES: Blueprint checks, such as a missing battlecard, that may explain it.
Open Diagnostics → Conversion to see the evidence: the card’s as of date, each step’s ACTUAL against BENCH, and whether its sample is big enough.

How the stage is chosen, and what each state means, is in Diagnostics: find your first constraint and the revenue flow canvas.

2. Fix it: a Fix playbook

Click Fix this: <playbook> on the first constraint (in the Stage Inspector or the Action Brief).
Read Why this was suggested and What you’ll do. If you’re a leader, click Start this playbook; the starting rate is recorded.
Work each step with Go →. Some steps tick themselves when Summit53 sees the work; press Done on the rest.
When the last step is done, the run shows Measuring and the date it ends.

If no playbook fits your constraint yet, there’s no Fix this button: use the SUGGESTED MOVE in the Stage Inspector and track it (step 3). See Fix playbooks.

3. Check it: did our advice work?

Under the canvas, the Did our advice work? band shows how many tracked actions worked, didn’t change, or are still being watched.
Click View all N outcomes →. Your run appears as Fix playbook: <title> with its progress, and its result once the window ends.
Read the result as what changed after: Improved, Didn’t improve or Not enough data yet.
Go back to step 1. The first constraint may have moved.

See Signals & the Loop for how results are judged.

From Claude or Codex

With the Summit53 connector (or the Summit53 plugin, which includes it), you can ask the same three questions in plain language. The answers come from the same data as the app.

Find: Show me my revenue engine — where’s the first constraint?The answer names the same first constraint as the app, its evidence and likely causes, and, separately, the first coaching layer to work on for your highest-priority rep. In Claude Desktop it can appear as the Figure-Eight. It’s for leaders with team-metrics access: managers, CROs, VPs of Sales, Sales Managers and workspace admins.
Fix: Is our Fix playbook working? Which step are we on? You get the suggested playbook, any open or recently finished runs, their steps and outcome. Starting a run or moving a step stays in the app.
Check: Did our advice work this quarter? You get worked, didn’t change, still watching and can’t-judge counts, with the rate worked out only from actions that could be judged.

These answers only read your data. If you’re not sure what to ask, start with What can Summit53 do? See Summit53 skills for Claude and Codex and the MCP setup guide.

When the data is thin

Not enough data yet. Until a stage has enough volume, nothing is named as the constraint, in the app or in Claude. That’s the honest answer, not an error.
Nothing constraining. Nothing is constraining the engine right now. is a real result: there’s enough data and no stage is at risk or critical.
Whose view. Everyone with an organisation-wide view sees the same first constraint. The Account Executive persona has none, and in Claude the diagnosis needs team-metrics access; without it you get Revenue Loop diagnosis is available to leaders with team-metrics access.
Likely, not proven. Likely causes are consistent with the stage failing. Results say what changed after a fix, not that the fix caused it.
Can’t judge isn’t failure. Closed deals, missing readings and thin samples stay in Watching and are left out of the worked rate.

Do it this week

Find: write your stages in a row, the rate between each pair, and the rate it should be. Circle the earliest one that’s badly below.
Fix: write three steps for it (look, change the cause, act), an owner for each, today’s rate and the date you’ll judge it.
Check: on that date, write one line: “After the fix, the rate went from X to Y.” If you can’t tell, write that.
Bring the sheet to next week’s review and start from step 1 again.

Troubleshooting

There’s no first constraint. Either there isn’t enough data yet, nothing is at risk, or you’re on the Account Executive persona. Diagnostics says which.
There’s no Fix this button. No playbook matches this constraint yet. Use the Stage Inspector’s suggested move and track it.
I can’t start the playbook. Starting needs a leader role, or workspace owner or admin access.
Claude says the diagnosis is for leaders. It needs team-metrics access. Ask your workspace admin about your role.
The run has no result yet. Results arrive after its measurement window ends.

Where is the engine stuck? Find it, fix it, check it