A practical operating system for service businesses. Keep projects, milestones, tasks, blockers, decisions, meetings and SOPs connected without forcing the team to live in the backend.
<aside>
👋
Start here
- Open Setup Guide once.
- Use Workflow 101 for daily execution.
- Use OPS Dashboard for the management view.
</aside>
What this system does
- One source, many views. Projects, milestones and tasks live once and appear wherever the team needs them.
- Context stays attached to execution. Decisions, meetings, notes and SOPs remain connected to the project instead of becoming separate Notion graveyards.
- Blockers are explicit. A blocked task carries the actual dependency, owner and due date.
- The backend stays boring. Most people work from dashboards and project pages; schema work lives in Admin.
How the operating model fits together
1. Project
The outcome and context container: goal, owner, dates, health and related work.
2. Milestone
A meaningful checkpoint that proves progress toward the project outcome.
3. Task
The next executable unit of work, with status, priority, owner and blocker context.
Decisions preserve why the system changed. SOPs preserve how repeated work should run once the pattern is proven.
Workspace
Run
OPS Dashboard
Workflow 101
Context
Projects
Resources
Set up
Setup Guide
Admin
Produced by keinekratzer.com
Custom setup & prices
KPS software & interactive demo
OPS Dashboard
Workflow 101
Projects
Resources