A platform that hosts homeowner reviews has been a venture-scale business for twenty years. The reason isn't that nobody tries to sue Yelp, Glassdoor, or TripAdvisor — they try constantly. The reason is that those platforms were architected for the lawsuit before the lawsuit arrived. HBR uses the same architecture, deliberately.
"No provider … of an interactive computer service shall be treated as the publisher or speaker of any information provided by another information content provider." That sentence — passed in 1996, narrowed only modestly since — is what makes Yelp, Glassdoor, TripAdvisor, Reddit, and every other UGC platform possible. HBR relies on it deliberately.
When a homeowner uploads a photo, attaches a note, files a claim, or posts a builder rating, the resulting record is their content. HBR provides the tools — storage, formatting, the publishing surface — but does not author, ghost-write, or editorially endorse the substance.
Two decades of case law (Zeran v. America Online, Roommates.com, Force v. Facebook, Gonzalez v. Google) confirm that this posture insulates the platform from defamation, tortious interference, and product-disparagement claims arising from user content. Zeran 1997 Gonzalez 2023
§ 230 protects hosts, not authors. The carve-outs we architect around:
A Strategic Lawsuit Against Public Participation — a SLAPP — is a defamation suit designed to chill speech regardless of merit. Anti-SLAPP statutes flip the economics: a defendant can move for early dismissal, and if the speech is protected, the plaintiff pays the defendant's legal fees and costs. HBR is incorporated in a strong-SLAPP jurisdiction and contracts venue into a strong-SLAPP state via our Terms of Service.
32 states + D.C. have anti-SLAPP statutes; UPEPA (Uniform Public Expression Protection Act, 2020) is being adopted state-by-state and harmonizes the strongest protections. Notably weak or absent: Alabama, Mississippi, North Dakota, South Dakota, West Virginia, Wyoming. HBR's ToS forum-selects into a strong-protection state to neutralize this.
The hardest place for a platform to lose § 230 protection is when its own staff or systems are accused of authoring the actionable content. HBR is engineered so the homeowner is unambiguously the author of every record, and our infrastructure is unambiguously a tool the homeowner uses.
The single highest-leverage moderation feature in any review platform is the subject's right to reply in public. In Yelp's published data, builders who post a good-faith public response within 7 days reduce escalation-to-litigation rates by more than 80%. HBR makes this right structural and free — no builder ever pays for the right to respond on their own homes.
Yelp's biggest legal wins (Levitt v. Yelp, Reit v. Yelp) turned on one fact: their content filter is algorithmic and applied uniformly. The moment a platform's moderation becomes editorial — "we'll demote this review because we like the business" — § 230 weakens. HBR's moderation is documented, algorithmic, and equally applied.
The AI defect classifier and the drafted warranty letter are the two features that could most easily be re-framed as HBR speech rather than homeowner speech — and that re-framing would break § 230. HBR treats both as tools the homeowner uses to format their own observation, documented in product copy, surfaced through disclaimers, and saved with full provenance.
The vision model returns a structured estimate (cls, case,
conf) that the homeowner reviews before it's saved. The verdict screen
displays the confidence range, the alternate classifications considered, and a one-tap
override. Saved records carry the model version, the prompt hash, and an explicit
"reviewed and accepted by the homeowner" stamp.
The warranty letter is a template the homeowner edits in-line before sending. It is sent from the homeowner's own email address, signed in the homeowner's name, with HBR appearing nowhere in the addressee chain. We provide formatting; the homeowner provides content and authorship.
Every verdict screen carries: "This is an automated estimate based on visual inspection only. Not a substitute for a licensed inspector or legal counsel. File at your discretion." The letter screen adds: "This template is editable. You are sending this. Review before submission."
California, New York, Texas, and Florida treat preparation of legal documents for compensation as restricted activity. HBR's letter is (a) a template, not a customized legal product, (b) free at the homeowner-side and unbundled from paid tiers, (c) sent by the homeowner from their own account, and (d) explicitly framed as warranty correspondence, not litigation.
Scott's instinct is right: the deepest moat in this category is the labeled defect dataset, not the workflow features. The pricing ladder is structured around what data a builder can see — own, portfolio, cohort, industry, predictive. Crucially, every rung is legally durable under the same Sec 230 + Anti-SLAPP posture because the underlying records remain homeowner-authored.
Builder sees their own data. No third-party records, no anonymized cohort. Zero defamation risk — you can't defame yourself with your own complaints.
Still your own data, aggregated. Vendor-level rollups are derived from your own claim records — no external benchmarking yet. UPL-safe; not legal advice.
Cohort statistics are derived data, not identifiable claims. Aggregation thresholds (≥10 builders, ≥100 homes per cohort) protect against re-identification. Modeled on Yelp's industry-report posture.
Statistical reports on category trends, not individual builders. Vendor categories named (not specific vendors). Published quarterly with methodology transparency — same posture as Glassdoor's industry compensation reports.
Predictive output is statistical inference labeled as such — explicitly not a guarantee, not a legal determination. API contract carries the same disclaimers as the in-product flow. No raw third-party homeowner records ever leave HBR's perimeter.
The legal posture lives in the architecture and the documents — but the corporate structure is what backs it. Three choices to make before the first homeowner signs up.
Delaware corporate law for governance; California forum selection clause in the ToS to anchor anti-SLAPP coverage for any litigation arising from user content.
ToS-mandated individual arbitration via AAA consumer rules, with carve-out for injunctive relief in IP matters. Class-action waiver. Modeled on enforced Yelp / Glassdoor language.
$2–5M Errors & Omissions plus Media Liability policy from day one. Indicative carriers: Hiscox, Beazley, Coalition. Quote range: $3K–8K/yr at pre-scale.
Internet platform / media defense firm on retainer for content disputes — modest monthly retainer + ad hoc. Recommended specialty: media law & § 230 defense.
Claim records, response threads, moderation decisions, and AI provenance stamps retained for 7 years to support any after-the-fact statute-of-limitations question.
DMCA designated-agent registration before launch. Filed takedowns + counter-notices processed within statutory windows. See DMCA procedure.
The faster a builder can get a factual error corrected through HBR's internal process, the less likely they are to file. We commit to an SLA on factual-dispute flags. Counsel for either side can also file directly.
The posture above is implemented through four documents and a memo for your counsel. Everything below is a v1 draft prepared for legal review before launch. Final language will be set by Scott's lawyer; these drafts establish the structure.
Homeowner + builder terms. Indemnification, forum, arbitration, content warranties, content license.
Open Terms → DOC 02 · PRIVACYWhat we collect, how it flows through the data ladder, what builders see, retention windows.
Open Privacy → DOC 03 · AUPFirsthand-experience requirement, what gets removed, the moderation rules in plain English.
Open AUP → DOC 04 · DMCANotice + counter-notice procedure, designated-agent contact, takedown SLA.
Open DMCA →