Docs
Episode 000 — I'm Building 100 Startups in 100 Days
The launch video for the 100 Startups Challenge. Full script, target audience, recording plan and YouTube metadata.
Episode 000
I'm Building 100 Startups in 100 Days (Here's Why)
Type: Channel trailer / Manifesto Target length: 6–8 minutes Status: Planned
Summary
This is not a build video. It is the foundation video — the one that explains who you are, what the challenge is, why it exists, and what viewers can expect from the channel.
Every future subscriber will likely watch this video first. It needs to answer four questions immediately:
- What is this channel?
- Who is this person?
- Why should I care?
- What do I get if I subscribe?
The tone should be honest, direct, and slightly raw. No polish. No hype. No corporate intro music.
Target Audience
Primary audience
Developers and engineers who want to ship more
- Age 25–40
- Working in software, either employed or freelancing
- Has ideas but struggles to execute fast enough
- Watches content on productivity, indie hacking, and building
- Follows creators like Theo, Fireship, Pieter Levels, Levels.io, Marc Lou
Secondary audience
Aspiring indie hackers and solo founders
- Wants to build a product but hasn't started yet
- Looking for proof that one person can ship real products fast
- Motivated by the challenge format — wants to watch someone do what they haven't done yet
What they are searching for
- How to build a startup fast
- Build in public channels
- Solo founder daily vlog
- Indie hacker challenge
- 100 days challenge developer
- Ship faster as a developer
Why they subscribe
They subscribe because they recognise the problem you describe — knowing how to build but not shipping fast enough. The personal honesty makes it feel real. The 100-day structure gives them a reason to keep coming back.
YouTube Metadata
Title options
I'm Building 100 Startups in 100 Days (Here's Why)
100 Startups in 100 Days — Day Zero
I Challenged Myself to Ship 100 Startups. This Is Day Zero.
Why I'm Building 100 Startups in 100 Days as a Solo Developer
Recommended:I'm Building 100 Startups in 100 Days (Here's Why)
Description
100 startups. 100 days. 1 engineer.
This is day zero of the 100 Startups Challenge — a live experiment
where I build and ship a new startup every single day for 100 days.
No team. No funding. No hype. Just Nuxt, Supabase, and whatever
idea makes the cut each morning.
I've been building software for 10 years. The problem was never
that I couldn't build — it was that I took too long to ship.
This challenge is me fixing that in public.
Every day:
→ One new startup built and shipped
→ One episode documenting the full build
→ One honest reflection on what worked and what didn't
Subscribe if you build things.
---
📌 Links
Docs & challenge notes: [your docs URL]
X / Twitter: @[your handle]
---
#100StartupChallenge #BuildInPublic #IndieHacker #SoloFounder
Tags
100 startups challenge, build in public, indie hacker, solo founder,
nuxt, supabase, daily startup, startup ideas, coding challenge,
ship fast, 100 days challenge, saas, product development,
software developer vlog, startup vlog
Thumbnail brief
- Dark background (
#0a0f1a) - Large bold white text: "100 STARTUPS"
- Smaller text below: "100 DAYS"
- Your face on the right, direct eye contact with camera
- Single green (
#00dc82) accent line or number element on the left - No cluttered text, no emojis, high contrast
Full Script
HOOK — 0:00 to 0:20
Start recording. No intro. No music. Just speak directly to camera.
"100 startups. 100 days. One developer.
I'm going to build and ship a new startup every single day for the next 100 days — solo — and I'm going to film every single one of them.
This is day zero. Let me tell you exactly what this is and why I'm doing it."
THE PROBLEM — 0:20 to 1:30
Shift to a slightly more personal tone. This is where you build connection.
"I've been writing software for 10 years.
I can build almost anything. That's not the problem.
The problem is how long it takes me to go from an idea to something that actually exists in the world.
I've watched other developers — people with less experience than me — ship more products, faster, with less overthinking. And I've spent years being the person who had ideas but waited for the right moment to build them.
The right moment never comes.
At some point I realised I wasn't missing skill. I was missing reps.
Speed is a skill. And the only way to develop it is to practise it — deliberately, consistently, with real stakes."
THE CHALLENGE — 1:30 to 2:30
State the rules clearly. You can show these as text on screen.
"So here are the rules I'm holding myself to for the next 100 days.
Rule one — one startup, every day, for 100 days.
Rule two — each one must be shippable by end of day. Not perfect. Shippable.
Rule three — every build gets documented and published. No hiding bad days.
Rule four — no skipping. No extensions. No half-builds.
Rule five — the system gets better every single day.
Some of these will be genuinely useful products. Some will be terrible. All of them will be real."
WHY IT MATTERS — 2:30 to 3:30
Zoom out. Give this some weight.
"This challenge is not about making 100 successful companies.
It's about building the operating system behind fast execution.
Every repetition teaches you something the previous one didn't. Where you're slow. Where you're overthinking. What parts of the process can be standardised and what parts actually need creative energy.
By day 100, the process should be dramatically faster and sharper than day 1.
And the documentation of that improvement — the full record of what changed and why — that's the real product of this challenge."
THE STACK AND SYSTEM — 3:30 to 4:30
Show screen briefly. Quick tour of the docs site. Keep it under 60 seconds.
"I'm not winging this.
The stack I'm using is Nuxt for the frontend, Supabase for the backend, and Nuxt UI to keep the interface work fast.
This docs site is the operating manual for the challenge. It's where I'll track every startup, every decision, every lesson, and every workflow improvement.
Each startup won't just produce a product. It'll produce a landing page, a YouTube episode, short-form clips, and documentation. The whole delivery system repeats every single day.
The goal is to compress that entire loop down — from idea to shipped product to published content — as fast as possible."
WHAT YOU WILL SEE — 4:30 to 5:30
Direct and practical. Set clear expectations.
"Every day I'll post one episode. Around 20 minutes.
Each video covers the full build — what I'm making, why, what decisions I made during the session, what shipped by the end of the day, and what I'm taking into the next one.
You won't see highlight reels. You'll see the process, including the parts that don't work.
This isn't a tutorial channel. I'm not here to teach you Nuxt or Supabase — there are better channels for that.
I'm here to document what it looks like when a developer stops optimising for perfect and starts optimising for shipped."
THE REAL REASON — 5:30 to 6:30
Drop the structure here. Speak naturally. This is the most important part of the whole video.
"Here's the honest version of why I'm doing this.
I've had startup ideas for years. Most of them never got built. Not because I couldn't build them — because I kept waiting. Waiting for the idea to be better. Waiting for the timing to be right. Waiting until I had more time.
None of those things happened.
100 days of forced execution is my answer to that. If I do this right, by the end of it I'll have shipped 100 real products and have a system that makes the next 100 dramatically easier.
And if even two or three of them turn into something real — that's already more than the last ten years of waiting produced.
So. Let's find out."
CLOSE AND CTA — 6:30 to 7:00
Short. Calm. Confident. Cut to black immediately after.
"Day 1 goes live tomorrow.
Subscribe so you don't miss it.
100 days. Let's go."
Cut to black. Channel name on screen. No outro.
Recording Plan
Setup checklist before filming
- Clean background or intentional setup — desk, monitors visible
- Good lighting — face lit evenly, no harsh shadows
- Camera at eye level — not looking up or down
- Microphone close — clear audio is more important than camera quality
- Close unnecessary tabs and notifications
- Have the script printed or on a second screen — do not read it, use it as a reference
- Record a 10-second test clip and review audio + video before the full take
OBS clip plan
Record in short segments, not one continuous take:
| Clip | Content | Approx time |
|---|---|---|
| A | Hook — direct to camera | 0:20 |
| B | The problem — personal, conversational | 1:10 |
| C | The rules — can read from screen | 1:00 |
| D | Why it matters — slightly more formal | 1:00 |
| E | Stack and system — screen recording of docs site | 1:00 |
| F | What you will see — direct to camera | 1:00 |
| G | The real reason — no notes, speak freely | 1:00 |
| H | Close and CTA — direct to camera | 0:30 |
Recording tips for this video
- Film the hook in one take without stopping — the energy of a continuous take matters
- The "real reason" section should be unscripted. Read the talking points once, then put the script down and just speak
- If you stumble, pause for two seconds and restart the sentence — easy to cut in edit
- Slightly under-light is better than over-lit — matches the dark aesthetic of the brand
DaVinci Resolve edit order
- Import and label all clips A through H
- Cut to the structure — do not follow raw chronology
- Remove dead air and repeated starts
- No music on this video — silence is intentional
- Add channel name card at end — 3 seconds, black background, white text
- Export at 1080p minimum, 4K if available
Post-Publishing Checklist
- Upload to YouTube with correct title, description and tags
- Set custom thumbnail
- Add to channel trailer slot in YouTube Studio
- Pin a comment linking to the docs site
- Post launch community update on YouTube
- Share on X with a short thread summarising the challenge
- Post on LinkedIn with founder angle
- Submit to r/SideProject and r/indiehackers
- Link from docs site homepage