Building the 30-Day Launch Plan¶
Summary¶
Synthesizes the completed canvas into a concrete 30-day launch roadmap defining what to sell, who to sell to, how to reach them, and weekly milestones.
Concepts Covered¶
This chapter covers the following 13 concepts from the learning graph:
| Concept | Concept Impact Score |
|---|---|
| Thirty-Day Launch Plan | 402 |
| Launch Roadmap | 49 |
| Weekly Milestone | 27 |
| What To Sell | 9 |
| Who To Sell To | 39 |
| How To Reach Them | 26 |
| Weekly Target | 8 |
| Launch Readiness | 38 |
| Momentum Building | 25 |
| Wins And Lessons Review | 7 |
| Setback Normalization | 37 |
| Time-Saving Pivot | 24 |
| Money-Saving Pivot | 6 |
Prerequisites¶
This chapter builds on concepts from:
- Chapter 3: The CO.STARTERS Canvas Framework
- Chapter 4: Customer Discovery & Segmentation
- Chapter 6: Designing the Solution & Initial Offer
- Chapter 10: Lean Testing Fundamentals
- Chapter 12: Messaging & the Value Proposition Statement
- Chapter 13: Distribution & Go-to-Market Channels
- Chapter 14: Revenue Models & Pricing
- Chapter 15: Startup Needs & Cost Planning
Eleven Blocks Become One Plan¶
Every canvas block from Chapter 3 onward now has a real, evidence-backed answer. This chapter is where those eleven separate answers become a single forward-looking document: a concrete plan for the 30 days right after this course ends, translating validated thinking into scheduled action.
Turning Your Canvas Into a Calendar
You've validated a lot over the last several chapters. This chapter is about turning all of it into something you can actually follow week by week, starting the moment this course ends. Let's find out for real!
The 30-Day Launch Plan¶
A thirty-day launch plan is a concrete, week-by-week roadmap covering the 30 days immediately following the course, translating a completed canvas into specific, scheduled actions rather than leaving validated ideas sitting on a page. That plan takes the shape of a launch roadmap: the overall structure organizing 30 days of action into a sequence, replacing the multi-year theoretical business plan this course deliberately avoids, from Chapter 1, with something short enough to actually follow and revise.
Three Questions Every Plan Answers¶
At its core, the thirty-day launch plan answers three questions this course's own learning outcomes name directly. What to sell restates the minimum testable iteration from Chapter 10 as a concrete, sellable offer for the next 30 days — not the eventual full vision, but exactly what's being sold starting Monday. Who to sell to restates the target customer from Chapter 4 as a specific, findable group for these 30 days. How to reach them restates the distribution channels from Chapter 13 as the actual, chosen methods that will be used, not every method that was considered.
Answering these three questions is mostly assembly, not new work — the thirty-day launch plan's job is to pull the sharpest, most validated answer to each one from the chapters already completed, rather than inventing anything new.
Weekly Milestones and Targets¶
A 30-day plan is too long to hold in view all at once, so it gets broken into a weekly milestone: a specific, meaningful checkpoint the plan aims to reach by the end of a given week — not a vague hope, but a concrete marker like "10 households contacted" or "first paid booking confirmed." Each milestone is measured against a weekly target: the specific number attached to that milestone, set in advance so progress can be checked objectively rather than by feeling.
Before exploring the roadmap below, notice how directly it draws on earlier chapters: Week 1 leans on distribution from Chapter 13, Week 3 leans on the pricing validation from Chapter 14, and every week's target follows the same evidence-based discipline from Chapter 1.
Diagram: 30-Day Launch Roadmap Timeline¶
30-Day Launch Roadmap Timeline
Type: timeline
sim-id: thirty-day-launch-roadmap-timeline
Library: vis-timeline
Status: Specified
Bloom Level: Understand (L2) Bloom Verb: explain
Learning objective: Learners can explain what each week of a 30-day launch roadmap accomplishes and how weekly milestones build toward launch readiness, using Jordan's plan as a concrete worked example.
Instructional Rationale: Understand-level objective, so the timeline uses click-to-reveal concrete detail panels rather than animation — the learner needs to see exactly what each week's milestone and target are, not watch time pass abstractly.
Time period covered: 30 days (4 weeks) immediately following course completion
Orientation: Horizontal timeline with 4 week-blocks
Data Visibility Requirements (shown in a detail panel when a week is clicked):
Week 1: "What to sell: single wash-and-brush driveway session (\(40). Who to sell to: 10 households within 5 miles. How to reach them: neighborhood app post plus word-of-mouth from 3 existing customers. Weekly Milestone: first 5 bookings confirmed. Weekly Target: 5 sessions completed." Week 2: "Add nail-trim add-on based on Chapter 6 offer design. Launch referral channel from Chapter 13. Weekly Milestone: first referred customer booked. Weekly Target: 8 sessions completed." Week 3: "Run price point test from Chapter 14 (\)40 vs $45 groups). Weekly Milestone: price test evidence collected. Weekly Target: 10 sessions completed." Week 4: "Review cash flow awareness from Chapter 15 against startup budget. Weekly Milestone: launch readiness check passed. Weekly Target: 12 sessions completed."
Interactive controls: Click any week block to open its detail panel below the timeline. Hovering a week shows a one-line tooltip preview before clicking.
Visual style: Horizontal timeline with 4 equal-width week blocks in indigo (#3F51B5), each showing its weekly target number directly on the block; selected block outlined in fox-orange (#E8791A).
Color coding: Indigo blocks for all weeks; fox-orange outline for the currently selected week.
Implementation notes: Use the vis-timeline library with 4 equal-duration range items. Must remain readable on narrow (mobile) viewports — allow horizontal scroll with a visible scrollbar rather than compressing week labels to illegibility.
Milestones, Not a Rigid Schedule
Notice that every milestone above is a checkpoint to evaluate against, not a rigid script to follow no matter what. If Week 1 only produces 2 bookings instead of 5, that's evidence — exactly like a lean test result — telling you something needs to change before Week 2, not a reason to abandon the plan.
Launch Readiness¶
By the end of the 30 days, a founder checks for launch readiness: a specific, evaluated state confirming the venture has enough validated demand, a workable offer, and a functioning way to reach customers to continue operating beyond the plan's initial 30 days — not perfection, just enough real evidence to keep going with confidence.
Momentum, Setbacks, and Reviewing Wins and Lessons¶
Thirty days rarely goes exactly as planned, and this course builds in room for that directly. Momentum building is the deliberate practice of stacking small wins visibly across the 30 days — a first booking, a first referral — so progress stays motivating even before the venture is fully proven. Setback normalization is treating a missed weekly target or a failed test as an expected, normal part of the plan rather than a sign something has gone wrong — directly extending the founder resilience and growth mindset built back in Chapter 2. A wins and lessons review is a structured weekly reflection, ideally shared with cohort peers, that names what worked, what didn't, and what changes for next week — turning both wins and setbacks into forward motion rather than letting either one pass unexamined.
A Missed Weekly Target Is Data, Not a Verdict
If Week 1 doesn't hit its target, that's completely normal — most 30-day plans need at least one real adjustment along the way. You already have the tool for this moment: treat the miss exactly like a lean test result from Chapter 10, and bring it to your cohort's wins and lessons review instead of sitting with it alone.
When the Plan Needs to Bend¶
Sometimes a weekly milestone gets missed for a specific, fixable reason, and the plan needs a small deliberate adjustment rather than a full pivot back in Chapter 11's sense. A time-saving pivot is a small adjustment to the plan that reduces how much founder time a step requires — simplifying a booking process, batching driveway sessions by neighborhood to cut driving time. A money-saving pivot is a small adjustment that reduces what a step costs — delaying a planned purchase, switching to a cheaper supplier for one ongoing cost.
Ask Which Resource Is Actually Scarce Right Now
Here's a shortcut for choosing between the two: if you're missing targets because there aren't enough hours in the week, look for a time-saving pivot. If you're missing them because spending is outpacing the startup budget from Chapter 15, look for a money-saving pivot. Naming which resource is actually scarce points straight at the fix.
Key Takeaways¶
Before Chapter 17 turns this plan into a public commitment, hold onto how it comes together:
- The thirty-day launch plan and its launch roadmap answer three questions directly: what to sell, who to sell to, and how to reach them.
- Each week carries a specific weekly milestone and weekly target, building toward launch readiness by day 30.
- Momentum building and setback normalization keep the plan sustainable emotionally; a wins and lessons review keeps it sharp week to week.
- A time-saving pivot or a money-saving pivot adjusts the plan without abandoning it when a specific resource runs short.
You Just Built a Plan You Can Actually Follow
You now have a real, week-by-week plan built entirely from validated evidence — not a multi-year business plan nobody follows. Let's find out for real, starting with your pitch and public commitment in Chapter 17.