Executive summary: Mission-driven organizations consistently over-invest in ideas before testing them. Tools like Lovable have made it possible to put something tangible in front of real users in a matter of hours, not weeks. A rough prototype that generates honest feedback is worth more than a polished plan that hasn't left the room. The first step isn't a vendor search or a scope document. It's a janky build and five honest conversations.
Most mission-driven organizations spend months preparing to build the wrong thing.
Not because the leaders aren't smart. Not because the idea is bad. Because the idea never left the building before resources were committed. It went from whiteboard to full execution without ever touching the people it was meant to serve, and by the time anyone found out it wasn't quite right, the budget was already spent.
This applies to products, campaigns, programs, and initiatives. The category doesn't matter. What matters is whether real people have reacted to something tangible before you go all in.
There's a cheaper way to find out if you're headed in the right direction. It takes about two hours, costs less than a dinner out, and produces the kind of feedback that no internal planning session ever will.
It starts with something janky on purpose.
The Real Cost of Skipping the Prototype
CB Insights analyzed 101 startup post-mortems and found that 42% failed because there was no market need for what they built. Not poor execution. Not bad timing. The thing they built wasn't something people actually needed.
That finding holds just as true for nonprofits and mission-driven organizations as it does for venture-backed startups.
The pattern is familiar once you've seen it a few times. A leader has a good idea. The team aligns around it. A vendor is hired or a staff member is assigned. Work begins. Months later, when real users finally interact with it, the problems surface — the wrong audience, the wrong feature set, the wrong framing. By then, the money is spent and the calendar is committed.
For mission-driven organizations, this is a stewardship problem, not just a strategy problem. The resources being spent belong to donors, boards, and communities. Internal alignment — everyone in the room agreeing the idea is good — is not the same as external validation.
A room full of people who believe in the mission can enthusiastically build the wrong thing together.
Earlier contact with reality is the fix.
The Bar Is Lower Than You Think
A prototype doesn't need to work. It needs to be real enough to generate an honest reaction.
IDEO, the design firm that made rapid prototyping a standard part of product development, operates by a simple internal rule: never spend more than a day building something you're not sure users want. The prototype's job is not to impress. It's to create something a real person can respond to — something that makes the idea tangible enough to test.
Dropbox understood this before they wrote a line of production code. Rather than building the actual product, they produced a three-minute explainer video showing the product working as if it already existed. Signups went from 5,000 to 75,000 overnight. The video wasn't the product. It was a low-fidelity representation of the idea, put in front of real people, generating real signal.
Today, tools like Lovable make this even more accessible. A non-technical founder can build a working interface in an afternoon — something clickable, something that looks like a real product, something a user can actually navigate.
"If you're not embarrassed by the first version of your product, you've launched too late."
— Reid Hoffman, co-founder of LinkedIn
The embarrassment is the point. Getting something in front of people before it's ready is the whole idea.
Tools worth knowing about
| Tool | What it does | Best for |
|---|---|---|
| Lovable | Builds working web interfaces from a text prompt | Non-technical founders building a first version |
| Figma | Design tool for clickable mockups | Visual layouts and flows without any code |
| Typeform | Fast forms and surveys | Testing concepts that live in a sequence or flow |
The bar to clear is low and specific: tangible enough that a real user can react to it, not polished enough to hide what's actually being tested.
Getting Your Prototype in Front of Real Users
The feedback conversation is where the real work happens.
Research from Nielsen Norman Group established that testing with five users reveals approximately 85% of usability problems. Beyond five, you start finding the same issues repeatedly rather than new ones. Five people is not a small sample size — it's the right sample size for this stage. You're not looking for statistical significance — you're looking for honest signal before you commit.
Finding five people is simpler than it sounds. They don't need to be recruited through a formal process. They need to be actual representatives of the people the product or program is meant to serve — not colleagues, not board members, not people who already believe in the idea. Those conversations will confirm what you already think. The five people who matter are the ones who have no stake in being polite.
What you ask matters as much as who you ask. Put the prototype in front of them, ask them to try to use it, and watch what happens. Here's what you're listening for:
Hesitation. Where do they slow down or stop without saying why? That pause is telling you something the user won't put into words.
Confusion. What do they try to click that isn't clickable? What do they look for that isn't where they expected it to be?
Unprompted questions. What do they ask you that you weren't expecting? These are the gaps between what you assumed was obvious and what actually is.
Unexpected use cases. How are they interpreting the idea? Sometimes users reveal a better version of your idea than the one you started with.
Charity: water did this before launching The Spring, their recurring giving program. Before any technology existed, they spent weeks in conversation with potential donors using nothing more than printed mockups. They changed the pricing structure, the messaging, and the primary value proposition based on what they heard. The Spring became one of the most successful recurring giving programs in the nonprofit sector. The printed mockups cost nothing. The conversations took days, not months.
What to Do With What You Learn
Early feedback produces one of three outcomes:
- You're on the right track. The core idea resonates, and the feedback tells you how to refine it.
- You need to build something different. The problem is real, but the solution you imagined isn't the one people need.
- You shouldn't build this at all. The need you assumed doesn't exist — or isn't strong enough to justify the investment.
Organizations treat the first outcome as success and the other two as failure. That framing is wrong. Finding out early that you need to build something different, or that you shouldn't build this particular thing at all, is the prototype doing its job. Resources that would have been spent on the wrong thing are now available for the right thing.
The language to use internally is stewardship. A two-hour prototype and five user conversations is how you protect the resources you've been trusted with. It's not a sign of uncertainty about the idea — it's a sign of seriousness about getting it right. Boards and donors respond well to that framing when they understand it. The leader who says "we tested our assumptions before committing the budget" is describing responsible leadership, not hesitation.
The goal of this stage is not to perfect the prototype. It's to make a better decision about what to build next. Either way, the decision is now grounded in something real.
That's what a janky prototype is for.
Ready to Test Your Idea?
Hillcraft helps mission-driven organizations move from idea to tested prototype quickly — without overbuilding before you know what you're building. If you have an idea that's been living in a document or a planning conversation, a discovery call is the right next step.
Book a Discovery Call