03 · Professional Workspace · For sponsors and delivery leads
The layer between the business case
and the backlog.
Turn an approved case into a team, a plan and a weekly delivery loop — and report progress against the case's objectives, not ticket counts.
Get started01
Learn
Understand what the job actually asks of you.
02
Work
Do realistic product work with real constraints.
03
Build
Turn what you did into an explainable record.
04
Prove
A coach confirms it. An outsider attests to it.
05
Advance
Use it in interviews, applications and live work.
Now taking design partners. We are working with a small number of organisations running 5–30 change projects a year, starting in healthcare and education.
Own the case, not the tickets.
Keep your task tool. Workspace holds what it does not: the case, its objectives, decisions, risks and the sponsor's view.
01
Business case upload
Bring the approved case as PDF, Word or text. Objectives, benefits and constraints are drafted out of it with a pointer back to the source line — you confirm each one.
02
Frozen baseline
Once agreed, the case is frozen with a checksum and kept as a version. Changes go through a change request, so progress is always measured against what was approved.
03
Teams formed from capabilities
Each workstream lists the capabilities it needs, not names. Role slots are filled by invitation, and an empty slot is logged as a delivery risk automatically.
04
Every task tied to an objective
Work items link to the objective they serve. Anything unlinked is flagged, so effort that does not move the case is visible early.
05
Objective health for the sponsor
The sponsor view leads with how each objective is tracking, not ticket counts. Every figure and every assistant answer cites the record it came from.
06
Evidence that belongs to the person
Observation is off by default. Managers never see capability scores. When a project closes, consented delivery evidence goes into each person's own portable record.
Six stages, each ending at a human gate.
Stage five repeats weekly until the sponsor closes the project.
01
Upload the approved business case
03
Form the team from needed capabilities
04
Plan work linked to objectives
05
Run the weekly delivery loop
06
Close and hand back evidence
Four roles. Nothing more to configure.
Planned pricing is per active project per month, from £750, with unlimited free contributors.
Sponsor
Owns the case. Approves the baseline, change requests and closure. Sees objective health first.
Delivery lead
Runs the weekly loop day to day: plan, decisions, risks and the approval queue.
Business analyst
Structures the case into objectives and requirements and keeps traceability honest.
Contributor
Engineers, QA and designers share one view with a role tag. Contributors join free.
AI drafts. Humans decide.
Actions, decisions and risks drafted from meeting notes wait in an approval queue. A rejected draft goes back with the reviewer's edits.
04
Committed to the record
The human ownership invariant
Nothing an assistant prepares becomes a commitment, a baseline change or an evidence entry until a named person approves it.
Questions people actually ask
Does this replace Jira or Linear?
No. Tasks stay minimal here; syncing with Jira and Linear is planned next. Workspace is where the case, objectives, decisions and risks live.
What is not included in the first version?
Gantt charts, resource levelling, timesheets, portfolio or programme views, and per-role dashboards beyond the four roles.
Is anything recorded about how I work?
Only if you switch observation on for that project. It is off by default, enforced in the database as well as the interface, and turning it off stops new records immediately.
Can an assistant submit work on my behalf?
No. Drafts arrive labelled as drafts. You approve, edit or dismiss them, and approving only creates working content — submitting is always a separate action you take.
What happens when I submit an artefact?
The text is frozen with a checksum, stored as an immutable version, and added to your evidence record. It cannot be edited afterwards, which is what makes it worth showing to someone else.
Is Team Copilot a separate product?
No. It is another name for the Professional Workspace, not a third thing to buy.
Complete Journey
Experience, Launchpad and the Professional Workspace together
The Professional Workspace is where delivery work happens; Experience is where you practise it and Launchpad is where you present it. The Complete Journey plan includes all three.
See the plans →