Free challenge · 48 hours
Build one useful tool in 48 hours
From one annoying task to a small tool on a public address that strangers can use without you. Seven steps, hour by hour.
- Hours 0–2 Pick the irritation
- Hours 2–4 Reduce the flow
- Hours 4–8 Choose the stack
- Hours 8–24 Build the useful path
- Hours 24–34 Make it explain itself
- Hours 34–42 Test it on a stranger
- Hours 42–48 Publish and ask
- Finish line A tool on a public address that does one job from start to finish
At the finish line, you have
Not notes about a plan: things that exist, that you can show.
- A tool on a public address that does one job from start to finish
- One sentence that tells a stranger what it does
- One real person who used it without your help
- Five people who have seen it, and their answer to one question
Ideas die in the notes app
Not because they are bad. Because “someday” has no end, so nothing ever gets cut, so the first version keeps growing until it is too big to finish on an evening. Then the next idea arrives.
A tool is the smallest thing you can finish: one input, one action, one result. Most of the free tools on this site started as an irritation I had on a Tuesday and were online by the weekend.
Why 48 hours
A fixed end forces the useful decisions early. You cut accounts, settings and dashboards because there is no time for them, and you discover that nobody missed them. You show it to a stranger because the clock says so, not when you feel ready.
How it works
Seven steps, each tied to a block of the 48 hours. Each step is a short read and a checklist. Tick everything and move on; if a box will not tick, that is the part to fix before going further.
At the end you have a tool on a public address, one person who used it without you, and five answers to the question that matters: what stopped this from being immediately useful?
The plan, step by step
Each step is a short read and a checklist. Tick everything, then move on.
- Step 1Hours 0–2 Read it now
Pick the irritation
Write the problem in one sentence, find three real examples of it, and decide who feels it and what a useful result looks like.
Done when: the problem written in one sentence; three real examples collected; the person who feels it, named; the useful result, described.
- Step 2Hours 2–4
Reduce the flow
One input, one action, one result. Remove accounts, dashboards, settings and anything that does not change the outcome.
Done when: the input written down; the action written down; the result written down; a list of what you will not build.
- Step 3Hours 4–8
Choose the stack
Prefer tools you already know. Decide what runs in the browser, what needs a server, and put an empty page on a stable address.
Done when: stack chosen from what you already know; an empty page live on its final address.
- Step 4Hours 8–24
Build the useful path
Make input, action and result work from start to finish, with your three real examples. Ignore polish until then.
Done when: input, action and result work from start to finish; the three real examples go through.
- Step 5Hours 24–34
Make it explain itself
The shortest possible explanation, then labels, empty states, errors, the keyboard, the phone and the first thirty seconds.
Done when: one sentence at the top says what it does; empty state and errors written in plain words; works on a phone; works with the keyboard alone.
- Step 6Hours 34–42
Test it on a stranger
Give it to one person without explaining it. Watch where they hesitate, and fix that before adding anything.
Done when: one person used it without an explanation; every hesitation written down; the worst one fixed.
- Step 7Hours 42–48
Publish and ask
A stable address, a tiny way to send feedback, five people who should see it, and one question for them.
Done when: live on its final address; a feedback link on the page; sent to five people; their answers written down.
It's for you if you are
- Developers whose ideas never leave the notes app
- Designers and product people who want to ship something of their own
- Anyone who wants proof they can finish before starting something bigger
It's not for
- Startups looking for a roadmap
- Tools that need accounts, payments or a team in their first version
Written by Ben Morin. I design, build and run software on my own: a platform for independent bike shops, lyric films for songwriters, a private journal that becomes a book, a planner, and a handful of free tools. These steps are the ones I follow.
Questions
Is it really free?
Yes. Leave your email address and every step opens. That address gets a link to open the challenge on your other devices, and nothing else unless you tick the box.
Do I need to know how to code?
Enough to build a small web page, alone or with an AI assistant. The steps are about decisions, not about a particular language or framework.
Forty-eight hours in a row?
No. The hours are a budget, not a clock. A weekend works; so do four evenings and a Saturday. What matters is that the end is fixed before you start.
What kind of tool?
Something that turns one input into one useful result. Look at the free tools on this site for the size: none of them needs an account, and each does one thing.
Where is my progress saved?
In your browser, on your device. Nothing about your tool or your answers is sent anywhere.
Free · 48 hours from now
Set the end date, then start.
A tool on a public address that does one job from start to finish.