You ship every week. Say it on camera.
The best build in public video ideas are the updates you already tweet — why you’re building it, what shipped, what broke, what you learned — said out loud in under a minute. Here are 40 for indie hackers, solo SaaS founders and vibe coders, each with an opening line, and most need nothing on screen but you.
The short version
- What to film: why you’re building it, the build log, what broke, numbers you’re comfortable sharing, lessons, tools, launch, users and pivots — 40 ideas below, each with a first line to say.
- Why video: a screenshot shows what changed. A talking video shows who’s building it and why — the part people actually follow.
- What to keep off camera: keys and admin screens, customer data, unfixed security problems and any number you haven’t decided to share.
- How often: one short for each thing you ship, plus one story a week. Film several in one sitting and post them through the week.
- Where: the same vertical video on X, LinkedIn, TikTok, YouTube Shorts and Reels — only the words around it change.
Why build-in-public videos beat another screenshot tweet
Because a screenshot shows what changed, and a video shows who changed it and why. Building in public works when people start following the builder, not just the changelog — and a face, a voice and a reason are much easier to follow than a cropped dashboard. A talking video also travels further: the same file works on TikTok, Reels and YouTube Shorts, where a screenshot tweet has nowhere to go.
| Screenshot tweet | Talking short | |
|---|---|---|
| What it shows | What changed | Who changed it, and why |
| Where it can go | X, maybe LinkedIn | X, LinkedIn, TikTok, YouTube Shorts, Instagram Reels |
| What people remember | The feature | You, and the problem you’re solving |
| What it takes | A few seconds | A minute of talking, then a cut |
| Best for | Quick proof that something shipped | The story behind it |
You don’t need a new kind of content to start. Take the update you were going to tweet anyway and turn it into a talking short:
Start with the line you’d tweet
Say the one-sentence version first: “I rolled back yesterday’s update.” That sentence is your opening line and, if you add one, your title card.
Add the why
Say what a screenshot can’t: why you did it, what you tried first, what surprised you. Two or three sentences is enough.
End on what’s next
Close with what you’re doing about it, or a question for the people watching. It gives them a reason to check back.
Keep it under a minute
One idea per video. If you have two things to say, that’s two videos — which is good news for your posting schedule.
Build in public video ideas: why you’re building it and what you shipped
Here are 40 build in public content ideas in nine groups. Each one is a talking video: an opening line you can say as written or in your own words, and a note on why it works. Swap in your own app, your own numbers and your own users.
Why you’re building it
The itch
Open with “I built this because I was sick of doing it by hand every Monday morning.”
The problem you felt yourself is the one story nobody else can tell. People with the same problem recognize themselves in the first line.
Why another one
Open with “There are already twenty apps that do this. Here’s why I’m building another one.”
It deals with the obvious objection up front, before someone raises it in the comments.
Who it’s for, and who it isn’t
Open with “This app is not for everyone. It’s for freelancers who send invoices from their phone.”
Naming your user out loud makes the right person stop and the wrong one scroll on. Both are useful.
Day one
Open with “Day one. I have a domain, an empty repo and a problem I can’t stop thinking about.”
It costs nothing to film before anything exists, and it becomes the video people go back to once the app gets somewhere.
What’s riding on it
Open with “I gave myself six months of evenings to find out if anyone wants this.”
A deadline or a stake gives people a reason to follow along and see how it ends.
The build log
What shipped this week
Open with “Three things shipped this week. One of them I almost didn’t ship.”
The weekly recap is the backbone of building in public. The twist in the first line is what makes it worth watching.
The feature and the reason
Open with “Everyone asked for dark mode. I built something else first, and here’s why.”
Your reasoning is more interesting than the feature, and it shows users you listen even when you say “not yet.”
The tiny detail
Open with “I spent a whole day on one button. Here’s why it mattered.”
Obsessing over small things out loud makes people trust the rest of the product.
What’s next
Open with “Next week I’m finally building the feature I’ve been avoiding since launch.”
Saying it in public sets up your next video and adds a little accountability.
How long it really took
Open with “I thought this would take an afternoon. It took nine days.”
Every builder watching has blown an estimate. Everyone else learns what building actually looks like.
Indie hacker video ideas: what broke, your numbers and your lessons
These are the videos a polished marketing account would never post, which is why they work. Honest beats impressive when people are deciding whether to trust a one-person company.
What broke
The outage
Open with “Yesterday I broke signups for four hours and didn’t notice.”
Owning a mistake in public earns more trust than a spotless changelog, and it shows you fix things.
The rollback
Open with “I rolled back the update people asked for. Here’s what went wrong.”
Users who asked for it want to know what happened. Everyone else gets a real lesson about shipping.
The rewrite you regret
Open with “I rewrote my whole backend last month. I shouldn’t have.”
Rewrite regret is universal among builders, and the reasons you give are useful to anyone about to make the same call.
The bill
Open with “My hosting bill jumped overnight, and it was completely my fault.”
Money mistakes are specific, a little painful and very easy to share with other builders.
The bug a user found
Open with “A user found a bug I’d missed for three weeks. Here’s how they found it.”
It credits your users and shows you respond. Ask before you name anyone.
Numbers you’re comfortable sharing
Numbers stop the scroll, but only share the ones you’ve decided to share before you hit record (more on that below). Where you see [brackets], your own number goes in.
The first dollar
Open with “Someone I’ve never met just paid for my app. Here’s how they found it.”
Everyone remembers their first sale, and “how they found it” is the part other builders can use.
The milestone, with context
Open with “We just passed [your number] users. Here’s what the first ten had in common.”
A milestone alone is a brag. What you learned getting there is a lesson.
What it costs to run
Open with “Here’s everything it costs me to run this app each month, line by line.”
Real cost breakdowns are rare and useful. Share only the lines you’re comfortable with.
The slow month
Open with “Signups went down this month. Here’s what I think happened.”
A bad-month video stands out because so few people post one, and it makes your good months believable.
Lessons
If I started over
Open with “If I started this app again tomorrow, I’d talk to users before I wrote a line of code.”
Advice from someone mid-build carries more weight than advice from someone selling a course.
Pricing
Open with “I changed my pricing three times before launch. Here’s where I landed and why.”
Every builder struggles with pricing, and hearing your actual reasoning helps them decide theirs.
Building vs distribution
Open with “Building it took two weeks. Getting the first ten users took two months.”
Leading with the two numbers stops the scroll, and the gap between them is the lesson.
Your biggest mistake
Open with “The biggest mistake I made in my first month of building in public.”
People watch mistake videos to avoid making the same one. You save them the trouble.
One question, ten users
Open with “I asked ten users one question. Their answers changed my roadmap.”
It shows you build from real feedback, and it hands other builders a question they can ask their own users.
SaaS founder video ideas: tools, launch, users and pivots
The last four groups cover the tools you build with, the launch itself, the people using your app, and the changes of direction every product goes through.
Your tools (vibe coding content ideas)
The stack in a minute
Open with “Here’s the whole stack behind my app, and why I picked each piece.”
Other builders will watch just for this, and it doubles as proof you know what you’re doing.
Building with AI, honestly
Open with “I built most of this app with an AI coding tool. Here’s where it helped and where I had to take over.”
Vibe coders want the honest version, not the highlight reel. The “where I took over” part is what they’ll remember.
The tool you dropped
Open with “I stopped using a tool I loved this week. Here’s what changed.”
Switching stories are useful to anyone weighing the same choice. Keep it about your needs, not about trashing the tool.
Your workflow
Open with “This is exactly how I go from an idea to a shipped feature in a day.”
Process videos are easy to film and easy to save. This is one of the few ideas where a short screen clip helps.
Launch
The countdown
Open with “Seven days until launch. Here’s what’s still broken.”
It turns your launch into a story with an ending people want to see.
Launch day
Open with “It’s live. If you’ve ever lost a client’s invoice in your inbox, this is for you.”
Opening with the problem instead of the product name tells the right people in one sentence that it’s for them.
The day after
Open with “Launch day is over. Here’s what actually happened.”
An honest recap gets watched by everyone planning their own launch.
What you’d change next time
Open with “Here’s what I’d do differently on my next Product Hunt launch.”
Launch lessons are only fresh for a few days. Film them while you still remember the details.
Your users
The unexpected first user
Open with “My first real user wasn’t who I expected.”
It shows who the app actually helps, which is often the best marketing insight you have.
The message that changed things
Open with “One message from a user changed what I’m building next.”
Paraphrase it rather than showing it, and leave their name out unless they’ve said yes.
The question everyone asks
Open with “This is the question new users ask me most, answered in under a minute.”
If users ask it, people deciding whether to try your app are wondering the same thing.
The request you turned down
Open with “Someone asked for a feature and I said no. Here’s why.”
Saying no shows what your product is for, and people respect a clear reason.
Pivots and cuts
The feature you deleted
Open with “I spent a month on a feature. Almost nobody opened it, so it’s gone.”
It shows you’ll kill your own work when users don’t want it, and early users are quietly betting on that judgment.
The pivot
Open with “This app started out as something completely different. Here’s what changed my mind.”
Pivot stories are honest proof that you follow what users do, not what you hoped they’d do.
A different user
Open with “I thought I was building this for developers. It turns out designers need it more.”
Changing who it’s for, out loud, brings the new audience in with you.
The ending
Open with “I’m shutting down my side project. Here’s what it taught me.”
Endings are part of building in public too, and they often get the most honest replies.
How to pair a talking short with your own screen clip
Let the talking short tell the story and a separate 10–20 second screen clip show the one thing you’re talking about. Post the talk first, then put the clip in the reply or the next post — or join the two in an editor you already use. Most ideas in this guide don’t need a clip at all: why you’re building it, what broke, numbers, lessons, users and pivots are stories, and the talk is the content. The build log, your tools and launch day are where a clip earns its place.
Say it first
Film the talking part with nothing on screen: what it is, why it matters, who it’s for. Promise what the clip will show — “here’s the one click that replaced my Monday spreadsheet.”
Capture one action
Record 10–20 seconds of your screen showing one thing, starting right where the action starts. No tour, no narration.
Make it readable on a phone
Zoom your browser in, use a narrow window, and crop close to the part that matters. Tiny text on a full desktop is unreadable in a vertical feed.
Clean the frame
Use a demo account with fake data, close other tabs, turn off notifications, and pause on every frame before you post (see the checklist above).
Join them or thread them
On X and LinkedIn, post the talking short and put the clip in the first reply or a follow-up post. On TikTok, Reels and YouTube Shorts, join them in your editor — talking short first, clip after — or post the clip as its own follow-up.
How often to post build-in-public videos: a cadence that follows your shipping
Match posting to shipping: one short for each thing you ship, plus one story a week that isn’t about a feature — a lesson, a user, a mistake. Film several in one sitting, then post them through the week. For a solo builder, two or three shorts a week you can keep up beats a burst of daily posts you can’t.
| If you ship… | Film | Post |
|---|---|---|
| Every day or two | One weekly batch: the three best things that happened | One short every couple of days, plus a Friday recap |
| Once a week | On ship day: what shipped, what broke, what’s next | The ship video that day; the story videos over the next few days |
| In bigger releases | Between releases: lessons and users. Before launch: the why, the countdown, what’s still broken | One or two a week between releases; one a day in launch week |
| Nothing yet | Day one, the problem, who it’s for, why you’re building it | One or two a week, so people already know you on launch day |
- Keep a running note while you build. Every bug, user message, surprise and decision is a video idea. By Friday you’ll have more than you can film.
- Don’t wait for a milestone. “Nothing big shipped” is a video too — what you’re stuck on is often the most honest update of the week.
- Alternate the kinds. For every feature video, post one story: why you’re building it, a lesson, a user or a cut. A feed of only features reads like a changelog.
- Miss a week? Post the next one. Nobody needs an apology video. Just pick up where you left off.
What to post on LinkedIn or TikTok right after you ship a new feature
Post a talking short that says what you shipped and why in the first sentence — the problem it solves, in your users’ words — with a screen clip in the reply if it needs showing. Then keep going: a feature launch is three videos, not one.
Ship day: the what and the why
Open with the problem, then the fix: “People kept telling me they lost track of unpaid invoices. As of today, the app chases them for you.” Add a screen clip in the reply if people need to see it.
Two or three days later: the story
What broke on the way, what you cut, how long it really took. This is the build-in-public part — the stuff a release note leaves out.
A week later: what happened
What users said, what surprised you, a number you’re comfortable sharing, or what you’re changing because of it.
On LinkedIn, write two or three lines above the video that say who the feature is for and what problem it fixes, so the post makes sense before anyone presses play. Lessons and the reasoning behind a decision tend to suit it best, especially for B2B and SaaS tools.
On TikTok, lead with the problem, not the feature name — people there don’t know your app yet, so a feature name means nothing to them. If you’re wondering how to promote your app on TikTok as a builder rather than a creator, that’s most of the answer: talk to the person who has the problem, in their words, not to other developers.
Where to post build-in-public videos
Post the same vertical video wherever your future users already scroll, and change only the words around it. X and LinkedIn reach other builders and B2B buyers; TikTok, Reels and YouTube Shorts reach people who have the problem and have never heard of you.
| Where | Best for | One tip |
|---|---|---|
| X | Other builders and early adopters following your build-in-public thread | Upload the video into the thread itself, with the one-line takeaway as the text. |
| B2B and SaaS buyers; lessons and the problem story | Put two or three lines of context above the video. Skip the wall of hashtags. | |
| TikTok | People who have the problem, not other developers | Say the problem in the first sentence, in the words they’d use. |
| YouTube Shorts | People searching for a fix to their problem | Title each short with the problem, the way someone would type it into a search. |
| Instagram Reels | Consumer apps and your personal story | Lean on the story videos — why you built it, what broke — more than feature updates. |
| Your landing page and changelog | Visitors deciding whether to trust a one-person company | Put your why video near the signup button, and a ship video in each changelog entry. |
| Builder communities | Feedback from people building similar things | Read each community’s self-promotion rules first. Share the lesson in text and offer the video; don’t just drop a link. |
| Product Hunt | Launch day | Link your why video in the maker comment. It answers the first question people ask. |
For the bigger picture — what app builders should talk about and how it fits around shipping — see how to market your app with short videos.
How to film these without writing a script
Don’t script them — talk them. Write the opening line on a sticky note, say it, then keep talking the way you’d explain it to a friend at a meetup. A script makes builders sound like an ad; a first line and an honest answer sound like you. A few habits help:
- Talk to a person, not the lens. Have a friend ask you the question on a call, or put the question on your screen and answer it.
- Batch them. Five opening lines, one sitting, one setup. It’s easier to keep going than to start.
- Redo lines freely. Say a sentence again until it comes out right. You only keep the best take.
- Start with your story. If you have no footage and don’t know where to begin, film your founder story first — why you started and the problem you kept seeing. If the camera is the hard part, read how to get over camera shyness.
If you’d rather have someone ask the questions for you, that’s what NoShotList does. You sit at your computer and talk with Remy, an AI video producer, like a podcast guest, while your phone stands beside your screen and films. Remy learns your app first — from your website or by brainstorming with you — then picks the topics and asks one question at a time:
- RemyWhy did you start building this app?
- YouHonestly? I kept dropping my own habits, and every tracker felt like homework.
- RemyHere’s a good way in — start with the problem. What made you open a new project that night?
- YouI’d just broken another streak, and I thought: tracking a habit shouldn’t take more effort than the habit.
- RemyGood. Now the build. What have you redone the most?
- YouThe onboarding. I’ve rebuilt it four times, and nobody’s even seen it yet.
About 10–12 minutes of that becomes about 3 captioned vertical shorts, cut only from your own whole sentences, with your cleanest take of each line kept and the “ums” removed. Your voice is never synthesized. Know what it does before you try it: NoShotList films you talking, and while you talk you can share your screen (up to 3 minutes a share) or add a clip from your camera roll, which can appear in the short as a split-screen or picture-in-picture cutaway. It isn’t a full demo editor, so a longer walkthrough is still yours to record. Your first session is free once you’re invited, and Solo is $49/month for about 12 shorts. More in NoShotList for app builders and short-form video when you have no footage.
Questions
How do indie hackers make build-in-public videos, not just tweets or screenshots?
Take the update you’d tweet and say it out loud, adding the part a screenshot can’t: why you did it and what you learned. Open with the one-line takeaway, keep it under a minute and upload the vertical video into your thread. If the update needs to show the product, capture a short screen clip separately and put it in the reply.
What should a solo SaaS founder post on LinkedIn or TikTok right after shipping a new feature?
A short talking video that says what you shipped and why in the first sentence — the problem it solves, in your users’ words — with a screen clip in the reply if it needs showing. On LinkedIn, add two or three lines of context above it. On TikTok, lead with the problem, not the feature name. A few days later, post the story behind it.
Do I need to show my screen in a build-in-public video?
No. Most of the best ideas — why you’re building it, what broke, lessons, numbers, users and pivots — are stories, and the talk is the content. Show your screen only when people need to see something, and use a separate 10–20 second clip with a demo account and nothing private visible.
Should I share my revenue when I build in public?
Only if you decided to before you hit record. Exact monthly revenue, milestones, growth, or no revenue at all can each work — building in public means sharing the process, not your finances. Check any investor or partner agreements first, and never show customer names or data without permission.
How often should I post build-in-public videos?
Tie it to your shipping: one short for each thing you ship, plus one story a week that isn’t about a feature, like a lesson or a user conversation. Film several in one sitting and post them through the week. For a solo builder, two or three a week you can keep up is plenty.
How do I promote my app on TikTok if I’m not a content creator?
Talk to the person who has the problem your app solves, not to other developers. Open with the problem in their words, say how you ran into it yourself, and show the fix in a quick screen clip if it helps. Keep each short to one problem, one lesson or one story, and post regularly.
Is there a tool that turns a conversation about my app into short videos?
NoShotList does. Remy, an AI video producer, asks you about your app — why you built it, what broke, what you learned — while your phone films from beside your screen. About 10–12 minutes of talking becomes about 3 captioned shorts, cut only from your own words. It films you talking; it doesn’t capture your screen or make demos.
What if I hate being on camera?
Talk to a person instead of the lens — a friend on a call, or a producer asking questions — with your phone beside your screen rather than in your face. Say the opening line, keep talking and redo lines freely. Our guide on getting over camera shyness has more.
Stop putting it off. Start talking.
NoShotList is an invite-only beta. Request access with your email; once you’re invited, your first session is free: up to 20 minutes with Remy, no card.