A founder answers every message personally, usually within minutes, frequently at night. With eleven customers this is entirely possible and it delights all of them.
At two hundred customers it is not possible. Replies now take a day, sometimes two, and arrive from somebody the customer has never spoken to.
Nothing was promised and everything was implied. Every early customer experiences the company getting worse at the precise moment it is succeeding, and several of them say so publicly.
Mistake 1: treating early capacity as a service level
Answering in four minutes because there are eleven customers is a circumstance, and customers experience it as a commitment.
Mistake 2: never stating a response time
Which means the observed time becomes the expected time, and it can only ever get worse from there.
Mistake 3: promising a time you cannot sustain
Better to state something achievable at ten times the size and beat it, which is the principle in support tier and response time questions.
Mistake 4: the founder answering everything personally
Which is valuable early and becomes the bottleneck described in founders who answer every message themselves.
Mistake 5: making no distinction between urgent and routine
So everything is answered at the same speed until nothing can be, and then the urgent things queue behind the trivial ones.
Mistake 6: answering at midnight without saying why
Occasional out of hours replies are fine when framed as exceptional and damaging when they establish a pattern.
Mistake 7: not telling customers when the standard changes
A quiet decline is experienced as neglect. An explained change, with a stated new commitment, is experienced as growth.
Mistake 8: keeping no record of what was answered
So the same question is answered from scratch repeatedly and the knowledge stays in one person's head.
Mistake 9: treating support as temporary
Founders assume it will be handed over at some point and never write anything down in the meantime.
Mistake 10: measuring nothing
Volume, response time and what the questions actually are, none of which most early companies track until the load is already unmanageable.
Mistake 11: hiring before documenting
Which produces somebody who asks the founder everything, and increases interruptions rather than reducing them.
Mistake 12: assuming customers want speed above all
Many would prefer a reliable next day answer to an unpredictable instant one, and nobody asks them.
Mistake 13: letting the early customers become a separate class
Served personally by the founder while everybody else uses a queue, which is unsustainable and visible.
Mistake 14: apologising for the standard rather than stating it
Founders who feel guilty about a next day response apologise for it, which tells the customer it is inadequate. Stating it plainly as the commitment, and meeting it, reads as a company that knows what it is doing.
Set a standard you can keep at ten times the size
An assistant handling the routine questions immediately, at any hour, means a startup can state a response commitment it will still meet at two hundred customers, and let the founder spend their attention on the conversations that genuinely need them. The early questions sit in early stage startups and their first customer questions, and the cost of delay in the hidden cost of slow support replies and how. Start at try, see features, and the sector view sits under startups.