The platform
One platform. Five questions. One source of operational truth.
Nebbos watches the work your organisation already does and turns it into foresight — predicting where things break, explaining why, and acting under your oversight. It all runs on one thing: the Operational Graph.
The mechanism
The Operational Graph.
Underneath every answer is a living map of how your organisation actually operates — who depends on whom, how work moves between teams, where it tends to stall. Nebbos builds it from the events your tools already emit, keeps it current as the work changes, and reasons over it.
It’s a temporal map — it holds not just how things stand today but how they got there. And it stores structured signal — patterns, thresholds, relationships — never the raw contents of your messages. That’s what makes its predictions specific to you, not generic.
teams, people, projects, commitments
dependencies, handoffs, ownership
velocity, capacity, thresholds
how all of it changes, tracked
End to end
The five questions, in order.
What's happening right now
Connectors read the events your tools already produce — tasks, messages, calendars, tickets, handoffs — and normalise them into one operational stream. Connect the stack you run; there's nothing new for teams to adopt.
What's about to go wrong
Deterministic detectors run continuously and cost nothing to watch. Only when one fires does Nebbos spend a model call to reason about it — so prediction is both cheap and sharp.
Why it's going wrong
A Pearl — one per department — works through the firing pattern against the graph and returns the cause in plain language with the evidence attached. Each prediction carries a confidence score and a "why" you can open.
What to do about it
Pearl proposes the next best action. Anything consequential pauses for a human checkpoint — autonomy is earned over time, bounded to what's been proven, and always reversible.
What you've learned
Every prediction, resolution and correction is written back to the Operational Graph. The system you run in month 24 has been shaped entirely around how your organisation works.
Deterministic first
Six checks run before any AI cost is incurred.
Deadline risk
Completion gap against capacity and a stalling velocity.
Capacity crunch
Overlapping deadline pressure across a dependency.
Velocity drop
A sharp week-on-week fall with deadlines still live.
Handoff stall
A cross-team handoff sitting past its threshold.
Absence signal
No activity where there should be, no leave on record.
Cascade risk
One team's commitment that a dependent team can't meet.
Because the deterministic detectors do the watching, model calls track the number of real problems — not the volume of events — so far less AI cost is incurred than a model-call-per-event approach.