how to prioritize initiatives is one of the top problems mentioned by product teams that we interact with Inari, so we’ve been exploring a bit this week on how to make prioritizing feedback, insights, and issues more effective and easy. i hadn’t researched prioritization

do you ever sit down sunday night, plan out your biggest project to tackle during the week, then get completely derailed when unexpected bugs pop up? well hey, dis me 👋🏼😅 this week we got an unexpected 10x+ influx in feedback ingested analyzed from several new orgs connecting

steph curry is a national treasure. we must protect him at all costs.

we’re stoked to ship a direct integration between Inari with GitHub today to make managing requests and communities more effective and easy! here’s how it works: 1. you can connect your github repos with inari then all open issues will be ingested and analyzed as new

two quick ships today in Inari! you can now directly integrate Zendesk with inari to ingest your support conversations for automated analysis and generating insights and issues based on customer comments. after connecting inari to zendesk, you can select specific groups

it's finally shipped 👋🏼 the top direct integration request for Inari is live now: Gong! you can now directly integrate gong with inari to ingest all sales call transcripts from specific workspaces then inari will automatically analyze each conversation for useful

spent the last 30 min testing a bunch of internal Inari prompts for analyzing feedback, generating insights + product ideas, etc on gpt4o vs gpto1 vs claude sonnet 3.5. seeing gpt4o > claude sonnet 3.5 > gpt o1 just based on my anecdotal review of a few sample outputs (which

building a great product and company requires talking to and learning from as many customers as possible. but as a company scales, it becomes increasingly tough to stay on top of problems and requests that customers are sharing with you on a regular basis. to help with this,