Savio is a table of feedback rows, feature requests that group them, and people and companies that carry MRR, with a triage inbox and a voting board on top. For one product an agent builds that in a sitting and swaps the support-tool connectors for CSV import and a feedback mailbox. What you lose is the live sync from Intercom, Zendesk, HubSpot or Salesforce, which is the reason teams pick it over a plain voting board. If your feedback already arrives by email and a spreadsheet, you won't miss it.
Before you buildSavio has no free plan. If you only need a public voting page and not per-request MRR, Fider or another open-source board costs nothing to run.
Build me a private feedback inbox with a public voting board to replace Savio, for one product. Requirements: - Node.js 22 + TypeScript: Fastify with server-rendered pages (Eta) and a little vanilla JS. `npm start` serves http://localhost:4750: team side at /admin, public voting board at /board. - Storage: better-sqlite3 in ./data/feedback.db: companies (name, plan, mrr_cents), people (name, email, company), feedback (text, source: email / csv / form / manual, person, feature request, created_at), feature requests (title, description, status new / planned / in progress / shipped / declined, priority 1-5, effort S / M / L, public flag), tags and board votes. - Inbox: new feedback arrives unlinked. One screen shows it, lets me pick or create a feature request with type-ahead over titles, add tags and mark it triaged, with keyboard shortcuts for next, link and skip. - Totals: every feature request shows its feedback count, distinct people and companies and the summed MRR, computed in SQL at read time and never stored; sort and filter by status, tag and MRR. - Intake: an IMAP poller (`imapflow`, IMAP_* in .env) turns mail to a feedback@ mailbox into feedback and matches the sender to a person by email; CSV import for customers (name, email, company, plan, MRR) and for feedback, each with a dry-run preview; a /submit form with a honeypot field and a per-IP rate limit. - Board: public requests sorted by votes, one vote per email confirmed through a magic link (nodemailer SMTP from .env), and a shipped list. When a request ships, email everyone who gave feedback on it or voted, once each, with an unsubscribe link. - Export: CSV of feedback and of feature requests with their totals. - Single team, one admin password in .env (signed cookie). No accounts, no telemetry, local-first; outbound calls are your IMAP and SMTP servers only. - Out of scope: Intercom, Zendesk, HubSpot, Salesforce and Jira connectors, a Chrome extension, SSO, several products or roadmaps. - README: setup, mailbox setup, backups (copy the SQLite file) and a Caddy snippet for /board.
Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.
The first prompt builds the core. Run these one at a time in the same folder to grow it into your own Savio.
Add Slack intake to the feedback inbox in this folder. Requirements: - A Slack message shortcut "Log as feedback" and a /feedback slash command, both posting to /slack/events, with the request signature checked against SLACK_SIGNING_SECRET and a 5-minute timestamp window. - Match the Slack user's email to a person; if none matches, create one with source "slack". - Store the message link on the feedback row and reply in-thread with a link to the inbox. - Ignore bots and messages in channels not listed in .env. - Update the README with the Slack app setup steps.
Add a weekly digest to the feedback inbox in this folder. Requirements: - Every Monday at a time set in .env, email the admin the top 10 open feature requests by summed MRR, with the change in MRR and feedback count since last week. - List requests that gained feedback this week but have no priority or effort set. - A Send now button and a plain-text version of the same email. - Compute everything in SQL from the existing tables; store only the date of the last send. - Update the README.
Add a roadmap to the feedback inbox in this folder. Requirements: - /roadmap shows public feature requests in three columns (planned, in progress, shipped) with vote counts, linked to their board pages. - Admin can set a short public note and a target quarter per request; a private request never appears, even by URL. - Shipped items show the date they changed status. - Add an RSS feed of shipped items at /roadmap.xml. - Update the README.
Product managers pay to answer 'which request is worth the most revenue' without a spreadsheet: every request shows its customers, companies and MRR, kept current by the support tool and CRM connections. The founder-run support is part of what the pricing page lists on every plan.
Estimate · A small VPS runs it for about $5 a month, or nothing extra on one you already have. Sign-in and ship emails fit an SMTP free tier at this volume. The build is token usage on your agent plan.
| Plan | Monthly | Annual, per month | What you get |
|---|---|---|---|
| Essential | $49 | $39 | 1 paid user included, unlimited free users, 1 roadmap and 1 product, triage, a public or private voting board, and Intercom, Help Scout, Slack and email feedback logging. |
| Professional | $99 | $79 | Everything in Essential plus 5 roadmaps, customer segmentation, product areas, the Chrome extension, Zendesk, Zapier, the API, Shortcut and Jira. |
| Business | $299 | $249 | Everything in Professional plus multiple products, unlimited roadmaps, Segment, HubSpot and Salesforce. |
| Enterprise | custom | — | Custom terms, SLA, priority support, custom onboarding, a custom data-processing agreement and payment by invoice. |
No free plan, but a 14-day free trial with no card. Contributors, viewers and submitters are free on every plan.
Yes. An AI coding agent such as Claude Code, Codex or Cursor can build a usable personal version in one session with the prompt on this page, running on your own machine.
About $49 a month on the Essential plan per seat, $588 a year (checked 2026-10-19).
Live customer and feedback sync from Intercom, Help Scout, Zendesk, HubSpot and Salesforce; The Chrome extension that logs feedback from any web page; Two-way status sync with Jira and Shortcut; Single sign-on and voting on behalf of customers on the board; Several products and roadmaps, which the higher plans add. If any of those matter to you, keep paying.
Yes: Fider (open source), LogChimp (open source), Quackback (open source).