Hey Product Hunt! I’m Reuben, a filmmaker building something different to my usual 👋
Hey everyone! I’m Reuben. My wife and I run a filmmaking studio called Nusa & North, creating travel and hospitality films together.
Alongside that, I’ve started a separate experiment called AI Coder Class. I’m building a service to help small developer teams make sense of what they’re paying for AI coding tools, starting with Claude Team and GitHub Copilot Business.
The idea is simple: review their redacted invoices, seat lists and available usage data, then give them a clear report on what checks out, what needs investigating and what to look at before renewing.
I’m still figuring out whether this solves a problem people care enough about, so I’d genuinely appreciate some honest feedback.
If you manage these subscriptions, how do you currently decide which seats and plans to keep? Has reviewing the bill ever turned up something unexpected?
Nice to meet you all! Excited to see what everyone else is building.
Replies
Welcome Reuben! Honest take from a very small team: for two or three people the bill itself is easy to read, what's hard is knowing if a seat on a cheaper plan would do the same work, or if the expensive one is the reason things ship. Spend on AI coding for us moves with how much we build that month, not with seats. So the report I'd actually pay for wouldn't be "this seat is unused", it'd be "these two people hit limits every week, this one never does, here's the plan mix that fits". The bigger teams with procurement are probably where the invoice audit angle lands best.