The one-week test, and the honest no

You can find out in a week whether this is worth six months. The test is not whether people like the idea - liking costs nothing and everyone is polite. The test is whether money is already moving to solve this badly.

Days one and two: pick the room you are already in

Your advantage is not that you can code. Millions of people can code. Your advantage is knowing which annoyance in some specific world is real, constant, and worth money - and you only know that from the inside.

So list the worlds you are already inside. Not the ones you find interesting. The ones where you know the vocabulary and the seasons and who complains about what.

• A job you have had, including a boring one. Especially a boring one.
• A family business, or a friend's, where you have seen the back office.
• A sport or hobby with gear, schedules, governing bodies, or fees.
• A club, team, church, band, or society that has to organise anything repeatedly.
• A niche software product you already use, where one workflow is clearly missing.

Then, for the strongest one, write ten annoyances from memory. Ten. If you cannot get past four without inventing, you are not actually inside that world and you should pick another.

Days three and four: count the paid workarounds

Here is the whole validation idea in one line: someone paying badly for a bad solution today is worth more than a hundred compliments about your idea.

So go count. For each annoyance on your list, look for evidence that money is already leaving somebody's account because of it. What counts:

• A person paid to do it by hand - an assistant, a temp, an offshore contractor, a staff member whose Monday is this task.
• A general tool bent into shape, on a paid plan, to do a job it was not designed for.
• An existing product that does it, with public reviews complaining about specific things. A competitor is evidence, not a reason to stop.
• A spreadsheet that a salaried person maintains as part of their week. Salary is payment. It just does not look like it.
• A consultant, agency or bookkeeper doing it as a line item on an invoice.

What does not count: search volume, a subreddit thread, your own irritation, and anyone saying they would definitely use it. Those are free to say and they will happily lead you into a six-month build.

Day five: write the paragraph

One paragraph, five sentences, no jargon. This is the thing you will send to people, and writing it is where a vague idea either becomes specific or falls apart in your hands.

1. 1Who it is for, named by role and narrowed as far as you can stand: not gym owners, but the person who runs the schedule at a single-location swim school.
2. 2What job they have to get done, in their words, on some fixed rhythm - every Monday, every invoice, every new client.
3. 3What it costs them today: hours, or an error they have to fix, or the tool they pay for that does it badly.
4. 4What your thing does, in one sentence, with a verb.
5. 5What it costs to use, as a monthly number. Yes, before it exists. If you cannot say a number you are not ready to ask anyone anything.

Days six and seven: ask five people for money

Send the paragraph to five people who actually have this problem. Not five friends. Ask a direct question with a price in it, because a question with no price gets a yes that means nothing.

There are two honest asks. The first is a pre-sale: you take money now for something not built yet, with a written date and an unconditional refund if you miss it. The second is a letter of intent: they put in writing that they will pay a stated amount when it is ready. The pre-sale is stronger. The letter of intent is still miles better than a compliment.

The go / no-go

At the end of the week you have a real answer. Do not soften it.

• GO if: you found at least three cases of money already moving on this problem, and at least two people gave you a price-carrying yes - a pre-payment, or a written commitment at a stated number.
• GO if: one person pre-paid. One person paying beats five saying yes, every time.
• NO if: everyone was encouraging and nobody would name a number. Encouragement is the most common false positive there is.
• NO if: the people with the problem cannot authorise spending. A brilliant tool sold to someone with no budget is a hobby.
• NO if: you could not find a single paid workaround. That usually means the job is not painful enough to be worth money, not that you have found untouched ground.
• NO if: you did not do the week. Not doing it is also an answer, and it is the answer about whether you will do the eleven months after it.

And to be plain about it: no is a completely respectable outcome of this course, and it is the outcome for most people who read it. You spent a week and nothing else. Go do one of the faster things on Learn, get paid, and come back to this when you have money coming in and a niche you know from the inside.

If it is a go, the rest of this course is the build. It gets more specific and less philosophical from here.