Post by RevOps Co-op

Most RevOps teams are positioned as a support function. Ticket queue. Reactive analytics. Win-loss at end of quarter. Amani Phipps thinks that's the wrong mental model entirely. His take: RevOps IS a product team. Your stakeholders are your ICPs. The unified system of tools, processes, and people you build and maintain? That's your product. And once you internalize that framing, everything changes — what you prioritize, how you structure your team, and how you deploy AI. Here's what that looks like in practice at Bonusly: 🤖 They built Bonusly GPT — an internal Slack-based AI tool that's now handled ~8,000 employee requests at a 70-person company. Some employees have used it 700–800 times individually. 📋 Deal desk tickets dropped from ~60/month to ~20/month. Time per ticket? Down ~90%. The rep gets an answer from a bot. Amani just verifies. 📞 A Gong-to-HubSpot integration (built with Claude Code) now parses call transcripts and auto-updates deal object properties — so sellers aren't doing data entry. They're selling. 📊 And they're currently building Signal Forge — a multi-agent analytics system with daily, weekly, monthly, and quarterly agents that aggregate context over time. The goal: eliminate most of the reporting work entirely. The thread connecting all of it? Start with education, not tools. Find the most obvious use case in your daily work. Fix your data foundation before you build anything on top of it. And keep a human in the loop — just move them upstream to the work that actually needs judgment. None of this happened overnight. It took iterations of team structure, a few key projects that proved RevOps could directly influence revenue, and a lot of late nights on data cleanup. But the direction is clear. Peep the highlight reel below ⬇️ 📺 Catch the full episode + write-up on our site: https://lnkd.in/gfx-qJcx #revops #revenueoperations #AI #gtm #salesops

Video Content