Guide
From idea to project: validating before you commit
An idea is a sentence. A project is a scoped thing with a first user and a next step. Here is how to make the jump without a year of planning.
The gap between "I have an idea" and "I am building something" is where most projects die — not from lack of effort, but from staying an idea too long. The fix is to convert the idea into a project: a scoped piece of work with a specific first user, a smallest useful version, and a next step you could take tomorrow.
Start by writing the idea down honestly
One page, four questions:
- Who has this problem, specifically? Not "everyone who budgets" — "final-year students managing a stipend and a part-time income."
- What do they do today instead? There is always a current workaround. If you cannot name it, you may not understand the problem yet.
- Why now? What changed — a technology, a cost, a rule, a behaviour — that makes this worth doing today?
- What is the smallest version that a real person would use once?
If you cannot fill this in, that is the first piece of validation: you have research to do, not code to write.
Validate the problem before the solution
Cheap validation is mostly conversations:
- Talk to five to ten people who have the problem. Ask what they did the last time it came up, not whether they would use your idea. Past behaviour is data; predicted behaviour is politeness.
- Look for people already paying — with money, time, or a clumsy spreadsheet — to solve it. Existing effort is the strongest signal.
- Try to talk yourself out of it. The idea that survives your own best counter-arguments is worth more.
Scope the smallest useful version
Once the problem holds up, cut hard:
- One user, one job, one path through the product.
- Something you can put in front of a real person in weeks, not quarters.
- The parts that are hard and essential first. The parts that are hard and merely nice can wait.
A project scoped this way is also far easier to bring people into — a collaborator can see exactly where they would help.
Make it a project other people can join
This is where a community earns its place. Turning your one-pager into a public project — with the roles you need spelled out — means the people who find it interesting can offer a specific skill instead of guessing. On FoundBrew, posting an idea and opening a project are the two front doors for exactly this: you go from a sentence to a scoped thing with people attached.