Threads
Conor Dwyer @Uploadpack · 1h · Building in public

I Used UploadPack to Decide What UploadPack Should Film Next

A slightly meta update from the build-in-public trenches. πŸ˜… I’ve just published a new UploadPack YouTube video around a question I think far more creators should ask: How do you know which YouTube video idea is actually worth making? Not β€œCan AI give me 20 ideas?” Not β€œWhich keyword has the biggest number?” But: Which idea actually deserves the time it takes to script, film and edit? That question is basically why I built UploadPack in the first place. And while using the platform on my own channel, I found several areas where the product itself could be clearer. So instead of ignoring them, I went back into the build. The latest updates include: πŸš€ A much clearer β€œwhat should I make next?” workflow πŸ” Research-backed ideas now flow directly into the Pack builder πŸ“¦ Packs have been simplified so the decision comes first and technical data sits behind expandable sections 🧠 Copy across the site has been rewritten around what to make β†’ why β†’ how to execute it πŸ”₯ A new Why UploadPack page explains the overlooked step before titles, thumbnails and SEO πŸŽ₯ The site now automatically features the latest UploadPack YouTube video βœ… More defensive checks have been added to stop broken or contradictory Pack outputs There’s something useful about building with your own product. You stop asking: β€œDoes this feature work?” …and start asking: β€œWould I actually want to use this?” That second question is much harder β€” and much more valuable. Still building. Still finding things to fix. Still using UploadPack to test UploadPack. That’s exactly how I want to build it. What’s one thing you only discovered was wrong with your product after using it yourself? #BuildInPublic #SaaS #YouTube #CreatorTools #ProductDevelopment #IndieHacker #UploadPack

1/2
0