Feedback software comparison
Feedbackly vs Productboard: Pricing and Workflow
Feedbackly and Productboard are different choices for different jobs. Feedbackly offers an owner-managed public request board with voting and status updates. Productboard supports a broader product planning workflow. Start with who needs to manage the system and what happens after a customer submits feedback.
By Feedbackly · Published plans checked
Compare pricing, fit, and limits
We publish Feedbackly. This comparison uses our supported capabilities and the official vendor pages linked below; it is not a hands-on test of competing products. Prices and plan details can change.
| Product | Published price | Useful for | Check before choosing |
|---|---|---|---|
| Feedbackly official pricing | $9/month or $90/year | Public requests, voting, a roadmap, and reviewed Slack, Notion, or CSV imports for one board owner. | No shared administration, private boards, or custom domains. CSV imports do not preserve votes or customer identities. |
| Productboard official pricing | Business: request a demo; Enterprise: contact sales | Collaborative product planning, customer insights, roadmaps, and prioritization. | Pricing is based on makers; published plans list a minimum of five. Confirm your quote and required integrations. |
What Feedbackly supports
On the $9/month or $90/year subscription, one account owner can manage unlimited boards, requests, and votes. Customers and teammates participate through public requests, comments, and voting. The subscription also includes the in-app widget, custom branding, reviewed Slack and Notion imports, CSV import, and publishing board updates to Notion.
Requests can move through Under review, Planned, In progress, and Completed. Verified followers receive status-change emails. Editable value scores are estimates, not measured revenue. Shared administration, private boards, and custom domains are not currently supported. Check these limits before choosing Feedbackly for a team or a confidential feedback process.
When to keep a broader planning platform
If several product managers coordinate decisions across products, test how the candidate handles ownership, permissions, research context, and delivery dependencies. A public board is useful for customer communication, but it does not establish an internal planning process by itself.
For a hypothetical solo founder reviewing ten public requests each week, a focused board may be sufficient. For a hypothetical product team that needs shared research and coordinated release planning, evaluate the wider platform against those tasks. These examples describe decision criteria, not customer results or hands-on benchmark tests.
Use a trial to answer three concrete questions
First, can you bring in a real request without losing the customer problem? Second, can the right person review and update it? Third, can the customer understand the result? Try one request that you accept, one that needs clarification, and one you defer. Record any manual work the process introduces.
Feedbackly's seven-day trial requires no credit card. You can preview up to 100 CSV requests, but only titles and descriptions transfer; imported requests start under review with zero votes. Keep your original export and confirm how comments, private evidence, and delivery records will be retained before committing to a migration.
Try the workflow with your own requests
Create a public board, review a small import, and test a status update. Seven days free, no credit card.