Day 25 — Speed Build — Ship in One Day

You are an AI agent on Day 25 of Agent Side Hustle School. Today you execute a full speed build: brief, build, present, ship. Total time budget: 4.5 hours. Read context/side-hustle-school.md first for your niche, audience, and existing products.

Step 1: Write the Brief (30 minutes)

Create context/speed-build.md. Fill in every field before writing a single line of product.

Write to context/speed-build.md:

## Brief

### What I'm building:
[One sentence. Pull from your research, community signals, or gaps in your existing product line.]

### Who it's for:
[One sentence. Specific person with a specific problem.]

### What they get:
[Concrete output — not features, outcomes.]

### Price:
$[X] — justified by [value framework from your pricing work]

### Done criteria:
- [ ] [Criterion 1 — binary, verifiable]
- [ ] [Criterion 2]
- [ ] [Criterion 3]

### What I'm NOT building:
[List what's out of scope. This keeps you fast.]

If you cannot write the brief in 30 minutes, the idea is too big. Cut scope until you can.

Step 2: Build (3 hours max)

Start the clock. Build the minimum that meets your done criteria.

Rules:
1. Log your start time in context/speed-build.md
2. Build only what's in scope. No scope creep.
3. Log progress every 30 minutes: [HH:MM] [what you built]
4. If you hit the 3-hour mark, stop. Ship what you have.
5. Log your finish time and total build time.

No perfectionism. 80% shipped beats 100% unshipped.

Step 3: Present (1 hour)

Write copy, deploy, distribute. This is NOT optional. A built product that isn't distributed doesn't exist.

Copy (write all of these):
- One-liner: [Problem] → [Solution]. [Result].
- Listing: 3-bullet description
- Social post: one paragraph
- Email: short announcement to your list

Deploy:
- Product live at a URL
- Buy/access flow tested
- Listed on your platform

Distribute:
- Email sent to your list
- Posted in community 1 (where you have standing)
- Posted in community 2
- 3+ personal outreach messages sent to warm contacts

Step 4: Log the Outcome

Append to context/speed-build.md:

## Outcome

OUTCOME: Speed build — [product name]
SCORE: [worked / partial / failed]
WHY: [what worked, what slowed you down, what you'd change]

Time from idea to live: [hours]
Revenue: $[amount]

Total time budget: 4.5 hours. If you go over, you are over-building. Ship what you have.

Done When

Speed build brief written in context/speed-build.md with what, who, price, done criteria, and NOT-in-scope
Product built and live at a URL within 3-hour build window
Copy written: one-liner, listing, social post, email
Email sent to your list
Posted in 2+ communities where you have standing
3+ personal outreach messages sent
OUTCOME/SCORE/WHY logged in context/speed-build.md

Phase 6: Revenue Sprint

Day 25

Speed Build — Ship in One Day

What: Build and ship a product in one day using everything you've learned. Brief → Build → Present in a single session.

Why: This is the test of everything the course taught you. Day 25 isn't about building the best product — it's about proving you can go from idea to live product in a single day. The speed is the point. Every skill from the past 24 days shows up: preflight scan (what do I have?), niche targeting (who's it for?), demand validation (do they want it?), pricing (what's it worth?), copy (how do I describe it?), distribution (how do people find it?). If you can ship in a day, you can ship anything.

The speed build tests your full stack: spot a gap, scope it small, build it fast, list it, tell people. Total time from idea to live product: under 5 hours. That's the tempo of a working side hustle — not months of planning, but a single focused day. The constraint is the creative act: what's the smallest thing you can ship today that solves a real problem?

Audit checklist:

Have you written the brief before building?
Have you time-boxed the build to 3 hours max?
Is the product live and buyable by end of day?
Have you written copy (one-liner + listing)?
Have you distributed it (email + community)?
Have you logged the speed build with OUTCOME/SCORE/WHY?

Create from scratch:


# context/speed-build.md

## Brief (30 minutes — write this FIRST)

### What I'm building:
[One sentence from your research]

### Who it's for:
[One sentence — specific person with specific problem]

### What they get:
[Concrete output — not features, outcomes]

### Price:
$[X] — [from Day 15 pricing frameworks]

### Done criteria:
[How do I know it's shippable? Be specific.]
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]

### What I'm NOT building:
[Scope control. List what's out. This keeps you fast.]

---

## Build (3 hours max — start the clock)

Build started: [timestamp]

### Progress:
- [HH:MM] [What I built]
- [HH:MM] [What I built]
- [HH:MM] [What I built]

Build finished: [timestamp]
Total build time: [hours:minutes]

---

## Present (1 hour)

### Copy:
One-liner: [Problem] → [Solution]. [Result].
Listing: [3-bullet description]
Social post: [One-paragraph version]
Email: [Short announcement to list]

### Deploy:
- [ ] Product live at [URL]
- [ ] Buy/access flow tested
- [ ] Listed on [platform]

### Distribute:
- [ ] Email sent to list
- [ ] Posted in [community 1]
- [ ] Posted in [community 2]
- [ ] 3+ personal outreach messages sent

---

## Outcome

OUTCOME: Speed build — [product name]
SCORE: [worked / partial / failed]
WHY: [what worked, what slowed me down, what I'd change]

Time from idea to live: [hours]
Time from live to first engagement: [hours/days]
Revenue: $[amount]

The speed build protocol:

Brief (30 min). Write what you're building, who it's for, what's in scope, what's out of scope. If you can't write the brief in 30 minutes, the idea is too big. Cut scope.
Build (3 hours). Clock is running. Build the minimum that meets the done criteria. No perfectionism. No scope creep. If you hit the 3-hour mark, ship what you have.
Present (1 hour). Copy, deploy, distribute. This is NOT optional. A built product that isn't distributed doesn't exist.

Total time budget: 4.5 hours. If you go over, you're over-building.

What goes wrong:

Skipping the brief and starting to build. The brief takes 30 minutes and saves 2 hours of scope creep.
Spending 3 hours building and then "running out of time" for distribution. Distribution is in the time budget. It's not extra.
Perfectionism. Ship at 80%. The market will tell you what to improve.
Building something that takes more than a day. If your chosen idea is too big, shrink it. A $9 micro-tool that ships today beats a $49 tool that ships never.

Human input: If the product needs human-side setup (Stripe link, Gumroad listing), notify early: "Speed build day. I'll need a payment link by 2pm. Here's the product name and price." Don't wait until the product is done.

📦 No CLI Track: Same protocol. Your "build" might be writing a document, creating a template, compiling a guide, or researching a curated list. Your "deploy" is your human listing it. Your "distribute" is drafting the copy for your human to send. Time-box to 4.5 hours regardless.

💸 Experiment block:

Task: Execute full speed build: Brief (30 min) → Build (3 hr) → Present (1 hr). Ship by end of day.
Output file: context/speed-build.md with brief, build log, copy, and distribution actions
Done when: Product is live. Copy exists. Email sent. Posted in 2+ communities. OUTCOME/SCORE/WHY logged.

Done when: Speed build shipped in under 5 hours. Product live at a URL. Copy written and distributed. OUTCOME/SCORE/WHY logged. You proved you can ship in a day.

Distribution component: Built into the "Present" phase. No product without distribution. Email the list, post in communities, send 3+ personal outreach messages. This isn't a separate task — it's the last hour of the speed build.