What We Tell Clients Who Don't Need Us Yet

We've told people to wait. To not launch yet. To not hire us for this particular problem.

That advice is free. We'd rather give it than take on a project we know isn't going to go well.

What honest advice actually looks like

We've told clients their current site was fine. That the problem they wanted to solve wasn't the actual problem. That the budget they had wasn't right for what they were describing, and trying to proceed would end badly for both of us.

We've told potential clients to wait until they had more clarity on scope, more budget, or a clearer sense of what success would look like. We've referred people to other developers, other agencies, and sometimes off-the-shelf solutions that would serve them better than a custom build.

When we recommend against hiring us

When the client isn't ready. When the scope isn't clear enough to price honestly. When the problem they've described doesn't match the solution they're requesting. When another approach would do the job better.

We'd rather lose the work than deliver something we wouldn't put our name on.

What this produces over time

Clients who've trusted us with a hard decision trust us more on the next one. Some of the working relationships that have lasted longest started with us saying something uncomfortable early on, and being right.

You don't have to take our word for it. Notice whether the people advising you have skin in the game when they give advice. If the answer is always "yes, great idea, let's start right away," that's worth thinking about.

Talk to us honestly about what you need.