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.
The strongest signal in your post is that cleaners already want to send the proof. So your onboarding should start with the next turnover, not some generic free trial. I'd make the first experience one property, one cleaner, one link, and one auto-generated report, because the second someone has to learn a whole new system, you lose the exact people who just told you they hate apps. I built DictaFlow around a similar lesson from a different angle: if the workflow change is bigger than the pain, people stick with the ugly workaround.
The gap between "this sounds useful" and actually trying it is where most validated ideas stall. The 35 people who replied are already the warmest possible audience and the bare-bones MVP suggestion is right because those same people already told you the problem is real. The question now is whether they'll do anything when you hand them a solution.
Closing that gap is almost always a trust and friction problem more than a product problem. The first version doesn't need to be good, it needs to be easy enough to try that saying yes costs them almost nothing.
One thing I've realized while building is that validation and adoption are two completely different milestones.
People can genuinely like your idea and still never use it because they don't need it today. The first users usually come when your product fits into an immediate workflow or pain point, not just because it sounds useful.
Those 35 replies are a great signal. I'd focus on getting 3–5 of those people to use it during their very next turnover rather than chasing more validation.
Strong signal already.
That gap is usually friction, not understanding. If it replaces texting photos, adoption comes from fitting the existing workflow, not changing it.
Have you tried framing it as a drop-in replacement for what they already do?
35 replies in 48 hours from one question in the right group is more signal than most founders get in months of building. The difference is asking where the frustration already lives rather than hoping people will come find you to complain.
The proof of work reframe is the most important insight here. Monitoring implies someone is being watched. Proof of work implies both sides benefit from the record existing. That single shift probably changes how both hosts and cleaners feel about adopting it.
Great framing shift from "monitoring" to "proof of work" - that's the insight that unlocks willingness. The gap between "sounds useful" and "I'll try it" is really about removing activation friction. Since your cleaners and hosts already exchange photos over text, what if the MVP is just a dead simple form they fill during checkout? No app, no login flow, just one link they text to their cleaner and the photos auto-upload to a timestamped report. You already have your early user list from those 35 replies - could you do a hand-delivery beta with just 5 of them, using their actual next turnover as the test case?
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.
This is the question that trips up most first-time builders. 35 replies feels like strong validation, but "people talked about this problem" and "people will pay to solve it" are separated by a canyon.
The most reliable signal I've found isn't engagement on your post — it's whether people are already spending time or money on a bad solution. In this case, the hosts manually saving photos to folders and the cleaners already sending photos voluntarily — that's actually a strong buying signal, because they've built a workaround. They're already "paying" in time.
Where it gets tricky is when people say "sounds useful" but have no current workaround — that usually means the pain isn't acute enough to convert. One way to pressure-test is to look at whether competing tools (Turno, Breezeway) have users complaining about specific missing features in their app store reviews. If hosts are writing "I wish Turno had photo verification built in" — that's someone who already pays for a tool and wants more. That's a completely different signal than a Facebook comment.
I kept running this kind of cross-referencing manually — Reddit threads, app store reviews, search volume — until it became my whole workflow. Eventually turned it into RightIdea.app to automate the process. But even without a tool, the principle holds: the best validation isn't "did people respond to my post" but "are people already hacking together a solution to this?"
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.