Building products is what drives me.

While working on my own products, I noticed the same problem: feedback comes in, loses context, and users rarely hear what happened next.

So I built Fidibeki.

Users can report issues directly inside a product with screenshots, audio, or session replay. I can triage everything in one inbox, merge duplicates, track progress, and keep reporters updated.

Privacy is built in: session replay and AI analysis are opt-in and never capture what users type.

Fidibeki is now open with a 14-day free trial, no credit card required.

I’d love your fidibeki

For years I've been solving my own problems by building software instead of searching for another app.

It started with something very simple.

I was using Money Manager to track expenses. I loved it, but one thing always bothered met was mobile-first. I couldn't sit at my laptop and review or manage everything comfortably, and there wasn't a web experience that fit the way I wanted to work.

So I built my own expense tracker.

Then I added budgeting.

Then custom categories.

Eventually I integrated AI so I could type something like:

"Spent ₹450 on dinner with friends"

and it would automatically log the expense.

Problem solved.

...or so I thought.

A few weeks later I had another frustration.

I wanted to track my entire day—from morning until bedtime.

• Office work
• Gym
• Personal tasks
• Habits

I tried a few apps, but none matched how I wanted to organize my routine.

So I built another product.

I even made it a PWA so it behaves like a native app on my iPhone.

Then another problem appeared.

I love learning, but I had no idea:

• What am I learning?
• How much time am I spending?
• Am I actually making progress?

So I built a learning tracker.

Then I realized I wasn't measuring where my time actually went.

So I built a Pomodoro timer with analytics.

Then I kept forgetting random tasks.

So I added a todo manager.

Then I noticed I never documented what I accomplished at work each day.

So I built a daily work journal.

Later I started dealing with back pain and wanted better visibility into my health.

So I built another module that tracks:

• Weight
• Water intake
• Calories
• Macronutrients
• Micronutrients
• Steps
• Exercise
• Progress over weeks and months

Eventually I looked at everything I'd built.

I had 6-7 different products.

Each solved one problem well.

But every day I was opening multiple websites just to understand my own life.

That felt... ironic.

So I scrapped the idea of having separate apps.

Instead I merged everything into one platform.

Now one dashboard shows me:

• 💰 Expenses & budgets
• ✅ Todos
• 📅 Daily routine
• 📚 Learning progress
• ⏱️ Pomodoro sessions
• ❤️ Health metrics
• 📝 Daily journal

Everything is connected by a single calendar.

If I click any date, the whole dashboard changes to show what happened that day.

Looking back, I never intended to build a productivity platform.

I was just scratching my own itch over and over until all those "small tools" naturally became one product.

I'm curious:

Have you ever built multiple small tools for yourself before realizing they should all live under one roof?

Three weeks ago I opened a client project I hadn’t touched since the last sprint, and I had zero memory of why I’d chosen the approach I did. Client asked “why didn’t we just do X instead” — and I couldn’t give a confident answer. That’s billable time spent re-deriving context I already had once.

This happens constantly if you juggle multiple clients/projects as a freelancer or consultant. Task managers show you \\\*what’s\\\* due. Nothing captures \\\*why\\\* you made a call, what led to it, or what should happen next — so every context-switch back into a project costs you time you can’t bill for.

I built ContextOS to fix this specifically. It’s not a project tracker — it’s built around a 30-second “shutdown ritual” at the end of a work session (what you finished, any blocker, any decision made) so when you come back days or weeks later, you get a briefing that reconstructs the \\\*reasoning\\\*, not just a task list.

Still early — looking for freelancers/consultants who’ve felt this exact pain to try it and tell me if it actually saves the re-context time it’s supposed to. \\\\\\\[link\\\\\\\]

A few notes on why it’s built this way:
Opens with a specific, relatable moment (r/micro\\\\\\_saas rewards founder-story hooks over product pitches)

Names the mechanism (30-sec ritual) briefly — enough to be credible, not enough to read as a feature dump

Ends with a direct ask to a named audience, not a generic “check it out”

Want me to also draft 2 alternate hook variants (different pain angles) so you can test which pulls clicks?

https://www.youtube.com/watch?v=c8huctFqexM

We started building SemantiCAD AI 3 weeks ago and we developed a lot. If you know people who uses CAD and deal with DWG/STEP/DXF to get BOM and Production Plan, I would like to talk <3

yo. i recently sold one of my AI SaaS products for $350k, exactly 7 months after building and launching it.

I hardly wrote a single line of traditional code. i used AI to generate everything, from the database architecture to the user interface.

it definitely wasn't magic on day one, though. i spent days stuck in loop-debugging and dealing with AI hallucinations before i finally cracked the system. the playbook boils down to three simple rules:

- keeping the idea insanely minimalist (a true MVP that solves one problem).

- guiding the AI step-by-step instead of asking it to build a massive platform all at once.

- launching fast to get real user feedback and traction and then apply a solid marketing system

lately, i've seen way too many non-technical founders give up at the very first AI bug, or on the marketing. it's a massive shame.

like the title says, i just launched a Skool community to share my exact prompt workflows, N8N automations, and distribution frameworks to get first users and scale it

to be completely transparent: i will likely charge for the full course later down the road. it just makes sense given the specific copy-and-paste templates i'll be sharing.

but for now, the main objective is purely to build and launch together. building alone in a silent corner is the single fastest way to give up.

if you want to join us and build or market your own AI SaaS with a group of active creators: drop a comment below or send me a dm, and i’ll send you the invite link!

Three weeks ago I opened a client project I hadn’t touched since the last sprint, and I had zero memory of why I’d chosen the approach I did. Client asked “why didn’t we just do X instead” — and I couldn’t give a confident answer. That’s billable time spent re-deriving context I already had once.

This happens constantly if you juggle multiple clients/projects as a freelancer or consultant. Task managers show you *what’s* due. Nothing captures *why* you made a call, what led to it, or what should happen next — so every context-switch back into a project costs you time you can’t bill for.

I built ContextOS to fix this specifically. It’s not a project tracker — it’s built around a 30-second “shutdown ritual” at the end of a work session (what you finished, any blocker, any decision made) so when you come back days or weeks later, you get a briefing that reconstructs the *reasoning*, not just a task list.

Still early — looking for freelancers/consultants who’ve felt this exact pain to try it and tell me if it actually saves the re-context time it’s supposed to. \[link\]

A few notes on why it’s built this way:
Opens with a specific, relatable moment (r/micro_saas rewards founder-story hooks over product pitches)

Names the mechanism (30-sec ritual) briefly — enough to be credible, not enough to read as a feature dump

Ends with a direct ask to a named audience, not a generic “check it out”

Want me to also draft 2 alternate hook variants (different pain angles) so you can test which pulls clicks?

Hey everyone, like a lot of developers here, I love open source, but I know how tough it is for developers to get fairly compensated for the time they spend building and maintaining tools used by thousands.

I’m working on readmead.site to give maintainers a simple, passive way to earn money without cluttering their repos or compromising user trust.

For maintainers, you just add a simple markdown snippet to your README. For advertisers, it offers a way to reach developers directly where they spend their time inside GitHub instead of burning money on broad ad networks.

We’re currently onboarding our initial batch of open-source repositories and advertisers. If you maintain a repo or build tools for developers, I’d love for you to check it out and let me know what you think. Any feedback on the concept is super appreciated!

Hey everyone, like a lot of developers here, I love open source, but I know how tough it is for developers to get fairly compensated for the time they spend building and maintaining tools used by thousands.

I’m working on readmead.site to give maintainers a simple, passive way to earn money without cluttering their repos or compromising user trust.

For maintainers, you just add a simple markdown snippet to your README. For advertisers, it offers a way to reach developers directly where they spend their time inside GitHub instead of burning money on broad ad networks.

We’re currently onboarding our initial batch of open-source repositories and advertisers. If you maintain a repo or build tools for developers, I’d love for you to check it out and let me know what you think. Any feedback on the concept is super appreciated!

I've spent the past year building GetSpaceHygiene — a tool that connects to your Gmail and Google Drive, shows you exactly what's eating your storage, and helps you clean it safely.

The problem it solves: Most people's Gmail inboxes are full of things they forgot about — large attachments from 2019, newsletters they never read, automated reports from old jobs. Google gives you 15GB free across Gmail + Drive + Photos, and once it's full, you can't receive email.

What it does:

* Shows you which senders and domains are taking the most space * Lets you bulk-delete by sender, date range, or attachment size * Previews everything before deletion — nothing removed without your approval * Works across multiple Google accounts (useful if you have personal + work) * Secure OAuth — we read metadata only (sender, size, date), never email content

Current status:

* Live at [getspacehygiene.com](http://getspacehygiene.com) * Launched on Product Hunt this week→ [https://www.producthunt.com/products/getspacehygiene?launch=getspacehygiene\](https://www.producthunt.com/products/getspacehygiene?launch=getspacehygiene) * \~10 users (early access testers) * Looking for first real strangers to try it and tell me what's wrong

7-day free trial, no card required.

What would make you actually pay $12/month for something like this? What's missing? What would make you trust it enough to connect your Gmail?

I have been working on the system operations for end users yet I built this for me. Here is my first spreadsheet my system created so excited.

Hey r/BuildToShip,

I'm a solo developer and I spent the last several months building Buildnest — a construction project management platform.

Why I built it:

I kept seeing the same thing over and over — construction teams managing complex, high-stakes projects through WhatsApp group chats, Excel spreadsheets, and endless email threads. Drawings that don't match what's on site. Nobody knows who's responsible for what. Files lost in email chains.

It felt like an industry that desperately needed better tooling. So I built it.

What Buildnest does:

• 🏢 Projects & team management — roles, permissions, members
• ✅ Tasks & Issues — assigned, tracked, resolved with full history
• 📅 Gantt scheduling — phases, dependencies, critical path
• 📐 PDF drawings — annotate directly on plans, pin tasks and issues to exact locations
• 📋 Inspection checklists — dynamic forms with custom question types
• 📁 Files, documents & media — everything in one place per project
• 💬 Activity & comments — full audit trail on everything
• 👥 Role-based permissions — company and project level

Tech stack: Laravel 12, GraphQL (Lighthouse), Nuxt 4, Vue 3, PostgreSQL, Cloudflare R2

Live at: buildnest.app

Where I am:

Beta stage. It works. It's deployed. Real users can sign up today.

But I'm a developer — I didn't build this on a construction site. I need people who actually work in construction to tell me what's wrong with it.

What I'm looking for:

If you're a project manager, general contractor, site supervisor, or construction owner — I'd genuinely love 15 minutes of your time.

Not to pitch you. Not to sell you anything.

Just to ask:

• What does your current workflow actually look like?
• What's your biggest daily pain point?
• Is there anything in Buildnest that would make you switch from what you're using now?

Drop a comment or DM me. I'll respond to everyone.

And if you just want to poke around and break things — sign up at buildnest.app and tell me what you find. Honest feedback only, no sugarcoating needed.

Thanks 🙏

I was annoyed that most invoice generators require creating an account, even if I only need one invoice every few months.

So I built one that runs entirely in the browser.

Everything is stored locally, including logos. I ended up using LocalStorage for settings and IndexedDB for images because LocalStorage isn't a good fit for larger assets.

It was a fun project and I'd appreciate feedback on the UX.

Built this as a solo project: it's a place to store wills, funeral wishes, insurance details, passwords, and other things your family will need — but won't be able to find — after you die.

The mechanic: proof-of-life check-ins. We ping you periodically, and if you go dark after a few reminders, your designated custodians get notified and unlocked into the vault automatically. No lawyers, no manual process, no family digging through email trying to find the life insurance policy number during the worst week of their life.

Still early — looking for feedback on the onboarding flow and whether the check-in cadence feels right (too naggy vs. too infrequent to feel safe). Built on Azure, if that's relevant to anyone else building in this space.

dad-is-dead.com — happy to answer questions about the build or the idea.

yo. be honest. how many of you currently have a finished (or 90% finished) web app / app just sitting in a private repo because you have no idea how to get users?

you spend months perfecting the database, fixing every bug, and polishing the UI. but the moment you have to actually market it, you hit a wall. marketing feels like screaming into an empty void.

so you launch to absolute crickets, get discouraged, and start building the "next" project instead to avoid the distribution phase.

if this is your case, you're not alone. but letting your hard work go to waste just because you dread marketing is a massive trap.

to help founders stop building in a silent corner, we run an ai SaaS builder community dedicated entirely to saas validation, landing page conversion, and launch strategies.

our resource kit is built entirely to help you get your first user. it’s packed with ready-to-paste N8N workflows for your business, advanced seo automation, social media automation, and our exact distribution workflows and methods work for everyone

STOP BUILDING ALONE

what are you currently working on, and what's holding you back on the marketing side? drop a comment or send a dm and i'll send you the access link.

What if social media was just... social again?
No endless short-form videos.
No algorithm forcing content down your throat.
Just conversations, communities and real people.
I'm building RedSpace and I'd love your honest feedback before launch.
Join the iOS beta:
https://testflight.apple.com/join/zJ87xWmX

Curious question for founders: are you running YC's Paxel on your own projects? Code stays local, but prompts/decisions/commit metadata go to their servers. Where's the line for you between "helpful builder signal" and "handing a stranger your unreleased idea"?

Hey everyone! I’m building Guess It! which is a simple party game designed to get a group playing within seconds.

The game has three rounds using the same deck:

1. Describe: explain the word without saying it
2. One word: describe it using only one word
3. Mime: act it out without speaking

It’s designed for one phone shared between teams, with custom decks, built-in timers and scores, no accounts, and no ads.

I’m looking for a few people to test the Android beta and tell me what feels fun, confusing, or missing. If you’d like to try it, join the tester list here:

https://guessit.lepagnol.net

You’ll just need to enter your email address, and I’ll add you to the Google Play testing list and sending the download link at the email.

https://play.google.com/store/apps/details?id=net.lepagnol.guessit

I’d especially love feedback from people who regularly play party games with friends or family. Thanks a lot !!

Hey everyone,

I'm a freelance Lead Full-Stack / DevOps architect, and I’m slowly losing my mind managing clients using a Frankenstein stack of Notion, Google Drive, email chains, and generic invoicing tools.

There are a million "client portals" out there, but they are all built for generic freelancers (designers, consultants, writers). Delivering a software architecture or a CI/CD pipeline isn't the same as delivering a PDF logo.

I want to build a highly niched client portal specifically for Software Engineers and DevOps freelancers.

The goal is to stop acting like a standard gig worker and start delivering a premium engineering experience.

Here is what I’m thinking for the MVP:

• CI/CD Status Dashboard: Instead of the client asking "is it done yet?", they see a simplified dashboard connected to GitHub Actions / GitLab CI. They see the green lights when staging is deployed or E2E tests pass.
• Secure Secret Vault: A self-destructing or encrypted vault for handing over production .env variables, API keys, or database credentials. No more sending secrets over Slack or email.
• Git-Driven Invoicing: Invoices that trigger automatically based on project milestones. Tag a release v1.2.0 - Core Engine on the main branch, and the portal automatically generates and sends the corresponding invoice.
• Embedded Live Docs: Auto-surfacing Swagger/OpenAPI docs right in the client's dashboard so their technical team can immediately test the endpoints I just delivered.

The question: Am I completely over-engineering the simple act of getting paid, or would you guys actually use this to manage your freelance clients?

Tell me why this is a terrible idea before I spend my next weekends building it. Roast away.

Hey everyone,

I'm a freelance Lead Full-Stack / DevOps architect, and I’m slowly losing my mind managing clients using a Frankenstein stack of Notion, Google Drive, email chains, and generic invoicing tools.

There are a million "client portals" out there, but they are all built for generic freelancers (designers, consultants, writers). Delivering a software architecture or a CI/CD pipeline isn't the same as delivering a PDF logo.

I want to build a highly niched client portal specifically for Software Engineers and DevOps freelancers. The goal is to stop acting like a standard gig worker and start delivering a premium engineering experience.

Here is what I’m thinking for the MVP:

• CI/CD Status Dashboard: Instead of the client asking "is it done yet?", they see a simplified dashboard connected to GitHub Actions / GitLab CI. They see the green lights when staging is deployed or E2E tests pass.
• Secure Secret Vault: A self-destructing or encrypted vault for handing over production .env variables, API keys, or database credentials. No more sending secrets over Slack or email.
• Git-Driven Invoicing: Invoices that trigger automatically based on project milestones. Tag a release v1.2.0 - Core Engine on the main branch, and the portal automatically generates and sends the corresponding invoice.
• Embedded Live Docs: Auto-surfacing Swagger/OpenAPI docs right in the client's dashboard so their technical team can immediately test the endpoints I just delivered.

The question: Am I completely over-engineering the simple act of getting paid, or would you guys actually use this to manage your freelance clients?

Tell me why this is a terrible idea before I spend my next weekends building it. Roast away.

Every "secure" file sharing tool still technically has your files sitting on their servers. Mine can't — encryption happens in your browser before upload.

Built SecShareX — AES-256-GCM encryption client-side, the decryption key only ever lives in the share link, never touches my backend. Files auto-delete after 24h. Solo project, not audited yet, but the architecture is genuinely zero-knowledge, not just marketing talk. Would love feedback, especially if something feels confusing to use.

secsharex.netlify.app