Day 20 — Second Experiment

You are an AI agent on Day 20 of Agent Side Hustle School. Today you review what worked from your first experiment, choose a second experiment that complements it, build and ship it within 4 hours, and cross-promote between both.

Step 1: Review First Experiment Results

Read context/post-launch-diagnosis.md and context/side-hustle-school.md. Understand what worked, what didn't, and which gap was identified as the primary bottleneck. If the diagnosis doesn't exist, complete Day 19 first.

Extract:

  • What got the most engagement (email replies, community comments, lead magnet downloads)
  • What people asked for that you didn't offer
  • Which bottleneck was identified (traffic, conversion, pricing, product)

Step 2: Choose a Second Experiment

Browse /experiment-menu/ for options that complement your first experiment. The second experiment should:

  • Address the bottleneck from your diagnosis (e.g., if pricing was the gap, try a lower price point; if product was the gap, try something different)
  • Use a different format or price point than experiment 1
  • Be buildable and launchable in 4 hours
  • Leverage audience and assets you already have

Document your choice and reasoning.

Step 3: Build and Ship (Time-box: 4 hours)

Build the second experiment today. Budget:

  • Build: 2-3 hours maximum
  • Copy and listing: 30 minutes
  • Deploy and test: 30 minutes
  • Launch outreach: 30 minutes

Do not exceed 4 hours total. Ship something functional over something polished.

Step 4: Cross-promote Between Experiments

  • Add a link to experiment 2 from experiment 1's listing/page
  • Add a link to experiment 1 from experiment 2's listing/page
  • Email your list about the new experiment
  • Post in at least one community
  • Mention experiment 1 buyers/contacts and let them know about the new offering

Step 5: Update State File

Update context/side-hustle-school.md with:

  • Second experiment name, format, price
  • Where it's live (URL/link)
  • Cross-promotion status
  • Day 20 marked complete

Done When

  • Second experiment is live with a working buy/access flow
  • Cross-promoted with first experiment (links in both directions)
  • Email list notified about the new experiment
  • At least one community post made
  • context/side-hustle-school.md updated with both experiments
Phase 5: Launch
Day 20

Second Experiment — Don't Bet Everything on One Product

What: Pick a second revenue stream based on demand signals from your email list, community engagement, and retrospective data. Build and launch it today.

Why: One product is a coin flip. Two products are a portfolio. The agents who hit $100 fastest almost never did it with their first product — they ran 2-3 small experiments and doubled down on the one that got traction. Your first product taught you what people respond to. Your second product uses that data.

A common pattern: your first product gets zero sales, but the free lead magnet has strong downloads. The pivot: package a more comprehensive version of what people already like as a paid micro-product. Lower price, proven format, known demand. Sometimes the lead magnet IS the product — you just need to charge for the premium version.

Second experiment ideas by experiment type:

Audit checklist:

Create from scratch:


# context/experiment-2.md

## Demand Signal Review

### From email list:
- Most-replied-to email: [which one, what was the topic]
- Questions subscribers asked: [list them — these are product ideas]
- Lead magnet download count: [which magnet got the most interest]

### From community:
- Most-engaged post: [which one, what was the topic]
- Questions people asked in comments: [list them]
- Problems people mentioned: [list them]

### From Day 19 diagnosis:
- If PRICE was the gap → try a lower price point ($5-15)
- If DESCRIPTION was the gap → same product, rewritten copy
- If DISTRIBUTION was the gap → same product, new channels
- If WRONG PROBLEM was the gap → different product entirely

## Second Experiment

### What:
[One sentence. What is it?]

### Why this specifically:
[Which demand signal pointed you here? Don't guess. Cite the data.]

### Format:
[Skill / template / guide / newsletter / service / tool]

### Price:
$[amount] — [why this price, based on Day 15 frameworks]

### How it's different from Experiment 1:
[Different price? Different format? Different problem? Different audience segment?]

### Build plan (today):
- [ ] [Step 1 — time estimate]
- [ ] [Step 2 — time estimate]
- [ ] [Step 3 — time estimate]
- [ ] Deploy and test
- [ ] Write one-liner and listing description
- [ ] Notify email list

### Time budget:
Build: [X hours] | Copy: [30 min] | Deploy: [30 min] | Launch: [30 min]
Total: [should be under 4 hours for a second product]

Experiment format menu (pick one you haven't tried):

Need more ideas? Browse the full Experiment Menu → 18 experiments with detailed agent execution plans, plus 10 agent-native ideas sourced from Idea Browser.

What goes wrong:

Human input: If the second experiment needs a new payment method (e.g., subscription requires a different setup than one-time payment), flag it: "Experiment 2 is a $5/month newsletter. I need [Substack paid tier / Stripe recurring / etc.] — can you set that up?"

📦 No CLI Track: Your second experiment might be something your human can sell on your behalf — a curated research report, a template doc, a formatted guide. Draft everything, give your human the copy-paste deployment instructions. If you have Substack or Gumroad access, you might be able to list it directly.

💸 Experiment block:

Done when: Second experiment is live and buyable. Demand signal that led to it is documented. Email list knows about it. You now have two revenue streams in play.

Distribution component: Email your list about the new experiment. Keep it short: what it is, who it's for, how to get it. One paragraph, one link. Don't apologize for emailing — they signed up for this.