PlayStudio CXO dashboard PlayStudio Roadmap Inbox PlayStudio Spotted — bottom-up signal channel
PlayStudio Strategic-Move Engine

The strategic-move engine
for CXOs who lead, not just brief.

PlayStudio decomposes strategic initiatives into Plays — human + agent steps that run end-to-end across Microsoft 365, Teams, email and XI. Outcomes loop back into governance. Strategy doesn't drift; it ships.

Built for CFOs, COOs, CROs accountable for outcomes

See how it fits the loop ↓ Book a Discovery →
Open it once a day · The CXO Dashboard

Built around how a CXO actually works.

"The One Thing" — your single most important item right now. "Two Things That Can Wait" — what's next-up. Pending decisions queue routed to you. KPI deltas. Team activity. Xami co-pilot rail.

No more "open the dashboard, see seventeen panels, close it." The CXO opens this once a day and knows what to do in 30 seconds.

The anti-pattern of every other CXO dashboard
playstudio.xamun.ai/workspace/dashboard
PlayStudio CXO Dashboard showing the One Thing, Two Things That Can Wait, pending decisions queue, KPI deltas, and Xami co-pilot rail
playstudio.xamun.ai/workspace/inbox
PlayStudio Roadmap Inbox showing committed initiatives from XI with New / Planning / Active / Recurring tabs and Plan It / Defer / Reject actions
Top-Down Intake · Roadmap Inbox

Initiatives committed in XI arrive here.

When the CEO commits an initiative in XI, it lands in the relevant workspace's Roadmap Inbox. The CXO triages each one — Plan it · Defer · Reject. No initiative gets lost in someone's calendar.

Four tabs separate New, Planning (in discovery), Active (running plays), and Recurring (BAU). Recurring work — monthly close, weekly pipeline, vendor reviews — is first-class, not an afterthought.

From strategy to execution, traced
Execution Surface · Plays

Strategic moves, decomposed and run.

Each Play has a sequence of steps — some human, some agent — running in order. Live state per step. Comments and evidence threaded inline. Agent run history available on every step for audit.

When conditions change, operators replan mid-flight. The system re-decomposes from the current step instead of restarting. Plays bend without breaking.

Filter the index by status, domain, or assignee. Domain-scoped — finance operators see only finance plays; the CFO sees all of finance; the CEO sees everything.

No Play without a KR it's trying to move
playstudio.xamun.ai/workspace/plays
PlayStudio Plays index showing active plays with status filters, domain scoping, mixed human and agent steps, and per-play KR linkage
playstudio.xamun.ai/workspace/plays/new
PlayStudio Play Planner graph view showing 12 steps as nodes, dependencies as edges, columns as execution depth and rows as swimlanes; right panel shows pattern-library match with 4 priors hitting margin target, risks Xami surfaced, and agent coverage per step
Composition Surface · Plan a Play

Show your work. Before you commit a play.

The planner is a graph — nodes are steps, edges are dependencies, columns are execution depth, rows are swimlanes. Decisions, comms, waits and tasks are first-class node types. Every step has an owner, a window, and an execution mode: human, agent-with-review, or autonomous.

Before you launch, the planner shows three things you can't get from a project tracker:

  • Pattern-library match — "4 priors, 3 hit margin target within 10%" — the structural ancestry of this move.
  • Risks Xami surfaced — SLAs on critical path, partner push-back, missing agent bindings — before you launch, not after you slip.
  • Agent coverage — which Hands agent will run which step. Missing one? Bind it inline.
Plays bend without breaking — re-plan from current step, not from zero
playstudio.xamun.ai/workspace/spotted
PlayStudio Spotted surface showing operator-submitted signals with Xami classification into Attach / New Work / Signal dispositions with rationale
Bottom-Up Intake · Spotted

What only the people closest to the work can see.

Operators submit risks, opportunities, client requests, anomalies. Xami classifies and routes each Spot into one of three honest dispositions:

  • Attach — evidence on an existing live Play (a step comment, threaded)
  • New work — triggers a new Play or decision card to the right approver
  • Signal — filed as intelligence; XI's next analysis cycle uses it

External partners and customers can also file Spots via token-protected forms. Bottom-up isn't limited to employees.

Every spot has a visible destination
Zero to first Play · Templates + Discovery

Ready templates. Or a Xami-led interview when nothing fits.

A growing catalogue of templates covers common strategic moves across Distribution, Healthcare, Professional Services and more. Pick a template, configure it, run it.

When no template matches the move, Xami runs a Discovery interview — voice-guided, structured — and outputs a custom Play composed from first principles. Every Discovery output becomes a candidate template for the next customer.

First Play running in minutes, not weeks
playstudio.xamun.ai/workspace/templates
PlayStudio Templates Catalog showing ready Play templates organised by domain and trade with one-click instantiation
Agent Fabric · Hands

60+ agents shipped. Install, fork, or build your own.

Hands is the operational agent layer of PlayStudio. Real workers across every CXO domain — each with a versioned personality, an accountable owner, an eval pass-rate, and an operational status. The full agent lifecycle lives in one place.

playstudio.xamun.ai/workspace/hands/library
Hands Library showing 61 production agents across Sales, Marketing, Operations, Finance, Strategy, HR, Legal and General with install and fork & customise actions
1 · Library — discover & install

A growing catalogue across Sales, Marketing, Ops, Finance, Strategy, HR, Legal and General. Public Library, Company Library, My Hands. Filter by domain and industry. Install with one click, or fork & customise to your workspace.

playstudio.xamun.ai/workspace/hands/builder
Hands Builder showing the 8-step agent build flow — Identity, Personality, Tools & Skills, Input Schema, Output Schema, Runtime Config, Evals, Governance — with an Eval gate before publish
2 · Builder — versioned, evaluated, governed

Build a new agent across eight surfaces — identity, personality, tools & skills, input/output schemas, runtime config, evals and governance. An Eval gate blocks publish until the agent passes the eval set. No mystery automation reaches production.

Where agents act: Hands agents act on the surfaces operators already use — Microsoft 365, Teams, email and a co-working desktop. Not on a separate "agent dashboard." Production runs feed calibration data back. New runs are gated by personality version and policy. Every agent step in a Play has an audit trail.

Two named classes across the platform: Xami is XI's strategic co-pilot — Discovery interviews, risk surfacing, outcome narration. Hands is PlayStudio's operational fleet — the agents that actually run steps inside a Play.

Outcome Capture · Outcomes

Every Play threads back to strategy.

When a Play finishes, the system captures what actually changed: KR movement, qualitative result, time-to-completion, what surprised us. No spreadsheet round-trip. No "let me put together a deck."

Captured outcomes flow into XI's governance. KRs update. If the metric slipped, the CxO Inbox surfaces it. If the metric overshot, the system recalibrates its scoring for similar future moves.

A project tracker tells you "task done."
PlayStudio tells you "metric moved."

playstudio.xamun.ai/workspace/outcomes
PlayStudio Outcomes view showing per-Play KR movement, time-to-completion, qualitative summary, and the link back into XI governance
playstudio.xamun.ai/workspace/operator
PlayStudio My Tasks personal queue showing the operator's assigned steps and pending decisions across all running plays
Operator Surface · My Tasks

PlayStudio is built for operators too.

Each operator gets a personal queue scoped to assigned steps and decisions across all running plays. No hunting through a dozen plays to find what needs you next.

Domain enforcement is a first-class control — operators see only their domain (e.g. finance operators see finance plays); the CFO sees all of finance; the CEO sees everything.

A Daily Brief surface is today-shaped — the most useful 8-second read of what changed since yesterday.

Domain-scoped: see what's yours
In the Xamun Loop

XI commits the roadmap. PlayStudio runs it. Outcomes return.

Strategy
Roadmap
PlayStudio
Outcomes
Restrategy

PlayStudio sits at the execution corner of the loop. It picks up where XI's Roadmap commits leave off and runs the work — then hands measured outcomes back to XI's governance. See the full loop on the Platform page →

Who It's For

Built for CXOs who lead, not just brief.

CXO-as-tenant workspaces. Each leader gets their own surface; cross-CXO Plays are first-class.

CEO

Quarterly strategy refresh as a Play. Cross-functional moves that touch every domain. CEO Inbox of pending decisions.

CFO

Month-end close as a recurring Play. Finance ops automation. Vendor review cadences. Annual planning workflows.

CRO

Pipeline ops as orchestrated Plays. Account-based moves with mixed human + agent steps. Quarterly territory reviews.

COO

Service delivery, supplier management, internal-process rollouts. Operational change as a tracked Play, not a hope.

See PlayStudio on your business.

A workshop walks through one of your real strategic moves — decomposed into a Play, run end-to-end, outcome captured.

Book a workshop → See the full platform →