/case-studies
Five ways of working. One system.
One connected system meets five very different lives: a founder running every role, a designer drowning in things he saved, a CEO holding a company together, a consultant juggling four clients, and an agency owner running content and sales at once.
Each case below opens with who the person is, what their workspace holds, and the film that walks through it. Pick the one that looks like your work.
Jump to: the note · the five cases · yours
/note · synthetic data
Read this before the films: these are demonstration personas.
These five cases are not customers. They are synthetic personas: demonstration cases we designed to show how different people can run SophionOS. The names, companies, and every number in the workspaces and the films are example values we assigned and seeded into a demo environment, so you can watch exactly how the system behaves. No real user data appears anywhere in these films.
The discipline is the point: each persona gets a complete workspace with consistent areas, goals, projects, tasks, notes, resources, topics, and contacts, and every number you see is computed from that workspace by the same rules the product ships. Swap in your own work and the mechanics behave identically.
Policy: demo fixtures and films use synthetic personas only. Never real notes, contacts, or exports.
/case-studies · the five
Different work, the same connected spine.
5 personas, 5 films. Choose a case and it opens in place: the situation, the film, how the workspace is used, and the seeded totals behind it.
Maya Chen
Indie SaaS founder · Inkwell
Every role, one person, one workspace.
Maya is 29 and building Inkwell, an AI writing tool, alone. Product, engineering, support, and marketing all rest on one person, which means her roadmap, her customers, and her own learning have to survive in one place.
She works inside Cursor and Claude Code, so the workspace cannot be another tab to remember. It has to be reachable from the tools she already lives in.
/the-film · 2:12 · 7 scenes
01One founder, every role
02Complete a task, watch the chain move
03The day ranked by an auditable score
04A goal page with the whole initiative
05Capture from inside the AI tools
06Recurring work and quiet areas
07Customers with follow-up clocks
/how-maya-uses-it
Capture from inside the AI tools
A task arrives as a sentence typed to her AI. The MCP server writes it into the same records every view reads, so it shows up in the project, the goal, and the dashboard at once.
The cascade keeps the roadmap honest
Completing the documents migration moves the project bar and the goal behind it. Nothing is retyped, because progress is computed from linked work instead of maintained by hand.
A day that is ranked, not chosen
Smart priority weighs due date, priority, goal alignment, and urgency, so the overdue auth endpoint surfaces first with the arithmetic visible.
A goal page with the whole initiative
Ship Inkwell v2.0 gathers its projects, open tasks, decisions, docs, and the contractor reviewing them, each behind a counted tab.
A rhythm that maintains itself
The weekly revenue review respawns after completion, and an area with nothing in it steps back on its own.
/at-a-glance · seeded totals
/the-films-close
"Maya writes the product. The workspace runs the company."
Every number on screen is computed from this persona's seeded demo workspace: project and goal progress, priority scores, derived statuses, and follow-up clocks all run through the same rules the product ships.
/case-studies · yours
None of these workspaces exist. Yours will.
Every persona on this page is an example we designed, which means the interesting case is the one we cannot design: yours. The Founding Cohort gets the workspace early and a direct line to shape what it becomes.