Non-technical founders ask me roughly the same question: "I have an idea. I want to launch in three months. What do I do?" Here's the 90-day playbook I've seen work most often. Not theory, the actual sequence that takes a real idea to a real launch.
Days 1–14: Understand the problem
You don't write code in week one. You don't write a brief in week one. You spend two weeks doing the work that tells you whether the rest of the 90 days is worth running.
- Talk to 20 potential users (the 20-conversation rule). Take notes verbatim.
- Map the existing alternatives. What do your potential users do today? Spreadsheets? A different SaaS? Nothing?
- Write a one-page problem statement. Who, what pain, what triggers them to look for a solution.
If at the end of two weeks you can't write that one page convincingly, stop. Don't move to week 3 until the problem is clear.
Days 15–28: Decide what you're building
Not how. What.
- Write a one-page solution sketch, five core flows, in plain English. No screens, no tech.
- Run it past 5–10 of your conversations from days 1–14. Does it match what they described?
- Cut ruthlessly. Use the cut-list framework. Aim for 30–40% of your original scope.
- Decide: web app, mobile app, or both? Most non-technical founders should start with responsive web. Mobile is a $30k decision; defer it unless it's mandatory.
Days 29–35: Get your three quotes
Now you can hire.
- Write a two-page brief (using the brief template).
- Get quotes from three vetted developers. FindDevs is exactly this service; do it elsewhere if you prefer, but get three.
- Run the quote-reading playbook on each. Pick on judgement, not just price.
- Sign the contract by end of day 35.
If you can't get three quotes in a week, your brief is too vague. Tighten it.
Your job in the first 35 days is not to build software. It's to know exactly what software is worth building.
Days 36–49: Discovery sprint
Most senior developers will start with a one-week paid discovery sprint. You should welcome this, it's where the real scope gets locked.
- Workshops to map the data model and key flows.
- Figma prototypes you can click through.
- A revised written scope and a fixed price for phase one.
- Your job: be available, decide quickly, push back where you disagree.
Days 50–77: Build phase one
Four weeks of build, two-week sprints, weekly demos.
- Show up to every demo. Test the working software yourself; don't wait for QA.
- File issues with screenshots and short videos. "Doesn't work" is useless feedback.
- Resist scope creep, yours. The biggest schedule risk on most projects is the founder adding "just one more thing" every Friday.
- Start your launch list now. Email list, ads, PR contacts, beta users from your day-1–14 conversations.
Days 78–84: Beta
The most useful week of the build.
- Get 5–20 real users on staging. Watch them use it. Don't help them.
- File the issues that emerge. Triage to "must fix before launch" vs "v1.1."
- Write the launch copy if you haven't already.
- Pre-line up the first 10 paying customers from your day-1–14 conversations.
Days 85–90: Launch
The release week. Plan for it; don't let it happen to you.
- Stage the launch: friends and family week, beta week, public launch.
- Write the launch tweet/post the night before, not the morning of.
- Have your developer on call for the first 48 hours. Things break.
- Email every one of your day-1–14 conversations. They're your first ambassadors.
What you should not do in the first 90 days
- Hire a designer separately if your developer has design covered. One throat to choke is better than two on a fast project.
- Build the second feature before the first is shipped.
- Start a podcast about your startup.
- Raise venture capital. If you're not yet shipping, you're not yet investable.
- Hire a marketer. Founder-led marketing on day one beats agency-led marketing on day 30.
The bottom line
Two weeks understanding the problem. Two weeks deciding what to build. One week hiring. Two weeks discovery. Four weeks building. One week beta. One week launch. That's 90 days, well spent.
If you want three vetted Australian developers ready to start your build by day 35, FindDevs gets you those quotes. Free, in 24 hours.