Source Reddit post: https://www.reddit.com/r/airbnb_hosts/comments/1ue00ee/is_this_normal_what_should_i_do/
One-line thesis: Build a lightweight AirCover evidence-pack workflow for small Airbnb/short-term-rental hosts that turns checkout photos, cleaner notes, guest messages, receipts/quotes, review timing, and claim deadlines into a submission-ready damage-claim packet.
Classification: opportunity / idea_filter.
This is a BUILD, but only with a narrow wedge. The pain is real: Airbnb’s own process requires hosts to document damage, request reimbursement, wait for the guest’s response, escalate when the guest refuses to pay or does not respond, and provide legitimate/verifiable evidence under tight deadlines. The seed Reddit thread shows the day-to-day version of the problem: a small host sees stained towels, sheets, a sofa, and a missing remote after checkout, has cleaner photos, is unsure whether to charge, and is worried about the review. A comment captures the core product insight: pre-check-in photos plus after photos are the strongest damage-claim evidence, and the review and claim should stay separate.
The opportunity is not “beat Airbnb support.” It is a support checklist and evidence assembly layer that helps small hosts avoid preventable claim failures: missing before photos, weak timestamps, no cleaner statement, no receipt/quote, messy message history, missed 14-day/24-hour deadlines, accidental review leverage, and no clean escalation packet when Airbnb Support asks for proof.
The biggest caution: a direct competitor already exists. HostClaim markets itself as an Airbnb/VRBO/Booking.com damage-claim assistant that organizes evidence, tracks filing windows, and prepares what the platform asks for. That validates demand but reduces novelty. The stronger build angle is a faster, host-and-cleaner workflow embedded at turnover time: “capture the evidence before it disappears,” then generate a packet for Airbnb’s Resolution Center.
Best initial customer:
Avoid at first:
1. The seed Reddit thread shows ordinary hosts are unsure what is claim-worthy and how to balance claims with reviews. The host asks whether stained towels, sheets, a sofa, and a missing remote after a 4-night stay are “normal” and whether to charge. Comments advise using the Resolution Center with photos, separating the review and damage request, and getting before/after proof. This is exactly the “support checklist under pressure” moment.
2. Airbnb’s own Help Center creates the evidence-pack job. Airbnb tells hosts to document damage with photos or videos, repair or cleaning estimates, and/or receipts, then file a reimbursement request in the Resolution Center within 14 days of the responsible guest’s checkout. The guest has 24 hours to respond. If they do not respond, pay partially, or decline, the host can submit under Host damage protection and Airbnb Support reviews the request.
3. Airbnb’s Host Damage Protection Terms require a structured proof bundle, not just a complaint. The terms require a Host Damage Protection Payment Request Form and “Legitimate and Verifiable Evidence” supporting the existence, extent, and amount of the loss. Airbnb lists time, cause, origin, receipts, photographs, videos, documents, complete inventory of damaged property, make/model, acquisition date, condition at time of loss/damage, repair/replacement cost, repair estimates, and cleaning invoices/receipts. That maps almost directly to a product checklist.
4. Guest refusal/non-response is built into the process. Airbnb’s guest-side Help Center says a guest has 24 hours to respond to a reimbursement request, and Airbnb may step in if host and guest do not agree. HostClaim’s guide uses the same pattern: escalate when the guest doesn’t pay. The product should preserve this language because hosts search for “guest refused to pay” and “guest doesn’t pay damage claim.”
5. Security deposits are not a simple default substitute for most Airbnb hosts. Airbnb says most hosts are not allowed to charge security deposits through the Resolution Center or outside Airbnb; Airbnb positions AirCover as the path for damage/accidents. This makes evidence quality more important because many small hosts cannot simply hold a deposit and charge it.
6. Airbnb Community threads show claim evidence can still feel insufficient. One host described submitting photos, videos, and Airbnb message logs before guest checkout and still receiving a denial/template replies. Another described a couch burn claim with photos, original receipt, and photos from past cleanings showing no prior damage while the guest denied responsibility. Whether or not Airbnb was right in those cases, the operational pain is clear: hosts need an organized support checklist, timestamped message history, before/after evidence, and escalation record.
7. Review timing is intertwined but must be handled separately. The seed Reddit thread includes advice to keep the review and claim separate and never use one as leverage. Airbnb’s review policy emphasizes authentic/trustworthy reviews and search-result snippets say reviews may not retaliate for enforcing Airbnb policy. A product that reminds hosts “review and claim separate” can prevent sloppy messages that hurt claims or violate policy.
8. Competitor behavior validates the category. HostClaim already sells a damage-claim assistant for Airbnb, VRBO, and Booking.com. Its landing page promises evidence organization, filing-window tracking, and claim preparation, with UI language like “damage photos uploaded,” “repair estimate on file,” and “checkout date logged.” Enso Connect and ChargeAutomation validate adjacent spend on damage deposits/waivers; Turno validates cleaner photo-checklist workflows.
Weekend-buildable first version: AirCover Evidence Pack Builder.
Input:
Core output:
1. Evidence checklist: damage photos, before photos, timestamp/source, item inventory, receipt/quote, cleaner statement, guest message, resolution request status.
2. Claim timeline: checkout deadline, next check-in warning, 14-day reimbursement request deadline, 24-hour guest response timer, 30-day supporting documentation reminder where relevant.
3. Damage inventory: item, room, claimed amount, repair/replace/cleaning basis, proof available, proof missing, policy-risk flag such as “linens/towels may be harder unless tied to qualifying circumstances.”
4. Message history packet: exportable chronology of Airbnb messages and a suggested neutral reimbursement request.
5. Review and claim separate guardrail: warnings if draft language sounds retaliatory or links a review to payment.
6. Support escalation pack: PDF/ZIP with table of contents, photos, receipts, estimates, before/after comparison, cleaner note, and concise claim summary for Airbnb Support.
7. Cleaner capture link: mobile link for cleaners to upload room/item photos immediately after checkout with timestamps and required angles.
Do not start with policy adjudication or reimbursement guarantees. Start with evidence completeness, deadline tracking, and a clean packet the host files themselves.
| Dimension | Score | Rationale |
|---|---|---|
| Pain | 8 | Damage claims are stressful, deadline-driven, and evidence-heavy; the Reddit seed and Airbnb Community threads show confusion around photos, message history, reviews, and guest refusal. |
| Willingness to pay | 6 | Hosts will pay during active claims, especially for furniture/smoke/pet/party damage; low-frequency hosts may resist subscriptions. |
| Reachability | 8 | r/airbnb_hosts, Airbnb Community, STR Facebook groups, cleaner networks, SEO, and co-host communities are reachable with checklist content. |
| MVP simplicity | 7 | A checklist/timeline/PDF pack builder is feasible without deep Airbnb integration; automated message/photo import is harder. |
| Competition | 5 | HostClaim is a direct competitor; PMS, cleaners, damage waivers, and property managers cover adjacent slices. |
| Overall | 7 | Worth testing as a cleaner-first, deadline-aware evidence pack, but only if positioned narrower than generic claim consulting. |
1. Interview 10 hosts who filed an AirCover claim in the last year: what evidence did they have, what did Airbnb ask for, what was denied, and what did they wish they had captured before cleaning?
2. Interview 5 STR cleaners: what damage do they notice, how do they send photos, and would a required capture link fit turnover workflow?
3. Manually build 5 anonymized evidence packs for active/past claims and measure host willingness to pay.
4. Test SEO/community landing pages around “Airbnb damage claim evidence,” “guest refused to pay Airbnb damage claim,” “AirCover photos receipts message history,” and “review and claim separate.”
5. Compare directly against HostClaim: find the underserved segment rather than copying the category.
The strongest objection is that this idea already has a named competitor in HostClaim. That does not kill the opportunity, but it means a generic “Airbnb claim assistant” is too broad. The product must win through timing and workflow: cleaner-first capture immediately after checkout, before/after photo matching, evidence completeness scoring, and review/claim guardrails.
The seed Reddit post is also relatively small-dollar: towels, sheets, sofa stain, and a remote. That could indicate a weak willingness-to-pay case for minor incidents. The better revenue cases are smoke odor, pets, parties, broken furniture, unauthorized guests, and repeated cleaner-documented issues. Still, the small-dollar thread is valuable because it shows how confusion starts before a claim is filed.
Some sources are vendor blogs or community anecdotes, so they should be treated as directional. The primary proof is Airbnb’s own documented process and Host Damage Protection Terms. Any product copy must cite Airbnb policies conservatively and update often.
Finally, software cannot manufacture evidence after the fact. If hosts do not take before photos or keep receipts, the pack may still fail. The right promise is “make your claim complete and organized,” not “get your claim approved.”
A practical, buildable SMB workflow for helping small STR hosts assemble stronger AirCover damage-claim packets, but distribution and differentiation versus HostClaim/templates need proof.