"Can you build this?" is almost never the right question. The honest answer is usually yes, and that's exactly why it's not useful. A better question is whether I'm the right person to build it, and sometimes the answer is no.
Turning down work sounds like bad business. In practice, taking on the wrong project is far more expensive, for both of us.
The projects I say no to
I'll happily point you elsewhere when a job isn't a fit:
- It's a solved product. If an off-the-shelf tool already does it well, you shouldn't pay me to rebuild it.
- It needs a team I'm not. Some work genuinely wants a bigger shop, and pretending otherwise would let you down.
- The goal isn't clear yet. If we can't say what "done" looks like, we're not ready to start building.
The best outcome of a first conversation is sometimes "you don't need what you think you need."
Why this is better for you
When I only take on work I can do well, you get my full attention and an honest estimate instead of a hopeful one. And when I send you elsewhere, you save the months and budget it would have taken to discover the mismatch the hard way.
A clear plan and a fixed price before a line of code is written. Tell me what you're considering and I'll give you a straight, honest answer.
Start a conversation →
