Overview

Revenue signals are Summit53’s ranked read of what is helping or hurting your revenue engine: a deal with weak qualification, an account whose renewal looks shaky, a lead source that is running below benchmark. Every signal carries a severity, a confidence and, where available, the evidence behind it. The Loop then closes the circle: when you start tracking a signal, Summit53 records where things stand and later reports whether the metric moved.

On the Revenue Engine home screen (/ or /revenue-engine) you meet signals in four places:

The canvas, where stage rings show where the pressure is.
The Stage Inspector, where the REVENUE SIGNAL section explains a stage’s top signal and lets you start tracking it.
The DID OUR ADVICE WORK? band below the canvas, and the Intervention ledger it opens.
WHY DID CONFIDENCE MOVE? inside the Forecast gap diagnosis panel.

Quick start

Open the Revenue Engine home screen and look at the canvas for the stage with the pulsing halo.
Click that stage. Under REVENUE SIGNAL in the Stage Inspector, read the headline, its confidence dots and the WHY line.
Read WHAT TO DO. If you are going to act on it, click Start tracking this.
Scroll to N MORE SIGNALS ON THIS STAGE and click tap → on a row to see its evidence, track it or open the record.
Return to the DID OUR ADVICE WORK? band below the canvas and click View all N outcomes → to review what has worked so far.

Signal rings on the canvas

Both canvas layouts, LINEAR (the Bowtie) and CURRENTS (the figure eight), mark stages with signal states. The canvas deliberately stays calm: one stage pulses, and the full list of signals lives in the Stage Inspector.

Pulsing halo — the single top constraint: the stage carrying the most severe negative signal. The halo is orange in Linear and red in Currents.
Solid red or amber ring — another stage with a critical (red) or high-severity (amber) signal, so a second serious stage is never mistaken for a minor one.
Soft green pulse — a stage that is recovering, such as accounts whose health has been improving. Green appears only once Summit53 has enough signal history to see the improvement.
Dashed, faded ring — a stage with lower-priority or still-building signals.
Plain ring — no signal on that stage.

There is no legend for these states on the canvas itself, so keep this list to hand. When nothing negative stands out, no stage pulses; that is an honest calm reading, not a fault. For the canvas layouts and stages themselves, see The Revenue Flow Canvas.

REVENUE SIGNAL in the Stage Inspector

Click a stage on the canvas to open it in the Stage Inspector, below the canvas. It opens on Pipeline by default. When the stage’s top record is a deal, account or lead with a ranked signal, a REVENUE SIGNAL section appears beneath the stage detail. It reads reading signals… while it loads. If the record has no ranked signal, the section does not appear and the stage detail stands alone.

The headline signal

Severity dot and headline — for example Weak qualification for a late-stage deal. The dot’s colour gives severity: red for critical, orange for high, amber for medium, teal for low and grey for informational. A green dot means the signal is improving and a grey one that it is neutral. The more severe the signal, the larger the glow around the dot.
Confidence dots — four dots plus a score from 0 to 1, for example ●●●○ 0.77. More filled dots mean more confidence; sparse or stale data lowers the score. Hover the dots to see the exact confidence.
Framing line — how the signal earned its place, in one of three forms:
- Among the top N% of your at-risk pipeline, by size and certainty. for signals ranked against the rest of your pipeline, such as deal and forecast signals. It appears only when the signal is in the top half.
- N points below where this should be. or Running below benchmark. for lead and source signals, which are measured against a benchmark in points, never in money.
- Based on data quality. for data-quality signals.
WHY — the evidence, for example Stage Negotiation, MEDDPIC score 0.38; $1,642,351.
WHAT TO DO — the recommended action.

The 0.35 building floor

A signal with confidence below 0.35 is a building signal: Summit53 has noticed something but does not yet have enough data to call it. Building signals are never shown as errors or zeros. Their dots read ○○○○ building, the hover text reads building signal — below 0.35 confidence floor, and they are listed under STILL BUILDING with a dashed outline and building….

Start tracking this

Click Start tracking this beneath the headline signal. The note reads We’ll record where things stand today and tell you if it moves.
The button shows Starting… while Summit53 records today’s value as the baseline.
A green confirmation replaces it: Now tracking followed by the metric being watched (for example win probability), then — we’ll tell you if it moves.
Click see the Loop → in the confirmation to scroll to the DID OUR ADVICE WORK? band.

If the request fails, the button stays in place so you can try again.

Other signals on the same record

Below the tracking button, further signals on the same record appear as rows, each with a severity dot, a headline and confidence dots. Where a row shows tap →, click it to show its WHY line, and tap ↑ to hide it again. Building signals follow under STILL BUILDING.

N MORE SIGNALS ON THIS STAGE

Below the REVENUE SIGNAL section, N MORE SIGNALS ON THIS STAGE lists every other signal on the stage, most severe first, leaving out the record already shown above. Each row shows a severity dot, the signal and the record name. Building signals appear faded.

Click tap → on a row to expand it.
For deals, accounts and leads, the row loads the evidence (reading evidence…) and shows its WHY line, or No detailed evidence recorded for this signal.
Click Start tracking ↗ to track the signal. It shows Starting… and then Now tracking. Organisation-level signals, such as a lead source or the forecast, can be tracked from here too.
Click View followed by the record type (for example View opportunity ↗) to open the deal, account or lead.

Rows without tap → cannot be expanded. If tracking is refused, the row shows Leader-only for org-level signals.; any other failure shows Couldn’t start tracking — try again.

Who can see and track what

In this section, leaders means anyone whose role is not Individual Contributor (Chief Revenue Officer, VP of Sales, Sales Manager, RevOps Leader, Customer Success Leader, Sales Enablement Leader or GTM Owner), plus organisation owners and admins. Everyone else is treated as a rep.

Canvas and stage signals: leaders see signals across the organisation. Reps see signals on the records they own plus organisation-level signals. Some persona views narrow this further to the signals relevant to that role.
Account and lead signal detail: only leaders and the record’s owner. Otherwise the REVENUE SIGNAL section does not appear for that record.
Tracking a record’s signal: the record’s owner, or any leader.
Tracking an organisation-level signal (a lead source, the forecast or the organisation as a whole): leaders only.
The Loop band and the Intervention ledger: leaders see every tracked action in the organisation. Reps see only the actions they own.

DID OUR ADVICE WORK?

The Loop band runs the full width of the page, directly below the canvas. It reads Loop · loading… briefly, then shows one of two states. It does not appear at all until at least one action is being tracked in your view.

Cold start

Until at least one tracked action has an outcome, the band shows a count with WATCHING, Summit53 recommended N actions, and Watching what changes after each one — results land once the check-in window is up.

With outcomes

Once outcomes arrive, the band shows the rate, for example 60% WORKED, with Summit53 recommended 12 actions, tallies for WORKED, NO CHANGE and (when any remain) WATCHING, and a bar showing the split.

Either way, a footer reads Based on what changed after each action — an association, not proof of cause. Actions we can’t yet judge never count against the score. Click View all N outcomes → to open the Intervention ledger. That count is the number of rows in the ledger, which list each record-and-signal pair once, so it can be lower than the number of recommended actions.

The band loads when the page opens. An action you have just started tracking appears after you reload the page.

The Intervention ledger

The ledger opens over the page, headed THE LOOP · INTERVENTION LEDGER and Did our advice work?. The header repeats the rate and the worked, no change and watching counts for every tracked action, with a bar and the line Based on what changed after each action — an association, not proof of cause. The X% is worked ÷ (worked + no change); the N still watching don’t count against it until their window is up. Before any action has an outcome, the header rate reads 0% worked; read it alongside the watching count.

How the rate is calculated

The rate is worked ÷ (worked + no change). Actions still being watched, and actions whose outcome could not be judged, are left out, so they never count against the score. The result is correlational: the metric moved after you acted, and Summit53 does not claim the action caused it.

Search and filters

Search entity or advice… — matches the record name or the advice text.
OUTCOME chips — ALL, WORKED, NO CHANGE and WATCHING, each with a count.
TYPE chips — ALL, ACCOUNTS, DEALS, LEADS and SOURCES, each with a count. Forecast and organisation rows appear under ALL only.
Showing X of Y tells you how many rows match.

The chip counts are counts of table rows. The header counts cover every tracked action in your view, so the two can differ — for example when the same signal on the same record has been tracked more than once.

Columns

ENTITY — the record name and its type (Deal, Account, Lead, Source, Forecast or Org).
WE ADVISED — the recommended action.
MOVEMENT — the metric being tracked, its starting value → its value after the window, and the change, or WATCHING while there is no outcome. A bar shows the current value, with a tick at the starting value.
OUTCOME — a pill reading WORKED, DIDN’T IMPROVE or WATCHING. The NO CHANGE chip filters to the Didn’t improve rows.
WHEN — for example acted 12 days ago, or while watching acted 3d ago · 27d to call it, followed by open → or org-level.

Click ENTITY, MOVEMENT, OUTCOME or WHEN to sort, and click again to reverse; the table starts with the most recent first. Click a deal, account or lead row (marked open →) to open that record. Rows marked org-level have no record to open. If nothing matches, the ledger shows No interventions match these filters with a Clear filters link.

The footer reads Correlational — the metric moved after we acted; we don’t claim we caused it. and Click any row to open the entity →. Close the ledger with ×, the Esc key, or by clicking outside it.

How outcomes are judged

When an action’s check-in window is up, Summit53 compares the tracked metric with its starting value. A clear rise counts as worked, as does a negative signal that has cleared while the metric held steady. A fall or no meaningful change counts as no change. If Summit53 cannot tell, for example because there is no comparable reading, the action stays in Watching and does not count either way.

Why tracked actions stay in Watching

The check-in window, 30 days by default, starts when an action is marked as done. Signals you track with Start tracking are recorded without a done date, and there is currently no button in the app to mark them done. Until one is set, they stay in WATCHING, and the WHEN column reads acted —d ago · measuring. After 90 days open, they are closed as unknown: they remain in Watching and never count against the score.

WHY DID CONFIDENCE MOVE?

At the foot of the Forecast gap diagnosis panel (in the right-hand column beside the Stage Inspector, or further down the page on a phone), a section explains how much forecast confidence has moved compared with an earlier recorded reading, and what drove it.

The headline shows the move in points, for example −1.3 pts, in green when confidence rose and red when it fell.
Five drivers follow: Pipeline shape, Execution health, Data quality, Account & renewal and Forecast accuracy. Each measured driver shows its points and a bar running right (improving, green) or left (worsening, red) from the centre.
A driver Summit53 cannot measure yet reads building… with a dashed bar, rather than zero.
The footer reads Each driver’s share adds up to the total move. Drivers we can’t measure yet are shown as still building.

It reads reading decomposition… while loading, and does not appear when there is no recorded history to compare.

Signals on My Engine

My Engine shows owner-only signal states: its canvas overlays only the records you own, and rows in MY STAGE INSPECTOR carry a severity dot and, where there is one, the record’s top signal and its severity. My Engine has no Loop band. See My Engine.

Troubleshooting

No stage is pulsing. No negative signal currently stands out in your view. The calm canvas is an honest reading, not an error.
The REVENUE SIGNAL section is missing. The stage’s top record has no ranked signal, or it is an account or lead you neither own nor lead. The N MORE SIGNALS ON THIS STAGE list may still show other signals.
“Leader-only for org-level signals.” Tracking was refused. Organisation-level signals can be tracked by leaders only, and a record’s signal by its owner or a leader. Ask a leader to start tracking it.
The DID OUR ADVICE WORK? band is missing. Nothing is being tracked in your view yet, or the band could not load. Start tracking a signal and reload the page.
A signal I just tracked is not in the ledger. Reload the page; the band and ledger load when the page opens.
A row says “acted —d ago · measuring”. The action has no done date, so its check-in window has not started. See “Why tracked actions stay in Watching” above.
The band’s counts differ from the ledger’s chips. The band and ledger header count every tracked action; the chips and View all N outcomes count ledger rows, which list each record-and-signal pair once.
WHY DID CONFIDENCE MOVE? is missing. There is not yet enough recorded forecast history to compare.

Revenue Signals & the Loop: Did Our Advice Work?