Test the idea before you build it.
A new feature or product always sounds good in the room where it was dreamed up.
Feasibility testing is how you check it against reality before the budget is spent. We validate the idea with prototypes, concept tests, and structured feedback, then give you an honest signal: build it, change it, or let it go.
The cheapest version of the idea
Building is the most expensive way to find out whether an idea works. Before you commit to a feature, a product, or a big change, we put a low-cost version of it in front of real people and watch what happens.
Sometimes the answer is yes, build it, and you proceed with confidence. Sometimes it is no, and you have just saved a large build from going nowhere. Most often it is yes, but not the way you pictured, which is the most valuable answer of the three. It redirects the budget toward what people actually want before a line of code is written.
Either way, you get a clear signal with the reasoning attached, so the decision rests on evidence rather than enthusiasm.
How we test
We build the smallest thing that can honestly answer the question, then put it in front of people.
Prototypes. A clickable or visual stand-in for the idea, built just real enough to react to
Concept testing. Putting the idea in front of your audience to gauge interest and, just as important, whether they understand it
Structured feedback. Sessions designed to get honest, useful signal rather than polite agreement
A technical read. When the risk is in the build rather than the demand, we look at what it would take to make it and where the hard parts are
A clear recommendation. Go, no-go, or change direction, with the evidence behind it
How a test runs
Most tests take two to four weeks. Speed is part of the point.
Name the risk you are actually carrying
We work out what would have to be true for this idea to succeed, and which of those assumptions is the one worth testing.
Make it just real enough
A prototype, a mockup, or a concept, built to the level the test needs and no further. Polish is not the goal here.
Watch what actually happens
Structured sessions with people who look like your real audience, run so we get honest reactions rather than encouragement.
Go, no-go, or change direction
You get a recommendation with the evidence behind it, and a scope for the build if the answer is go.
Feasibility testing or user research?
These overlap, so here is the difference as we see it.
User research is open-ended. It is about understanding your users, their needs, and their behavior, usually before you have a specific idea. It asks what people need.
Feasibility testing is pointed. You have a specific idea, and the question is whether it holds up. It asks whether this particular thing will work.
If you are weighing a concrete feature or product, you are in the right place. If you are earlier than that and still figuring out what to build at all, start with research. We will help you tell which stage you are in.
What to expect on cost
Most feasibility tests run $3,000 to $8,000 and take two to four weeks. The number moves with how real the prototype has to be and how many people we need to put it in front of.
If the test leads to a build, the work carries straight into it. The prototype, the findings, and the scope all get used, so nothing gets thrown away.
Honest answers to the questions we get most
- Does feasibility testing mean technical feasibility, or whether people want it?
-
Both, and we will tell you which one your idea actually hinges on. Most tests focus on whether people want the thing and understand it. When the risk is technical, we also look at what it would take to build and where the hard parts are, since we are the ones who would build it.
- How is feasibility testing different from user research?
-
Research is open-ended: understanding your users before you have a fixed idea. Feasibility testing is pointed at a specific idea you are weighing. If you already know what you want to test, this is the faster path.
- How long does a feasibility test take?
-
Usually two to four weeks, depending on how real the prototype has to be and how many people we need to put it in front of. Speed is part of the point.
- What if the feasibility test says no?
-
Then it did its job. A clear no before you build saves the much larger cost of building something that would not have worked. We give you the reasoning so you can trust the call.
- Do you build the prototype, or do we provide it?
-
We can build one to whatever level the test needs. It does not have to be polished, just real enough for people to react to honestly. If you already have a prototype, we will test that.
- What if Discovery tells us we shouldn't build?
-
Then we'll say so. The goal of Discovery is to find the right answer, not to sell you a build. If there's a tool that already does what you need, we'll name it. If the economics don't work for custom development at your scale, we'll tell you that too. A $3,500 Discovery engagement that saves you from a $50,000 build that wasn't the right fit is a good outcome. We'd rather that than the alternative.
Weighing whether to build something?
A free consultation is the fastest way to pressure-test it. Tell us the idea, and we will tell you honestly whether a quick feasibility test would save you from an expensive guess, and what testing it would involve.