Built for founders

Where founders rise on merit, not connections.

Share your journey, publish your startup, build your team, climb the global rankings — every founder here has a face, a team, and a story behind the product.

Filtered by #uploadpack Clear
Uploadpack.io

Today was one of those days....

Today was one of those days where progress and problems seemed determined to arrive together. UploadPack has moved forward massively over the last few months, and today should have been about enjoying some of that progress. Instead, I found myself dealing with a chain of issues that only really show themselves when you start pushing a product properly. A channel connection problem exposed data in the wrong workspace. Fixed. A deployment configuration issue knocked the application sideways. Traced it, restored it, fixed it. Then, just as everything looked stable again, Pack generation started failing. Another investigation, another cause found, another problem removed. And finally, when I generated a fresh publishing Pack, I spotted something I liked even less: evidence from an earlier piece of research had found its way into a completely unrelated topic. That one mattered. UploadPack is being built around evidence, context and trust. If it tells somebody why an idea is worth producing, the information behind that decision has to belong there. So instead of brushing it off as an annoying edge case, I stopped, traced where the contamination came from, tightened the evidence ownership rules, separated genuine topic matches from broad competitor comparisons, added new regression tests and rebuilt the release. Tonight, v55.49.5 is live. Not because everything went smoothly. Because it didn't. Building software has taught me that progress isn't always a straight line. Sometimes you move forward, discover something uncomfortable, sidestep, solve it properly, and then carry on from a stronger position. I don't particularly enjoy finding problems. But I'd much rather find them now than have a customer find them later. Back at it tomorrow.
Uploadpack.io

UploadPack has an affiliate program now.

I’ve kept this pretty simple. If you work with YouTube creators, channel managers, agencies, consultants, or people building content-led businesses, and you think UploadPack is genuinely useful, you can now earn from referring people to it. That’s really the whole idea. I’m not interested in turning this into one of those “drop a link everywhere and hope” affiliate setups. I’d much rather work with people who understand the space, know the problems creators actually deal with, and only recommend tools they’d be comfortable putting their name behind. UploadPack is built for people who want more than random video ideas, recycled analytics, or another dashboard full of noise. It helps users work out what is worth publishing next, why an idea deserves attention, and how to turn that decision into a proper publishing plan. So if you already speak to creators, advise channels, run a community, publish educational content, or simply know people who would benefit from that, the affiliate program is now open. You can take a look here: https://uploadpack.io/affiliates/ I’m looking forward to seeing who gets involved.
Uploadpack.io

UploadPack project update: moving from building to proving

A small but important milestone today. I’ve now moved UploadPack into a structured external testing phase with a group of independent testers from different YouTube backgrounds. The aim isn’t to collect compliments. It’s to find out where the platform is genuinely useful, where it falls short, what feels confusing, and whether it actually improves the way serious creators and channel managers decide what to publish next. The testers are being asked to use UploadPack properly — multiple ideas, repeated workflows, research, opportunity scoring, titles, packaging, descriptions, chapters, keywords, promotional assets, and everything in between. They’ll also be looking for bugs, inconsistencies, slowdowns and anything that simply doesn’t make sense. What matters most to me is this: • Would they actually use it in a real YouTube workflow? • Would it save time? • Would they trust the research? • Would the recommendations feel specific to the channel? • Would it help them make a better publishing decision before spending hours producing the wrong video? That’s the stage I’m at now. Less “look what I built.” More “let’s see if it holds up when experienced people really use it.” I’m still bootstrapping the whole thing, still building, still fixing, still learning. But this feels like one of those moments where the project starts becoming less about my opinion and more about whether the market agrees. That’s exactly where I want it to be. https://uploadpack.io
Uploadpack.io

Another tiny step nobody really cares about — and that’s fine.

Today I created a proper demo video for UploadPack using Supademo. That sounds like a small thing. And to everyone else, it probably is. No applause. No big announcement. No sudden spike in users because I made a demo walkthrough. Just another job ticked off the list. But that’s kind of the point. Building something properly is full of these little steps nobody sees: The research. The rewrites. The bugs. The testing. The product decisions. The onboarding. The marketing. The outreach. The demo videos. Most of it is completely unglamorous. And I’m fine with that. I know what it takes because I’m actually doing it. I’d much rather build, test, learn, make mistakes, fix them and share the process than spend my time telling other people how to build a SaaS business when I’ve never actually been through it myself. There’s a lot of “here’s how you should do it” content online. I’m more interested in: “Here’s what I did. Here’s what worked. Here’s what didn’t. Here’s what I learned.” That feels more useful to me. So yes, today’s milestone was a demo video. Tomorrow it’ll be something else. None of these individual steps look particularly impressive on their own. Stack enough of them together, though, and eventually you have a real product, real users and something you can be proud of. I’ll take that over pretending to have all the answers. Every time.
Uploadpack.io

Six months ago, I had a clear vision for UploadPack.io. But...

But despite my experience, knowledge and skillset, the doubts of others still got into my head. Founders, developers and fellow entrepreneurs kept pointing to existing platforms and asking what made UploadPack different. Their feedback made me second-guess the idea, so I stepped back and spent months researching the problems YouTube creators, channel managers and agencies repeatedly face. The frustrating part? The pain points were almost exactly the same as they had been six months earlier. Creators did not need another dashboard packed with keywords. They did not need random AI-generated titles. They did not need recycled data they could already see inside YouTube Studio. They needed help deciding what to publish next, why the idea was worth pursuing, and how to turn that decision into a complete publishing plan. That is the vision others could not see. UploadPack is not trying to serve every casual creator. It is built for serious creators, managers and agencies who value their time, care about the quality of their content and want evidence behind their decisions. It researches the opportunity, assesses demand, competition, audience fit and commercial value, explains the reasoning, recommends the strongest angle and builds the publishing pack around it. It is narrower by design. And that is exactly why it is different. The six-month delay was painful, but it also gave me certainty. I was not solving the wrong problem. I had simply allowed people who could not see the full vision to make me question it. So here is the lesson I am taking forward: Listen carefully. Research properly. Stay open to criticism. But never let someone else’s limited view make you abandon something you understand deeply. Do not let others make you question yourself. Ever. https://uploadpack.io