Why I Sometimes Say No to a Project (And Why That Builds Trust)
By Chris Adkins / July 15, 2025 / No Comments / Uncategorized

Recently, I was asked to provide a quote for a capital improvement project. On paper, it wasn’t overly complicated, but something about it didn’t sit right. As I reviewed the scope, my gut told me this was one of those projects that could look good on day one and become a headache by year two.
Now, my natural instinct is to say “yes” to a challenge. That’s how I’m wired. I’ve built my career by taking on tough projects and finding creative ways to deliver results. But over the years, I’ve learned that being a trusted advisor sometimes means saying no, even when saying yes would mean another signed contract.
In this case, I had to tell the client I didn’t recommend moving forward with the improvement as designed. Not because we couldn’t do it, but because I didn’t believe it would serve them well long-term. It might not look right, or worse, it could create functional or maintenance issues that they’d regret down the line.
This isn’t an easy thing to do in an industry where some contractors say yes to everything, for the sake of a paycheck. But that’s not how I choose to operate. I believe the reason clients continue to come back isn’t because I say yes to every job. It’s because they know I’ll tell them the truth. Even when it’s inconvenient. Even when it costs me the work.
Because at the end of the day, I’m not just building projects, I’m building relationships. And I’d rather walk away from a quick dollar today than lose trust tomorrow.
If you’re looking for someone who will shoot you straight, help you think through long-term implications, and stand behind their work for years to come, that’s what I’m here for.
Let’s build something that lasts.
