The Features We’ll Never Build
Here’s a confession: we have a list of feature ideas that could keep us busy for years. New poll types, integrations, analytics dashboards, team management, conditional logic, file uploads – you name it, we’ve thought about it. Some of these ideas are genuinely exciting.
And yet, most of them will never make it into Letsfind.
That might sound like a weird flex, but hear us out. Because the hardest part of building a product isn’t adding features – it’s knowing which ones to leave out.
When Simple Tools Stop Being Simple
You’ve probably experienced this yourself. You discover a tool that does one thing really well. It’s clean, fast, and you immediately get it. No manual needed. You tell your friends about it.
Then the updates start rolling in. A settings page here. A new menu there. Suddenly there are tabs you didn’t ask for, toggles you don’t understand, and a pricing page that reads like a legal document. The tool you loved now feels like a job to use.
This isn’t hypothetical. It’s basically the story of every productivity tool that gained traction in the last decade.
Take Doodle, for example. Back in the day, Doodle was the tool for scheduling group meetings. Share a link, tick your available dates, done. Simple. Beautiful. Everyone used it.
Fast forward to today and Doodle has transformed into a full enterprise scheduling platform with four separate products, mandatory email addresses for every participant, a free tier so packed with ads it’s nearly unusable, and – our personal favorite – a UI that shows you seven weekdays at a time even when you only proposed one date. Their Trustpilot rating? 2.1 out of 5 stars, with 91% one-star reviews. Users describe the interface as “impossible to navigate.”
Oh, and you want to create a poll? You’ll need to hand over your email first. Not to send you the poll link – to sign you up for an account.
That’s not a failure of engineering. That’s what happens when you say yes to every feature request without asking: does this make things simpler for the person using it?
How We Keep Letsfind Simple
At Letsfind, we think a lot about what we don’t build. And we’ve developed a simple test for every new feature idea:
Does it make the core experience better, or does it just make the product bigger?
There’s a difference. A bigger product isn’t a better product. A better product is one where every element earns its place by helping you get from A to B faster.
Here’s what we mean. When you open Letsfind for the first time, the entire flow looks like this:
- Pick a poll type
- Type your question, add your options
- Hit create
- Share the link
That’s it. No account required. No onboarding wizard with five steps and a progress bar. No “complete your profile” popup. No “would you like to enable notifications?” modal. No cookie banner. You came to create a poll, so we let you create a poll.
This sounds obvious, but it’s surprisingly rare. Most tools can’t resist the urge to introduce themselves before letting you do your thing. We’d rather get out of your way.
A Simple Poll Tool Doesn’t Mean a Limited One
There’s a common misconception in product design: that simple means limited. That if a tool is easy to use, it must be lacking features. We disagree.
Simplicity isn’t about removing things until nothing is left. It’s about removing the right things until only what matters remains. The goal is clarity, not emptiness.
Letsfind currently has three poll types: Date Polls, Text Polls, and Live Polls – with a fourth one (Matrix Polls for availability scheduling) on the way. That’s it. We could have twenty. But a handful of focused poll types covers the vast majority of group decision scenarios – from finding a dinner date to running a live audience vote in front of hundreds of people. Each poll type is distinct and purposeful. None of them overlap.
The same thinking applies to our voting experience. When someone receives your poll link, they tap it, see the question, pick their answer, and they’re done. No signup wall. No “download our app for the full experience” interstitial. Just the poll.
We’ve seen tools where the act of voting – the simplest possible interaction – requires creating an account, verifying an email, and accepting three different permission prompts. At that point, your friend group just goes back to the WhatsApp chat and argues for another hour.
The Design Principles Behind Letsfind
We’re not going to pretend we invented these ideas. Good design has been studied and written about for decades. But here are a few principles that genuinely guide how we build Letsfind:
Reduce decisions, not options. Every choice a user has to make is friction. “Do I need an account?” is friction. “Which of these 12 poll types do I need?” is friction. We aim for the user to make as few decisions as possible before reaching their goal. A few poll types, clear names, obvious differences.
Progressive disclosure. Not everyone needs advanced settings. So we hide them behind a toggle. The default path is clean and simple. Power users can dig deeper if they want. But the 90% who just need a basic poll never have to see options they’ll never use.
Optimize for the participant, not just the creator. The person creating a poll visits once. The people voting on it might be dozens or hundreds. That’s why the voting experience is ruthlessly simple – because most of your users are voters, not creators.
Ship less, ship better. We’d rather have a few poll types that work flawlessly than twelve that kind of work. Every new feature introduces complexity not just for users, but for us as developers. More code means more bugs, more edge cases, more things that can break. Staying lean keeps quality high.
The Hidden Cost of “Just One More Feature”
Here’s the honest truth about building something simple: it’s really, really hard.
We love getting feature requests – seriously, keep them coming. Every suggestion we receive helps us understand how people actually use Letsfind, and some of the best features we’ve shipped started as a message from a user. If you have an idea, hit us up at contact@letsfind.app. We read every single one.
But here’s the thing: loving an idea and building it aren’t the same thing. Because even a great feature comes with hidden weight. A comments section means moderation tools, notification settings, spam filtering, and a new surface area for abuse. Conditional logic means a new editor, new validation rules, and a steeper learning curve. Custom colors mean a color picker, a preview mode, and accessibility testing for every possible combination.
One feature doesn’t just add one thing. It adds the complexity of that thing interacting with everything else.
So when we evaluate a feature, we don’t just ask “is this useful?” We ask “is this useful enough to justify the complexity it introduces for every user, including those who will never use it?”
Sometimes the answer is “not right now.” And that’s okay. It doesn’t mean the idea is bad – it means we’re being careful about what we put in front of you. Your feature request might very well shape a future version of Letsfind. That’s exactly why we want to hear from you.
Why We Built Letsfind This Way
We built Letsfind because the tools we were using felt unnecessarily complicated. Creating a simple poll shouldn’t require a PhD – or even an account. It should be as easy as typing a question and sharing a link.
That belief hasn’t changed since day one. If anything, it’s gotten stronger. Because the longer we build this product, the more we realize that simplicity isn’t a starting point you grow out of. It’s a discipline you practice every single day.
The next time you create a poll on Letsfind and think “wow, that was fast” – know that a lot of thought went into making it feel that effortless. The best design is the one you don’t notice. And we intend to keep it that way.
Got ideas, feedback, or just want to say hi? We’re always listening at contact@letsfind.app.
Laters. ✌️