Side Project Validation: Test an Idea in 2 Weeks

Side project validation means getting strangers to commit money before you spend your evenings building: twenty conversations in two weeks, then a presell. If nobody pays, you kill the project and lose a fortnight, not six months.

Most validation advice assumes you have time to waste. You do not. A side project lives on nights and weekends, so the real cost of building the wrong thing is not money, it is the only hours you had. This guide adds what other guides leave out: a time-box, a signal table and a kill rule decided before you start.

Side project validation: why evenings change the maths

The book budgets about ten to fifteen hours a week for building while employed: an hour before work, two hours after dinner, and four to six hours of deep work at weekends. That is a hard ceiling. Whatever you spend it on, you cannot spend on something else.

Here is what the wrong choice costs. In the book, a product manager we'll call Marc spent six months building a scheduling tool for freight forwarders. He never spoke to one. When he finally sent it to twenty of them, three replied, and the one who tried it wrote back that his company already used a tool bundled into its customs software. The cost: four thousand euros on tools, two hundred evenings, twenty-five weekends and most of the goodwill he had with his wife. Marc is an archetype, not a real case, and the pattern is the one the book calls the most common founder story it knows.

Marc skipped validation for the reason everyone does. It does not feel like progress. Code accumulates and features ship. Conversations leave you with a messy notebook. That feeling is wrong, because it rewards visible output over right output. Building is for after the evidence.

How to validate a startup idea in two weeks

To validate your startup idea on a side-project schedule, run the twenty-conversation sprint. The shape is simple:

1. Define one narrow buyer. "Operations leaders at logistics companies," not "small businesses." If you cannot get narrow, the idea is too vague to test.
2. Name thirty people who fit. From LinkedIn, industry communities and conference rosters. Real names, in a spreadsheet.
3. Send sixty short messages. About one in three people responds, so sixty messages get you roughly twenty conversations. Three sentences: who you are, that you are researching a problem and not selling, and a thirty-minute ask.
4. Ask about the past, never the future. How do they handle the problem now? What does it cost them? What have they already tried? Then: what would they expect to pay, and would they be one of your first ten customers? Never ask "would you use this?"
5. Log exact quotes. Your interpretation is a story your brain tells to feel better. The quote is evidence.

The full script and the five sections of each call are in How to Validate a Business Idea in 20 Conversations. If you do not want to write code at all, read Validate an Idea Without Code: The 2-Week Method. If you have only a weekend, use The 48-Hour Validation Sprint.

When you have twenty rows, read them on a Friday evening and trust the spreadsheet over your gut. Here is how to score them:

Signal	What you see in the spreadsheet	What to do
Red: kill it	Most people do not have the problem, cannot quantify its cost, or call it "interesting" but cannot say what they would pay	Stop. Start again with a different idea
Yellow: sharpen	Most have the problem, a few have tried to fix it, prices are scattered, two or three soft yeses	Ten more conversations with a tighter buyer definition
Green: presell	Most have it, can put euros or hours on it, have tried tools they do not love, prices cluster, and at least five want to be early customers	Move to the presell test
Bonus green	They already pay for something that almost solves it	The easiest sale you will make: win on your version, not on the category

The red row hides the trap. "Nice idea" sounds like validation and means the opposite: I would take it if it were free. "Nice Idea" Is a Red Flag shows how to read it, and 6 Validation Mistakes That Fake Your Market Signal covers the rest of the ways a sprint lies to you.

Test a business idea with money: your first paying customer

Conversations prove the problem is real. They do not prove your solution is. For that you need a presell: a sale before the product exists. Not a waitlist, not "I'd be interested." Money.

For a software product, that is how you land your first paying customer for a SaaS before writing any of it:

1. Take the five to ten people who said they would be early customers.
2. Build a one-page site with a clear description, a price (the book suggests about half of what you plan to charge later) and a checkout. An AI assistant can draft it in an hour.
3. Email each of them: you decided to build it, here is the page, here is the early price, delivery in eight weeks.
4. Count the payments. In the book's words, if three out of ten pay you have a business. If none do, you have data: they were polite, not customers.

For a service, skip the page. Write a one-page offer with scope, deliverables, timeline, price and terms, and send it to the three or four people who showed interest. The first paid invoice is the validation. Do it within about three weeks of the conversation, because warmth fades fast. The whole presell takes about three hours, and it is the highest-leverage thing in the book. The detail is in Pre-Sell Before You Build: The Only Validation That Counts.

Set a kill rule before the side project starts

This is the part nobody writes down, and it is why side projects drift for two years. Founders are terrible at killing their own ideas, so decide the rule while you are still objective. Write these on paper before message number one:

• No conversations. If thirty messages across different channels get you nowhere, your buyer does not care enough about the problem to give you half an hour. That is a signal, not an outreach problem.
• No pain. If most people you talk to do not have the problem, or cannot say what it costs them, stop.
• No money. If none of your ten warmest contacts pay at a presell, stop.
• A pivot is allowed, drift is not. If fifteen people keep raising a different problem unprompted, reframe and run five to ten calls on that one. Do not finish the original sprint pretending you missed it.

Killing is cheap when you do it early. The book compares a founder who kills three ideas in three months, spending about twelve hundred euros, with one who builds a single idea for six months and about forty thousand euros before it fails. The first is closer to a real business. Before you spend your first evening, read When to Kill Your Business Idea (and When to Pivot).

A four-week plan that fits a job

1. Week 1: write the buyer definition, list thirty names, send the first ten messages, write your kill rule.
2. Week 2: hold the conversations, log quotes after each, send the rest of the messages.
3. Week 3: read the spreadsheet on Friday. Red, yellow or green. If green, send the presell.
4. Week 4: count payments and apply the kill rule. Build, sharpen or stop.

Frequently asked questions

How long should side project validation take?

Two weeks for the conversations, a short time after for the presell. The book's sprint is twenty conversations in two weeks, and it can be done on nights and weekends before you write any code. If it drags beyond a month, your kill rule should have fired.

How many people do I need to talk to before I build?

Twenty is where patterns become legible. At ten conversations you can convince yourself of anything. At fifty you are only refining. Five is noise, so do not build on three optimistic calls.

Can I use my friends and family to test a business idea?

Not as evidence. Friends want you to feel good, colleagues want to be supportive, and your partner is the worst validator of all. The right people are strangers in your target market who have nothing invested in your feelings.

How do I get my first paying customer before the product exists?

Presell it. Send your warmest conversations a link to a one-page site with a price and a checkout, or an offer document for a service, and ask for payment. Money is the only signal that survives politeness.

Should I validate a side project before leaving my job?

Yes, and long before. Validation is cheap and fits around a salary, which is why the book places it first. If you are unsure how urgently you want out, take the Corporate Suffocation Index, then read The Solopreneur Revolution or join the Solopreneur Accelerator to run the sprint with a cohort.