Agency ops
Multi-client ops without tool soup
Agency ops break when every client is a different folder stack and status lives in chat. Onnie is multi-client operations on shared spines — not a fourth “agency” persona page.
// who it's for
// friction
Tool soup doesn’t scale handoffs
Each account reinvents status. Account leads re-explain context. The studio record stays empty.
// on onnie
Ops as shared Projects and trackers
Client Projects on Work. Ops Tables for capacity and status. Canvases for shared boards. Routines for reporting. Connectors and agents for handoffs in tools you already use.
This is an ops use case — never a Users “agency” room.
// workflow on the os
How studio ops actually moves
Click each step. Multi-client Projects + ops Tables — boards and Friday report share one OS.
// a week in studio ops
Residue, not theater
Ops Table open. At-risk accounts surface on Canvas board.
Tables · CanvasLeads work inside client Projects — same spine DNA.
Projects · WorkPages land on client Work; capacity rows stay honest.
Pages · TablesLead reassignment gate from ops law. No new tool for status.
Tables · AgentsRoutine drafts capacity + at-risk · Needs you before send.
Routines · Work// proof · multi-client ops table
Multi-client ops — one system, many rooms
Ops Table bound to account Projects — load, health, open Work, next residue. Never a Users agency pitch.
| Project | Lead | Open Work | Load | Health | Next residue |
|---|---|---|---|---|---|
| Northwind · brandProject · engagement live | Pip | 3 Work | 82% | hot | Week 3 digest |
| Orbit · siteProject · phase | You | 2 Work | 61% | ok | Spec review |
| Acme pilotProject · pilot | Sam | 1 Work | 44% | ok | Kickoff notes |
| Studio retainProject · retainer | You | 4 Work | 91% | hot | Capacity rebalance |
// nearby domains
Same OS, different residue
Peer use cases — not a Why hub dump, not a persona pitch.
// faq
Common questions
Run ops on one OS, many Projects
Stand up account Projects, put capacity in Tables, run Friday report as Routine.