My landing page names six different kinds of customer. Six cards, each with its own headline and its own reason this is for you. The thing behind them does exactly one job, and it does it identically no matter which of the six you happen to be.

I wrote the six on purpose. The logic was that a stranger scrolling wants to see themselves on the page, and one generic line does that for nobody. Recognition is cheap to add and it feels like it ought to help.

I've started to think the six cards are doing the opposite. A page that speaks to six people can read like it was written for none of them, and the more specific each card gets, the more obvious it is that nothing underneath changes when you pick one.

Three moves I've looked at and not made.

I came across DeepSeek's new Search & Fetch APIs and thought they might be useful for something I'm building.

I'm working on a tool to find competitors and discover discussions about similar products on Reddit. Right now, I'm exploring ways to make that research less manual.

The APIs seem promising, but I'm wondering how well they'd work for this use case.

Has anyone tried them in a real project? Would they cover most of what I need or would I still need to build a separate crawler.

We re happy @Mercury customers here at Product Hunt. We previously used SVB (I ve used them at other startups as well), but the interface was clunky, and the bureaucratic process was frustrating so we switched to Mercury and couldn t be happier!

Mercury recently introduced expense and reimbursement features. While it may not have all the bells and whistles and detailed permissioning of longer-established options like @Brex , it meets our current needs.

Git is a lifesaver but checking massive diffs after every AI prompt gets exhausting real fast. A lot of times the AI introduces subtle bugs that still compile fine, so tests don't catch them immediately.

Writing a quick automated test before asking the AI to add a new feature has saved me so many times because the test instantly fails if it messes up existing code.

Do you rely on unit tests or just manually review every single line in the diff view?

Ok so i'm a solo maker and over the years i've ended up with way too many small products lol some react/ui libraries, a few native mac apps, some cli stuff and plugins. same guy behind all of them (me) but honestly each one lives its own life: own site, own release cycle, a couple even have their own newsletter.

lately people keep asking me "ok but where do i report bugs / ask for features / just hang out" and tbh i don't have a good answer yet.

We've been fully remote for over two years now.

While daily coding output felt high we kept hitting a wall where features got shipped with small logic gaps that no one caught during planning.

We recently started getting the team together in person just once a month not for long presentations but just to sit and work in the same room.

Having that physical proximity dropped our rework rate significantly.

I ran a check on my own site today and found markup for a feature that stopped existing in May.

Google added a deprecation notice to the FAQ rich result on 8 May 2026, saying it would no longer appear in Search from 7 May. On 15 June they deleted the documentation page entirely. The reason they gave was that the feature is no longer shown in Search results.

My site never noticed. My own /faq route returns 200 today and still serves an FAQPage block with 18 acceptedAnswer entries in it. Twenty route files emit the same schema, plus a helper that builds it for every blog post.

Nothing failed, and that is the part worth sitting with. The FAQPage type is still defined in the vocabulary, so every validator passes it. The build compiles. No test covers whether Google still renders the thing. The only change happened on Google's side, and there is no channel that carries it back to you.

When starting out, it's easy to write down ambitious long term plans for scaling and team expansion. But reading through those exact notes years later can be an eye opener when you realize your mindset has changed.

I caught myself working toward targets that I wouldn't even enjoy hitting today. It's tough to notice that subtle shift while you're busy running things day to day.

Have you ever caught yourself pushing toward an old goal that no longer fits what you want for your business?