Saying No to a Project Was the Right Call, Here's How I Knew

A prospective client offered a budget well above my usual range for what sounded, on paper, like straightforward server-side tagging work. Every freelancer instinct I have says take the money. I didn't, and in hindsight it's one of the better business decisions I've made.

What tipped it: the budget conversation happened before any scoping conversation. They knew what they wanted to pay before anyone had described what needed doing. That's backwards in a way that usually means one of two things — either the scope is going to balloon to match an arbitrary number nobody actually estimated, or the client has a fixed outcome in mind that isn't technically achievable for any number, and the big budget is meant to compensate for how hard that's going to be to deliver.

The other signals that stacked up

• Three different internal stakeholders described three different versions of what the project was actually for
• A request to start immediately, before a contract or scope document existed, framed as urgency rather than disorganization
• An unwillingness to show me the current tracking setup before signing, which usually means it's worse than described
• A previous vendor relationship described as 'they just couldn't deliver,' with no specifics about what was actually asked for

A big budget offered before a real scope exists isn't generosity. It's usually a price tag on a problem nobody wants to name yet.

What happened after I declined

I heard through a mutual contact about eight months later that the project went through three different vendors and still hadn't shipped. Not because any of those vendors were incompetent — because the underlying ask was never actually defined, and no amount of budget fixes a scope that doesn't exist yet. Declining wasn't a leap of faith. It was just taking the warning signs from the discovery call seriously instead of letting the number override them.