The Frill alternative for feedback boards inside WordPress
Frill is a SaaS for public roadmaps, feedback widgets, and changelogs, embedded on your site through a script. SleekView covers the feedback and roadmap workflow inside WordPress itself, with ideas as CPT posts and votes as meta fields.
♾️ Lifetime License available
Roadmaps and feedback as WordPress views, not a SaaS widget
Frill is a SaaS feedback platform that has built a strong niche around public roadmaps, in-app feedback widgets, and changelog announcements. Teams typically embed Frill through a script tag or a hosted subdomain, with the boards, ideas, and votes stored in Frill's database. The product is well-known for its clean widget UX and its integrations into product analytics and PM tools.
SleekView's approach is structural rather than feature-based. The feedback board is a view over a CPT in WordPress: ideas are posts, statuses are a taxonomy or ACF select, votes are a meta field on the post, and the same CPT renders as a kanban grouped by status for the team or a sortable table for reporting. The board ships as a shortcode or block, not as a third-party widget, and the data lives in the WordPress install rather than a SaaS account.
The honest framing is that Frill keeps its edge on the SaaS surface: the in-app widget, the cross-stack embed, hosted SSO across multiple products, and analytics tuned for feedback teams. SleekView's edge is on WP-native posture: ideas are real posts, the pricing does not scale per user, and the same data renders as kanban and table views inside the site without a second tool.
Workflow
How a Frill board becomes a SleekView feedback view
Pick the CPT
Add the fields
Configure the feedback view
Embed in WordPress
Comparison
SleekView vs Frill at a glance
Differences
What changes when you move off Frill
The Frill way
- Ideas and votes live in Frill's database, not WordPress
- Embedded via script widget or subdomain
- Per-seat pricing scales with seats and feature tiers
- ACF and Meta Box are outside the model
- Reuse on WordPress side goes through the Frill API
The SleekView way
- Feedback board over any CPT
- Ideas stored in your WordPress database
- No per-user fees, included with the plugin licence
- Same data also as kanban and table
- Shortcode and block embed, no third-party widget
Features
Three things that actually change how you work
WordPress-native, not a widget
Frill ships a polished script-based widget that works across any stack. SleekView is a WordPress-only plugin, which is the trade-off and the point: the feedback board lives inside the site as a shortcode or block, not as an embed on top.
Flat plugin pricing
Frill's plans scale with seats and feature tiers. SleekView is a single plugin licence (also part of the Sleek All Access Pass), so adding contributors or boards over the years does not raise the per-user cost.
One CPT, three views
Frill separates roadmap, ideas, and changelog into modules. SleekView ships the public feedback board, an internal kanban grouped by status, and a sortable table for reporting as three views over the same CPT, with no duplicate data sets to maintain.
Migration
Moving from Frill to SleekView
1. Export from Frill
Use Frill's CSV or API export to dump ideas, statuses, categories, and vote counts. Note any custom attributes per board so they can map cleanly to ACF or Meta Box fields on the WordPress side.
2. Define a feedback CPT
Create a CPT in WordPress for ideas, with ACF or Meta Box fields for description, area, status, and a vote-count meta field. Mirror the attribute set Frill used so the import is a one-to-one mapping.
3. Import the data
Bring the export into the CPT through WP All Import or a similar tool. Carry Frill vote counts as meta values; SleekView takes over voting from there. Map authors to existing WordPress users where IDs align.
4. Embed and retire the widget
Replace the Frill script widget or subdomain with a SleekView shortcode or block on the same page, add a kanban view for the team, and once verified, cancel the Frill subscription.
Audience
Where teams move from Frill to SleekView
WordPress-first product sites
Sites where the product and the marketing site both run on WordPress (membership SaaS, plugin businesses, online courses) often prefer feedback to live in the same install. SleekView covers the workflow without a separate SaaS embed.
Data-sovereignty setups
Teams that want feedback data inside their own database (regulated industries, enterprise procurement) move from Frill to SleekView to keep ideas, votes, and statuses under the same backup and access controls as the rest of the site.
Reporting alongside other content
When the team wants to slice feedback together with release-note posts, articles, and products in one report, having ideas as a CPT lets WP_Query handle the joining. No reaching into Frill's API for every report.
The bigger picture
Why feedback inside WordPress beats feedback as a widget on top
Frill is a clean answer to the question "how do I bolt feedback onto any product I run, regardless of stack?" The widget is small, the UX is polished, and the multi-stack embed model means the same Frill account can serve a WordPress site, a React app, and a mobile in-app feedback panel. For teams that operate across stacks, that is genuine value. For a WordPress-first product or business, the same widget model creates a gap.
The feedback data lives in Frill, not WordPress, so cross-references from release-note posts, homepage widgets, internal reports, and search all need to go through Frill's API or live with the embed as a black box. Pricing scales with seats, even though the WordPress install is the only place the data is used. SleekView answers a narrower question ("how do I make feedback first-class in WordPress?") and tries to answer it well.
Ideas become a CPT, votes become a meta field, statuses become a taxonomy or ACF select, and the feedback board is one of three views over that CPT alongside a kanban for the team and a table for reporting. The pricing is the plugin licence, not a per-seat plan, and every cross-reference uses the same WP_Query, REST, and theme template surface the rest of the site already runs on. The honest reading is that Frill keeps its edge on multi-stack and in-app widget setups; SleekView wins for the WordPress sites that just want feedback to live where the rest of their content lives.
Questions
Common questions about switching from Frill
For the public roadmap and feedback-board parts, mostly yes. SleekView does not ship Frill's in-app widget, hosted SSO across multiple products, or changelog module as a separate product. Teams that lean heavily on the in-app widget on non-WordPress apps may keep Frill or pair it with SleekView. For WordPress-only sites the core workflow is covered.
In your WordPress database, as posts in the CPT you choose. Vote counts are meta fields with a separate voter ledger that enforces one vote per user. No feedback data leaves the install, so existing backup, access, and compliance settings apply.
Frill's pricing scales with seats and feature tiers; SleekView is a flat plugin licence (or part of the Sleek All Access Pass) with no per-user fees. Teams typically save once they have multiple admins or boards, though small setups on Frill's lower tiers may see comparable cost at the smallest scale.
Not in the SaaS sense. SleekView is a WordPress plugin, so the feedback board appears as a shortcode or block on any page. For sites that need a floating widget on every page, a small theme-level script can show the SleekView board in a slide-out panel, but it is not a one-line script tag the way Frill's widget is.
Through WordPress's standard login system. Any SSO plugin or custom OAuth setup already used for WordPress applies to voting, commenting, and posting ideas in SleekView. There is no separate SSO layer to configure.
Yes. Use a taxonomy or ACF select for area, then expose it as a filter on the feedback view. The same field drives grouping on a kanban view and a column on a table view, so one taxonomy serves all three renderings.
Yes, as initial meta values on the imported posts. SleekView treats the imported count as the starting number and adds or removes votes from there as users vote inside the new board. Frill's voter ledger does not migrate, but the visible totals do.
Yes. Frill stays embedded while SleekView is built over the new CPT. Once verified, swap the embed for the SleekView shortcode, redirect the Frill subdomain if used, and cancel the subscription.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout