From a RevOps seat, the questions are always the same: can I trust the data, and can I move it where it needs to go? For us, it’s been yes on both. Attribution windows are configurable by program, we dedupe partner-sourced signups against paid search so we’re not paying twice for the same customer, and webhook delivery has been reliable enough that I stopped building a reconciliation job around it. Just as important, everything I see in the UI is available in the API, so I’m not stuck with gaps when I need to automate or audit. We’ve also connected the MCP server, and that’s changed how the go-to-market team asks questions—they can ask in plain language now instead of filing a request with me.

I’m essentially the entire partnerships department at a 30-person company, so anything that requires a dedicated admin is a non-starter for me. This doesn’t. Partners can self-serve through a branded portal, get their own links and stats, and I only get pinged when something actually needs a decision. And because nobody charges me per partner, I can say yes to a small creator without having to stop and do a cost calculation first. The one thing I’d genuinely miss is the MCP connection. I can ask Claude, “Which partners dropped off this month, and what did they have in common?” and get a useful answer right away, instead of having to learn BI tooling that I honestly have no business learning.

Subscription businesses break most affiliate tools because a conversion isn’t a one-time event; it’s an ongoing relationship that renews, downgrades, churns, and sometimes comes back. This handles that reality well. It lets me pay commission on MRR for a defined window, syncs with Stripe in a way that reflects plan changes instead of only the first charge, and includes HubSpot attribution so my sales team stops arguing with my partner team about who actually sourced a deal. Trial-to-paid attribution also resolves correctly, which sounds basic but is apparently hard to get right.