How WantBorn works
State the problem so it can be checked. Build the smallest version. Put it in front of people who actually have the problem, and turn what they tell you into your first real users.
Nothing asks you to declare which of these you are. Both columns below are things one account can do, and most people end up doing both — where a step is not yet open to everyone, it says so.
If you're building something
From an idea to people who use it — with the validation step actually done, not skipped.
- 1
Start the project in LaunchOS
One guided path — idea → validation → SLC/MVP → your first 1/3/5/10 real users → revenue. Each stage tells you what to do next and which framework fits it. It nudges when you skip something; it never locks you out of the next stage. Needs an account, and works with nobody else on the platform.
- 2
Check the demand before you build it
Run a demand-research report on the problem, and post it on the Forum as a quest: the problem, who has it, and the criteria a real solution must meet. New quests are reviewed before they go live.
- 3
Ship the smallest lovable version
Declare what it does, why someone would love it, and — the part people skip — what you deliberately did not build. The cut list is stage discipline you can point at later.
- 4
Open it for testing and send the link
Say what you want tried and what you want to hear about. You get a link that never changes. Anyone signed in can leave one structured note. You can reply to a note; you cannot delete one.
- 5
Turn notes into real first users
Promote a note into the first-users tracker. It lands as 'replied' — never straight to 'using it' or 'paid', because those are the numbers the whole product depends on being true.
If you have the problem
The side that makes validation mean anything — and the side that is hardest to fake.
- 1
Post a problem you actually have
No account needed — a quest takes the problem, who else has it, and the must-have criteria. If you're posting from research rather than experience, you say so and link the evidence; the form asks for it.
- 2
Say if you have the same problem
One line, in your own words: you have this problem too, or it doesn't ring true for you. You can't check your own quest, you can't check one you've claimed to build, one check per person, and there's a daily cap. It shows as a raw count with your note attached — never a 'verified' badge.
- 3
Try an app and leave one honest note
What you actually tried, what confused you, and one of three coarse verdicts — would use again, maybe, not for me. No stars and no 1–10, because nothing here averages into a rating we can't stand behind.
- 4
Claim a problem nobody has solved
When a quest is flagged as a gap, it can be claimed with a build plan — that promotes it into a brief with the plan attached and puts a name on it publicly. Any signed-in account can claim one.
When a problem is actually validated
“Validated” is computed, never typed in by us. A quest reaches it when at least three people who are neither the poster nor the builder who claimed it have said they have this problem too, and at least one person has given a real demand signal — committing to test it, or backing it. A free test-commit counts; an abandoned checkout does not.
That bar is high on purpose. Most quests will not reach it, and a board that showed everything as validated would be worth nothing.
What we don't do
- No automated matching. Finding a builder's first real users is meant to be done by hand, because that is the part that actually works at this size.
- No escrow. WantBorn does not hold or move money between people.
- No pay-to-rank. Nothing on a public board can be bought into a higher position.
- No invented numbers. Every count shown is one the code computed, and anything self-reported is labelled as self-reported.
Get in early
Join the list for one confirmation now — you can start using the Forum, LaunchOS and Try It right now without it. If something here is worth telling you about later, you'll hear from a person, not an automated ping.