Free
For solo builders testing the waters.
$0/mo
- 1 project
- Up to 15 open feature requests
- Track 15 customers by name and revenue (MRR)
- Community upvoting
- 25 AI agent calls per day (read-only)
- Reqio badge on your widget
User feedback tool
User feedback that's structured, prioritized, and acted on.
Stop reading through support tickets and Slack threads. Reqio collects structured feedback in your product, sorts it by votes and revenue, and gives your AI agent direct access to the backlog.
No credit card required · Embed in 2 minutes
Built for product teams
The feedback tool for teams that ship, not survey
Most feedback tools are built for marketers running NPS surveys. Reqio is built for product teams who want to know what users actually need and who want that signal organized, prioritized, and accessible to their whole workflow, including their AI coding agent.
Revenue-weighted feedback
Know who's giving the feedback, not just what they said
The Reqio identity SDK (available for Node.js, Next.js, Python, PHP, Ruby, and Go) lets you pass a signed user identity token to the widget. When you do, every submission and vote is tied to a real user in your system, complete with their email, display name, and MRR tier if you pass it.
- See whether high-MRR customers or free-tier users are driving the most requests
- Sort the backlog by revenue impact, not just vote count
- Know which company or account submitted a critical error report
One request, three surfaces
See how a request travels
1
A user submits in your embedded widget, routed and categorized before it reaches you.
2
It lands in your dashboard backlog, revenue-weighted and sorted by votes.
3
$ mcp connect https://reqio.app/p/my-project/mcpConnected. 20 tools available.$ call list_features --limit 2 --sort votes{"features": [{ "id": "feat_x42", "title": "[user-submitted] Dark mode support", "status": "NEEDS_ACTION", "voteCount": 42, "commentCount": 8 },{ "id": "feat_x19", "title": "[user-submitted] CSV export", "status": "IN_PROGRESS", "voteCount": 19, "commentCount": 3 },]}$ call reply_conversation --id conv_7r9 --body "Shipped in v2.4. Let us know if anything looks off."Reply sent.Subscriber notified.
Your AI agent reads it, triages it, replies to the conversation, and when it marks it complete, subscribers hear about it automatically.
Async conversations
Your team and your users, in one thread
Every private submission (bug report, unexpected behavior, feedback, or question) opens a shared conversation thread. Your team replies in the dashboard. The user gets notified and can reply by email. Their reply lands back in the same thread. It is async, not live chat, so it works on everyone's schedule.
How it works
From user friction to shipped fix, without the chaos
Capture feedback where it happens
The widget is embedded on your product, not on a feedback portal. When a user hits friction, they click the widget and describe it in the moment, with context.
Feedback is structured automatically
Users pick their path (make a request, report a problem, or talk to you) before they type. Every submission arrives routed, with the page URL and optional diagnostic context attached.
Prioritize by votes and revenue
Other users vote on submissions they care about. If you pass MRR data via the identity SDK, the backlog shows you demand weighted by paying customer value, not just raw vote counts.
Ship and close the loop
Move a request to Completed. The users who submitted or upvoted it see the update. No changelog emails to write, no manual follow-up.
For product teams
Feedback features built for the people who act on it
In-product capture
Feedback submitted from the screen where the user experienced something is 10x more useful than a feedback form they fill out three days later.
Routed from the first tap
Five paths in three groups, picked before the user types. Your backlog arrives organized from day one, with no post-hoc tagging required.
Identity-aware
Pass a signed identity token from your own auth system. The backlog shows names, emails, and MRR tiers, so you know who your loudest users are.
Votes by real users
Voting is scoped to users who are actually on your product. The numbers reflect genuine demand, not gameable anonymous internet votes.
Team inbox and triage
Invite your team. Triage together. Internal notes are private to your team; status updates are visible to the users who asked.
Full project management via MCP
Your AI coding agent can triage requests, reply to conversations, send announcements, and configure the widget via the built-in MCP server. 20 tools, all gated by the connecting user's role.
Common questions about user feedback
What makes Reqio different from other user feedback tools?
Most feedback tools are either survey platforms (one-shot) or support inboxes (unstructured). Reqio is a persistent, structured feedback layer embedded in your product. Every submission is categorized, votable, and tracked through a status pipeline. The result is a living backlog rather than a pile of emails, and it's accessible to your AI coding agent via MCP.
How does Reqio capture feedback in context?
The Reqio widget is embedded directly on your product using one script tag. A small button appears on every page (or on specific pages if you configure it that way). When a user has something to say, they click it and describe their feedback right there, not by navigating to a separate feedback portal or filling out a survey email.
Can I tie user feedback to my actual users from my database?
Yes. The identity SDK lets you mint a signed JWT on your server and pass it to the widget on page load. The widget sends this token with every submission and vote, so the feedback is tied to your user record, including their name, email, and any MRR or plan data you attach.
How does Reqio handle error reports differently from feature requests?
The widget opens with a category picker. If a user selects Error, the submission captures additional diagnostic context automatically: the page URL, browser details, and any JavaScript errors on the page at the time of submission. Bug reports arrive with the context your team needs to reproduce them.
Can I filter user feedback by category or status?
Yes. The backlog dashboard lets you filter by category (feature, bug, unexpected, feedback, question), by status (Needs action, In progress, Completed), or by both at once. You can also sort by vote count or by submission date.
Is user feedback private to my team?
Yes. Users who submit feedback through the widget can see the status of their own request, but they cannot browse other users' submissions or see any identity information about other users. The backlog is only accessible to you and your invited team members.
Pricing
Start free. Upgrade when you're ready.
The free plan includes one project and community voting. No credit card required.
Get started free
Pro
For teams actively shipping based on user feedback.
$24.17/mo
billed annually $290
- Up to 2 projects
- Unlimited feature requests
- Track 100 customers by name and revenue (MRR)
- Threaded comments on requests
- Internal notes on each request
- Custom brand color and logo
- Up to 3 developer seats
- 300 AI agent calls per day with write access
Business
For scaling teams that need more room to grow.
$82.5/mo
billed annually $990
- Everything in Pro, plus
- Up to 10 projects
- Track 1,000 customers by name and revenue (MRR)
- Up to 15 developer seats
- Remove Reqio branding from the widget
- 3,000 AI agent calls per day with write access
Give your product team a structured view of what users actually need.
No credit card required · Embed in 2 minutes