CheckinDocket

1. One-liner

Proves the guest got in on time, and files the waiver claim inside Vrbo’s 10-day window when they didn’t.

2. Trend signal — why now?

On 1 October 2025 Vrbo turned a bad night into a bill. Its Host-Initiated Cancellation Policy stopped being about hosts who cancel and started being about hosts who don’t answer the phone.

The specifics are what make this a product:

• The 100% tier is new, and inaction triggers it. The US fee ladder runs 10% of reservation value for a cancellation more than 30 days out, 25% at 2–30 days, and 50% within 48 hours — including non-responsiveness that violates the Communications Policy. Effective 1 October 2025, a new 100% tier applies when a reservation is “passively not honoured” due to unresponsiveness, or a guest is denied entry without justifiable cause. The guest also gets a full refund. A single bad check-in can cost roughly twice the booking value.
• The trigger is operational, not a decision. Vrbo counts it as host-initiated when a guest arrives within expected hours and cannot enter, when the host fails to send codes or directions, or when Vrbo cannot reach the host by phone or message. A dead lock battery, a code that didn’t push, a missed call at 11pm — same penalty as deliberately cancelling.
• The response clock is brutal and explicit. Critical stay information must be answered within 24 hours at 5+ days out, 12 hours at 1–4 days, and 1 hour on check-in day and during the stay (08:00–21:00 property time). Vrbo states plainly: “You must resolve the specific issue or tell them when it will be resolved. An automatic reply does not count.”
• Premier Host went zero-tolerance on 1 January 2026. Standards moved from 95% acceptance / ≤1% cancellations / 4.4+ rating to 99%+ acceptance, a 0% owner-initiated cancellation rate, 4.6+ average rating and 5+ reviews. Recognition also dropped to the individual listing level, and metrics are assessed quarterly (1 Feb, 1 May, 1 Aug, 1 Nov) over a trailing 365 days. One incident poisons a listing for a year.
• There is a waiver — on a 10-day fuse most hosts never learn about. Hosts can request a cancellation waiver within 10 days, submitting the reservation ID, an explanation, relevant guest communication and supporting evidence. One industry guide puts it bluntly: “most hosts don’t know this window exists.” Miss it and the fee sticks.
• The exposure is expanding. Vrbo can charge up to 100% of the booking amount as a penalty, and the policy is expanding to international properties in 2026. Vrbo carries over 2 million bookable listings worldwide, and its bookings skew large — whole-home, longer stays, with a $3,000 reservation described as a typical 7-night booking and Vacation Rentals of the Year running $400–$4,000 a night.

Money is moving here too: Hostaway raised $365M at a $925M valuation (Dec 2024, General Atlantic) and Guesty has raised $409M. North America STR gross bookings hit $78B in 2025, projected to grow ~5% to $81.8B in 2026.

The tell is what those well-funded vendors actually shipped. Hostaway, Hospitable, Hostfully and Zeevou have all published explainer articles about the Vrbo cancellation policy. Not one of them sells a feature that files the waiver. Hostfully’s page promotes its channel manager and pre-arrival messaging, then leaves the host to email support alone.

Provenance:

• Signal 1 (demand): Vrbo’s Host-Initiated Cancellation Policy, effective 1 Oct 2025, charges up to 100% of the booking amount when a guest is denied entry or the reservation is “passively not honoured” through unresponsiveness — on top of a 100% guest refund — with hosts publicly calling it “crazy” and threatening to leave the platform — https://www.steadily.com/blog/vrbo-host-cancellation-policy-explained and https://www.expedia.com/newsroom/vrbo-cracks-down-on-properties-that-cancel-on-guests-raises-standards-for-premier-hosts — observed 2026-09-04
• Signal 2 (feasibility): The waiver is a documented, structured claim — reservation ID, explanation, guest communication and supporting evidence, filed within 10 days — against published, machine-checkable response SLAs (1 hour on check-in day, 12h/24h before), which makes evidence capture and claim drafting an automation problem rather than a judgement problem — https://ensoconnect.com/resources/vrbo-host-cancellation-policy-how-to-stay-compliant and https://www.hostfully.com/blog/vrbo-cancellation-policy/ — observed 2026-09-04
• Signal 3 (economic): Vrbo raised Premier Host standards to a 0% owner-initiated cancellation rate effective 1 Jan 2026, assessed quarterly on a trailing 365 days at individual-listing level, in a North American STR market worth $78B in 2025 where Hostaway ($365M at $925M valuation) and Guesty ($409M) are funded but ship only explainer content on this policy — https://www.rentalscaleup.com/vrbo-premier-host-2026-standards/ and https://techcrunch.com/2024/12/17/travel-is-back-hostaway-raises-365m-at-a-925m-valuation/ — observed 2026-09-04 Category: Platform shift

3. The opportunity

Vrbo created a penalty that is charged automatically and reversed only manually — and then hid the reversal behind a 10-day clock.

Look at the asymmetry. The fee is assessed by Vrbo’s systems from booking data they already hold, and deducted from future payouts. The waiver requires the host to notice the charge, understand a waiver exists, assemble a message history proving they met the 72-hour and 1-hour rules, gather lock logs or photos, write an explanation, and submit it within 10 days. One side is automated. The other side is a human remembering to fight.

That is the same shape as chargeback defence before chargeback tooling existed. The merchant always had the right to represent the dispute; almost nobody did, because assembling evidence under a deadline is work nobody staffs for. An entire software category grew in that gap.

The incumbents cannot easily close this. Hostaway, Guesty and Hospitable are channel managers and PMSes — their job is to prevent problems, and they’ve done the preventive half already (Hospitable sends a backup code when it fails to set a guest code; Airbnb sends backup codes when a lock goes offline). Prevention is genuinely solved-ish. What nobody owns is the twenty minutes after it goes wrong, when a $3,000 penalty is already booked against your payout and a 10-day clock is running.

There is a second, subtler gap. Vrbo’s SLAs are defined in elapsed time against specific message types — critical stay information, at 1 hour on check-in day. No PMS measures that. They measure average response time as a vanity metric across all messages. Nobody tells a host “you are 40 minutes into a 60-minute window on a check-in-day access question for tonight’s arrival.” That’s a live meter with money attached, and it doesn’t exist.

The product is therefore two halves that share one dataset: a shot clock that stops the penalty from being earned, and a docket that fights it when it is.

4. Target market

• Primary customer: Owner-operators and small managers with 2–40 Vrbo listings, US-first, running self-check-in with a smart lock. They self-manage or have one VA; they are not staffed for a 1-hour overnight SLA. Vrbo-heavy portfolios skew to whole-home, larger properties in beach/mountain/lake markets — Gatlinburg, the Florida Panhandle, Scottsdale, Smokies, 30A.
• Why they buy: One incident costs more than four years of subscription. Hosts describe the policy as “crazy” and are questioning “whether the platform remains worth the risk.” Practitioners flag that “critical stay information is vague and could be abused by guests with buyer’s remorse, or misinterpreted by offshore support” — which is precisely why a host wants a timestamped record rather than an argument.
• Rough TAM reasoning: Vrbo lists 2M+ properties worldwide. Vrbo skews to whole-home and to the professionalising owner-operator. If even 3–5% of listings sit in the 2–40 unit self-managed band that feels this acutely, that’s tens of thousands of businesses — far more than the few thousand customers this needs.
• Why now for them: Two dated changes stacked in ninety days. The 100% penalty tier landed 1 Oct 2025; zero-tolerance Premier Host landed 1 Jan 2026 with the first quarterly assessments through 2026. The international rollout in 2026 widens the exposed population beyond the US.

5. Product sketch (MVP)

• Check-in shot clock. Watches inbound Vrbo guest messages, classifies which ones are “critical stay information” (access, safety, key amenities), and starts the correct 1h / 12h / 24h timer with escalating alerts to phone, SMS and a second responder.
• Access-proof capture. Pulls smart-lock events (Seam-style integration across August, Yale, Schlage, igloohome), code-push confirmations and messaging timestamps into a per-reservation record. Answers “did the code exist, did it work, when did the door open.”
• Pre-arrival readiness sweep. 72 hours out, checks each arriving reservation for a pushed code, sent access instructions, lock battery level and lock online status — the four things that actually cause lockouts — and flags the ones that will fail.
• Penalty watch. Detects host-initiated cancellation fees and reservation-value deductions appearing against payouts, and starts a visible 10-day waiver countdown the moment one lands.
• Waiver docket builder. Assembles the claim Vrbo asks for: reservation ID, a drafted explanation, the full guest message history proving SLA compliance, lock logs, photos, and any force-majeure or guest-conduct evidence — as one submittable packet.
• Premier Host ledger. Tracks owner-initiated cancellation rate, acceptance rate and review average per listing against the 2026 thresholds, on the trailing-365-day basis Vrbo assesses each quarter.
• Incident timeline export. A clean, timestamped PDF per incident for support escalations and, when needed, for disputes with a co-host or cleaner about who dropped the ball.

6. AI angle — what’s load-bearing

Two jobs that are genuinely hard without a model, and trivial with one.

Classifying “critical stay information.” Vrbo’s 1-hour clock only applies to a subset of messages, and the definition is a phrase, not a schema. “The code isn’t working” is a 1-hour message. “Is there a hairdryer?” is not. “Where do we park?” on arrival day probably is. A host receives dozens of messages per stay; a naive keyword rule either cries wolf until it’s muted or misses the one that costs $3,000. This is short-text intent classification with a cost-asymmetric error function — exactly what a small model does well, and exactly what a regex does badly.

Drafting the waiver. The claim is a narrative argument built from evidence: here is the message at 19:04, here is the lock log showing the code was valid, here is the guest’s message saying they went to the wrong address. Turning a heterogeneous evidence pile into the specific argument Vrbo’s support reads — mapped to the qualifying categories they actually recognise — is generation work. A host writing this cold, at midnight, angry, writes a bad claim. That’s the difference between a waived fee and a stuck one.

Strip the AI out and you have a dumb timer plus a folder of screenshots. The host still has to decide what’s urgent and still has to write the argument — which is the part they don’t do.

7. Localization angle (if any)

N/A — this is a global play, US-first. The policy is Vrbo’s, not a jurisdiction’s, so the product travels wherever the policy does. The 2026 international expansion is a sequencing decision, not a localization one: launch US (where the 100% tier already bites and the property values are highest), follow the rollout into the UK, EU and ANZ. The only real localization is property-timezone handling for the 08:00–21:00 response window — a correctness requirement, not a market wedge.

8. Business model — path to $1M–$5M ARR

• Pricing: $29/mo for 1–3 listings, $79/mo for 4–15, $199/mo for 16–40. Optional success fee of 15% of any penalty waived — hosts accept contingency pricing readily when the alternative is a certain loss.
• ACV: ~$950 blended, before success fees. Land in the $79 tier.
• Rough math to $1M ARR: ~1,050 customers at $79/mo. Against 2M+ listings, that is a rounding error of the addressable base.
• Rough math to $5M ARR: ~4,400 paying accounts plus success-fee revenue, requiring the Airbnb equivalent (Airbnb has its own host-cancellation fee ladder and Superhost thresholds) and Booking.com, which triples the reachable base and makes the product a channel-neutral “platform penalty defence” layer.
• Expansion path: Listings-based tiering is the natural escalator. Then success fees, then multi-platform, then a co-host accountability module (which staff member missed the window) that turns a solo tool into a small-manager tool with real seat expansion.

The unit economics are unusually kind: one waived $3,000 penalty pays for three years of the $79 tier. The pitch is arithmetic, not persuasion.

9. Go-to-market wedge — first 100 customers

• Ride the outrage threads. The policy generated Reddit and social backlash with hosts calling it “crazy.” r/vrbo, r/AirBnBHosts and r/ShortTermRentals contain dated, named complaints. Reply with the single most valuable fact — the 10-day waiver window exists and here’s the evidence Vrbo asks for — and link a free waiver-letter generator. Being the person who tells hosts about money they can reclaim buys the first 200 conversations.
• Free “Premier Host risk check” as the lead magnet. A host connects Vrbo and sees, per listing, their trailing-365-day owner-initiated cancellation rate against the 0% threshold and the next quarterly assessment date (1 Feb / 1 May / 1 Aug / 1 Nov). This is a genuinely alarming number that nobody currently shows them. Free tier surfaces the risk; paid tier defends it.
• Facebook groups are where this audience actually lives. STR host groups run 20k–100k members and are markedly more active than Reddit for this demographic. Post the quarterly Premier Host assessment calendar as a reusable asset ahead of each 1 Feb / 1 May / 1 Aug / 1 Nov date — four predictable, recurring demand spikes per year.
• Smart-lock adjacency. Hosts running August/Yale/Schlage locks are self-check-in operators — the exact exposed population. Integration listings and lock-community forums pre-qualify better than any generic STR channel.
• Target the managers, not just owners. Small managers (10–40 units) carry 10–40× the exposure and buy faster. Scrape Vrbo listing pages in the top whole-home markets (Gatlinburg, 30A, Broken Bow, Blue Ridge), cluster by manager, and send a per-portfolio risk estimate: “you have N listings; at your booking values one access failure costs roughly $X.”

10. Build complexity — justification

Low. The Vrbo/Expedia Partner integration plus a smart-lock abstraction layer (Seam covers the major brands with one API) is standard integration work. Message classification and claim drafting are off-the-shelf model calls. There is no custom infrastructure, no data science, no hardware. A competent pair ships a credible v1 in 8–10 weeks; a solo builder in 12.

The one genuinely fiddly part is timers: property-local timezones, the 08:00–21:00 window, and reliable escalation to a human who is asleep. That is careful engineering, not hard engineering. Notification reliability is the thing to over-invest in — a tool that silently fails to alert is worse than no tool.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Helping a host document facts and file a waiver the platform itself offers. Vrbo has zero tolerance for fabricated waiver reasons — the product must document what happened, never invent it.
Ethical — no harm / dark patterns	✅	Aligned with guests: the primary function is making sure people can get into the house they paid for.
Market exists (evidence above)	✅	2M+ listings, dated policy changes, documented backlash, funded adjacent vendors shipping only blog posts.
1–5 person team can build this	✅	Off-the-shelf APIs and models throughout.
Launchable with <$50K / ₹40L	✅	Two people, three months, integration costs. Well under.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	17/20	Up to 2× booking value per incident, plus a 365-day Premier Host penalty from a single event. Not daily pain — but severe, dated, and unbounded when it hits. Held below 18 because most hosts have few incidents a year; the fear is bigger than the frequency.
Demand evidence	15	12/15	Documented policy with exact tiers and dates, public host backlash, funded vendors publishing explainers instead of features. Docked for reliance on secondary reporting of host sentiment rather than a large verbatim complaint corpus I could count.
Build feasibility	15	13/15	Integrations plus model calls; 8–10 weeks. Not 15 because Vrbo/Expedia partner API access is the gating dependency and its self-serve status is unverified.
Distribution clarity	15	12/15	Named subreddits, named FB groups, four predictable quarterly spikes, scrapeable manager portfolios in named markets. Not higher because STR hosts are notoriously noisy channels with heavy vendor spam.
Revenue mechanics	15	11/15	$79/mo against a $3,000 downside is easy arithmetic, and success fees add upside. Held down because a low-incident host may churn after a quiet year — the classic insurance-product retention problem.
Time to first revenue	10	8/10	Waiver-drafting alone is sellable in week one, before any integration ships.
Defensibility	10	3/10	Execution-only. Any PMS could bolt this on, and the policy itself could change. Accumulated incident/outcome data (which waiver arguments actually get approved) is the only real compounding asset.
Total	100	76/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · content-heavy

Integration and model work up front; then a content engine aimed at host communities, because this audience is reached by being consistently useful in forums rather than by ads.

Key assumptions to validate (3–5)

1. Assumption: Vrbo/Expedia partner API access, including message-level read access, is obtainable by a small independent developer. How to test: Apply in week one and get a written answer. If messages are unavailable, the shot clock degrades to email-forwarding — a materially worse product. This is the single highest-risk item.
2. Assumption: Hosts experience these penalties often enough to pay continuously. How to test: Poll 200 hosts across the named subreddits and FB groups — “have you been charged a host-initiated cancellation fee since October 2025, and did you request a waiver?” Need >15% charged, and a majority of those unaware of the 10-day window.
3. Assumption: Waiver requests with a well-built evidence packet get approved at a materially higher rate than bare emails. How to test: Hand-file 20 waivers as a done-for-you service before writing software. Track approval rate against hosts’ self-reported historical rate. This also validates the success-fee model.
4. Assumption: Hosts will grant lock and inbox access to a new vendor. How to test: Measure connect-rate on the free Premier Host risk check.

Risk flags

1. Platform dependency: Absolute. Vrbo can soften the policy, add a native waiver button, or restrict API access, and the core product evaporates. Multi-platform expansion (Airbnb, Booking.com) is the structural hedge and should start early, not late.
2. Incumbent absorption: Hostaway and Guesty are heavily funded and already hold the integrations. If this works, it becomes a feature request. The defence is speed, host-community brand, and the outcome dataset on which arguments win.
3. Retention/insurance dynamics: A host with a clean year questions the subscription — the same churn problem every protective product faces. The Premier Host ledger and readiness sweep are the answer: they deliver visible weekly value even when nothing goes wrong.
4. Evidence integrity: The product must never help fabricate a waiver reason. Vrbo escalates fabrication to account termination, and a vendor implicated in that is finished. Document only; never invent.

14. Structured verdict

Score:                  76/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder who will personally live in STR host communities for six months
Time to revenue:        4–8 weeks (manual waiver service first, software after)
Capital to launch:      $8–15K
Top 3 assumptions to validate first:
  1. Vrbo/Expedia partner API grants message-level access to an independent developer — apply week one, get it in writing
  2. >15% of surveyed hosts charged a host-initiated fee since Oct 2025, majority unaware of the 10-day waiver window — poll 200 hosts
  3. Evidence-backed waivers beat bare email requests — hand-file 20 claims manually and measure approval rate
Kill criteria:
  - Abandon if partner API message access is denied AND a forwarding-based workaround loses >30% of hosts at onboarding
  - Abandon if <10% of 200 surveyed hosts report being charged a host-initiated fee since October 2025
  - Abandon if hand-filed waivers approve at no better rate than hosts' unaided attempts across 20 claims
  - Abandon if Vrbo ships a native one-click waiver flow with pre-attached evidence

15. Next step — 1-week validation sprint

• Day 1–2: Submit the Vrbo/Expedia partner API application and ask explicitly about message read access. In parallel, post the “10-day waiver window” fact in three host communities with a free waiver-letter template, and count replies from hosts who say they’ve been charged.
• Day 3–4: Run the 200-host poll on charge incidence and waiver awareness. Simultaneously, offer to hand-build waiver packets free for the first 10 hosts who report an open penalty — this is the real test, and it starts generating outcome data immediately.
• Day 5: Decide on two numbers. Go if ≥15% of respondents report a host-initiated charge since Oct 2025 and ≥10 hosts hand over an open penalty for a free hand-built packet within 72 hours. No-go if charge incidence is <10%, or if the API answer forecloses message access with no host willing to accept a forwarding workaround.

The falsifiable core: hosts either have open penalties they’ll hand to a stranger this week, or they don’t. Ten live claims in 72 hours means the pain is real and reachable. Zero means it’s a policy that frightens people more than it bills them — and the product is a vitamin, not a painkiller.