General
p/generalShare and discuss tech, products, business, startups, or product recommendations
trending
•

4mo ago

OpenAI has ACP, Google has AP2, Shopify has its own thing. Whats next?

The web was built for human eyes. Now the "customer" is increasingly an AI agent that can't read your layout, guesses at your forms, and renders a whole page just to find one price.

So everyone's shipping a protocol to fix it:

  • OpenAI + Stripe ACP (Agentic Commerce Protocol) - the rails behind ChatGPT's Instant Checkout.

  • Google AP2 (Agent Payments Protocol) - mandate-based, 60+ partners (Mastercard, PayPal, Amex), now handed to the FIDO Alliance.

If you run a store, this should feel familiar. It's the "build a separate app for every assistant" trap. IE vs Netscape. A native app per platform. Do you now integrate ACP and AP2 and MCP and whatever Amazon ships next quarter - and re-do it every time a new agent shows up?

•

4mo ago

Fantasy sports players: what is still missing from your tool stack?

Hey Product Hunt! I m Lawrence. I m a longtime fantasy football player currently building in the fantasy sports space.

For those of you who play fantasy football or other fantasy sports, do you use anything outside of the platform hosting your league, such as ESPN, Sleeper, or Yahoo?

That could include rankings, start/sit tools, injury alerts, AI assistants, league-sync products, spreadsheets, Discord communities, or anything else that helps you manage your teams.

I m especially curious about three things:

•

4mo ago

What separates an AI tutor from a chatbot?

AI tutoring tools are becoming more common, but I think there s still a big gap between answering questions and actually teaching. A chatbot can explain a concept, but a tutor identifies misconceptions, asks guiding questions, adapts explanations, and helps learners build confidence over time. I m curious how other builders and educators think about this. If you were designing an AI tutor today, what capabilities would you consider essential before calling it a tutor instead of a chatbot?
•

4mo ago

Why 80% of D2C brands get their packaging architecture wrong (and how to fix it)

Over the years working with growing retail and e-commerce brands, I ve noticed a recurring pattern: founders spend months perfecting their product, but treat packaging as an afterthought.

Packaging architecture isn't just about throwing a logo on a cardboard box it's a precise system of corrugation strength, fluting balances, shipping weight optimization, and engineering the ultimate unboxing experience without breaking the bank on high MOQs.

I wanted to open up a discussion here:

1 What s the biggest packaging or unboxing challenge you ve faced while scaling a physical product?
2 Have you ever had to redesign your packaging because of shipping damages or high dimensional weight costs?

Let's share some notes and solve some packaging puzzles together!

•

4mo ago

Why are AI vision tokens so much cheaper than text tokens for long context windows? 💸

Anthropic and Google charge heavy text token rates when you feed them huge context windows, logs, or codebases. But if you render that exact same text into a dense PNG, vision OCR pricing kicks in cutting overall token costs by ~60%.

•

4mo ago

Post-launch distribution vs. product optimization: How are you pacing your first 30 days?

After the initial launch spike on Product Hunt, most early-stage founders face a critical fork in the road: whether to double down immediately on aggressive paid distribution or spend those first weeks refining onboarding based on launch feedback.

From analyzing recent SaaS releases, a recurring pattern shows up: startups often see high top-of-funnel traffic during launch week, but bounce rates spike on cold channels (like LinkedIn or Meta Ads) because abstract AI features are hard to demonstrate visually in under 15 seconds.

On the other hand, focusing purely on product tweaks without an active acquisition engine quickly kills launch momentum.

For makers and tech builders who have shipped recently:

The most trust-building thing an AI feature can do is say "no" change my mind

Last week I tested an AI feature I'd built with a deliberately tight-finances scenario and asked: "Can we afford a $4,000 trip this fall?" Instead of the encouraging answer I half-expected, it came back with: you'd be ~$3,500 short using non-emergency funds, your monthly cash flow is negative so the gap widens over time, and the emergency fund stays off-limits. Verdict: "Not without a plan."

It refused to be nice. And it was the first output that made me believe someone would pay for the feature because anyone can ship an AI that says "sure, go for it." The value turned out to live entirely in the moments it pushes back with receipts.

Every roadmap bet needs a kill condition

Before we build a feature, I want one observable result that would make us stop, simplify, or change direction. Without that, every weak result becomes an argument to add another feature.

A kill condition is not pessimism. It protects the team from negotiating with the evidence after time and ego are already invested. The hard part is writing it before the build begins, when changing your mind is still cheap.

What condition would make you stop your current roadmap bet?

•

4mo ago

My AI model broke down 2 times in 8 days and it made me think differently about choosing one

Picking the AI model is a crucial decision for my product, and I really underestimated how hard it would be to pick one.
Before launch, I was considering things like:

  • Will users trust something that processes their messages with a model they have never heard of?

  • What is the real uptime record, versus the claimed one?

  • Do I go cheap/free, or pay more for something that will last longer?

  • Self-hosted? Or just ride on someone else s frontier model and take their roadmap?

    I took a solution and moved on, as you do when there are fifty other decisions to be made. And then on July 9th everything just stopped. There were no warnings I could see I spent hours debugging my own code before realizing the model itself was the problem. It turns out it was being decommissioned that October, and apparently a silent outage is how that gets communicated.
    I re-engineered the architecture to always have a backup model running in parallel, which quietly nibbled into margins I had already modeled carefully. Then again, same thing happened July 16. I don't think I've really worked this out so much as I've gotten better at taking it in when it happens again.
    For other founders building on someone else's AI model -- do you build in redundancy from day one or did it take getting burned once before you took it seriously?

•

4mo ago

Should AI tools be designed to say “wait”?

Most AI products are built to produce an answer, recommendation, signal, or action every time a user asks for something.

But in areas like trading, investing, healthcare, or cybersecurity, forcing an answer can be dangerous. Sometimes the most responsible output might be:

Wait.

There is not enough information.

First
Previous
•••
549550551
•••
Next