Saying Yes to the Wrong Project Taught Me More Than Saying No Ever Did

I knew, during the discovery call, that this project had at least two of my own red flags — a vague scope the client kept describing in metaphors instead of specifics, and a budget that seemed set before anyone had actually scoped the work. I took it anyway, because the timing was good and I talked myself into believing I could shape the scope once we started.

I could not. The engagement sprawled for four months past its original two-month estimate, the vague scope turned into a running negotiation over almost every deliverable, and the metaphor-heavy communication style never resolved into anything I could point to as a finished requirement.

Every red flag I ignored during that discovery call showed up later, in exactly the shape I'd worried about, just more expensive to fix after the fact.

What it actually taught me

• A vague scope described in metaphors during discovery doesn't resolve itself once work starts — it has to be forced into specifics before signing, not after.
• A budget set before scoping is a signal the client has a number in mind that may not match the actual work, and that mismatch becomes your problem, not theirs.
• My own instinct to "shape the scope once we start" is almost never true — I don't have that leverage once a contract's signed and work is underway.
• The discomfort of saying no in a discovery call is small and immediate. The discomfort of a bad four-month engagement is large and ongoing.

What changed afterward

I now treat those two specific red flags — vague metaphor-heavy scoping, and a budget set before the scope exists — as hard stops, not soft concerns to be managed. Every project I've declined on that basis since has, as far as I can tell from how those companies' other vendor relationships have gone, been the right call. I'd rather learn that lesson once, expensively, than keep relearning it every time the timing looks convenient.