Where your governed apps actually run.
Departments mirror the revenue stack your team already runs. Tabs follow each function’s workflow. And autonomy isn’t a mode you switch into — it’s a property of each capability, set one at a time.
One place to run the whole revenue stack.
Pick a department to see its capabilities. Each one carries its own autonomy state — supervised or autonomous — and where it supports both, you flip it right here.
- ProspectDraft outreach for a new leadSupervised
- QualifyScore & route inboundAutonomous
- CloseFlag at-risk dealsSupervised—
new capability? import a skill file — not a release.
Not a mode. A property of each capability.
A capability marked supervised drafts and proposes; a person approves before anything reaches a customer. The badge tells everyone exactly where the human still stands in the loop.
A capability promoted to autonomous runs on its own inside its guardrails and logs every run. The two-accent system makes the difference legible at a glance — teal stays supervised, amber runs.
Because autonomy lives on the capability — not the navigation — two reps can run the same workspace with a different trust posture on the very same job. The buyer keeps judgment exactly where they want it.
Add functionality by import, not release.
Every capability is defined by a portable skill file. New functionality arrives the way a document does — you import it — not the way software usually does, gated behind a vendor’s release cycle.
That keeps the workspace yours to extend, and keeps the judgment a capability carries portable inside your organization — an asset you hold, move, and reuse on your own terms.
- jobqualify inbound lead
- data scopeleads, accounts (read)
- metricmeeting booked
- autonomysupervised
import → governed, gated, ready to run