At the beginning of 2025, I wrote that every person at Glyphic contributed to customer success.

That was true, and it was a real advantage. Engineers saw customer questions directly. Founders stayed close to the details. Product decisions happened quickly because there were few layers between a problem and the people who could solve it.

Our most consistent source of leads was customer recommendations. There was no secret growth loop behind it. We solved problems quickly and helped users get more value from the product.

Then our customer base tripled.

“Everyone does customer success” started to acquire a second meaning: nobody owns customer success.

The principle had not become wrong. The operating model had stopped scaling.

This is a common startup transition. Early on, specialization feels dangerous. The company is learning too quickly, and creating a separate function can put distance between builders and customers. Shared ownership keeps information flowing.

As the company grows, the failure mode reverses. A request appears in a shared channel. Everyone can see it, so everyone assumes someone else will handle it. The urgent issue gets attention, while the quiet work of onboarding, adoption, follow-through, and pattern recognition becomes inconsistent.

Hiring our first customer-success manager was not an admission that the rest of the company could stop caring about customers. It was a way to preserve the original principle under greater load.

Ownership and participation are different things.

One person can own the system: ensuring that every customer has a plan, requests have a clear next step, patterns reach product and engineering, and promises do not disappear. The rest of the company can remain deeply involved where its context and judgment matter.

Good organizational design often works this way. A value begins as an informal behavior. Growth puts that behavior under pressure. The answer is not to abandon the value or pretend the original process will scale forever. It is to build an explicit system that protects the value.

The useful question is not “Should everyone own this?” It is:

“Who owns making sure everyone contributes effectively?”

Everyone should care about customer success. Someone still has to own the loop.