When to Fire a Customer: Signs It's Time to Move On

Published 2026-05-27 · fivedaylaunch blog

You should fire a customer when their servicing cost exceeds their lifetime value and they show no signs of improving — but the hard truth is most founders wait too long to make that call.

Keeping a customer who drains resources, demands unprofitable service, or creates constant friction isn't loyalty. It's accounting malpractice. A $500/month client who requires 20 hours of support and customization per month is costing you $25/hour in labor alone, before product, infrastructure, and opportunity cost. That math doesn't work.

The Five Signs It's Time to Part Ways

1. They consume disproportionate support relative to revenue. If one customer generates 30% of your support tickets but only 5% of revenue, they're a net loss. Track support hours per account. When the ratio inverts, it's a signal.

2. Chronic non-payment or payment friction. A customer who's perpetually 30+ days late, constantly disputes invoices, or requires dunning cycles costing you thousands in payment processing and administrative time isn't a customer—they're a debt collection project. The cost of chasing payment often exceeds the contract value.

3. Misaligned expectations that won't resolve. Some customers fundamentally don't understand what you deliver. They bought a website expecting a mobile app, or a landing page expecting ongoing marketing strategy. If training, demos, and documentation haven't aligned expectations after 60 days, it won't happen. The mismatch will stay toxic.

4. Scope creep that's normalized. They started with defined needs. Six months in, they're requesting features outside your product, demanding integrations you don't support, or expecting custom builds at standard pricing. If gentle boundary-setting hasn't worked, they won't respect your limits.

5. They damage your reputation or team morale. Some customers are just mean. They leave hostile reviews, contact your team directly to vent, or demand impossible timelines with threats. One loudmouth customer can poison your team's motivation and tank your reputation faster than silent revenue loss.

The Financial Threshold

Set a simple rule: if a customer's annual revenue divided by their monthly support cost is under 12 months, evaluate firing them. A $1,200/year customer costing $150/month in support (weighted as salary, tools, and overhead) breaks even by month 8 and runs at loss for months 9-12. That's not a sustainable relationship.

When building a new product or service, you face this decision early. If you're using a custom development partner to validate an idea, the setup should be lean. A $799 website from fivedaylaunch takes five days and includes ownership of the code—low friction for testing a market without overcommitting resources to a customer that might not scale.

How to Actually Fire Them

Be direct and professional. Don't ghost or manufacture excuses. Send a brief email: "We've realized we're not the best fit for your needs. We're transitioning you off by [date]. Here's what happens next." Offer 30 days notice, export their data, and document everything in case they dispute the separation.

Sometimes offer a soft exit: "We're pausing this product line" or "We're consolidating our offerings." But don't over-complicate it. Most founders actually feel relief after firing a bad customer—that's your body telling you it was the right call.

The freed capacity, reduced stress, and improved morale are real returns. You'll serve your good customers better. You'll sleep better. Do it sooner than you think you should.

Want this applied to your business?
See pricing across all tiers →