Try the idea before you build the company.
Stand up a real backend in an afternoon, put it in front of actual people, and watch what they do with it. If it takes off, it grows with you. If it doesn't, you're out a weekend.
Where it stops
You shouldn't need production to test a hunch.
The usual path asks you to stand up infrastructure built for millions, and pay to keep it running, before a single person has opened the thing. So the cost of finding out lands before the answer does — and ideas get talked about instead of tried.
What that looks like here.
A full backend — auth, database, storage, functions, hosting — in the time it used to take to pick a stack.
Signals is already counting. Sign-ups, activation, what people actually reach for — your own data, no analytics vendor to bolt on.
Feature flags let you try a change on some of the people using it, then widen it — or turn it off in a click.
How it goes.
- 1Build the real thing, quickly
Not a mockup — a working app with a real database behind it, because that's the only version that tells you anything.
- 2Put it in front of people
Publish it, send the link, let them sign in. Real use, not a survey.
- 3Watch what actually happens
Events and metrics in the console from the first minute, plus logs when something goes sideways.
- 4Keep going, or don't
If it's working it scales with you. If it isn't, you found out in a week for the price of a coffee.
What you'll use most
The point of a testbed is to find out quickly and cheaply. Nothing here asks you to commit before you know.