ai.com
Product strategy

The Command Center
for ai.com

The simplest possible surface over the most powerful possible engine.

Jeet ZandawalaStrategy & working prototypeJune 2026
The tension

The capability is here.
The surface isn't.

Our agents can run an almost unlimited diversity of workflows. That's the strength — and the trap. If every workflow earns its own buttons, panels and screens, the product collapses under its own optionality. We can't win by adding surface area. We win by removing it.

What scales
∞ workflows
What must not
the UI
The job
one surface
The principle

One next action
per screen.

Not a menu of things you could do. The single thing that needs your judgment, right now. Everything else runs underneath and stays out of the way until it's ready for you.

The one idea

Every workflow becomes a Routine

A named, repeatable play. It runs on a trigger, pauses at a gate when it needs you, and leaves a receipt of what it did. The same shape wraps a metrics review, a competitor watch, or a feature ship — so the UI never has to grow to fit them.

Trigger
It starts itself
A schedule, a threshold, an event. Or you run it from chat.
Runs
It does the work
Reads and drafts with the narrowest access that works.
Gate · needs you
It stops for judgment
Nothing leaves or changes until you approve.
Receipt
It shows its work
Logged to Activity — every step, every source, undoable.

The gate is where judgment lives. Everything to the left of it is automatic; everything to the right is trust.

The vocabulary

Four words, one of them on screen

You see
Today
The single focus that needs your judgment. The whole product, most days.
foreground
The play
Routines — running as Watches
Named, gated workflows. Set to watch, they run in the background and earn the right to interrupt you.
gated
Underneath
Skills + Connections
Invisible capability packs and the sources a routine may touch. Users never manage these directly.
invisible

A Skill is an invisible capability pack; a Routine is the named, gated play it powers; a Watch is a routine left running; Today is the one thing it surfaces.

The home

Today shows you one thing

Not this

A wall of everything the agent could do. Optionality the user has to triage.

This
Needs you · from your Activation watch
Activation is down 12%, entirely in new-team signups, since Friday's onboarding change.
No one has flagged it. The agent investigated, correlated it to the release, and drafted the fix.
Review the fixWhat the agent did · 4 steps

When nothing needs you, it says so. Your agent is watching.

The product, end to end

Five surfaces, one model

Today is where you live. The other four exist so Today can stay a single decision. Playbook is yours to shape — Watches run quietly; Explore is the conversation where your agent suggests and re-ranks, and you correct it. Activity is the proof — the canonical log of what each routine did and why it earned your attention.

What we built

A working prototype, not slideware

ACompetitive watch
Needs you
Acme, Northwind and Vela all asked for granular admin roles this week.
Highest revenue behind it — none of it is on the roadmap.
Researched the move · read-only
Drafted the battlecard · every claim sourced
Write 3 roadmap changes to Jira
Nothing changes in Jira until you approve.Approve & write
  • The real ai.com design system and org rail — same tokens, same chrome
  • First-run setup that assembles your Watches from what you already do
  • Playbook with live Watches, an Explore tuning loop and a Now / Next / Later board
  • Activity receipt log — every run, sourced and undoable
  • Describe a routine → your agent proposes steps, scopes and the gate
  • Seeded with real cases: activation drop, feedback themes, competitive watch
Why this wins

One bet, three payoffs

01
Infinite workflows, fixed UI
Every new capability is another Routine, not another screen. The surface stays simple as the engine grows without limit.
02
Safe by default
The gate makes the product trustworthy enough for regulated, high-consequence work — where the real revenue and the real moat are.
03
Built for the other 90%
No prompts to master, no blank page. The product proposes the next move; the person keeps the judgment. That's how this reaches everyone.
The one open decision

Where does the user land?

The bet I made
Today — a single daily focus
The home is the one thing that needs you, fed by Watches running underneath. Chat lives inside it as a venue.
Truest to one next action per screen
The alternative
Chat as the literal front door
Conversation is the home; routines and focus surface within the thread. Closer to where the category is converging.

Next: pressure-test the home model, wire the gate behind the existing approval flow, and ship the first three routines — metrics review, competitive watch, feature ship — to a small internal cohort. The prototype is ready to click through today.

ai.com · Command Center
01 / 10
← → to move