StaySquare — permit navigator for short-term rental hosts

1. One-liner

Tells small Airbnb and VRBO hosts which permits their city demands, then files them before fines or delisting hit.

2. Trend signal — why now?

The short-term-rental (STR) compliance world just flipped from “ignore it” to “comply or get delisted,” and it happened in the last six months.

• California SB 346 (effective Jan 1, 2026) lets cities compel Airbnb, VRBO and other platforms to hand over host data — so cities can now cross-reference listings against permit rolls automatically.
• Houston’s STR ordinance hit enforcement April 1, 2026 — platforms began removing unregistered listings. Not fines you can argue later; your listing vanishes and your bookings die.
• Six small/mid cities advanced new STR ordinances in May 2026 alone — Madison WI, Bakersfield CA, Berea OH, Decatur AL, Arapahoe County CO, West Columbia SC — each with different fees, deadlines, buffers and grace periods. ~7,500 listings, $150M+ annual revenue at risk across just those six.
• Penalties are brutal and per-day: Decatur AL fines $500/day; LA up to $2,000/day. A lapsed renewal can trigger daily civil penalties before you even get a hearing notice.
• The enforcement side is already an arms race. Granicus Host Compliance and Deckard’s Rentalscape scrape 70–100+ listing sites daily, cross-check permit databases, and auto-generate court-defensible violation notices. Deckard claims 500+ jurisdictions. Cities pay $10K–six figures a year for this.

Translation: cities bought AI to hunt non-compliant hosts. Hosts have nothing pointed back the other way.

Provenance:

• Signal 1 (demand): Six small-city STR ordinances advanced May 2026 with per-day fines and platform delisting; ~7,500 listings / $150M+ revenue at risk — https://www.airroi.com/blog/second-tier-city-str-ordinance-wave-2026 — 2026-06-08
• Signal 2 (feasibility): SB 346 (Jan 1 2026) forces platforms to share host data; Houston began delisting unregistered STRs April 1 2026 — https://bbklaw.com/resources/la-010625-new-state-law-helps-cities-get-short-term-rental-information-from-airbnb-vrbo / https://www.steadily.com/blog/airbnb-host-rule-changes-cancellations-landlords — 2026-06-08
• Signal 3 (economic): Cities pay $10K–six figures/yr to Granicus Host Compliance & Deckard Rentalscape (500+ jurisdictions) to enforce against hosts — https://deckard.com/short-term-rental / https://granicus.com/product/short-term-rentals-host-compliance/ — 2026-06-08 Category: Regulatory arbitrage

3. The opportunity

The whole STR-compliance software industry is built to serve cities, not hosts. Granicus, Deckard/Rentalscape and Harmari are enforcement tooling — scrape listings, match to permits, mail the violation. The host is the target, never the customer.

So when a new ordinance drops, the small host’s options are: read a 40-page municipal PDF, doom-scroll a city subreddit, or hand the whole property to a property manager (giving up 20–30% of revenue) just to make the paperwork someone else’s problem. There is no cheap, host-side tool that says “here’s exactly what your address owes, here’s the deadline, here’s the filled-in form.”

The gap exists because the money was always on the city side — six-figure enforcement contracts vs. a fragmented mass of hosts who are individually cheap. But two things changed: (1) enforcement got automatic and listing-killing, so host pain spiked, and (2) LLMs made per-jurisdiction ordinance parsing cheap enough to productize. The arbitrage: point the same AI the cities use at the host’s defense instead.

The incumbent to disrupt isn’t a host tool — it’s the status quo of “DIY the city PDF or pay a property manager 25%.” A focused product does the compliance slice for a flat ~$20/property/mo.

4. Target market

• Primary customer: Independent and small STR hosts with 1–5 listings, no in-house property manager, operating in a newly-regulated or about-to-be-regulated US small/mid city. Roughly $15K–$80K annual STR income per property.
• Why they buy: “I didn’t even know there was a new rule until my listing got pulled.” Hosts run informally; the administrative/fiscal/legal complexity has outgrown what they can absorb alone, and many would rather pay than risk fines or delisting. One missed renewal = daily penalties + lost bookings.
• Rough TAM reasoning: The US has well over 1M active STR listings; a large and growing share sit in jurisdictions with active registration regimes. Even 100K compliance-anxious small hosts at ~$20/mo per property is a $24M+/yr ceiling — well inside the $1–5M ARR target with low single-digit penetration.
• Why now for them: SB 346 data-sharing + platform delisting (Houston April 2026) means non-compliance is no longer invisible. The cost of ignoring just went from “maybe a fine someday” to “listing gone this week.”

5. Product sketch (MVP)

• Address-in, rules-out: Host enters property address + listing URLs; the product returns the exact permits, business licenses, occupancy taxes, occupancy caps, and insurance minimums that jurisdiction requires — in plain English, with dollar amounts and deadlines.
• Personalized to-do checklist ranked by penalty risk and deadline (“Register by July 1 or face $500/day — Decatur”).
• Pre-filled filing packet: auto-populates the city registration / business-tax / TOT forms with the host’s data; one-click submit where the city has an online portal, downloadable packet where it doesn’t.
• Renewal & deadline watch: tracks each permit’s renewal date and pings the host 60 days out (the classic “$275 fee easy to overlook until the certificate lapses”).
• Ordinance change monitor: watches the host’s city for new or amended STR rules and alerts before they take effect.
• Delisting early-warning: flags when a host’s listing is missing a registration number a platform now requires, before the platform pulls it.
• Multi-property dashboard for hosts with 2–5 units across different cities.

6. AI angle — what’s load-bearing

AI does the thing that made this impossible to productize before: reading thousands of inconsistent municipal ordinances, ingesting amendments as they pass, and mapping a specific address to a specific obligation set. Every city writes its rules differently; there’s no API for “what does Berea, Ohio require.” An LLM pipeline that extracts structured rules (fee, deadline, cap, buffer, insurance floor, renewal cadence) from raw ordinance text — and re-extracts when the text changes — is the engine. Remove the AI and you’re back to a human paralegal manually maintaining a 50-city rulebook, which is exactly why no host-side product exists. AI also drafts the pre-filled forms and explains obligations in host-readable language.

7. Localization angle (if any)

US-first by city, not country — the “localization” is hyper-local: the product’s value is precisely that it speaks Decatur, Bakersfield and Madison fluently when generic guides only cover LA/NYC. The same engine extends cleanly to the EU wave already underway (Spain’s NRU delisted tens of thousands of listings since July 2025; EU-wide STR data-sharing rules land May 2026), making international expansion a rules-ingestion problem, not a rebuild. Start with the 10–15 hottest US enforcement cities, expand city-by-city as ordinances pass.

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

• Pricing: $19/mo per property (compliance monitoring + renewal watch + change alerts), plus a one-time $49 “get-compliant” filing packet per property per new jurisdiction. Multi-property hosts get a small per-unit discount.
• ACV: ~$250–$400/yr for a typical 1–2 property host (subscription + occasional new-filing fees).
• Rough math to $1M ARR: ~3,500 paying hosts at ~$290 ACV ≈ $1.0M. Across a dozen active enforcement cities, that’s a few hundred hosts per city — a single-digit share of listings in markets with thousands each.
• Rough math to $5M ARR: ~15K hosts and/or move upmarket to small property managers (20–100 units) who’ll pay $5–10/unit/mo for a compliance dashboard across a portfolio. PM seats are the expansion lever.
• Expansion path: more cities covered → more of a host’s portfolio billable; add tax-remittance filing (occupancy/TOT) as a premium tier; add a “PM edition” for the 20–100 unit managers.

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

• Ride each ordinance as a launch event. When a city sets an enforcement date (Decatur July 2026, Houston already live), that city’s hosts are actively panicking that month. Scrape the active-listing set Deckard-style (public listings are scrapeable) and run targeted outreach + local-keyword content (“Decatur AL Airbnb registration deadline”) timed to the deadline.
• Subreddit + Facebook host groups. r/AirBnB, r/airbnb_hosts, and city-specific STR Facebook groups (every regulated city has one) are where blindsided hosts gather. Post a free “Is your [city] listing compliant?” address-checker as the top-of-funnel hook.
• Free address checker as the wedge. The single-property compliance check is free and instant; converting to paid happens at “now file it for me” and “watch my renewals.” Classic free-tool → paid-action funnel.
• Partner with cleaning/turnover and STR-insurance vendors who already have host lists and zero compliance product to cross-sell.
• Property-manager referral: small PMs decline 1–5 unit owners as too small — a referral path that hands those owners somewhere to go.

10. Build complexity — justification

Medium. The web app, billing, alerts and form pre-fill are off-the-shelf. The real work is the ordinance-ingestion pipeline: collecting source texts for the first 10–15 cities, building the LLM extraction + human-QA loop, and keeping it current as rules change. That’s a few months of focused build plus ongoing data-ops, not a research problem. A technical founder plus a part-time STR-compliance-savvy operator could ship a credible v1 covering ~12 cities in 3–4 months. The defensibility and the risk both live in the rulebook’s accuracy.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Helping hosts comply with public law; no gray area.
Ethical — no harm / dark patterns	✅	Pro-compliance; reduces fines and illegal operation.
Market exists (evidence above)	✅	Active ordinances, delisting, per-day fines, $150M+ at risk in six cities.
1–5 person team can build this	✅	Web app + LLM extraction pipeline + data-ops.
Launchable with <$50K / ₹40L	✅	Mostly off-the-shelf; cost is founder time + data-ops.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	16/20	Per-day fines + listing delisting = real money, felt at each new ordinance and each renewal. Not daily, but acute and recurring.
Demand evidence	15	12/15	Strong structural signals (SB 346, delisting, six May-2026 ordinances, $10K–six-figure city enforcement spend). Docked: thin verbatim host quotes; willingness-to-pay at $19/mo still to be proven.
Build feasibility	15	12/15	App is easy; the ordinance-ingestion + QA pipeline and keeping it current is the real lift. 3–4 months, not 6 weeks.
Distribution clarity	15	11/15	Ordinance-driven, time-boxed campaigns per city + host groups + free checker. Concrete, but conversion math unproven and channel is city-by-city grind.
Revenue mechanics	15	12/15	Pricing sane vs. fines and PM fees; $1M path needs only a few hundred hosts per active city. Churn risk once a host is “compliant” is the open question.
Time to first revenue	10	7/10	A single hot enforcement city can yield paying hosts within weeks of launch, but only after the first cities’ rulebooks are built.
Defensibility	10	6/10	Moat = the accumulating, accurate multi-city rulebook + host trust + renewal lock-in. Copyable by a funded enforcement vendor flipping to the host side; that’s the main threat.
Total	100	76/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · domain-expertise-required

Key assumptions to validate (3–5)

1. Assumption: Small hosts will pay ~$19/mo per property for compliance peace-of-mind. How to test: Pre-sell to 30 hosts in Decatur/Houston/Bakersfield host groups with a Stripe link before building beyond one city.
2. Assumption: Ordinance text for the first ~12 cities can be extracted to a reliable structured rulebook with acceptable accuracy. How to test: Hand-build and have a compliance-savvy reviewer audit 3 cities; measure error rate against the actual city portals.
3. Assumption: Churn after a host becomes compliant is low enough to sustain subscription (renewal watch + change monitor retain them). How to test: Track 60-day retention of free→paid converts; watch cancel-after-filing rate.
4. Assumption: Platforms/cities won’t ship a free host-side compliance helper that kills the value. How to test: Monitor Airbnb’s host tooling roadmap and city portals; the more cities require it, the more Airbnb may absorb it.

Risk flags

1. Accuracy/liability risk: Tell a host they’re compliant when they’re not and they eat a fine — reputational and possibly legal exposure. The rulebook must be conservative and clearly disclaimed; human QA is non-negotiable.
2. Platform dependency / absorption: Airbnb could bundle a free compliance nudge, or enforcement vendors (Deckard/Granicus) could launch a host-facing tier and out-cover you on cities.
3. Churn after compliance: The job feels “done” once filed; retention depends entirely on renewals + ongoing rule changes being valuable enough to keep paying for.
4. Market timing per city: Value is concentrated around enforcement events; in quiet cities urgency evaporates and conversion drops.

14. Structured verdict

Score:                  76/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder + part-time STR-compliance operator/advisor
Time to revenue:        6–10 weeks after first cities' rulebooks are built
Capital to launch:      $8–15K ($/founder time + LLM/data-ops + QA reviewer)
Top 3 assumptions to validate first:
  1. Hosts pay ~$19/mo/property — pre-sell 30 via Stripe in 3 hot enforcement cities
  2. Ordinance extraction is accurate enough — audit 3 city rulebooks vs. city portals
  3. Post-compliance churn is survivable — track cancel-after-filing on first cohort
Kill criteria:
  - Abandon if <10% of 100 targeted hosts in a live-enforcement city convert to a paid plan
  - Abandon if the multi-city rulebook can't be kept accurate without a full-time analyst per ~10 cities (data-ops doesn't scale)
  - Abandon if Airbnb or an enforcement incumbent ships a free, broad host-side compliance tool before your v1 covers 12 cities

15. Next step — 1-week validation sprint

• Day 1–2: Hand-build the structured rulebook for 3 live-enforcement cities (Houston, Decatur, Bakersfield) — permits, fees, deadlines, taxes, renewal cadence — and verify every field against the city’s own portal.
• Day 3–4: Stand up a one-page “Is your [city] STR compliant?” checker and a Stripe pre-sell link for a $19/mo plan. Drop it into those three cities’ host Facebook/Reddit groups and DM 100 hosts whose listings lack a visible registration number.
• Day 5: Decide go / no-go on a falsifiable bar: ≥10 of 100 contacted hosts either pre-pay or join a paid waitlist with card on file. Below that, the urgency isn’t converting to dollars — rework the wedge or pass.