Learning to say no to custom features

A customer asks for a small change that only they need. It sounds harmless and it's usually quick. The cost shows up later, when you maintain that special case across every release.

I try to ask one question: would three other customers want this? If yes, it becomes a real feature. If no, I offer a workaround, or a paid custom engagement with clear boundaries.

Saying no politely is a skill. People accept it more easily when you explain what you're protecting: a product that stays simple, stable and fast for everyone.