I’ve been using WPFeatureLoop on two of my own plugins for just over a month. In that time, I collected over 150 votes across 11 feature requests, and it already changed what I’m building next.
Here’s what the data actually looks like, and what it taught me about my own blind spots as a developer.
The Raw Numbers
Two plugins, two different user bases, one month of data:
| Feature request | Votes | Comments |
|---|---|---|
| Feature A | 41 up · 9 down | — |
| Feature B | 51 up · 29 down | — |
| Feature C | 4 up | — |
| Feature D | 14 up · 4 down | 2 comments |
| Feature E | 8 up · 1 down | — |
| Feature F | 7 up · 1 down | — |
| Feature G | 5 up · 1 down | — |
| Feature H | 6 up | — |
| Feature I | 5 up | — |
| Feature J | 4 up · 1 down | — |
| Feature K | 1 up | — |
Nothing groundbreaking at first glance. But the interesting part isn’t the table — it’s what it told me I was wrong about.
I Was Going to Skip the Most Requested Feature
One of these plugins is a delivery system for WordPress. When a customer places an order, the flow ends with a WhatsApp message to the store owner. Simple, effective.
I had been considering adding a proper order confirmation screen — the kind you see on any e-commerce checkout: “Your order has been placed, here’s your order number, here’s what you ordered.”
I almost didn’t build it. My assumption was that it would add friction to the checkout flow. The user already gets the WhatsApp confirmation. Why add another step?
Then the votes came in. Over 20 upvotes for an order confirmation screen. It was one of the most requested features, significantly more than things I assumed were higher priority, like advanced coupon rules.
That was a clear signal. My users didn’t see it as friction. They saw it as trust. A confirmation screen tells the customer “your order went through.” Without it, some customers weren’t sure if the WhatsApp message actually sent.
I moved it to the top of the roadmap. It’s now built and shipping.
The point isn’t that I was wrong. The point is that without the data, I would have confidently skipped a feature my users actively wanted. That’s the most dangerous kind of product mistake: the one you don’t even know you’re making.
A Feature Request That Became a Business Signal
The second plugin is a WooCommerce extension. One feature request stood out immediately: integration with the official WhatsApp Business API.
50+ upvotes. And not just votes — users subscribed to get notified when the feature would be ready.
This isn’t just “people want this.” This is demand validation. When users actively subscribe to a feature they can’t use yet, they’re telling you: “I will pay attention when this ships. I might pay for this.”
That changes the conversation. It’s no longer a question of whether to build it. It’s a question of how to monetize it and when to ship.
Without the voting data, this would have been one more item on a backlog. With it, it became a strategic priority with a clear signal of willingness to engage.
Why This Matters for Plugin Developers
If you’re building WordPress plugins, you’re probably making roadmap decisions based on some combination of support tickets, gut feeling, and what competitors are doing.
Support tickets are biased toward problems, not opportunities. Gut feeling is unreliable at scale. Competitor analysis tells you what others are building, not what your users want.
Feature voting fills a specific gap: it tells you what your users value before you build it.
Here’s what I learned in one month:
Downvotes are data too. Feature B had 51 upvotes but also 29 downvotes. That’s not consensus, it’s a polarizing feature. Building it means pleasing some users and frustrating others. That context matters for prioritization and for how you ship it (maybe as an optional setting, not a default).
Volume isn’t everything. Feature K had 1 upvote. That doesn’t mean it’s worthless — it means it’s niche. If that one user is a high-value customer or represents a segment you want to grow, it might still be worth building. But you know not to prioritize it over a 40-vote request.
Silence is a signal. The features nobody votes on are just as informative. If you were planning to build something and it gets zero engagement from your user base, that’s useful information before you spend three weeks on it.
The Real Value Is in the Assumptions You Catch
The confirmation screen story is the one that keeps coming back to me. I had a strong opinion. It felt like the right call. And without any data, I would have shipped a roadmap that skipped one of the most wanted features.
That’s what feature voting actually does. It doesn’t replace your judgment, it challenges your assumptions before they become expensive decisions.
One month. Two plugins. Over 150 votes. Two roadmap changes I wouldn’t have made otherwise.
That’s the case for putting a feedback loop inside your plugin, not on a separate page your users will never visit.
WPFeatureLoop is a feature voting platform for WordPress plugin developers. Add a voting widget directly inside your plugin’s admin, no external pages, no friction. Try it free.