How We Prioritize Features (Spoiler: It’s Not Just Votes)
Ah yes, feature requests — the beautiful chaos of building software.
You submit ideas, vote on others, and patiently wait as we either build your dream... or leave it in the void forever (we’re sorry 😅).
But have you ever wondered what really happens after you hit "submit feature request"?
Let’s break down how we actually prioritize what gets built.
🗳 Votes Matter… but Only a Little
Look, we love democracy. But if we built only what got the most votes, we’d be drowning in emoji reactions and “can you add AI?” requests.
Votes help us spot patterns — but they’re not the whole story.
🔥 1. Pain > Popularity
We ask ourselves:
Is this feature solving a real pain point, or is it just ✨nice to have✨?
If 5 users are screaming for something that blocks their workflow, it might take priority over 50 quiet votes for a cosmetic change.
We care more about impact than hype.
⏱ 2. How Long Will It Take?
If something is high-impact and low-effort, it’s a no-brainer.
If it’s high-impact but requires three weeks, two engineers, and a blood pact, we pause and plan accordingly.
And sometimes, a tiny feature hides a big tech debt monster. Surprise! 🎉
🧩 3. Does It Fit the Vision?
Not every idea — no matter how clever — aligns with where we're heading.
Our north star: Help SaaS teams communicate better with their users.
So if a request takes us off that path (looking at you, cryptocurrency payment plugin), it goes in the "someday, maybe" pile.
💬 4. What’s Support Saying?
Our support team is basically our early warning system.
If they’re getting the same question 20 times a week, that’s a red flag — and usually a sign we need to fix or build something.
They’re also great at spotting confusing UX, missing documentation, or where users are rage-clicking.
📊 5. Usage Data Doesn’t Lie
We look at what features people actually use — not just what they say they want.
Sometimes there’s a big disconnect between “this would be cool” and “I use this every day.”
We prioritize what drives real engagement, not just wishlist fluff.
🛠 So… What Happens After That?
Once we’ve run a request through all those filters, we put it into one of three buckets:
- Build Soon – It's impactful, aligned, and doable ✅
- Needs Design/Research – We like it, but gotta figure it out 🤔
- Not Right Now – Good idea, not a priority 💔
🎯 TL;DR – How We Prioritize
1. Votes help, but pain points matter more
2. Impact > effort > alignment > timing
3. Our roadmap is strategic — not just reactive
4. Yes, we read every request. Even the weird ones.
Got an idea that’s keeping you up at night?
[Send it our way](#). The worst that can happen?
It ends up in our meme channel.
Thanks for helping us build better, one weird request at a time 🙌