Field note

The Job I Turned Down That Changed How I Run My Business

A few years back, I almost took a job that looked fine on paper.

The scope was decent. The budget was reasonable. Nothing about it raised an obvious flag.

I was close to signing.

But the first meeting felt off.

Not a red flag exactly. More like a pattern I’d seen before and couldn’t quite name yet.

The client kept asking about price before we had settled the scope. They pushed on contract language in a way that told me they had been burned before. They were already managing the relationship from a place of distrust.

That is not bad faith.

It is history.

But history like that makes a job harder before it ever starts.

I know what those jobs feel like from the inside.

The work is fine.

The relationship is the problem.

A bad relationship follows every invoice, every change order, every schedule conversation. It wears on the crew and makes small issues bigger than they need to be. A straightforward job ends up costing you more than money.

So I walked away.

What changed for me was not a rule.

It was a filter.

I started paying attention to the first conversation the same way I pay attention on a site walk, looking for what does not add up before I am too deep to do anything about it.

The hesitation that feels off.

The question behind the question.

The tone that tells you how things will go once pressure shows up.

Most contractors chase volume because it feels like progress.

But not every job moves you forward.

Some just take up the space where a better one could have been.

The job I turned down cost me nothing.

The ones I should have turned down and didn’t cost me plenty.

#Construction #Contractors #BuiltWorld #BuildLogIQ

Ryan Yang
Co-Founder & Head of Operations, BuildLogIQ