Every other week, a founder messages me with a version of the same question. 'I have an idea. Should I build it?' And the answer I wish I could give every time is: I do not know, and neither do you, until you test it. Here is the exact two-day process I use when I want to find out whether an idea is worth building before I write a single line of code.
Saturday morning: write the pitch
Before anything else, force yourself to write a one-sentence pitch. Who is it for, what does it do, why is it better than the current workaround. If the sentence is hard to write, the idea is not ready for validation yet. Go back to the idea and sharpen it.
Then write the three sentences that would follow that pitch if you were explaining it to a friend. The problem, the solution, the moment of magic. This is the raw material for everything else in the weekend.
Saturday afternoon: build a fake landing page
Not a real one. A fake one. You can use Framer, Carrd, Notion, or Google Sites. The page has three things on it: the one-line pitch, two or three images or mockups, and an email capture that promises early access. Do not build a product. Do not even hint at a product. The whole page exists to see if anyone will give you their email in exchange for the promise.
The page should take you two or three hours. If it takes longer, you are overbuilding.
Saturday evening: decide where to send people
This is the step most founders skip, and it is the step that matters most. A landing page with no traffic teaches you nothing. You need to know, before Sunday, where you are going to find ten to fifty real potential customers. A Reddit community. A WhatsApp group. Three DMs to people you already know fit the profile. A single small ad. It does not matter which channel, it matters that you have one.
Sunday morning: send the traffic
Post in the community. DM the three people. Run the small ad. Do not write a dissertation. Share the link with one sentence of context and ask people to take a look. Nothing else. Then go make coffee.
Sunday afternoon: read the signal
By Sunday afternoon, you will have one of three signals.
Signal 1: Nobody clicked
You cannot reach this audience through the channel you picked, or the pitch does not stop the scroll. Either way, you do not know whether the idea is bad, you only know the package is not landing. Go back to the pitch.
Signal 2: People clicked but nobody gave you their email
The pitch is interesting enough to click but not interesting enough to sign up. This is the hardest signal to read. It usually means the promise is too vague, or the audience does not yet trust that you will deliver it. Tighten the pitch. Try again.
Signal 3: People gave you their email and asked follow-up questions
This is the signal you were looking for. People want the thing. Now you have a reason to build it, and you have a list of specific humans to build it for. Reply to every single email personally. Ask them what they are doing today to solve the problem. This is the most valuable information you will get for months.
What to do on Monday
“If the weekend worked, you now have something most founders never have: a list of people who said yes to the promise, before the product existed.”
If the weekend worked, talk to the first five people on the list. Then, and only then, think about building. If it did not work, do not take it personally. The weekend cost you two days and fifty dollars of ads. The alternative was building a product for three months based on a guess. You saved yourself the three months.