We turn down work. Not because we are busy, though we deliberately stay small, but because the honest answer to “should we build this” is sometimes no. The most valuable half-hour we spend with a prospective client is often the one where we talk them out of the project entirely.
That is an unusual thing for a development studio to admit, because saying no costs us a sale. We think it is among the most important things we do.
The three no’s we give most often
When we decline a build, it is usually one of three reasons, and none of them is that the client is wrong to want a solution.
Something already exists
Sometimes an off-the-shelf tool already does ninety percent of what you need for a fraction of what custom software would cost. Custom is the right call when your problem is genuinely yours, when existing tools would force your operation to bend around them, or when owning the thing matters. It is the wrong call when a well-made product already fits. We will tell you which situation you are in, even when the answer sends you to a subscription instead of an invoice from us.
The real problem is not software
Often what looks like a software problem is a process problem wearing a software costume. Building an app to manage a broken workflow just gives you a faster broken workflow, at ten times the price. When that is what we see, the honest move is to say so, and sometimes to help you fix the process first. The best software is built on top of a process that already makes sense.
The timing is wrong
Sometimes the idea is good and the moment is not. The funding is not there yet, the problem is not painful enough yet, or the organization is about to change in a way that would make today’s build obsolete. Waiting is not failure. It is often the difference between building the right thing and building the thing you happened to want in a particular month.
Why we can afford to say no
A shop that needs every possible sale cannot give honest counsel, because its advice is compromised by its incentives. If the only thing you sell is a custom build, every problem starts to look like a custom build.
We keep our number of projects deliberately low and our costs sane, which means we do not have to say yes to survive. That is not a moral flourish. It is the structural reason our advice can be trusted. Honest counsel is only possible when you can afford to give it.
What you get when you hear “not yet”
Clients who hear “not yet” or “not us” from Prairie Code tend to come back. They come back when the timing is right, when the off-the-shelf tool finally hits its limits, when the process is fixed and ready for real software on top of it. And they send the people they know, because a studio that told them the truth once is a studio worth trusting with the next thing.
We would rather be the shop that told you not to spend the money than the one that happily took it for a project that should not have been built. If you have an idea and you want a straight answer about whether it is worth building, that is a conversation we are glad to have. The answer might be no, and that answer is free.
Written by
Miles Bassett
Founder and principal craftsman at Prairie Code. He writes and speaks on deliberate AI adoption for small businesses and institutions.