Savio's Mental Model
This guide gives you a short overview of the high-level concepts in Savio, and how they relate to each other. When you're done reading it, you'll have a much better grasp of the building blocks Savio uses to help you collect, manage, and analyze your customer feedback to make good product decisions.
Savio's Building Blocks
Savio has three core building blocks: People, Feedback, and Feature Requests.
They're covered more in detail below, but here's a simple way of thinking about how Savio works:
- People send in Feedback from tools your team uses, like Intercom, Zendesk, Help Scout, Salesforce, and Hubspot CRM
- That Feedback lands in your Savio Feedback Inbox, where your product team triages it
- During Triage, Feedback is assigned to a Feature Request. A Feature Request can have many pieces of Feedback
- During planning, you can filter your Feature Requests by number of People requesting it, MRR, Plan, and more.
- You can also drill into a Feature Request to see who's requested it and to reach out to the Person for more information
Each Person in Savio:
- has a name and email address
- belongs to an optional Account (if you use Accounts).
- has MRR and Plan properties (if you use Accounts, we'll pull MRR and Plan from the Account)
Each piece of Feedback has:
- a customer problem
- the Person who submitted it
- the type of person at that moment in time (a churned customer, active customer, lost deal, etc)
- a link to a Feature Request
When Feedback is sent to Savio, it lands in your Feedback Inbox. Feedback can be sent to Savio in one of nine ways:
- by applying a tag to a message in Intercom
- by applying a tag to a message in Help Scout
- by tagging a message in Zendesk
- by tracking win/loss feedback in Hubspot
- using the Chrome Extension
- it can be pushed from Slack
- because someone on your team emailed it to Savio
- it's sent in using the Savio API
- it can be entered directly in Savio
3. Feature Requests
Each Feature Request has:
- a title and description
- links to many pieces of Feedback
- the cumulative MRR of the people who've sent you Feedback
- a Status (Untriaged, Under Consideration, Planned, In Progress, Shipped, Won't Do)
- one or many Tags. A tag is a way to group Feature Requests together. They could be things like "Lower Churn", "Increase Activation", "Quality of Life Features", etc.
- a Priority and Effort (none / low / medium / high)
Putting it together
Now that you've got a good understanding of how Savio hangs together, here's a quick summary.
- You've got People (with MRR and Plan) who send Feedback to Savio. That Feedback gets assigned to a Feature Request.
- You can filter your Feature Requests to see requests from People that meet an MRR threshold, or are on a specific plan.
- You can drill into a Feature Request to see the People that requested it, and to reach out to those People to validate problem, solution, and to close the loop with them after it's built.