HN user

sameerav

3 karma

Founder, Entrepreneur with 15+ years of experience in customer acquisition and start-up growth

Posts6
Comments4
View on HN

That’s super helpful, thanks for sharing. We’re hearing the same pattern — analysis is exciting, but acting independently is a trust barrier.

We’ve been experimenting with a “propose → approve → execute” workflow (like you suggested with “pause the underperforming ads”), so the AI drafts the plan, but a human clicks yes before it runs. Kind of like a pull request for actions.

Version control / auditability is a great call — especially if people want to roll back or see exactly what changed. We’ve been thinking about logging each action almost like a Git commit history for ops, so nothing is a black box.

Do you think teams would adopt “propose + approve” mode first, and then maybe move to full autonomy later as confidence grows?

We’ve been experimenting with this question while building something new, and I’d love to hear how this community thinks about it.

Most teams we talk to still juggle data across Gmail, Slack, CRMs, Ads, spreadsheets, and custom internal systems. The dream is:

- Ask a natural-language question (“Which campaign gave us the best ROI last month?”) - Get the answer instantly, without waiting for a data team - And even take an action from the same place (“pause the underperforming ads,” “send a report to Slack”)

The obvious challenge: trust.

Would you let AI touch your production data or execute actions? Or should it remain read-only, with humans approving the final step?

We’ve built something in this space (hyperif.com), but I’m genuinely curious how you all see the balance between convenience and control.

- Where do you draw the line today? - What guardrails would you expect? - Is “analyze only” useful, or would “analyze + act” be the real unlock?

Would love to hear your perspectives.

Creator here. As a developer of several other saas solutions, I realized that the least creative and time-consuming work was building integration connections to service providers. Building an OAuth 2.0 framework and configuring + maintaining servers to manage tokens for multiple providers was a hassle. I knew there was a better way to do this.

So, I built Pathfix. I wanted to take away the pain of managing OAuth servers and tokens with an easy to use solution that allows you to offer integrations to your customers, in minutes.

Happy to answer any questions.