The pattern that pushed me to build this was simple: when a homeowner calls a contractor and nobody picks up, most people don't leave a voicemail. They just call the next name on the list. For a one or two-person shop, that missed call often happens at the worst possible moment up a ladder, under a sink, or driving between jobs.
I kept losing quick notes behind 20 open windows. Regular sticky notes covered my work, and notes apps got buried. So I built HideNStick Notes for Windows.
It s a free tool for recording that a specific version of your code existed at a certain time. Your source code stays on your device. The service records its digital fingerprint and gives you a certificate backed by a trusted timestamp and a blockchain record.
One use is documenting a version before sending it to a client or partner.
I'm Shubham, the maker of NoSus. I'd appreciate help choosing the clearest starting workflow for people who share files.
The product includes one-time Burn notes/files and document links with watermarks, access logs, and revocation. There's also a phone-approved workflow for selected files on a borrowed computer.
You can try the Burn tool at https://nosus.foo without creating an account. Use a dummy note, open its link in another browser, and try reopening it. I'd love to know which step feels unclear or unnecessary.
For product validation: when did you last need a file to be opened just once, or need to stop future access after sending a document? What did you actually use? What would make another tool worth the extra step?
I think most developers have experienced this: you build a really cool side project, the tech stack is solid, the code is clean... but then nothing happens. No users, no sales, no marketing. I m great at building, but marketing have never been my strong suit. And whenever I tried finding someone on LinkedIn or Reddit to team up with, it was either full of corporate recruiters or spam filters blocking genuine collaboration. Even with a friend, i felt like i did 90% of the work. So I decided to build a dedicated place for this: Co-Found (https://co-found.site/). It s completely free to browse and test out. The idea is simple: Filter and find co-founders based on actual tech stacks and roles (developers, designers, growth, idea people). Instead of cold connection requests, you pitch what you want to build together. Built-in workspaces with chat, task boards, and a quick "prenup" tool so both sides agree on expectations and equity before spending months coding. And so much more features and tools i wont be able to fit in here haha. Since this community is full of developers who actually build things: What has your experience been trying to find co-founders or team members for side projects? If you check out the site, what s the first thing you feel is missing or broken? Im always looking for feedback and listening to my users all the time to improve this site. So it would mean alot if you all in the community would check it out and give me feedback!
Baby is due literally any day. In the weeks leading up to paternity leave I've been building Sprout a one-stop-shop for new parents in the UK.
The problem I was trying to solve: Every app for new parents does one thing. Peanut does friend-matching (women only). Happity does classes. Childcare.co.uk does nurseries. Nothing combines the stuff you actually need day-to-day into one place and nothing includes dads properly.
What Sprout does:
Find other parents nearby with babies the same age
AI assistant you can ask anything at 3am (including sending photos)
I've been building an enterprise AI product around a problem I've experienced firsthand: companies can have dozens of SaaS tools, dashboards, and databases, yet understanding what is actually happening across the business can still require a lot of manual work.
A sales issue might be connected to something in customer support. A revenue change might have an operational cause. An IT problem might eventually affect sales or customer experience.
The data exists but it's usually separated by systems and departments.
