2.4 Operational AI agents are live

Operational control
without the chaos.

Rapidesk unifies projects, tasks, knowledge and operations into one calm workspace — purpose-built for teams that have outgrown messy tools.

Status — All systems operational SOC 2 · Type II EU-West & US-East
Operations · Q3 plan ×
Blueprints
rapidesk.app / nova-collective / operations
Operations › Q3 Plan
⌘K
+
Q3 Operational Plan
Cross-functional rollout · 14 workstreams · Owner Naomi K.
In flight
48
+6 this week
Completed
312
+24
Blockers
3
+1
Cycle time
4.2d
−0.3
Workstream
Status
Owners
Progress
Atlas — auth refactor
In progress
72%
Partner ops handbook v3
Review
91%
Migration playbook — EMEA
Planning
34%
Customer ops dashboards
Backlog
8%
Scroll
02 · The platform

Five surfaces. One operating system for your business.

Most teams stitch projects, docs, workflows and admin together with tape. Rapidesk treats them as one operational fabric — designed for organisations that need real structure, not more tabs.

Projects, tasks, workspaces, knowledge and operational controls live in the same model. You build once; the structure follows your teams everywhere.

/ 01
Projects & Tasks
Bi-directional structure — every task belongs to a project, a workspace, and a blueprint.
/ 02
Workspaces
Tenant-aware surfaces with their own data, permissions and AI context.
/ 03
Knowledge — The Vault
Versioned, searchable, addressable. Every doc has a permanent operational anchor.
/ 04
Operational controls
Admin, audit, permissions, automations and analytics — first-class, not bolted on.
↳ live project
Atlas — auth refactor
PRJ-042 · Q3
Doing2
ENG
Token rotation worker
Owen R. · today
OPS
Roll out per-tenant flags
Mira S. · 1d
Done9
QA
Audit existing flows
Mira S.
DOC
Sequence diagram v2
Naomi K.
14 tasks · 3 owners 72% complete
Throughput · 30d
38.4 /wk
Vault entries
1,284
+42 added this week · 12 awaiting review
03 · Architecture

Six core areas, designed to be lived in.

Each surface is a first-class part of the platform — not a sidebar plugin. They share data, permissions and AI context, but stay purpose-built for what you do there.

/ 01 — VAULT

The Vault

Versioned operational knowledge. Every document has an address, owner, and policy.

VLT-104 · Onboarding handbookv3.2
VLT-091 · Partner SLAv1.4
VLT-082 · Incident playbookdraft
VLT-075 · Hiring rubricv2.1
/ 02 — HOME BASE

Home Base

The operational front page for every person — assignments, briefs, and what changed overnight.

3 assignments due today⌘1
2 briefs from Rapidesknew
Atlas migration · 72%live
4 follow-ups parkedlater
/ 03 — BLUEPRINTS

Blueprints

Reusable operational templates. Spin up new programmes from your own institutional patterns.

Customer onboarding · 12 stepsused 38×
Incident responseused 14×
Quarterly planningused 4×
Partner kick-offdraft
/ 04 — WORKSPACES

Workspaces

Tenant-aware surfaces with their own data, permissions, branding and AI context.

Nova Collective42 members
Atlas Studio14 members
Tributary Partnersguests
Project Lumenprivate
/ 05 — COMMAND HUB

Command Hub

One palette. Create anything, navigate anywhere, route work through your business logic.

New project from blueprint⌘N
Ask AI brief⌘'
Route to workspace⌘⇧R
Search the Vault⌘F
/ 06 — ADMIN

Admin

Permissions, audit, identity, billing, retention. Operational governance that scales with you.

3 role policies enforcedSOC 2
SCIM provisioningenabled
Audit log · 142k events30d
Backup verifiedtoday
04 · Difference

Why Rapidesk feels different.

Most operational tools start as document apps and grow tabs. Rapidesk was designed from the operational model down — so your structure becomes more useful as you scale, not noisier.

01 / Clarity

Operational clarity, not feature soup.

Every object has a place, an owner, and a policy. You always know where work lives and who carries it.

02 / Density

Calm density over empty whitespace.

Senior operators want to see what matters at a glance. Our surfaces are tuned for working speed, not first impressions.

03 / Structure

Scalable by design.

Workspaces, projects, blueprints and policies compose. The model gets sharper as your business gets larger.

04 / AI

AI inside the model.

Agents read your structure — projects, blueprints, permissions — so suggestions are operationally aware, not generic.

05 / Flow

Centralised creation.

One Command Hub creates anything, routes it through your business rules, and lands it where it belongs.

06 / Context

Workspace-aware everywhere.

Permissions, search, AI and notifications all respect tenant boundaries. No spillover. No surprises.

05 · Operational AI

AI agents that understand the way you actually work.

Rapidesk's agents are embedded in your operational model — they read your projects, blueprints, permissions and Vault, so the answers feel like a coworker, not a chatbot.

01

Operational, not generative

Agents reason over real work — workstreams, owners, SLAs — not just text.

02

Embedded in every surface

Press ⌘' anywhere. The agent inherits the surface's context, permissions and data scope.

03

Business-aware intelligence

Your blueprints, policies and history shape every suggestion. Less guessing, more leverage.

04

Specialised agents (Q4)

Ops, finance, HR and engineering surfaces will each ship a specialist agent built for their work.

Rapidesk · ⌘' scope · Operations / Q3 plan
You
Where are we on the Atlas migration, and what's blocking the EMEA rollout?
Rapidesk · Agent
Atlas refactor is at 72% — Owen finished the token rotation worker last night. EMEA migration is at 34%, blocked on the partner-ops handbook v3 (currently in review with Naomi). I can route the review to Mira if you want to unblock it.
Reassign review Draft status brief Open Atlas project
06 · Product

A closer look — across the surfaces you actually use.

Switch between the surfaces operators spend their day in. Every view is built around the same operational model.

My week

Mon — Fri · 14 tasks · 3 owners
Sequence diagram v2 Mon Naomi
Token rotation worker Tue Owen
Roll out per-tenant flags Wed Mira
Refresh-token spec Thu Naomi
Migration playbook · EMEA Thu Owen
Customer ops dashboards Fri Mira
Blueprint · BP-014 · Customer onboarding · v3.2 · used 38×

Customer onboarding handbook.

The Rapidesk blueprint for spinning up new customer accounts — from contract signature through go-live. Every step has an owner, a target duration, and an operational policy.

Operational anchor
This blueprint replaces 6 internal documents and 2 Notion spaces. Updates auto-propagate to every project created from it.

The onboarding sequence runs across four phases — discovery, configuration, migration and go-live. Each phase is its own project template, with permissions scoped to the customer's workspace.

Steps
12
Avg cycle
14d
Owners
3

Operations · Q3 dashboard

Last refresh · 02:14 UTC
In flight
48
+6
Completed
312
+24
Blueprints used
14
+2
Cycle · median
4.2d
−0.3
Throughput Blueprints applied

Operational knowledge

1,284 entries · 92% reviewed in 90d
Onboarding handbook · v3.2 Live Naomi
§ Partner SLA · v1.4 Live Owen
Incident response playbook Review Mira
Hiring rubric · v2.1 Live Naomi
Retention policy Draft Owen
07 · Roadmap

The next 12 months — operational, not aspirational.

Hover any pill for the brief. Dates are intentionally directional — we ship when the operational model is right, not before.

Q2 · Now
Q3 · Aug
Q4 · Nov
Q1 · Feb
AI Agents
Operational agent (live)
Specialised agents · ops / finance / HR
Automations
Trigger studio (beta)
Multi-step automations
Policy-driven workflows
Integrations
Slack, Drive, GitHub
Calendar & Email
Public API v2
Mobile
iOS Home Base (private)
iOS & Android · GA
Operations
Advanced permissions
Operational intelligence
Analytics studio
Workflows
Blueprint marketplace
Programmable views
08 · Early access

Run your business like it's one system, because it is.

Rapidesk is rolling out to operationally-mature teams through Q3. Reserve your workspace — we'll set you up within a week.

Rapidesk · 2026