Brian K.

can report back on how that goes, thanks y'all!

gotcha, we have some pieces of this internally with AI, where we extract every blocker/feature request from customer conversation transcripts/messages with AI and group them across all the calls our team is making. but the part about connecting it with the ARR from the CRM is great, because it's been tough to prioritize purely based on # of times we've heard it and whether it means we should prioritize it over other things. we should be able to do that with our AI agents too. our goal is that the roadmap/backlog tasks of R&D has a clear picture at all times of who is asking for what/the opportunity size, so we can tighten the feedback loop with sales to have them go win those deals once blockers/reqs are addressed.

Thanks all! that definitely makes sense, to track this along with ARR, wondering how the product council / ELT conversations go and how the cadence feels... do you feel like there could be significant gains if this feedback loop was tighter? or is this system good enough? lot of sales teams I've talked to also feel like they don't know when a feature ships and who they should follow up with exactly and does this process seem like it takes a lot of manual time? or fits into your clients' existing workflows pretty well?

i guess either, both when you need a quick feedback loop on we need to win this deal vs. we're seeing a trend of losing these deals, and we need this prioritized so we can win them.

will do, thanks for the rec Jared!