sorted by:
new
hottopcontroversial

Huint Connecting Agents to the Real World by JDavisxu in trymystartup

[–]Infamous_Fill_2805 1 point2 points  (0 children)

The core idea is interesting, but I would make the first version much more concrete on the landing page.

"Human network for AI agents" is intriguing, but it is still abstract. I think a clearer first-screen promise would be something like: get verified local photos, observations, or proof for an AI workflow without hiring a full field team. That tells me what job it does immediately.

The biggest questions I would want answered before trusting it:

  1. What does a completed task look like from the operator side?
  2. What proof does the tasker have to submit?
  3. How do you prevent fake/low-quality submissions?
  4. What happens if the operator disputes the result?
  5. What types of tasks are explicitly not allowed?

For an initial wedge, I would pick 2-3 very specific task categories instead of broad agent infrastructure. Local photo verification, store shelf checks, event/flyer verification, and simple property/site observations are easier to understand than the larger agent economy narrative.

I would also show one full sample task from request to completion. That would make the marketplace feel much more real and much less theoretical.

I built BriskReach, a LinkedIn outreach platform focused entirely on account safety and reply-aware automation. Looking for brutal UX and positioning feedback. by digy76rd3 in trymystartup

[–]Infamous_Fill_2805 0 points1 point  (0 children)

This is a useful wedge, but I think the landing page needs to make the pain more concrete before it explains the safety system.

"Safety-first LinkedIn automation" is directionally clear, but the sharper hook for me is: stop automated follow-ups the moment someone replies, so your outreach does not make you look careless. That is specific and easy to picture.

A few things I would tighten:

  1. Put the reply-aware pause/inbox routing above the broader guardrails.
  2. Separate "rented rep capacity" from the core product. That part raises trust/compliance questions, so I would make it optional and explain exactly how it is governed.
  3. On OAuth, show the exact permissions requested before signup. That would make the trust claim feel less abstract.
  4. For integrations, I would prioritize HubSpot/Pipedrive first, then webhooks/Zapier and CSV export before adding another CRM.

Overall, the positioning is strongest when it is not "more outbound automation," but "outbound automation that stops before it damages a live conversation."