Best Products
Launches
Launch archive
Most-loved launches by the community
Launch Guide
Checklists and pro tips for launching
News
Newsletter
The best of Product Hunt, every day
Stories
Tech news, interviews, and tips from makers
Changelog
New Product Hunt features and releases
Forums
Forums
Ask questions, find support, and connect
Kitty Points Leaderboard
The highest scoring community members
Streaks
The most active community members
Events
Meet others online and in-person
Advertise
Subscribe
Sign in
Clear text
recent
p/pushary
by
Aadil Ghani
β’
24d ago
Your agent does something wrong. How far does it reach before anyone notices?
... hand back to the terminal took us longer to settle than building the delivery did. So did reaching the one person who can answer when they are not sitting in front of your product, and being able to
prove
afterwards who approved what. The two I still cannot answer, and I do not think anyone has: How do you reach the person who has to decide, when they are not looking at your product and never installed anything of yours ... ... rather than hold the line forever. A stalled job that took the cautious path is recoverable. A stalled job that just sat there is a support ticket. Comment from Dale Mooney(@dalemooney): @alex_amancio_candoa_ @aadilghani Constant
versus
168
210
p/pushary
by
Aadil Ghani
β’
3mo ago
How do you stay aware of what your AI coding agents are doing?
... have actually diverged in outcome in the ledger so far and if it's inferred, what's your cold-start before a single divergence has been observed? Comment from Alexander Bering(@alexanderbering): @aadilghani The reason "edit
vs
. tell-it-to-revise
vs
505
391
p/rankfender
by
Imed Radhouani
Featured
β’
5mo ago
We spent 6 months building for enterprise. Nobody bought it.
... thought we knew We assumed enterprise customers wanted the same things as our small business users, just more of it. More security. More control. More features. We never talked to them. We read blog posts. We looked at
competitor
pricing pages. We guessed. Here's what we missed: Procurement cycles. Enterprise deals take 6-12 months. We had 30-day sales cycles. We weren't built for that. Security reviews. We needed SOC2. We didn't have it. Customers asked ... ... care about SSO or audit logs they cared that we sat with their team for two weeks understanding their workflows before writing a single line of custom code. Your data table showing SSO (4 requests, 2 actual users)
vs
130
167
Subscribe
Sign in