FRAMEWORK USED: A — STORY POST: Six months into our first $30,000-a-year enterprise contract, I started to question something I’d believed for years: “The customer is always right.” The client’s account manager was repeatedly calling our engineers at 10 p.m. about non-urgent fixes. Eventually, our lead developer told me he was updating his résumé. That got my attention. My cofounder asked me a simple question: “If every client was like this, would you still want to run this company?” My answer was no. So we gave the client 60 days’ notice and refunded the final quarter. It felt counterintuitive to walk away from revenue, especially as a bootstrapped company. But retaining a client isn’t free if the cost is paid by your team. Within 90 days, we signed two better-fit clients. The developer stayed. Our NPS increased by 18 points. The lesson for me wasn’t that difficult clients should always be fired. It was that revenue alone isn’t a good enough reason to keep a client who consistently damages the way your team works. For SaaS founders and agency owners, it’s worth asking: **If every client behaved like your most difficult client, would you still want to run the business?** WHY THIS WORKS: The post uses a specific client situation to create tension, then lets the decision and outcomes carry the lesson without turning it into a generic “fire bad clients” argument. It connects the financial decision directly to team cost while preserving the concrete facts and results from the source material. ALTERNATIVE HOOKS: 1. **We walked away from a $30,000-a-year client—and it turned out to be one of the better business decisions we made.** 2. **The moment a lead developer starts updating his résumé because of a client, the client problem becomes a company problem.**