Why we turn down about 1 in 5 inbound briefs

Roughly one in five inbound project briefs we receive, we turn down, either outright or by recommending a different kind of partner entirely. That's a real, deliberate share, not an occasional edge case, and being honest about why has generally earned more trust with prospective clients than accepting projects that were never going to be a good fit for either side.

If a client needs a genuinely custom eCommerce platform in two weeks, we say so directly rather than quoting an unrealistic timeline to win the project and then delivering something rushed or missing the date. This is the single most common reason we turn something down, and it's rarely about capability, it's about a timeline that isn't physically achievable regardless of team size or budget.

We'd rather tell a founder honestly that their $3,000 budget doesn't cover the custom marketplace platform they're describing, and suggest either a much narrower first version or a different kind of build entirely, than take the project and quietly cut corners to hit the number. This conversation is uncomfortable in the moment and has led to some of our best longer-term relationships, once the founder came back later with a validated idea and a realistic budget.

We don't build enterprise-scale internal software systems or highly regulated fintech infrastructure requiring specialized compliance expertise we don't have in-house, and we say so rather than stretching into unfamiliar territory on a client's dime. Referring these out, when we have a genuine referral to make, tends to matter more to a prospective client's actual outcome than us reluctantly taking on work outside our real expertise.

Occasionally a prospective client's approach during scoping itself, an insistence on unrealistic terms, a pattern of disrespect toward the team on early calls, signals the working relationship itself would be difficult regardless of how well-matched the actual project scope is. We've learned to trust this signal and decline rather than assume it'll improve once a contract is signed. In our experience, it rarely does.

Whenever we decline a brief, we try to say specifically why, not just "not a fit," and where relevant, point toward what would actually solve their problem, whether that's a different type of vendor, a narrower first scope, or more runway before the project makes sense. A well-explained no is worth more to a founder than a yes that was never going to end well for either of us.

It's tempting to assume turning down one in five inbound briefs costs real revenue, and in the short term, on any individual project, it obviously does. Over a longer horizon, the projects we would have taken and struggled with, rushed timelines delivered late, underfunded scopes cut down until the result disappointed the client, adversarial relationships that drained the team, would have cost more in reputation and team morale than the revenue was worth. Word of mouth referrals, which remain our best source of new work, come overwhelmingly from projects that went well, not from projects we technically completed under difficult conditions.

We track this informally rather than with a precise ROI calculation, but the pattern has held consistently enough across several years that saying no has become an easier, more confident decision than it was early on, when every inbound lead felt too valuable to turn away regardless of fit.

In our early years, some of these mismatches only became clear a few calls into the scoping process, after both sides had already invested real time. We've since built a short set of qualifying questions into our very first response to an inbound brief, timeline expectations, rough budget range, the specific problem being solved, specifically to surface a likely mismatch before either side sinks meaningful time into a conversation that was never going to lead anywhere. This hasn't eliminated late-stage declines entirely, but it's reduced how often we reach that point after several hours of scoping calls rather than after one short exchange.

When we decline a project, we don't just close the conversation, we spend a few minutes thinking about who might actually be the right fit, a specific freelancer we've worked alongside before, another agency with the relevant specialization, or occasionally a suggestion that the founder handle the first version themselves with a low-code tool before spending real money on custom development. This costs us a few minutes on a project we're not getting paid for, and it's consistently one of the things prospective clients mention when they do come back to us later with a different project.

We've had multiple clients return eighteen months or two years after an initial decline, once their timeline or budget had caught up to what their project actually needed, specifically citing the honest no and the useful referral as the reason they thought of us again. That outcome doesn't happen every time, but it happens often enough that we treat a well-handled decline as a real, if delayed, part of how new business actually reaches us, and we've stopped thinking of a well-explained no as pure lost revenue, treating it instead as an investment in a relationship that might just be arriving too early rather than a door closing for good. It's a small shift in framing, but it's changed how the whole team approaches these conversations.

The one-in-five figure isn't a target we manage toward; it's just where the honest math has landed once we started actually tracking it. Some quarters it's closer to one in eight, some it's closer to one in three, depending on what's coming through the inbound pipeline that particular quarter. What's stayed constant is the underlying instinct: a project we're not genuinely equipped to do well costs both sides more than a clear, early no ever does, and that's been true regardless of how the specific ratio has moved around from year to year.