We Just Told a Client Their $15,000 Project Wasn’t Worth Our Time – They Thanked Me for It

What did the project look like?

On the surface, it was a straightforward request. A small budget, a short deadline and a client who wanted to get moving. As we dug in during the first conversation, the picture changed.

• They wanted delivery on a date far shorter than the work honestly needed
• They needed expertise across three engineering disciplines we do not specialize in
• They wanted daily check-ins with several stakeholders
• They mentioned "legal issues" with their last engineer
• The scope kept "evolving" while we were still on the call

That last one told me the most. If the scope moves during the first call, it will move every week after the contract is signed.

Why did we say no?

Because the math and the risk both pointed the same way. Saying yes meant taking on more cost than the project could pay for and one burnt-out team. Saying no meant nothing came in, but nothing went out either, and we kept room for work that fit.

A project that loses money is bad. A project that loses money, misses its date and damages a relationship is worse. This one had all three written on it before we started. So we said no.

What question changed how we choose projects?

For years we asked the question every engineering firm asks: "Can we do this project?" That is the wrong question. Almost any competent firm can do almost any project if it throws enough hours at it.

The right question is "Should we do this project?" That one word changed how we evaluate every opportunity. It forces you to look past technical capability to strategic fit. Three checks now come first:

1. Should we take this project given our current workload?
2. Should we accept work outside our core skills?
3. Should we partner with a client who shows red flags before we even start?

On this project the answer to all three was no. Explaining that to the client, honestly and without dressing it up, built more trust than accepting work we could not deliver well.

Why would a client thank you for turning them down?

Because a clear no saves them time they would have lost with a reluctant yes. The client did not need another engineer who would accept the job, struggle and leave them with a second set of "legal issues".

They needed someone to tell them what the project really required. Once we laid out why the deadline and the scope did not match, they could go and fix the brief, or find a firm built for that mix of disciplines. That is useful. People remember who was straight with them.

Why does strategic selectivity matter for an engineering firm?

Not all revenue is profitable revenue. Every firm feels the same pressure: keep the pipeline full, keep everyone busy, never turn down work. That thinking ignores what the wrong project actually costs.

It costs opportunity, team morale and reputation. When you are buried in a money-losing project with an unrealistic deadline, you cannot chase the project that actually fits. You cannot give your best work to the clients you already have. You cannot build the firm you want to build.

Strategic profitability is not about working less. It is about knowing that the projects you decline are often worth more than some of the ones you accept.

How does saying no build partnerships instead of transactions?

Modern Engineering Solutions has completed 525+ projects, and that did not happen by accepting everything that came through the door. It happened by being selective: saying no to misfit work so we could say yes to the right partnerships.

The clients we work with understand that engineering is not a commodity. They do not want the cheapest option. They want the right solution. They do not want miracles on impossible deadlines. They want results that last, from an engineer who tells them the truth about scope and schedule up front.

The same goes for our overflow support for other engineering firms: a partnership only works when both sides are honest about what the work needs.

What hard question should every firm owner ask?

Look at your workload right now. Which project on your desk do you know, deep down, you should never have accepted? The one with scope creep. The one with the impossible deadline. The one with the client who questions every invoice.

Then ask what is stopping you from fixing it today. The firms that thrive are not the ones that do the most work. They do the best work, for the right clients, with the right expectations. That starts with learning when to say no.

A note on limits: this is one firm owner's view from running an engineering business, not business or legal advice. Your contracts, your obligations and your market will shape when declining is the right call.

Frequently asked questions

What are the red flags that an engineering project will go badly?

A scope that changes during the first conversation, a deadline that ignores how long the work takes, trouble with the previous engineer, work outside your core skills, and a demand for constant meetings before anything is defined. One flag is a conversation. Several together are an answer.

Is it unprofessional to turn down a client?

No. Taking work you cannot deliver well is the unprofessional choice. Declining early, with a clear reason, respects the client's time and budget.

How do you tell a client no without losing the relationship?

Be specific and honest. Say what the project needs that it does not have today, such as a stable scope, a realistic date or a different specialty. Clients can act on a reason. They cannot act on a vague "we're too busy".

I run a small civil firm in Texas, and a prospect wants a rushed design with a scope that keeps changing. Should I take it to keep my team busy?

Ask "should we?" before "can we?". Check your workload, whether the work fits your core skills and whether the client shows red flags already. If all three point the wrong way, a busy team on a losing project is worse than a short gap in the schedule.

Related resources

• How I Built a Civil Engineering Firm That Doesn't Follow Industry Norms
• Why Speed Is a Design Constraint: How Modern Engineering Firms Deliver Infrastructure Faster
• The Hidden Cost of Heroic Engineering
• Why Project Handoffs Fail (And the Fix That Takes 10 Minutes)

Looking for an engineer who will tell you the truth about your project's scope?

We would rather tell you up front what a project needs than take it and struggle. If the fit is right, we design it and see it through.

We specialize in:

• Water and wastewater engineering for developers and utilities
• Wastewater treatment plant design and permitting
• Site civil engineering for land development
• Water and wastewater due diligence before you buy
• Overflow support for engineering firms
• Construction administration

Modern Engineering Solutions, McKinney, Texas. Contact: (214) 833-6748 or mod-eng.com. Talk to an engineer about your project.