I posted one question in a Facebook group and got 35 replies — here's what I learned about validating a SaaS idea
I'm building a lightweight tool for Airbnb hosts to collect cleaning photo proof from their cleaners. Before writing any code, I wanted to validate the problem.
So I posted this in an Airbnb host Facebook group:
"For remote Airbnb hosts: how do you verify your cleaner actually finished every room before the next guest checks in?"
35 replies in 48 hours. Here's what surprised me:
Good cleaners WANT to send photo proof. 9 cleaners replied, and the best ones already do it voluntarily — because it protects them when a guest lies about damage.
The #1 "system" is no system. Most hosts collect photos via text message and manually save them to folders. When a guest complains, they can't find anything.
Cleaners hate downloading apps. Multiple hosts mentioned Turno and Breezeway, but also said their cleaners resist learning yet another app.
The framing that changed everything. A cleaning company owner said: "Photos aren't about distrusting cleaners. They're about proving the condition of the home before and after guests." That shifted my whole product direction — from "monitoring" to "proof of work."
I'm now building Cleanproof: one link for the cleaner, room-by-room photos + checklist, timestamped report for the host. No app download.
The question I'm stuck on: how do you cross the gap between "this sounds useful" and "I'll actually try it"?
The strongest signal here isn’t the feature idea—it’s the shift in who benefits from the proof.
When cleaners want to submit evidence, the product stops being about verification and starts becoming coordination. Most tools fail here because they frame it as monitoring, when in reality it’s a shared accountability system between two parties with aligned incentives.
This is the underrated unlock — going where the audience already is beats posting into your own empty feed every time. The 35 replies came because you asked in a room that was already full. Curious: did any of them convert to actual users/emails, or was it purely signal? The gap between "people engaged" and "people who'd pay" is where a lot of validation gets misread.
the gap closes when you remove the setup effort and tie first use to a real event. you already have your beachhead: the exact people in that thread who said "sounds useful" are warm leads. DM those 35, offer to set up the link for their next turnover — done-for-you. adoption here isn't evergreen, it's event-triggered: nobody tries proof-of-work in the abstract, they try it the day they've got a cleaning scheduled and a guest checking in. and lead with "your cleaner clicks one link, no app" — that's the host's real fear. don't build a landing page and wait; hand-deliver the first turnover to the people who already raised their hand.
Great post. That final question — "how do you cross the gap" — is the one every indie tool builder hits.
We ran into the exact same wall with a different product. We validated the problem (creators need help finding conversations on Threads), got the "sounds useful" nods, then spent €20 on Google Ads and got 0 installs.
What's working for us instead: showing up where the users already hang out and proving value through conversations, not ads. Reply to people talking about the problem, show you understand it, and only mention your tool if they ask.
The "ask a question instead of pitching" approach you used for validation works for distribution too. We post insights about our space daily. Some people click through. Some don't. But the ones who do are already sold because they saw the thinking first.
Would love to hear how Cleanproof goes — the framing shift from monitoring to proof of work is smart.
Great approach. Asking a question instead of pitching is such an underrated validation tactic. People are much more willing to share their workflow than review a product they haven't used yet. The quality of feedback is usually much higher too.