The Customer Who Ruins Your Company

Let me tell you about the deal that almost killed a friend's startup.

Series A company. Solid product. Growing nicely. Then a Fortune 500 logo showed interest. The kind of logo that makes investors salivate and founders update their LinkedIn.

The deal was $400K annually. More than their next 20 customers combined.

They signed it.

Eighteen months later, the company was a shell of itself. The entire roadmap had been hijacked by this one customer's requests. The engineering team was demoralized from building features nobody else wanted. Churn on their core product spiked because they'd stopped improving it. And when the Fortune 500 finally churned anyway—because of course they did—there was nothing left.

One customer. One "win." Nearly destroyed everything.

Here's what nobody tells you: Not all revenue is good revenue. Some customers will pay you money while slowly poisoning your company. And the most dangerous ones usually look like your biggest wins.

The Enterprise Deal That Kills Your Product

Enterprise deals are seductive. Big logos. Big checks. Validation that "serious" companies take you seriously.

But enterprise customers want enterprise things. They want custom integrations. They want security reviews that take 6 months. They want features that only make sense for companies with 10,000 employees. They want you to bend your roadmap around their procurement cycle.

And because they're paying 10x what your other customers pay, you do it.

Slowly, your product stops being yours. It becomes a custom solution for one customer wearing the disguise of a SaaS product. Your team spends 60% of their time on 5% of your revenue. Your actual target customers—the ones you can scale—get ignored.

I've seen this movie end three ways:

1. The enterprise customer churns and you're left with a Frankenstein product nobody else wants

2. You become a captive vendor, essentially an outsourced IT department for one company

3. You wake up and fire the customer (more on this later)

The enterprise logo isn't worth it if it costs you your company.

The Customer Who Pays The Most But Costs The Most

Revenue isn't profit. This is obvious on paper but founders forget it constantly.

Your biggest customer might also be your least profitable. They might require:

• Dedicated support that eats 20 hours per week

• Custom SLAs that stress your infrastructure

• Executive hand-holding that pulls you out of building

• Legal reviews, security audits, and compliance theater

• Constant escalations because nothing is ever good enough

When you do the math—really do the math—you sometimes find that your $100K customer costs you $120K to service. You're literally paying them to be your customer.

But you don't fire them because the revenue looks good on your dashboard. Because you've already announced the logo. Because admitting the deal was bad feels like failure.

So you subsidize them with the profits from your good customers. And you wonder why growth feels so hard.

Custom Work Disguised As Product Development

Here's the lie founders tell themselves: "This custom feature will become part of our core product. Other customers will want it too."

Sometimes this is true. Usually it's not.

Usually, the custom feature is so specific to one customer's workflow that it's useless to everyone else. But it lives in your codebase forever. Your engineers maintain it. It creates edge cases that break other things. It adds complexity that slows down every future feature.

The customer got exactly what they wanted. You got technical debt and a slower product.

The test is simple: Before building anything for a single customer, ask yourself—would you build this if they weren't paying you? Would this make your top 10 prospects more likely to buy?

If the answer is no, you're not building product. You're doing consulting and pretending it's product development.

The 80/20 Rule, Applied Ruthlessly

In most startups, 20% of customers drive 80% of the headaches. Support tickets. Feature requests. Complaints. Escalations. Threats to churn.

These are often—not always, but often—the same customers who negotiated the hardest on price. They're paying you less than others while demanding more.

Meanwhile, your best customers are quiet. They pay on time. They don't complain. They refer other customers. They're profitable and pleasant.

So who gets your attention? The squeaky wheels. The difficult customers. The ones who generate noise.

This is backwards. You should be obsessing over your best customers—understanding why they love you, finding more like them, making their experience even better.

Instead, most founders spend their energy on customers who will never be happy. It's a trap.

When To Fire A Customer

Yes, fire. As in: give them their money back and tell them to leave.

This sounds insane when you're struggling for revenue. But some customers have negative lifetime value when you account for everything they cost you.

Fire a customer when:

They're warping your roadmap. If one customer's demands are pulling you away from what the rest of your market needs, they're not a customer—they're a distraction.

They're abusing your team. Some customers treat support staff like punching bags. Some make unreasonable demands and throw tantrums when they're not met. Life's too short. Your team's morale matters more than one customer's revenue.

They're unprofitable. Do the math. If servicing them costs more than they pay, you're running a charity. Stop.

They're a bad fit you forced. You knew during the sales process they weren't quite right, but you needed the revenue. Now you're paying for it. Cut your losses.

They're blocking your focus. Sometimes a customer isn't terrible—they're just consuming attention you need elsewhere. That's enough.

The first time you fire a customer, it feels terrifying. The second time, it feels liberating. By the third time, you realize it's just good business.

The Customer You Actually Want

Here's what good customers look like:

• They have the problem you solve and know they have it

• They pay full price without months of negotiation

• They use the product as designed (not demanding custom everything)

• They give feedback that helps you build a better product for everyone

• They refer other customers like them

• They renew without drama

These customers exist. But you'll never find them if you're too busy servicing customers who are slowly killing you.

The Bottom Line

Revenue is not the goal. Sustainable, profitable revenue from customers you can actually serve is the goal.

The wrong customer doesn't just fail to help you—they actively hurt you. They consume resources, distort priorities, and exhaust your team. They make your company worse, not better.

So be picky. Not every deal is worth closing. Not every logo is worth chasing. Not every dollar is worth taking.

The best founders I know have a clear picture of who their customer is—and who their customer isn't. They say no to bad-fit deals, even when it hurts. They fire customers who aren't working, even when the revenue would be nice to keep.

Because they understand something most founders learn too late: The customers you say no to matter just as much as the customers you say yes to.

Choose wisely.

—Brendan Ward

P.S. - If you read this and thought of a specific customer, you already know what you need to do. The question is whether you'll do it.