We built a custom feature for a $2,000/mo client. It broke our product for everyone else.

When we landed our first big client paying $2,000/month, we were ecstatic. They were a massive logistics company, and they had one specific requirement: they needed a completely custom reporting dashboard that synced with their proprietary internal software.

We didn't want to lose the deal. So, my co-founder and I spent six weeks building this custom integration. It was a massive hack—duct-taped together with webhooks and custom database queries. But it worked. The client was happy, and we had our first real revenue coming in.

Then the nightmare started.

Because we hardcoded this custom feature into our core app, every time we tried to push a new update, the custom dashboard broke. We spent the next three months firefighting bugs for this one client instead of improving the product for our other 150 users. Our overall churn rate ticked up by 5% because our standard features were falling behind, and the codebase became a mess to maintain.

We eventually had to tell the client we were deprecating the feature to save the product. They churned, and we lost the $24k annual revenue. We essentially acted as a custom dev shop for six months instead of a SaaS company.

For founders who have fallen into this trap: How do you say no to high-paying clients who demand custom features?

Do you build a separate "Enterprise" version of your product? Do you charge massive setup fees to make it worth it? Or do you just have the discipline to walk away?