Decision OS
Where your team's decisions get made — and remembered
PreviewA decision workspace for startups and companies: frame the call as a question, pin the evidence, let an analyst interrogate it — and make the judgment yourself, on the record.
Three ways good teams decide badly
Big calls happen in scattered chats
Market entry, budget shifts, key hires — argued across threads, docs, and someone’s head. No owner, no deadline, no single place where the decision actually lives.
What Decision OS does
Every consequential decision becomes one context: a question with an owner, a deadline, a status, and everything attached to it. The dashboard shows what must be decided soon, by whom.
Decisions ignore what just changed
A rate move, a regulation, a competitor’s earnings — the information existed, but nobody put it next to the decision it should have changed.
What Decision OS does
Pin evidence to the decision: Guidances coverage, scenarios, and earnings, plus your own links and numbers. The analyst frames why it matters, who is affected, and what to look at next.
Six months later, nobody remembers why
The rationale leaves with the person who had it. The same debate reruns; the same mistake repeats.
What Decision OS does
The Decision Log keeps what was decided, by whom, on which evidence — searchable by domain and status. Your team’s judgment becomes an asset that compounds.
One loop, five steps
Step 1
Frame it
State the decision as a question — strategy, marketing, finance, market response, or operations. Starter questions per domain get you moving.
Step 2
Pin the evidence
Articles, scenarios, earnings, external links, your own metrics. The pin is what you saw when you decided.
Step 3
Get questioned
The analyst answers why it matters, who is affected, what to look at next — then hands you the questions only you can answer. It never recommends.
Step 4
Bring the team
Share the context. Teammates read the framing and add their questions to the same list. Only the owner answers.
Step 5
Decide — and remember
You make the call. The log keeps the decision, the decider, and the evidence trail.
The AI here never decides
Every AI tool wants to answer for you. This one interrogates for you. For each decision it answers exactly three things — why it matters, who is affected, what to look at next — and then hands the decision back with the open questions only your team can answer: your constraints, your appetite for the downside, what you would regret. No buy/sell/hold, no best option, no confidence-scored picks. The judgment belongs to a named person on your team, in front of their team.
Built for teams, priced by seats
Decision OS ships with the Team and Enterprise plans. One subscription covers your whole team — invited members join on your seats, no accounts of their own to pay for.
Why you can trust what gets pinned
Decision OS sits on the Guidances intelligence pipeline — articles, Market Lens, Scenario Tree, WorldPulse and Earningbird — where every cross-pipeline step is human-gated; nothing bridges layers automatically.
Evidence with provenance
Guidances evidence traces back through published, human-gated pipelines: articles pass editorial review, market links need two-step approval, scenarios pass human gates.
No admin bypass
Decision contexts are owner-and-team data. Nobody else — including Guidances admins — can read them. Enforced in the database, pinned by tests.
Verdicts are rejected in code
“You should choose A” is a hard contract violation, not a style preference. The analyst’s output is machine-checked before it reaches you.
Honest degradation
When a feed degrades to sample data, the UI says so instead of pretending. What you see labeled live is live.