The foundation, connected to the way work actually moves.
The Operating Workspace links your knowledge, templates, and tools into one system, so a project moves from inquiry to delivery with fewer handoffs carried in your head.
Projects move from inquiry to delivery as one connected system, with approval points where judgment matters.
- Owners whose work crosses email, files, calendar, and deadlines
- Foundation, 5 skills total, 1 connected workflow, 3 templates, 1 scheduled workflow, correction loop, training
- Payment plans available
Who Operating is for
A good fit if
Projects stall between your inbox, your files, and your calendar, and you are still the person who checks every step.
Not yet if
You cannot yet name the workflow you repeat. Foundation, or a Sprint, will surface it first.
One connected path
Inquiry to onboarding as one connected path, with content requests and checklists generated along the way.
Revision rounds, tracked
Briefs, drafts, and revision rounds tracked against your process, with client feedback summarized into a clear next draft.
What Operating includes
Your business context, established
The full Foundation knowledge base and exactly 3 starter skills, built first so connections have something sound to connect to.
One connected workflow
A core process, such as inquiry to proposal to onboarding, that reaches the approved tools it needs, with access limited to that job.
3 rebuilt templates
Your existing documents rebuilt as workspace assets, so proposals, updates, and delivery notes share one standard.
1 scheduled workflow
A weekly pipeline review or follow-up list prepared on a rhythm, when your setup supports it.
A correction loop
Your edits and preferences are captured into the knowledge guides, so the same miss does not repeat.
Training and a 30-day check
Training on live work for you and any collaborator who will use it, then a review of adoption after 30 days.
Access and approval in a connected workflow
Each workflow gets only the access its job needs. Drafts wait for your approval, and high-stakes communication, money, contracts, and client commitments always stop at a person.
Connected in the install, checked before it runs on a rhythm.
The install follows the same guided model as Foundation: folders and instructions emailed ahead, by video call, you logged in and making every click, including every tool connection and scheduled task setup.
The connected workflow and the scheduled workflow are connected and set up by you in the install, not switched on in the background. Approval points are checked before anything runs on a rhythm, so drafts still wait for you where judgment matters.
The test is the connected path run end to end on a real project, from inquiry through the steps that used to stall between tools, with the scheduled workflow's first prepared output reviewed before it becomes routine.
The install ends with a short written record: what was installed, what each workflow connects to, what access it has, and where approval stops it. The install sessions included are named in your written scope.
Operating questions
What counts as one connected workflow, and one scheduled workflow?
A connected workflow is one core process that reaches the approved tools it needs, with access limited to that job and approval points where judgment matters. A scheduled workflow is work prepared on a rhythm, for example a weekly pipeline review or follow-up list, when your setup supports it. Both are set up by you in your own account.
What if my workflow needs more than the base?
It is discussed in the proposal, priced, and approved in writing before scope changes. No component is added, and no price changes, without your approval first. If the need is bigger than Operating, the proposal says so plainly, with the Flagship scope and price, instead of stretching Operating past what it is.
The work record
Every skill writes a work log entry as it works: the date, the task, the decision made, and the next step, so nothing important relies on memory or on a conversation alone.
If your goals call for it, your scheduled workflow can be a nightly export of that work log and task status to your own Notion, where due and overdue tasks are visible. That export takes the place of a weekly pipeline review as your scheduled workflow, unless your proposal names and prices a second scheduled workflow.
This option is available in Operating and Flagship builds, when your goals call for it, and is named in your proposal if it applies. It is not a default in a Sprint or Foundation build.
Make one whole workflow easier to run.
Bring the process you currently carry from tool to tool by hand.
Talk about an Operating Workspace