Built a tool to answer a question I couldn't answer for myself: is what I'm doing with money actually okay, or not?

Most personal finance calculators assume you already know what "good" looks like. I didn't, I could do the math on savings rate, debt-to- income, emergency fund coverage, but had no reference point for whether my numbers were fine or a problem.

A few months back, one of our early users sent us a message that stuck with me. She said the AI drafts we generated were genuinely good but she still spent just as long copying them into her CRM, scheduling them, checking if the numbers matched her dashboard.

We'd built a tool that was great at writing, and completely useless at finishing.

That one message changed how we thought about the whole product. We stopped asking "how do we make the output better" and started asking "how do we make the work actually done." That shift is the reason Dolv exists today. It doesn't stop at a draft, it goes and does the task across the tools you're already using, and only stops to ask you when something's about to reach a customer.

We're still early and have a lot to improve, but we're excited to finally put Dolv in front of real users.

AI have really generalized the knowledge, to the extent that things are really there, at the tip of your finger, when you need them, however you need them. While people like Elon Musk would love to enjoy the "abundance", as a Zen believer, I believe that the books are still better. But how many books can you really read in a unit time?

Not much! So I built Open Commonplace. It is the commonplace book built by the community, and for the community. Key Takeaways (and different notes) from the different books are here to be read by anyone. And you can post them too.

Hey Product Hunt!

I wanted to share a project I've been building called Screen Stickynote (https://screenstickynote.com/). It's a completely free, purely offline productivity workspace designed around an infinite 3D canvas.

I built Code Factory for my own needs after too many assistant-generated changes passed tests and then failed when I actually used them. The wasted time and frustration pushed me to put planning, evidence, and review into one proof-first workflow. I am sharing it free.

v0.32 adds a Counterfactual Arena to Graph Ops. It compares 2 12 supplied repair candidates, rejects failed proof, surviving mutants, scope escape, or changed receipts, and explains exactly why the smallest eligible repair won. It cannot generate or apply code; the human remains in control.

Solo builders get a readable choice before accepting an AI fix. Teams get a reproducible, hash-bound decision record. Time, token, and cost savings are shown only with an exact paired baseline; otherwise they remain Not measured.

I also used the open Prestige skill on the UI. In my own observation it materially improved the visual hierarchy and readability; the repo records its deterministic design checks without presenting that observation as measured conversion.

When vibe coding took off, it became possible to quickly turn product concepts into working software rather than leaving them in Figma or notes. But fast prototyping also made it easy to start projects without clarity, and I ended up abandoning a couple early on.

Now I m focused on one specific problem: building a community app for expats and travelers from my country. It s designed as a curated map where people pin local spots, share trusted services, and find businesses abroad where they can communicate comfortably in their native language.

For those building products for local communities or expats:

• How do you approach the initial cold-start problem (getting enough verified places onto the map)?

• What has been your biggest takeaway from previous projects that didn't take off?

Hey Product Hunt community!

I noticed a lot of small business owners and freelancers spend way too much time wrestling with Word templates or manual forms just to get a professional delivery note ready for shipment.

To solve this, I built the Free Online Delivery Note Maker by FDM AI. It s designed to be the fastest way to generate professional packing lists and proof of delivery documents.

Why I built it:

Most startups don t fail because of bad ideas.
They fail because of slow execution.

Take something like building a full eCommerce product:

Traditionally, it takes months sometimes 3 to 6+.

Hey Product Hunt

I m a solo developer and I ve been building NovaCapture, a native screen recorder for Mac.

I started building it because I kept finding that recording a good product demo takes more work than the actual demo. You record the screen, move the cursor around, and then spend more time editing everything to make it easier to follow.

That led me to build NovaCapture around automatic zoom, smooth cursor movement, webcam, and audio with the goal of making a clean demo straight from the recording.