The consistency cliff: why support quality drops exactly when you're growing fastest

There's a pattern I've noticed in almost every SaaS company that grows past 10-15 customers per month.

I call it the consistency cliff.

It goes like this:

Phase 1: Founder support (0-50 customers)

Quality is high. Every response is personal. Problems get fixed fast. Customers feel known.

This phase feels like cheating — support is easy when one person does it all and that person built the product.

Phase 2: First hire (50-200 customers)

Still okay. One new person, well-trained by the founder. Consistency holds. Volume is manageable.

Phase 3: Small team (200-500 customers)

This is where the cliff happens.

3-4 people handling support. No shared answer library. No documented escalation protocol. No response standards.

The founder isn't reading tickets daily anymore.

And suddenly:

Customer A asks: "What's your refund policy?"
Gets answer: "We offer refunds within 14 days."

Customer B asks the same question three days later.
Gets answer: "Refunds are handled case by case."

Both answers came from real policies. Neither was wrong exactly. But they're different. And if Customer A and Customer B ever compare notes — you have a trust problem.

What causes the cliff:

Not bad hiring. Not bad intentions. Just the absence of systems that should have been built before they were needed.

What prevents it:

Three documents. That's it.

1. A shared answer library (Q&A pairs for the 30 most common questions, reviewed monthly)
2. A tone guide (5-6 sentences about how the brand sounds in support)
3. An escalation map (who handles what, and when)

We built all three in a single afternoon. Combined, maybe 6 hours of work.

The consistency cliff costs far more than 6 hours to recover from once it's happened.

What systems did you build early that saved you later? And what do you wish you'd built sooner?