Skip to content

Meeting rhythm

The recurring meetings that keep the functions in functions/ coordinated. TODO: this is a proposed starting rhythm, not a confirmed one — adjust to match what the team will actually sustain, and delete anything that turns out to be theatre.

Meeting Frequency Attendees Purpose Output
Delivery stand-up Weekly Delivery team Surface blockers, confirm RAG status is current Updated RAG in ops-hub
Pipeline review Weekly Sales + Principal(s) Review HubSpot pipeline movement, proposals in flight Actioned follow-ups
Leadership sync Weekly Principal(s) + function leads Cross-function blockers, quarterly priority check-in Updated priority status
Financial review Monthly Principal(s) + Finance P&L, margin by project, overdue invoices Decisions on pricing/cost issues
Quarterly planning Quarterly Principal(s) + function leads Set next quarter's priorities (see strategy) New quarterly priorities doc
Annual planning Annually Principal(s) Revenue target, service-line mix, headcount plan Annual plan doc

Principles

  • Every recurring meeting needs a stated output — if it doesn't produce a decision, an update, or an unblock, question whether it should exist.
  • Status should be visible in ops-hub before the meeting (RAG status, pipeline stage, invoice status) — meetings are for discussing what the data can't explain, not reading numbers aloud.