All hubs

Operations

Running the business — operations for small startups

Operations at a startup is the unglamorous discipline of making sure the machine keeps running while everyone is busy building the next thing. Done right, it's invisible; done badly, it's where good companies decay into stuck ones. Most pre-Series-A teams need three cadences and maybe ten written processes. Anything more usually slows the company down faster than it helps.

Last updated May 21, 2026

Who this is for

Founders running a team of 1-30 who feel the lack of process but don't want to ossify the company.

What you'll learn

  • The three cadences that matter (weekly review, monthly close, quarterly planning)
  • Minimum-viable processes — when to add, when to resist
  • The tool stack a 5-person team actually needs
  • How to document SOPs without becoming a bureaucracy
  • When operations needs a dedicated hire (and when it really doesn't)
Get the SOP template

The three cadences that matter

Weekly review (founders, 30-60 min) — what happened this week, what's blocked, what's next week's one priority. The minimum-viable management ritual. Skip it once, the team drifts within a fortnight.

Monthly close (founder + finance lead, 2-4 hours) — books closed, MRR/ARR computed, runway updated, investor update sent within a week of month-end. The discipline that turns gut into numbers.

Quarterly planning (whole team, 1-2 days) — what we accomplished last quarter, what the three biggest bets are this quarter, who owns each. Goes wrong when teams plan twelve things; it works when they plan three.

Pre-Series A you don't need OKRs, weekly KPI reviews, all-hands every week, or a separate operations meeting. Add when the symptom appears, not in anticipation.

Minimum-viable processes

Process is debt. Add it when the absence of it hurts; pay it down when it stops earning its keep.

Process you almost always need:

  • Onboarding for new hires (a 1-page Notion doc, not a 30-page handbook)
  • Standard customer pricing (so sales doesn't make every deal a one-off)
  • Hiring scorecard for any role you've hired twice
  • Incident response (someone is on call, knows what to do when prod breaks)
  • Monthly close routines (so books don't drift)

Process you usually don't need pre-Series A:

  • Multi-stage approval workflows
  • Quarterly performance reviews (replace with weekly 1:1s)
  • Detailed expense policies (just trust people; review on close)
  • Engineering RFC processes for every change
  • A separate "ops team" function

When in doubt, write it as a checklist not a policy. Checklists adapt; policies calcify.

The stack a 5-person team actually needs

Communication: Slack or Discord (one channel structure, ruthlessly pruned).

Docs + tasks: Notion or Linear + Notion. Avoid running parallel systems.

Email + calendar: Google Workspace.

Code + CI: GitHub. Vercel or Fly.io for deploy. Linear for issues.

Customer: A CRM only when sales > 1 person; before then a Notion DB is fine.

Finance: Stripe (charging), Xero or QuickBooks (books). Mercury or Wise for banking. Don't add layers unless the existing one breaks.

HR / payroll: Deel or Gusto. Avoid bespoke spreadsheets after the first two hires.

What to NOT buy: an LMS, a help-desk product before you have any tickets, a dedicated ops platform, a project management add-on, a "team OS." All of these are vendor-suggested; almost none are problem-suggested.

Step-by-step action plan

Do these, in order

  1. 1Set up weekly review, monthly close, quarterly planning — block them on the calendar this week
  2. 2Write your first 5 SOPs (onboarding, incident response, customer pricing, hiring, monthly close)
  3. 3Audit the tool stack — kill anything not used weekly
  4. 4Stop adding process until something specific breaks; then add the minimum to fix it
  5. 5Decide the next hiring move based on whether the founder is currently >40% on coordination

Frequently asked questions

When do we need a Head of Ops?
Usually around 25-40 people, or when the founder is spending >40% of time on coordination instead of building/selling. Hiring earlier rarely pays back; hiring later quietly compounds the cost of disorganisation.
Should we use OKRs?
Below 15 people, OKRs usually add ceremony without much focus benefit. Replace with one quarterly priority per team and a weekly review. Above 30, OKRs start helping align cross-team work.
How do we keep speed as we add process?
Default to checklists, not policies. Time-box new process for 90 days, then ask: "does anyone use this?" Kill what isn't used.
What does "closing the books" actually mean for an early startup?
Reconciling bank + Stripe + invoices to a clean Profit & Loss; computing MRR/ARR/runway; recording the month. A founder + bookkeeper can do this in 2-4 hours/month with Xero or QuickBooks until you outgrow it.

Related resources

Related tools

Related templates

Related courses

Related hubs