MRR-weighted votes
A vote from $5K MRR isn't equal to a vote from a free trial.
Every other feedback tool sorts feature requests by raw vote count. Supoid pulls MRR from Stripe (read-only restricted key) and weights every vote by the revenue behind it — so you stop shipping for free users while paying customers churn waiting.
Restricted key, 3 read-only scopes (Customers, Subscriptions, Prices). We can never charge, refund, or modify your billing. Encrypted AES-256-GCM at rest.
We auto-create a Stripe webhook at connect time (if your key has webhook_endpoints:write). Subscription changes flow in within seconds. Otherwise hourly polling sync.
Stripe sync + MRR weighting is included on every plan, including Free. No per-event metering, no Salesforce add-on like UserVoice.
Why this matters
Stop shipping what free users ask for
47 free-trial votes for dark mode vs 12 paying-customer votes for the Linear integration. Sort by votes and you ship dark mode. Sort by MRR and you ship the integration — and the $4,800 MRR cohort renews instead of churns.
Filter the inbox by revenue
Saved view: 'Show me only feedback from $1K+ MRR customers this week'. The triage queue you've been begging for, without writing a single SQL line.
MRR pill on every surface
Inbox row, detail header, cluster strip, customer profile, customer table. Always visible, never buried in a separate report.
Read-only, not Stripe Connect
We use a restricted key (you keep ownership). No platform onboarding, no settlement delays, no 'Powered by Supoid' on your invoices. Disconnect anytime — your customer data stays.
How it works
- 01
Connect Stripe in Settings
Settings → Integrations → Stripe. Click the prefilled key-creator link (we send you straight to dashboard.stripe.com with the right name and 3 scopes pre-checked). Paste the key, done.
- 02
Sync pulls every active subscription
First run scans all customers (paginated, capped at 5,000). Yearly plans normalised to monthly ($990/yr → $82.50/mo). Sub-cost yearly = $0 MRR. Cancelled / past_due skipped — no stale revenue overcount.
- 03
Match voters by email
When a feedback is submitted (logged-in user via widget, public-board submission with email, or imported), we lowercase the email and look it up in identified_users. Found = MRR pill appears. Not found = anonymous.
- 04
Per-feedback MRR impact
When you sort the inbox by MRR, we sum identified_users.mrr_cents across all voters of each feedback. A correlated subquery keeps the row shape unchanged — no pre-aggregation cron required.
- 05
Cluster MRR rollup, dedupe by email
Each cluster shows total MRR represented across all member feedback, deduped by voter email. Two feedback from the same $5K MRR customer count once, not twice.
- 06
Webhook for real-time updates
If the restricted key carries webhook_endpoints:write, we register a webhook automatically. customer.subscription.* events trigger a fresh per-customer sync within seconds. Otherwise polling sync runs hourly.
Side by side
| Feature | Supoid | Featurebase / Canny / Productboard |
|---|---|---|
| MRR-weighted votes, native | — | |
| Stripe restricted-key (read-only) | manual API key setup | |
| Real-time webhook auto-create | — | |
| Inbox sort by MRR represented | — | |
| Cluster MRR rollup (email-deduped) | — | |
| MRR pill on every row | Productboard customer profile only | |
| Filter saved view: '$1K+ MRR' | — | |
| Salesforce CRM sync (full bidirectional) | via Salesforce integration | Canny + Productboard native |
| Pipedrive / HubSpot deal value sync | via HubSpot integration | Productboard native, others via Zapier |
| Custom CRM segments (NRR / ARR cohorts) | — | Productboard Enterprise |
| Included on Free plan | — |
Ready to hear what your customers actually want?
Six minutes from sign-up to your first clustered, tagged, actionable feedback. Free forever for solo founders.
No credit card · Cancel anytime · GDPR self-service