# "Repeatable" Means Something Different at Every Stage of the Business.

Most GTM advice is written for one stage and handed to everyone. That's why so much of it doesn't apply to you yet, or already stopped.

## Wrong-stage advice is worse than no advice

- Scalability-era rigor (forecasting cadences, comp plans, territory carve-outs) gets installed on a Stabilization-era team, producing process theater on top of the same chaos.
- Founders hire for a stage they have not reached yet — "hire a VP of Sales" is Repeatability-stage advice, and handing that job to a Stabilization-stage company with no documented process to inherit sets the hire up to fail.
- Repeatability-stage teams never graduate to Scalability because leadership keeps re-solving problems that are already solved instead of building the measurement layer that would let them scale with confidence.

## The four stages

- Stabilization: revenue depends on heroics, not systems. What "repeatable" means now: a written, followed process, even an imperfect one, that is not only in someone's head.
- Foundation: some systems exist but aren't consistent or cross-functional. What "repeatable" means now: whether the handoff between functions survives without someone standing in the middle of it.
- Repeatability: playbooks are documented and followed, but scaling further requires more rigor. What "repeatable" means now: whether it works without the same three people running it every time.
- Scalability: GTM is systematized, measured, and continuously improved. What "repeatable" means now: not stability, but innovation and a moat competitors cannot easily copy.

## Frequently asked questions

### How is this different from the GTM Gap® Scorecard or the self-audit tool?

This page explains the model. The self-audit scores where you actually fall against it, in about ten minutes, across strategy, sales, marketing, and customer success.

### Can different functions be in different stages at the same time?

Yes, and it is common. Sales can be at Repeatability while marketing is still at Stabilization. The goal is bringing the whole function up together.

### Can you skip a stage?

No, not without cost. Teams that install Scalability-era rigor on a Stabilization-era team just add process theater on top of the same underlying chaos.

### How do we know when we have actually graduated to the next stage?

Not a date on a calendar. A real handoff test: someone new can run the process correctly without the person who built it standing next to them.