Not All Money Is Good Money

I wish more founders and CEOs would remember that not all money is good money.

Some revenue brings opportunity. Other revenue brings sacrifice.

And if you’ve ever led Customer Success, you know exactly what I mean.

For 14 years in CS leadership, I often had to live with business decisions that were made in the name of growth. My team and I were the ones who had to “make it work.” We were the ones told to “figure it out.” And when things went sideways, we were often the ones absorbing the impact.

That’s the part people don’t talk about.

The Whale That Almost Took Us Down

I remember working at one organization where we did everything we could to close a large Enterprise customer. It was going to be a whale. A logo everyone would recognize. A deal that would make the board happy.

There was just one problem.

We had no ability to support them.

Not from a product standpoint.

Not from a process standpoint.

Not from a resource standpoint.

Concerns were raised. Repeatedly. Clearly.

We closed the deal anyway.

You can probably guess what happened next.

Despite our best efforts, the customer had a poor experience. They churned early. They moved to a competitive solution.

We didn’t just lose the account.

We lost credibility.

We damaged morale internally.

Word spread in the market.

And to make matters worse, our competitor used that failure against us in future competitive deals.

One “big win” turned into a long tail of consequences.

That’s bad revenue.

What Bad Revenue Actually Looks Like

Working in SaaS, I saw bad revenue show up in a few consistent ways:

Customers churn before CAC returns

Accounts that become a drain on resources

Deals that force misaligned product strategy

Bad revenue is expensive. It just doesn’t show up that way on the day the contract is signed.

It shows up six months later when your team is underwater.

It shows up in roadmap chaos.

It shows up in Net Revenue Retention that never quite stabilizes.

And most painfully, it shows up in your people.

Because when teams are constantly trying to save deals that should have never been closed, morale takes a hit. High performers burn out. Trust erodes between departments. CS becomes reactive instead of strategic.

What Good Revenue Feels Like

Good revenue, on the other hand, feels very different.

It looks like:

Successful customers who stay and grow

True partners who advocate for your business without being asked

Product innovation that disrupts the market… in a good way

Good revenue compounds.

It creates clarity in your product strategy.

It fuels confident forecasting.

It builds internal alignment instead of friction.

And here’s the biggest difference:

Good revenue gives you leverage.

Bad revenue takes it away.

The Real Difference: Time Horizon

The difference between good revenue and bad revenue is often the immediacy of it.

Bad money fixes short-term problems while quietly creating long-term ones.

It helps you hit this quarter’s target.

It helps you tell a better board story.

It might even help you raise the next round.

But it can cost you retention, reputation, and team health later.

And that trade-off is rarely discussed openly.

Early-Stage vs. Mature Decisions

I understand that when you’re building a business in the early days, you’re trying to determine product-market fit. You’re experimenting. You’re learning. Not every customer will make sense. Some of that is part of the journey.

But when you’re more mature — further along in your growth — and still choosing to make misaligned decisions just to “hit targets,” that raises some big red flags.

At that stage, it’s not experimentation.

It’s avoidance.

Avoidance of hard conversations about ICP.

Avoidance of disciplined qualification.

Avoidance of saying no.

And saying no is a leadership skill.

A Note of Humility

I also know this isn’t black and white.

I wasn’t always privy to every board conversation. I didn’t see every cash flow model. I understand there are moments of pressure most CS leaders aren’t fully exposed to.

But I do know this:

Customer Success always feels the downstream impact of revenue decisions.

Always.

So before chasing “bad money,” I would encourage leaders to pause and consider the ripple effect.

Ask:

Can we actually support this customer well?

Does this align with who succeeds in our product?

Are we building toward the company we want to be — or just the quarter we need to survive?

Because not all money is good money.

And the revenue you choose today becomes the company you’re running tomorrow.