Turning “this should be an agent” into real workflows (live on PH)
We just launched something we’ve been quietly building for a while on the “agentic AI for ops” side at DronaHQ, and I’d love feedback from this community.
Most AI tools I see are great for content, chats, or personal productivity. We went the other way and focused on real‑world ops: approvals, CX, sales, finance, and data workflows that actually touch your systems.
The DronaHQ Agentic Platform lets you plug into your existing stack (CRMs, helpdesks, billing, internal tools) and spin up production‑ready agents without wrestling with infra, stitching tools, or managing vector DBs. You describe the workflow, wire it to your tools, and let agents handle things like:
Invoice processing and approvals
Recruitment and candidate screening flows
Lead enrichment, routing, and follow‑ups
Travel desk and reimbursements
Data cleanup, sync, and reporting agents
Under the hood, it ships with 1000+ tools, native RAG, memory, guardrails, and observability baked in so you can actually trust agents in a live environment.
We’re live on Product Hunt today:
https://www.producthunt.com/products/dronahq/launches/dronahq-agentic-platform
Two asks from this group:
If you have 2–3 minutes, I’d really appreciate an honest comment on the PH page – what makes sense, what feels off, what’s missing.
What’s the craziest or most painful “this should really be an agent” workflow in your world right now? I’d love to hear ideas, edge cases, or “this would only work for me if it did X/Y/Z.”
Happy to answer anything about how we’re thinking about agent design, guardrails, memory, or real deployment stories in the thread.
Replies