The day we realised hosts needed to stop saying yes to every enquiry
Three months into Findr's first year, a photography studio owner in Manchester messaged me at 10 pm. 'I've had 47 booking requests this month. 47. I'm approving ones that don't work because I can't keep up.' She wasn't complaining. She was exhausted.
When opportunity becomes a problem
What sounds like a good problem to have isn't always. The studio owner had done everything right: beautiful portfolio, fair pricing, responsive to messages. She was attracting genuine enquiries from renters who wanted to book her space. But the approval workflow for every single booking was killing her ability to actually run her studio.
That's when I realised we'd built Findr in a way that only scaled so far. Our core flow worked beautifully: a renter finds a space, sends a booking request, the host approves or declines, everyone confirms dates and times through in-app messaging. It's collaborative. It's safe. Neither party feels pressured.
But somewhere around 30 or 40 active bookings per month, that flow starts to feel like a second job. The host is still running their actual business. They're teaching classes, shooting photos, running events. Every notification becomes an interruption.
The tension between control and friction
Here's where it got complicated. We couldn't just flip a switch and make all bookings instant. That would solve the host's problem but create a new one for renters. No one wants to book a £400 studio session only to find out the date was actually unavailable, or the host changed their mind. The approval step exists for a reason.
We spent weeks talking to hosts who'd expressed interest in faster bookings. What we found was clear: most of them wanted choice. A yoga instructor with a morning and afternoon slot wanted Instant Book for her reliable morning regulars, but preferred approval for evening bookings (when logistics get messier). A meetup coordinator wanted instant confirmation for recurring weekly sessions but manual approval for one-off events.
That's when the answer became obvious. Not instant for everyone. Instant for the venues where a host felt confident enough to say yes automatically.
How Instant Book found its shape
We built Instant Book as a Pro tier feature because it needed guardrails. A host who enables it on a supported venue is saying: I trust this booking to proceed without my approval, as long as the renter follows my calendar and my rules. The renter still sees the exact same listing details, availability, and terms. They still message the host if they need to. Nothing changes except the speed of confirmation.
It sounds simple, but the engineering required thinking hard about edge cases. What happens if a host disables Instant Book after a renter has already sent a request? What if calendar data doesn't sync in time? We had to make sure the system never leaves either party in limbo. The renter's deposit is secure through Stripe. The host's calendar is protected. Both parties have an auditable record of what was agreed and when.
The Pro tier made sense as the home for this feature because hosts who've reached that level of booking volume are usually the ones who need it most. They're running their space seriously, often with multiple listings or a solid calendar system already in place.
What changed when we launched it
The first week after launch, I watched the data come through. A handful of hosts turned on Instant Book immediately. A London event space with two listings activated it on her main hall but kept approval on her smaller breakout room. A photography studio in Bristol enabled it across the board. A dance studio in Glasgow left it off entirely, saying the conversation with each renter was part of why she loved the work.
That last host taught me something. Instant Book isn't a feature that every host needs. It's a feature for hosts who've outgrown the approval workflow and want to keep hosting. For hosts who don't want to say no to bookings because they're too busy managing yes.
The renters who use it report something unexpected: it feels less like a transaction and more like confirmation. There's no waiting. No anxiety about whether the host will approve them. They see the space, they know the rules, they book. The host who enabled it has already made the decision that the space is worth booking.
The bigger picture: when features solve real friction
Building Instant Book taught me something about feature development that I wish I'd understood from the start. The most useful features aren't the ones that sound impressive. They're the ones that solve a specific moment of friction in someone's real working day.
That Manchester studio owner messaged me again a month after Instant Book went live. She didn't enable it on all her bookings, but she enabled it on her peak evening slots where she got the most enquiries. 'Now I'm not choosing between answering messages and actually using my studio,' she wrote.
That's the whole point. Findr exists because creatives and organisers need space. Hosts need to earn from their space without that earning becoming a full-time job of managing approvals. When you build a marketplace, you have to remember both sides. A feature that only serves the renter or only serves the host isn't really complete.
If you're a host running a space and you're drowning in approval requests, that might be a sign that Instant Book could work for you. But it also might be a sign that your space is worth a lot more, to more people, than you realised. What would change if you didn't have to say no to any booking?