Benefits by role Describe benefits as how Sphere helps. Don't quote numbers unless a published benchmark has been provided. Sphere is a shared control plane for change — not only an IDE chat for developers. ## Business analysts and product - State needs in plain language and see plans that map to the real system. - Collaborate on the same board and plan record as engineering and QA. - Less translation loss between “what the business asked” and “what got built.” ## Engineering leaders - Larger, multi-component changes become deliverable with less senior supervision. - Status you can trust: done means verified, not "the agent said so". - A consistent way of working across teams and AI tools. - Knowledge stays in the system model when people move on. - Fair ROI evaluation against harness-only practice (tokens, scope, human interactions) — see roi-and-evaluation.md. ## Architects - Architecture becomes the working input to delivery, not a stale diagram. - Cross-component impact is visible in the plan before anything is built. - Model updates are proposed for review — nothing rewrites architecture silently. - Open SCAN notation keeps the model portable and readable (Architecture as Code). ## Developers - Less time feeding context, re-prompting and chasing failing builds. - A clear plan with acceptance criteria before work starts. - Verified results to review, with a record of what was done and why. - Keep using the coding agents you already like — Sphere directs them. ## QA - Acceptance criteria and checks are part of the plan, not bolted on afterward. - Visibility into what was verified and what failed in the fix loop. - Same control plane as BA, Dev, and Architect — one reality for “done.” ## Product managers and operators - State needs in plain language and see a plan you can understand. - Visibility of where each change is and what has been checked. - People involved where judgment matters, not for routine follow-up. ## Founders and small teams - Deliver like a larger team: Sphere carries the delivery process around the code. - Grow a prototype into a production system with cleaner structure. - Begin with one connected system and grow from there. ## Enterprises - Governance in the workflow: approvals, audit trails and human review points. - Deployment choices from managed cloud to private environments. - Portfolio-level visibility across many systems and teams.