The problem
Ops teams at growing startups inherit Notion-databases-of-Notion-databases. Each function (people, finance, IT, CS) ends up with its own duct-taped tracker because Linear is too dev-shaped (issues, sprints, branches), and Asana is too generic. The result: every Tuesday all-hands is half spent reconciling "what's the actual status of <thing>" because three sources of truth disagree. Founders eventually hire an Ops Manager whose first 90 days are spent migrating six Notion DBs into one — and then the next quarter migrating that one into something else.
Our solution
OpsKit is opinionated where Linear is opinionated. Workflows for the ops-shaped work patterns: vendor onboarding, customer escalations, hiring loops, AP/AR. Each function ships a template, not a blank canvas. The core primitives are projects and runs (a run is a single instance of a workflow, e.g. "onboard Acme Corp as a vendor") with status, owner, due date, and structured fields. The opinionated bit: we ship the workflows, you don't draw them. If your process doesn't fit a template, fork it — but you start from a real template, not from scratch.