Mar 16 — Apr 19
Fix critical bugs. Build go-live requirements (A/B testing, support chat, payment flows, ToS). Stand up Mac Mini with Marco and Sentry. Prep remaining department configs. Build Launchomation landing page using Launchomation.
WK 1-2
All P0 bugs fixed — domain pricing, Stripe wiring, budget display, God Mode, Deliver auth
WK 2
Mac Mini live. Marco + Sentry operational. — first two departments running
WK 2+
Sentry running daily platform test sweeps — catching regressions on every fix
WK 2-4
Go-live requirements built — A/B testing, credit card capture, support chat, grace period billing, ToS
WK 4
Launchomation.com landing page built BY Launchomation
WK 5
Department 3-9 configs prepped — ready to flip on at launch
WK 5
Folder structure + naming convention for raw footage established
WK 5
Zero-error end-to-end. Platform is public-release ready.
Apr 20 — May 3
Open the door. Promotion decoupled from launch — the door is open, no blast. Firefight what real users find. Flip on the squad. Start white-glove betas Week 7.
WK 6
Launchomation.com goes live to the public
WK 6
Blaze, Scout, Ace, Kip activated — departments 3-6 online
WK 6
Kip begins transcribing and cataloging every recording from day one
WK 6
Scout begins organic channel testing — Reddit, Twitter/X, Facebook groups, SEO
WK 6
Tim calls UCR contact — 3-4 month lead time for September
WK 7
White-glove beta launches begin — Claire, Vaka, Hollister, HowManyTeeth
WK 7
Blaze attempts first autonomous launches — validating the end-to-end flow
WK 7
Ace begins monitoring launched businesses — first proactive recommendations
May 4 — Jun 14
Stand up Dash, Nash, Sage, Rex. All 10 departments running with daily standup. Build proof assets. Start earning visibility. Collect real data across all channels.
WK 8-9
Dash, Nash, Sage, Rex activated — all 10 departments operational
WK 9
Daily standup running — Marco coordinating full squad
WK 8+
Dash running weekly outreach to event organizers, podcasts, and HARO
WK 9+
Nash researching and contacting universities, SCORE chapters, foundations
WK 9+
Sage producing weekly intelligence briefs — competitive monitoring, financial tracking
WK 9+
Blaze running launches consistently — testing replicable ideas, building Idea Kit pipeline
WK 10
First hero case studies produced — WrestleBetter, Manapuna Meats, early launches
WK 11
First paid ads to launchomation.com — proof assets now exist to back them up
WK 11+
Kip managing full content queue — producing weekly, approve-and-post from phone
WK 11
First free visibility event delivered — SCORE chapter, SBDC workshop, or co-working space
WK 12
YouTube channel live. Content flywheel producing weekly.
◆
Tim checkpoint #1 (Week 13) — Real data from 7+ weeks of operations. Conversion rates, acquisition channels, launch count, early revenue, squad activity reports. Sage has the full brief.
Jun 15 — Aug 9
Interns arrive. AWI show launches. Stress-test Launchathons. Collect the data that resolves every open question. Hosting auto-bills start hitting.
WK 14
EFTA interns arrive — 5-15 interns, 100% Launchomation
WK 14
"Another Worthless Idea" show launches — batch of 3-5 episodes from stockpiled footage
WK 14+
Nash advancing partnership conversations — university pipeline building, Chris Koerner prep
WK 14+
Dash continuing outreach for visibility opportunities — stages, podcasts, media
WK 15-16
Intern stress tests — 15 ideas launching simultaneously through the platform
WK 16
First public Launchathon — 15-30 people, free, film everything
WK 17
Post-event data captured — hosting %, domain %, ad %, revenue curve, success rate
WK 18-20
Additional Launchathons — iterate format, test different approaches
WK 19
First hosting auto-bills trigger — 30-day grace from Week 6 launches expires
WK 20
Launchathon run without JG — intern or ambassador facilitates
WK 15
20+ total launches through the platform
◆
Tim checkpoint #2 (Week 21) — The big one. Every open question answered with data: grace period, paywall placement, Launchathon economics, unit economics, partnership pipeline status. Sage has 15+ weeks of numbers.
Aug 10 — Sep 27
Continue local Launchathons informed by data. Activate partnership pipeline. Chris Koerner formal pitch. UCR flagship event. The system starts running without JG in the day-to-day.
WK 22+
Local Launchathons continue — format and frequency informed by Phase 2 data
WK 22+
Nash activating warm pipeline contacts — universities, SCORE, foundations responding to outreach
WK 22+
Blaze continuing launch velocity — proven ideas feeding Idea Kit pipeline
WK 22+
Sage producing Tim-ready reports on demand — full financial picture, unit economics, projections
WK 23
Chris Koerner formal partnership pitch — Nash has full prep: content history, live demos, proposal
WK 24
UCR logistics locked — venue, date, department buy-in
WK 27-28
UCR Launchathon — the flagship university event
Where we are at week 28
PROVEN
The model works. The data proves it. The path to 1,000 customers is clear.
DATA
Every question answered
PIPELINE
Partners ready to activate
What the data unlocks
MONTH 8-10
Replicate locally. Take the proven Launchathon format and run it at partner locations — SCORE chapters, SBDCs, co-working spaces — that Nash has already been building relationships with. Each new location means new launches, new hosting revenue, new rev share.
MONTH 10-12
First cities beyond home base. Use the Launchathon playbook and partnership pipeline to run events in 2-3 new cities. Licensed event model — trained facilitators running the Launchomation format, similar to how Techstars or MLH chapters operate.
MONTH 12-18
Idea Kits at scale. By now Blaze has tested hundreds of ideas. The proven winners become $250 kits that anyone can buy and launch in their own market. Each buyer is a new $25/month hosting customer plus 3% rev share. This is the compounding engine.
YEAR 2-3
National scale. 3,000+ organizations in the US have entrepreneurship budgets and charters. Nash has been building that pipeline since Week 9. The question isn't whether the demand exists — it's how fast we can serve it with a proven model.
Every step above depends on the data we collect in the first 28 weeks. We don't assume any of this — we earn it by proving each phase before moving to the next.