Gtm Operating Cadence

This is a meeting architecture and planning framework for companies scaling from 20 to 300+ people. It breaks down five meeting levels (daily standups through quarterly planning), a weekly metrics dashboard that catches problems before they compound, and a three-week quarterly planning cycle that prevents strategic drift. The core insight is simple: the meeting structure that worked at 30 people collapses at 100, and the failure mode is always the same,too many people in too many meetings making too few decisions. Use it when leadership is drowning in alignment meetings but decisions still take forever, or when growth is making cross-functional coordination worse instead of better. Written by someone who's clearly watched companies hit these exact breaking points.

skills.sh installs: 1.6K
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill gtm-operating-cadence --agent claude-code

Installs into .claude/skills of the current project.

Files

Operating Cadence

The meeting structure that worked at 30 people collapses at 100. What worked at 100 collapses at 300. The failure mode is always the same: too many people in too many meetings making too few decisions.

When to Use

Triggers:

"Our meetings don't produce decisions"
"We're growing but alignment is getting worse"
"How often should we meet?"
"Nobody knows what's happening across functions"
"Decisions take forever"
"Leadership is in meetings all day"

Context:

Companies scaling from 20 to 300+ people
Post-PMF through growth stage
Distributed / remote teams
Any stage where "we need to talk about this" has become the default

Core Frameworks

1. The Five-Level Meeting Architecture

The Pattern:

Different meetings serve different purposes. Conflating them creates either inefficiency (too much time) or confusion (unclear decisions). Separate meetings by function, frequency, and decision authority.

Level 1: Daily Standup (15 min, teams only)

SKILL.md on GitHub