CapTally — night-cap monitor for multi-city short-let operators

1. One-liner

Tracks aggregate nights sold across Airbnb, Booking and Vrbo against each city’s legal cap before you overshoot and lose the licence.

2. Trend signal — why now?

The EU Short-Term Rental Data Regulation (2024/1028) hits full enforcement 20 May 2026 — days after this is written. Platforms must now transmit, per listing per month, the address, registration number, nights rented and guests-per-night to each member state’s Single Digital Entry Point (SDEP). That turns previously-invisible municipal night caps into machine-enforced limits: Paris 90–120 nights/year, Amsterdam 30 (a proposal exists to halve it to 15), Madrid 90 without a commercial permit, plus district-level caps.

The economic signal is unambiguous: Spain fined Airbnb €64M for advertising unlicensed listings (Dec 2025, upheld March 2026). France’s Loi Le Meur sets €10,000 for a missing registration, €20,000 for a false declaration, €50,000 for serious infractions, with Paris cases reportedly reaching €1M for commercial-scale violators. Greece escalates €5K → €10K → €20K within a year. Portugal: up to €40,000 for an Alojamento Local breach. Lisbon has already revoked ~40% of STR permits; San Sebastián pulled 300+ licences for day-limit breaches.

Analysts are explicit that the regulation redistributed rather than removed the burden: “A property management company with portfolios across Paris, Madrid, Rome, Lisbon and Berlin must support five different registration formats and five different SDEP API contracts.” A non-resident French host is quoted as “uncertain as to how to get this” registration number. The pain is now operational and dated.

Provenance:

• Signal 1 (demand): Multi-city operators face 5 registration schemes + per-city night caps with €10K–€1M fines and licence loss; analyst calls it burden “redistribution,” host quoted “uncertain how to get this” — https://www.airroi.com/blog/eu-str-regulation-may-20-deadline-2026 — 2026-04
• Signal 2 (feasibility): PMS/channel managers (Guesty, Hospitable, Lodgify) optimise the opposite — auto-filling vacant “gap nights” — and have no per-municipality legal-cap-vs-aggregate-nights model — https://hospitable.com/compare/guesty-vs-lodgify — 2026
• Signal 3 (economic): Spain’s €64M Airbnb fine upheld March 2026; EU-wide SDEP enforcement live 20 May 2026 across 27 systems / 116,000+ listings — https://www.airroi.com/blog/eu-str-regulation-may-20-deadline-2026 — 2026-03 Category: Regulatory arbitrage

3. The opportunity

Every PMS and channel manager (Guesty, Hostaway, Hospitable, Lodgify, Uplisting) is built to maximise occupancy — Hospitable literally markets auto-offering vacant “gap nights.” None of them models the legal ceiling: how many nights this specific unit may legally sell this calendar year in this municipality, summed across every channel it’s listed on. The incumbent’s optimisation goal is the operator’s compliance hazard.

The gap is precise: a host with one Paris flat listed on Airbnb + Booking + a direct site has three calendars and one 90-night legal cap. Nobody totals them against the cap, warns at 75%, and freezes the channels at 90. When the SDEP cross-checks reported nights against the cap, the operator finds out via a suspension order with a 10-working-day (or 48-hour) remediation window — too late. CapTally is the missing legal-ceiling layer that sits beside the PMS, not replacing it.

4. Target market

• Primary customer: Owner-operators and small property managers running 5–50 short-let units across 1–4 EU cities, multi-listed on 2+ platforms, who pay for a channel manager but not an enterprise compliance team. Concentrated in “Code Red” enforcement markets: Spain, Portugal, Italy, Greece, France.
• Why they buy: “I don’t even know if I’m over the limit until the city tells me — and then I’ve lost the licence.” Caps differ per city and change by decree; tracking nights across Airbnb + Booking + direct in a spreadsheet is error-prone and nobody does it monthly.
• Rough TAM reasoning: AirROI cites 116,000+ listings across the 27 SDEP systems at the deadline; Portugal alone ~90,000 registered STRs, Spain far larger pre-cull. Small multi-unit operators are a large minority of these. A serviceable target of 30,000–60,000 small operators in capped EU cities at €40–120/mo is a multi-million-ARR market well under any VC’s radar.
• Why now for them: 20 May 2026 the cross-check goes live. Spain’s €64M fine and Lisbon’s 40% permit revocation made it visceral. The cost of being wrong jumped from “warning letter” to “licence gone + five-figure fine.”

5. Product sketch (MVP)

• Connect each property’s Airbnb, Booking.com and Vrbo calendar (iCal sync — the same connection a channel manager already uses) plus manual/direct-booking entry.
• Per-property legal cap profile: city, unit type, primary-vs-secondary residence, current municipal night cap and rule basis.
• Aggregate night counter per property per calendar year, summed across all channels, shown against the legal cap with a clear % gauge.
• Threshold alerts (email/WhatsApp): 60% “watch”, 80% “act now”, 95% “freeze recommended” — with the exact remaining-nights number.
• Audit dossier per property: registration number + proof, listing URLs, monthly nights ledger, screenshot archive — a one-click PDF for when the authority asks.
• Municipal rule library covering the Code Red cities first (Paris, Madrid, Barcelona, Lisbon, Rome, Amsterdam), each rule dated and source-linked, updated as decrees change.
• Portfolio dashboard: every unit’s compliance status on one screen, sorted by risk.

6. AI angle — what’s load-bearing

Two load-bearing jobs. First, municipal rule extraction: STR caps live in municipal decrees, gazettes and council PDFs in five languages, and they change (Amsterdam 30→15 proposal, Lisbon revocations). An LLM pipeline ingests these sources, extracts the structured rule (cap value, unit-type conditions, residence conditions, effective date) and flags changes for a human reviewer — turning a research analyst’s week into an afternoon of review. Without this the rule library rots in three months and the product is worthless. Second, listing-to-property reconciliation: matching the same physical unit across differently-titled Airbnb/Booking/Vrbo listings so the night count actually aggregates correctly — fuzzy address/photo matching, not a regex. Strip the AI out and you have a spreadsheet that’s wrong by next quarter.

7. Localization angle (if any)

This is the localization play — it’s EU-first and municipality-deep by definition. Five registration formats (France Declaloc 13-digit, Spain NRA, Italy CIN, Portugal RNAL/AL, Greece AMA), rules in five+ languages, per-city caps. Pricing in EUR with a sub-€50 entry tier that works for a 5-unit Lisbon operator where a $200/mo enterprise PMS add-on can’t. Distribution via vernacular STR host communities (Spanish, Portuguese, French Facebook groups and forums) where global English-only tools never reach. A generic global “compliance dashboard” cannot win here — the moat is municipal-rule depth per city.

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

• Pricing: €19/mo for up to 3 properties (solo host), €59/mo up to 15, €129/mo up to 50, plus €1.50/property/mo overage. Annual discount.
• ACV: Blended ~€700/year (mix skews to the €59 tier; small managers cluster at 10–25 units).
• Rough math to $1M ARR: ~1,300 paying accounts at €700 ACV ≈ €910K ≈ ~$1M. ~1,300 of 30,000+ small EU operators in capped cities = ~4% penetration. Plausible within 18 months given a hard regulatory forcing function.
• Rough math to $5M ARR: ~6,500 accounts, or hold accounts and lift ACV via more cities + a “filing-ready monthly report” upsell + accountant/PM-agency reseller tier. Requires expanding the rule library to 25+ cities and a partner channel.
• Expansion path: more cities per account as portfolios grow, per-property overage, premium “regulatory change alerts + impact memo” tier, white-label for PM agencies who manage owners’ units.

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

• City-specific fear content + scrapeable lists: Lisbon, Madrid and Barcelona STR Facebook groups and forums (tens of thousands of members) actively panicking post-€64M-fine. Post a free “Am I over my night cap?” calculator for one city; gate the multi-property tracker. Convert the calculator users.
• Channel-manager refugees: Scrape/identify operators publicly complaining that Guesty/Hostaway/Lodgify don’t track legal caps (their own comparison forums and review sites). Direct outreach: “your PMS fills gap nights — here’s the one it can’t see.”
• Accountant & PM-agency partners: Portuguese/Spanish accountants servicing STR owners now field “am I compliant?” panic. Offer a referral/reseller cut — they have the trust and the client list. 10 firms × 20 clients = 200 leads.
• Enforcement-news jacking: Every new city fine/revocation is press. A tight “what this means for your cap” explainer + tool link, distributed in the relevant national host community within 24h of the news.

10. Build complexity — justification

Low. iCal calendar sync is the same commodity integration channel managers already use — no fragile platform API approvals needed (the tool reads calendars, it does not touch the SDEP, which is the platform’s obligation). The genuinely custom work is the AI rule-extraction pipeline + reviewed municipal rule library, and listing-to-property matching — both off-the-shelf-LLM-shaped, not research-grade. A technical founder plus a part-time EU-STR domain expert ships a 6-city v1 in ~8–12 weeks. Ongoing cost is rule-library maintenance, not infra.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Compliance aid; reads calendars the operator owns. No scraping of platforms required.
Ethical — no harm / dark patterns	✅	Helps operators stay legal; opposite of a dark pattern.
Market exists (evidence above)	✅	116K+ listings under SDEP, €64M fine, 5-scheme burden documented.
1–5 person team can build this	✅	iCal + LLM pipeline + rule DB. 8–12 weeks to v1.
Launchable with <$50K / ₹40L	✅	Solo/pair build, commodity infra, no licences.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	15/20	Hair-on-fire for the subset that’s near a cap; for the rest it’s “should track this.” Licence loss + five-figure fine is severe, but not every operator feels it weekly until the cross-check bites.
Demand evidence	15	11/15	Strong regulatory + economic signal (€64M fine, deadline, 5-scheme burden, analyst + host quote). Weaker on direct verbatim host demand for this specific tool — Reddit threads were thin.
Build feasibility	15	12/15	iCal sync is commodity; rule-extraction LLM pipeline + listing matching is the real work but off-the-shelf-shaped. 8–12 weeks.
Distribution clarity	15	11/15	Named communities, news-jacking, accountant partners — concrete. Conversion from free calculator unproven.
Revenue mechanics	15	11/15	Pricing fits EU SMB wallets; $1M needs ~4% penetration of a real base. Churn risk if an operator exits a capped city.
Time to first revenue	10	8/10	Hard deadline = urgency now; free-calculator-to-paid funnel can convert in weeks, but a credible 6-city rule library must ship first.
Defensibility	10	5/10	Moat is maintained municipal-rule depth + workflow lock-in (it’s your audit dossier of record). Copyable, but rule-library upkeep + city coverage is a real 6–12 month grind for a cloner.
Total	100	73/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy (LLM pipeline + integrations), domain-expertise-required (EU STR municipal law — needs a domain advisor or co-founder).

Key assumptions to validate (3–5)

1. Assumption: Small operators (5–50 units) will pay €40–130/mo for cap-tracking they currently do badly in a spreadsheet. How to test: Pre-sell to 30 operators in Lisbon/Madrid host groups with a one-city calculator + paid waitlist; target ≥10% of engaged users putting a card down.
2. Assumption: iCal sync gives night data accurate enough to count against a legal cap (blocked-vs-booked distinction). How to test: Reconcile iCal-derived nights vs actual platform booking history for 20 real properties; require ≥98% match or build a correction step.
3. Assumption: The municipal rule library can be kept current with <0.5 FTE across the first 6 cities. How to test: Run the LLM-extract-plus-review pipeline against 6 cities for 8 weeks; measure analyst review hours and miss rate vs a manual baseline.
4. Assumption: PMS incumbents won’t ship cap-tracking before a v1 head start matters. How to test: Audit Guesty/Hostaway/Lodgify roadmaps and changelogs; treat any announced legal-cap feature as a kill signal.

Risk flags

1. Platform dependency: Relies on iCal feeds from Airbnb/Booking/Vrbo. If a platform degrades or paywalls calendar export, data quality drops. Mitigation: manual entry fallback + multi-source reconciliation.
2. Incumbent encroachment: A channel manager could bolt on a cap tracker. Defensibility is the rule-library depth and being the audit-dossier of record, not the counter itself.
3. Regulatory churn: Caps and SDEP details shift per municipality and decree — this is also the moat, but a maintenance treadmill that breaks the product if it stalls.
4. Market timing/contraction: Aggressive enforcement (Lisbon −40% permits) shrinks the operator base even as it raises per-operator pain. Net effect on TAM is uncertain.

14. Structured verdict

Score:                  73/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder + EU-STR domain advisor/co-founder
Time to revenue:        8–12 weeks (deadline-driven urgency, free-calc-to-paid funnel)
Capital to launch:      €5–10K ($6–11K)
Top 3 assumptions to validate first:
  1. WTP €40–130/mo — pre-sell to 30 Lisbon/Madrid operators, need ≥10% card-down
  2. iCal night data ≥98% accurate vs actual bookings on 20 real properties
  3. Rule library maintainable <0.5 FTE for 6 cities over 8 weeks
Kill criteria:
  - Abandon if <10% of 30 engaged operators will pre-pay after seeing the one-city calculator
  - Abandon if iCal-derived night counts can't hit ≥98% accuracy without heavy manual correction
  - Abandon if a major PMS (Guesty/Hostaway/Lodgify) ships per-municipality legal-cap tracking before v1

15. Next step — 1-week validation sprint

• Day 1–2: Build a single-city (“Madrid 90-night”) free web calculator: paste 2–3 listing iCal links, see aggregate nights vs cap. No accounts.
• Day 3–4: Drop it into 3 Spanish/Portuguese STR host Facebook groups and 2 forums riding the €64M-fine news. Instrument it. DM 30 operators who engage with a paid-waitlist offer (€39 founding-tier, card now).
• Day 5: Go/no-go. Go only if ≥3 of 30 (10%) put a card down for the founding tier AND iCal night counts matched booking reality on the 5 properties tested. Anything less → the pain isn’t worth paying for yet; revisit when enforcement deepens.

Falsifiable: a card-down rate and an accuracy number, not “people seemed interested.”