The Cost of Saying Yes

Some of the most expensive decisions in a business begin with three little words:

“Sure, we can.”

Sure, we can make an exception for this customer.

Sure, we can take on that project even though it’s outside our usual work.

Sure, we can hold the price, absorb the extra effort, or squeeze one more thing into the schedule.

Any one of those decisions might make perfect sense. The trouble comes when they pile up. Eventually, you’re busy serving commitments you never really chose as a whole.

[BRANDED INTRO]

Welcome to Things Entrepreneurs Should Know — a podcast about the decisions, tradeoffs, and occasional hard lessons that come with building a business of lasting value. I’m Chip Schweiger. And, I’ve spent more than thirty years working with businesses and the people who run them.

In that time, I’ve seen how easily a business can become crowded with commitments that made sense when someone first said yes. 

So today, we’re talking about what those yeses cost—and how to recognize when it’s time to give a different answer.

And I need to admit something before we go any further: I’ve spent plenty of time helping owners see where their businesses were giving too much away. I just haven’t always been as good at seeing it in my own.

 [BUMPER MUSIC]

Welcome back.

There’s a version of saying yes that every business needs.

A new company has to be willing to solve problems. An owner who refuses every request outside a narrow job description probably won’t build much of a business. Flexibility helps you win trust. It teaches you what customers need. Sometimes an unusual request becomes the best service you offer.

So I’m not here to argue that you should become difficult to work with.

I’m talking about the yes that feels small when you give it, but creates an obligation that lasts much longer than you expected.

Maybe a customer asks for one more revision. You can do it, so you do.

A project comes along that doesn’t quite fit your business. The revenue would help this month, so you take it.

Someone asks you to serve on a committee, make an introduction, or help with a problem that isn’t yours to solve. You like the person, and you know you could be useful.

None of these is an obviously bad decision. That’s what makes them hard.

The price isn’t always on the invoice

When owners evaluate a request, they usually look at the visible cost. How many hours will it take? Will we make money on it? Can we fit it into the schedule?

Those are fair questions. They’re rarely the whole calculation.

A custom job might be profitable on paper but require the attention of your best people at exactly the wrong time. A discounted customer might still generate a healthy gross margin, yet demand so many calls, changes, and favors that the team struggles to serve everyone else.

And a commitment you personally take on might cost the company nothing in cash while consuming the one resource you can’t hire more of: your own judgment and attention.

That cost doesn’t appear neatly in the financial statements.

Instead, you see it in the work that waits. The proposal you don’t send. The process you don’t improve. The conversation with a key employee you keep postponing.

You can be fully occupied and still be avoiding the work that would move the business forward.

I’ve certainly done that. It’s easy for me to recognize an owner who has become the answer to every question in the business. It’s harder to catch myself agreeing to one more thing because I know I can handle it.

And usually, I can handle it. That isn’t the test.

The better question is: What will this yes prevent me from doing?

Why capable people get caught here

People who build businesses often take pride in being dependable. We solve problems. We come through. When somebody asks for help, we can picture how to get it done.

That ability is valuable. It can also make a request feel almost impossible to turn down.

Sometimes there’s a financial reason. Cash is tight, and the project offers immediate revenue. Sometimes it’s a relationship you care about. Sometimes you’re worried that a no today will close a door later.

And sometimes the request is simply flattering. Someone trusts you enough to ask.

I don’t think we make much progress by pretending those reasons aren’t real. Saying yes may have been the right call when you made it. Circumstances change, though, and a commitment that once served the business can become a poor fit.

You’re allowed to revisit it.

That can be especially hard with a good customer. You’ve built the relationship by being responsive. You may feel that drawing a boundary now will sound like a change in character.

But there’s a difference between serving a customer well and training everyone, including yourself, to treat every request as urgent and included.

If the customer needs something outside the agreed work, you can still help. You can give them a price. You can offer a later date. You can refer them to someone better suited to it.

A thoughtful no often sounds like, “Here’s what we can do.”

Look for the pattern

One exception probably won’t hurt you. In fact, exceptions can tell you something useful. They show where customers need more than you anticipated.

Pay attention when the same exception keeps coming up.

If every project requires a few unbilled extras, the scope or price may be wrong. If your team regularly has to rush work for one customer, the problem may be in the way that account is managed. If you keep accepting assignments that pull you away from the business you’re trying to build, it may be time to decide what work you actually want.

This isn’t a call to put a rigid rule around every interaction. It’s a call to notice what your yeses are adding up to.

Take a look at the last month. Where did your time go that surprised you? Which commitments generated value, and which ones mostly generated more commitments?

Then ask what you said no to by default because those earlier yeses had already filled the calendar.

That’s the part we often miss. Every yes contains a no, whether we say it out loud or not.

Make the decision before the request arrives

It’s easier to make a sound decision when you aren’t staring at a person who needs an answer.

If you know that custom work requires a separate scope and price, you don’t have to invent that boundary during an awkward conversation. If you’ve decided how much of your time you can give to outside commitments, you can consider an invitation against something real.

For an owner, that might mean a few simple questions before accepting new work:

Does this fit what we do well?

Can we deliver it without shortchanging work we’ve already promised?

Will we be glad we took it six months from now?

And if we say yes, what are we choosing to delay or give up?

You won’t have perfect answers. I know I don’t. But asking the questions creates a little space between the request and your response.

You can also say, “Let me look at what we’ve committed to and get back to you.”

That sentence has saved me from more than one yes I would have regretted.

The commitments you already made

Of course, some of us have more work to do than slowing down the next yes. We have to look at the ones we’ve already given.

That doesn’t mean walking away from promises or surprising people who relied on us. It may mean finishing a project and declining the next one. Renegotiating a scope that has grown. Raising a price to reflect the work involved. Handing off something that no longer requires us personally.

Some conversations will be uncomfortable. But letting an arrangement drift indefinitely usually isn’t kinder to either side. Resentment grows, service suffers, and eventually a small correction becomes a difficult one.

I’m reminding myself of that as much as I’m telling you.

A full calendar can make you feel useful. A business with plenty of requests can look healthy. Neither tells you whether your time and your company’s capacity are going where they should.

Saying no isn’t automatically wise. Saying yes isn’t automatically generous. The judgment lies in knowing what the commitment will cost and making that choice deliberately.

So here’s one question worth taking back to your business this week:

What are you still saying yes to because you said yes the first time?

[OUTRO]

That's all for this episode. Thanks for spending a few minutes with me.

If this episode made you think about your own business a little differently, send it to another owner or business leader who might appreciate it.

You can find the show notes and more episodes at TESKPod.com.

This is Chip Schweiger, reminding you that if you always do what you've always done, you'll always get what you've always gotten.

I look forward to seeing ya next time.