The question that changed how we built Findr
The filter fatigue problem nobody talks about
Most venue marketplaces work the same way. You land on a map. You pick a borough. You untick 'kitchenette' and tick 'natural light'. Then you scroll through seventeen results, half of which don't match what you actually wanted. By result twelve, you've forgotten why you came.
I spent weeks watching how Findr users actually booked. Not through our product flow charts or use cases, but through support messages and booking data. The pattern was clear: people who got frustrated weren't looking for features. They were looking for speed. They wanted to describe a need and see relevant spaces, immediately.
The moment we knew we had to change
Launch week was chaos in the best way. Hundreds of signups, real bookings happening, hosts uploading spaces. But something became obvious when I read through the first week of feedback: free users were hitting their three monthly booking request limit in days, not weeks. They were requesting over and over because our filters kept missing the mark.
We realised we were doing the work for people. Instead of letting them describe their needs and surfacing the right spaces, we were forcing them to know the right language of our interface. A photographer needs "tall ceilings" and "north-facing light". Our filter buttons said "ceiling height" and "natural light condition". Small words, big difference.
What changed when we listened
The Plus tier now includes what we call natural-language search. Type in actual sentences. "I need a studio with a kitchen for a half-day workshop in Zone 2" or "Photography space with a white cyc wall, available next Saturday morning". The system reads what you've written and returns spaces that match, ranked by relevance. No filter menus. No guessing which button means what.
We tested it internally first. Our team tried the old filters, then the new search, on the same requirements. The new search saved minutes per session. But more importantly, it felt right. It felt like talking to someone who understood venue booking, not wrestling with a tickbox form.
Hosts noticed the difference too. The quality of booking requests went up. People were asking for spaces they actually needed, not spaces that happened to survive our filter logic.
The bigger picture: what renters actually value
I think the reason this matters isn't technical. It's about respect for time. A photographer booking a studio for a shoot has maybe twenty minutes to sort out her space. An event organiser managing a launch has chaos everywhere. Nobody wants to be clever about search syntax or learn which filters are buried behind which dropdown.
What changed for us was accepting that a booking platform should work like a conversation, not a directory. You describe what you need. You see spaces that fit. You message the host if something's unclear. That's it.
The Plus tier also includes advanced filters, which matter to the people who want them. But they sit underneath the search. You can start with natural language and refine from there if you need to. Or you can reverse it, filter first and then adjust with a sentence. The choice is yours.
We've been careful not to oversell what this does. It doesn't find spaces that don't exist. It can't book instantly (that's the Pro tier with Instant Book on supported venues). It's a filter, really. But it's a filter that speaks English.
Why this matters for how we build
Launching Findr taught me that the easiest feature to ship isn't always the one renters need. For months, I assumed people wanted more filters. Bigger maps. More booking power. What they actually wanted was to be understood quickly.
The business side works too. Hosts get better-qualified bookings. Renters book faster. The friction drops. And something interesting happened: people on the free tier started upgrading to Plus not because we marketed the features hard, but because the search actually saved them time. That's the kind of feedback loop that matters.
When was the last time a search felt like a conversation instead of a puzzle? Maybe that's the question we should all be asking more often.