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 #productdevelopment Clear
VIVID

Another productive day building VIVID. 🚀

Today, I focused on strengthening the VIVID admin infrastructure and improving the video management workflow. What I worked on today: • Connected the Admin Videos section with the backend • Replaced demo video data with real backend records • Implemented permanent video deletion • Added video status tracking for Processing and Completed videos • Improved video search and admin management • Tested the API and database flow to make sure changes persist after refresh • Investigated a temporary production API/CORS issue • Continued planning VIVID’s future user accounts and automatic video history I'm deliberately building VIVID in stages — getting the foundation right before adding more complex features. 🚀VIVID Beta is also live. If you're interested and want to see what we're building, try the beta and share your feedback with me. vividedit.online Your feedback can directly influence what we build next. Still early. Still building. ⚡
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.

Build Less , Understand More , Solve Better 🍂

The Code Is Not the Product A founder doesn’t need to write every line of code. But a founder must understand what the code is supposed to achieve. Technology is only valuable when it solves a real problem. Before asking: «“Which technology should we use?”» Ask: «“What problem are we solving, for whom, and why does it matter?”» A great product isn’t built by adding more features. It’s built by understanding users, validating ideas, making smart technical decisions, and improving continuously. Build less. Understand more. Solve better. 🚀
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.