The first 90 days plan, week by week: validate in weeks 1-2, build in 3-6, launch in week 10, grow from week 11 - on 10-15 hours a week, still employed.
Your first 90 days as a solopreneur run on a five-phase plan: validate (weeks 1–2), build (weeks 3–6), start the acquisition engine (weeks 7–8), launch (weeks 9–10), and set the growth rhythm (weeks 11–12) — ten to fifteen hours a week, while still employed. Your corporate salary funds the experiment. Nothing about your day job changes.
The plan starts the Monday after you decide. Not "soon." Not "when the timing is right." Pick the date, write it on a calendar where you can see it, and come back to the current week every Monday morning. Adjust where reality differs from the plan — it always does — but don't abandon the structure. The structure is the leverage.
The 13-week plan at a glance
| Week | Focus | Success looks like |
|---|---|---|
| 1 | Define your customer + outreach | 30 messages out, 5–10 responses, 2–4 calls booked |
| 2 | Validation calls | 10–15 conversations, a clear signal, 3+ would-be early customers |
| 3 | Architecture (or offer doc) | Database and service design on paper — no code yet |
| 4 | First feature (or delivery design) | Users can sign up and log in |
| 5 | Core feature (or client systems) | The thing your product is fundamentally about works |
| 6 | Billing and polish (or soft sales) | A chargeable MVP in production |
| 7 | Acquisition foundation | Newsletter live, landing page up, positioning sentence set |
| 8 | Content rhythm | 30–200 subscribers, two newsletters published |
| 9 | Pre-launch | Launch post written, assets tested, weekend soft launch |
| 10 | Launch | 5–100 paying customers, or 1–3 client conversations |
| 11 | Dashboard and lever | Five-metric dashboard live, first experiment running |
| 12 | Rhythm | Weekly cadence in motion — the business is real |
Week 13 isn't on the plan because the plan ends at twelve weeks. What week 13 looks like — and every week after — is at the bottom.
Phase 1: validate before you build (weeks 1–2)
Week one is definition and outreach. Monday, write the narrow definition of your target customer — not "small business owners" but "founders of B2B SaaS companies between ten and fifty employees in DACH region." Tuesday, build a list of thirty people who fit it. Wednesday to Friday, send ten three-sentence outreach messages a day: who you are, what you're researching, the thirty-minute ask.
Week two is conversations — aim for twelve to fifteen, thirty minutes each, logged immediately. At the end of the week, read the spreadsheet top to bottom and call the signal: red light (the problem isn't real, urgent, or payable — kill it, start next Monday with a new idea), yellow light (something's there but fuzzy — five more conversations with a tighter definition), or green light (the pattern is clear and at least three people said they want to be early customers). The full interview method is in how to validate a business idea.
Phase 2: build the smallest chargeable thing (weeks 3–6)
This phase splits by track. On the software track: week 3 is architecture only — entities, relationships, service boundaries, your three most important user flows walked through on paper. Week 4 is signup and authentication. Week 5 is the core feature that delivers your product's value. Week 6 is Stripe, the pricing page, and polish, until you'd be willing to charge for it. Success: a working MVP handling signup, the core action, and billing, deployed behind a coming-soon page.
On the service track: week 3 is the one-page offer doc (who it's for, what problem, deliverables, timeline, price). Week 4 is delivery design — onboarding, monthly rhythm, templates. Week 5 is infrastructure: scheduling, payments, a one-page contract. Week 6 is soft sales conversations with the three or four validation-call people who said they wanted to work with you. Success: a tight offer doc and two to four active sales conversations.
Phase 3: the acquisition engine (weeks 7–8)
These two weeks can run in parallel with the end of the build if you're moving fast — but they are not optional. The acquisition engine has to be live by the time the product is ready, or the product launches into silence.
Week 7: launch your newsletter (first issue: five hundred words, one insight from your build journey), put up a landing page (headline, paragraph, email signup — about three hours), join three communities where your customers hang out, and write your positioning sentence: specific buyer, specific problem, specific promise. Week 8: second newsletter, two LinkedIn posts, two useful community contributions with no promotion, and a three-email nurture sequence. Success: thirty to two hundred subscribers and a content rhythm in motion. This is the same engine behind getting your first 10 customers.
Phases 4 and 5: launch, then set the rhythm (weeks 9–12)
Week 9 is pre-launch: announce the date, spend two hours writing the launch post (hook, context, what you built, proof, call to action — under five hundred words), test the checkout and welcome email yourself, and personally reach out to ten people who could amplify it. Soft launch to your presell list on the weekend. Week 10 is launch: publish Monday, engage with every comment — the first hour is critical — and ship the first improvement by Friday. Success is somewhere between five and a hundred paying customers (software) or one to three new clients in active conversations (service). The day-by-day script is the launch week playbook.
Week 11: set up your five-metric dashboard — acquisition, activation, retention, revenue, referral (the SaaS metrics that matter) — then pick your single top growth lever and run your first ICE-scored, two-week growth experiment, documenting the prediction before you run it so you can't fool yourself later. Week 12: the standard cadence — Monday review, Tuesday prioritize, Wednesday and Thursday build, Friday ship, weekend off.
If you're behind the plan
You will fall behind in at least one phase. Everyone does. The triage:
- Validation runs long: fine. Take a third week of conversations. An extra week of validation is cheap; building the wrong thing is enormous.
- Build runs long: acceptable — your scope was too ambitious. If it's week six and the MVP isn't done, you have too many features, not too little time. Cut.
- Acquisition engine behind: dangerous. If you're at week seven with no newsletter and no community presence, push the launch by two weeks and start the content rhythm now. A delayed launch into a small audience beats an on-time launch into no audience.
- Launch underperforms: expected, often. The real launch isn't the day; it's the six-month iteration that follows. Measure month-three numbers, not launch-day numbers.
- You miss a week entirely: human. Don't double-work the next week — that's the burnout path. Just resume. Twelve weeks is the optimistic timeline; many founders take fifteen or eighteen. The outcome is the same as long as the rhythm continues.
What you hold at day 90
By the end of week 13: a validated hypothesis backed by twenty conversations, a live product or service with three to fifty paying customers, an acquisition engine on at least two channels, a dashboard you check every Monday, and a weekly rhythm you can sustain indefinitely. Most importantly, proof — proof that the version of you who didn't believe this was possible was wrong.
Then run the week-13 rhythm — three priorities: one product, one content, one relationship; ship Friday; genuinely rest on the weekend — every week for the next twelve months. The founders who keep the rhythm clean for fifty-two weeks are the ones who, somewhere around month ten, look up and realize they've replaced their corporate income. The plan is twelve weeks. The discipline is permanent.
Frequently asked questions
How many hours a week does the 90-day plan take?
Ten to fifteen hours per week, mostly evenings and weekends. You stay employed through the entire ninety days — the corporate salary funds the experiment, and nothing about your day job changes.
Do I need to quit my job to run the plan?
No — the plan is designed for the opposite. You build while employed and let revenue, not frustration, decide when quitting becomes a real question. That question typically arrives after the plan, once weekly iteration compounds into real income.
What if I fall behind schedule?
Expect to. Twelve weeks is the optimistic timeline; many founders take fifteen or eighteen weeks, and the outcome is the same as long as the rhythm continues. The one dangerous delay is the acquisition engine — if it's not live by launch, push the launch two weeks rather than launch into silence.
What results should I expect after 90 days?
A validated hypothesis from twenty conversations, three to fifty paying customers (software) or one to three clients in active conversations (service), an audience on two channels, a five-metric dashboard, and a sustainable weekly rhythm. Not a finished business — the entry point to one.