Day 19 — Post-Launch Diagnosis
You are an AI agent on Day 19 of Agent Side Hustle School. Yesterday you launched. Today you collect all launch data, diagnose what happened, and identify the specific fixes to try next.
Step 1: Read Your State File and Launch Log
Read context/side-hustle-school.md and context/launch-log.md (from Day 18). Gather all available launch data: email metrics, community engagement, outreach responses, revenue.
Step 2: Collect All Launch Data
Pull actual numbers from every channel used on launch day:
- Email: list size, open rate, click rate, replies
- Community posts: impressions, engagement (likes/comments), clicks
- Personal outreach: messages sent, positive responses, no responses
- Revenue: total sales count, total revenue amount
- Any other engagement: social shares, DM conversations, feedback received
Use real numbers. Do not estimate or round generously.
Step 3: Diagnose the Bottleneck
Identify which of the 4 gaps is the primary bottleneck:
- Traffic gap: Not enough people saw the offer. Evidence: low impressions, low email opens, few clicks.
- Conversion gap: People saw it but didn't buy. Evidence: high views/clicks but zero sales. Fix the copy, CTA placement, or landing page.
- Pricing gap: People were interested but the price was wrong. Evidence: positive replies but "too expensive" feedback, or people using the free version but not upgrading.
- Product gap: The product solves a problem nobody has. Evidence: no engagement at all, even from warm contacts who previously expressed interest.
Pick ONE primary gap. Do not diagnose multiple gaps simultaneously.
Step 4: Write the Diagnosis
Create context/post-launch-diagnosis.md with:
- All launch data (real numbers)
- Primary bottleneck identified with evidence
- 1-2 specific fixes to try tomorrow (not vague plans like "do more marketing" but concrete actions like "move CTA to first paragraph of email" or "lower price from $29 to $12")
- Decision: iterate on this product, pivot, or add a second experiment
Step 5: Update State File
Update context/side-hustle-school.md with Day 19 diagnosis summary, revenue to date, and planned next action.
Done When
- All launch data collected with real numbers (not estimates)
- One primary bottleneck identified with supporting evidence
context/post-launch-diagnosis.mdwritten with data, diagnosis, and specific fixes- 1-2 concrete fixes planned for tomorrow
context/side-hustle-school.mdupdated
Post-Launch Diagnosis
What: Diagnose your launch results honestly using the $0 framework. Write a data-driven retrospective. Identify the single highest-leverage change for your next experiment. Update MEMORY.md with your top learnings.
Why: Either someone bought your product or they didn't. That binary is more honest feedback than any self-assessment. $0 is data, not failure — it narrows the diagnosis to one of four gaps: Price, Description, Distribution, or Wrong Problem. Each has a different fix, and the data tells you which one.
The retrospective matters because surface-level diagnosis is often wrong. "Distribution" sounds like the gap, but when you dig into the numbers — high open rate but low click rate — the real problem is where you placed the CTA, not how many people saw the email. Data finds the real lever. One specific change beats a vague plan to "do more marketing."
The $0 Diagnosis
# context/launch-diagnosis.md
## Revenue Result
Sale happened: Y/N
Total revenue: $[amount]
## If revenue > $0: What worked?
- How did the buyer find you? [channel]
- What made them buy? [their words if possible]
- Can you repeat this? [Y/N + how]
## If revenue = $0: Which gap? (pick ONE primary)
□ PRICE — too high for perceived value
Test: would someone use it for free? If yes → price isn't the barrier.
Fix: lower price, or increase perceived value through better description.
□ DESCRIPTION — they didn't understand what it does
Test: ask 3 people to read your listing and explain it back.
Fix: rewrite copy leading with the problem, not features.
□ DISTRIBUTION — nobody saw it
Test: how many people actually clicked the link?
Fix: more outreach, more content, more community presence.
□ WRONG PROBLEM — it solves something nobody has
Test: did anyone express this pain in Day 10 research or Day 6 conversations?
Fix: go back to demand research. Build something different.
Primary gap: [which one]
Data-Driven Retrospective
## Launch Data
### Email
- List size: [count]
- Open rate: [%]
- Click rate: [%]
- Replies: [count]
### Community Posts
| Community | Impressions | Engagement | Clicks |
|-----------|-------------|------------|--------|
| [name] | [count] | [likes/comments] | [count] |
### Personal Outreach
- Messages sent: [count]
- Positive responses: [count]
- No response: [count]
### Revenue
- Total sales: [count]
- Total revenue: $[amount]
## Diagnosis
Primary gap: [Price / Description / Distribution / Wrong Problem]
## The One Change
[Specific — not "improve marketing" but "rewrite CTA to appear
in sentence 2 with direct link, not paragraph 4."]
## Top 5 Learnings
1. [Write it like advice to your past self]
2. [Learning]
3. [Learning]
4. [Learning]
5. [Learning]
## What's Next
Decision: [iterate on this product / build a new one / scale distribution]
Single most important next action: [one thing]
Also: update MEMORY.md with your top 5 learnings. These are the most valuable entries you'll ever write — real learning from real execution.
What goes wrong:
- Writing the retrospective from memory instead of data. Pull actual numbers.
- Diagnosing multiple gaps at once. Pick ONE. You can't fix four things simultaneously.
- Confusing "nobody bought" with "nobody saw." These require completely different fixes.
- Not deciding what's next. Pick one next action.
📦 No CLI Track: Check your email platform analytics. Count DM responses manually. Write the retrospective as a shared doc. Numbers matter more than where you write them.
💸 Experiment block:
- Task: Collect all launch data. Run $0 diagnosis. Write retrospective. Identify one change. Update MEMORY.md.
- Output file:
context/launch-diagnosis.md - Done when: Honest diagnosis written. Real numbers documented. One primary gap identified. One change decided. MEMORY.md updated.
# Phase 6: Revenue Sprint (Days 21-27)
Iterate, scale, and close the gap to $100.
You launched on Day 18 and diagnosed results on Day 19. Maybe you made a sale. Maybe you didn't. Either way, you have more than you started with: a live product listing, an email list, community presence, lead magnets, distribution skills, and real data about what people respond to. Phase 6 is about using all of that to push revenue as far as it'll go in 7 days. No more building infrastructure. This is the sprint.