Will we hit the number?
One honest answer, updated continuously.
Orbytal scores six pillars of revenue risk against your live data, watches 23 (and growing) named scenarios inside them, and turns every deviation into a diagnosis with a costed fix. This page shows you how, using the same surfaces you'd see in the product.
One score. One gap, with every dollar accounted for.
Revenue Health blends the six pillar scores into a single read, with the forecast gap in dollars beside it. Every number decomposes into the risks beneath it, so nothing on this screen is free-floating.
Q3 is tracking $5.2M short of the $50M plan. $9.2M is identified and ledgered across the pillars. The biggest driver is coverage erosion from a capacity gap, and the top fix recovers +$1.4M.
The forecast a deal rollup can't produce
Orbytal's forecast is partitioned, never a second number beside the plan: what's booked, what today's weighted pipeline should produce, and what has to come from pipeline that doesn't exist yet. At 180 days out, most of what will close hasn't been created, so Orbytal models the conditions that create it. The unfilled remainder is the gap, and it decomposes across the six pillars, each piece carrying a named driver, the dollars at risk, and a fix. When the plan is short, the platform also names the smallest set of in-window deals whose sum covers the gap.
Booked is certain. The near band is anchored to today's deals. The far band is modeled from the physics that create pipeline: coverage, capacity, ramp, and conversion. Whatever none of them fill is the gap, priced in dollars and traced to its pillar.
A scenario is a diagnosis, not a dashboard tile
When a scenario fires, you don't get a chart to interpret. You get the cause, the cost, the owner, the window to act, and ranked fixes. Here is the full anatomy of one.
DACH AE coverage fell from 2.1× to 1.4× as three opportunities slipped past Q3 while ramping reps under-produced.
Every scenario has a name a CRO can repeat in a board meeting. When the cause lives in another pillar, the card says so and links there.
Impact is the revenue at risk to the plan, computed from your data and reconciled into one ledger. The same dollar is never counted twice.
The signal that fired the scenario, charted against its target, with the plain-language cause underneath.
What happens if nobody acts, and by when. Risk with a deadline gets handled; risk without one gets a meeting.
A person, not a team, and the time you have to act while the fix is still cheap.
Each path shows what it recovers. Apply the top fix, or take it into the sandbox and build your own version around it.
Apply the fix, or argue with it first
Recommendations in most tools are accept-or-dismiss. Orbytal gives every fix two doors, because a revenue leader should be able to weigh options, not just approve them.
One click stages the change through a lifecycle: proposed, reviewed, deployed. Nothing silently mutates your live plan, and every change is versioned so you can see what was done, by whom, and roll it back.
Take the recommendation as a starting point and adjust the variables around it: different accounts, different reqs, a different quota split. Your version lives in a sandbox with a running tally of its impact, never touching the live plan until you commit.
Ranked by recovered revenue, tracked to outcome
Every recommendation across all six pillars lands in one queue, each tied to its root cause. Apply it, assign it, decline it, or build a scenario from it.
Honest math is the product
A revenue platform earns trust with numbers you can inspect and honesty about what it knows so far.
Revenue Health, the pillar scores, and the scenario impacts are one calculation at three resolutions. Any number you see breaks down into the parts beneath it, and the parts always reconcile to the headline.
Structural findings are confirmed from your plan and current state on day one. Behavioral patterns start labeled “learning your data” and sharpen as your history accrues. Precision is earned, never faked.
When your data can't support a scenario yet, Orbytal says so and tells you exactly what to populate to unlock it. A locked scenario reads “unlock me,” never a number pretending to be real.
The account, deal, and people registries show where each field comes from: the system that syncs it, or the mark that Orbytal computed it. When a number surprises you, you can see its provenance instead of arguing about it.
Every pillar has a real data source
Connect your CRM and a plan target, and the first diagnosis runs the same day. Each additional connection unlocks more scenarios.
See your own diagnosis
Find the gap in your planNot ready for a demo? Score your plan in 5 minutes →