CleartoSet — vendor-insurance clearance for wedding venues

1. One-liner

Collects and date-verifies every wedding vendor’s insurance certificate per event, so the venue is never the uninsured one.

2. Trend signal — why now?

The wedding-venue category is big and stable — ~35,829 wedding venues operate in the US as of late 2025, and venues take the single largest slice of a $65–100B wedding-services market (24–40% of spend per event). Every reputable venue now enforces a non-negotiable rule: every outside vendor (caterer, bartender, DJ, florist, rentals) must hand over a Certificate of Insurance naming the venue as additional insured before the event. Industry guides call it “a non-negotiable policy for any paid vendor at your venue,” and forum consensus is blunt — “almost every venue requires insurance from every vendor except officiants.”

What’s changed in the last 12 months is the tooling landscape around it, and it changed in a way that opens this niche rather than closing it:

• Generic COI trackers went free at the bottom and stayed enterprise at the top. TrustLayer Starter is now 100% free up to 50 vendors, then $10/vendor/mo; meaningful deployments are quote-only and start well above $500/mo. Those tools model a static roster of recurring vendors (construction subs, property vendors) — not a venue’s reality of a different, rotating cast of one-time vendors tied to each dated event.
• Venue CRMs still have no COI feature. Perfect Venue, Tripleseat, and HoneyBook run the booking pipeline, BEOs, and invoicing — none ingest or verify vendor insurance. The coordinator does it by hand, per wedding, in email.
• Carrier portals only manage policies they sell. Insurance Canopy / The Event Helper give a venue a free portal — but only for COIs issued on their policies. A caterer who already carries State Farm or Next can’t be cleared through it.

Provenance:

• Signal 1 (demand): Venues universally require per-vendor additional-insured COIs; framed as “non-negotiable,” coordinators chase them by email per event — https://www.shfweddings.com/post/what-to-do-when-a-vendor-refuses-to-list-your-wedding-venue-as-additionally-insured & https://boards.weddingbee.com/topic/potential-venue-requires-all-vendors-to-show-proof-of-insurance-is-this-normal/ — 2026-06-30
• Signal 2 (feasibility): Incumbent COI trackers (TrustLayer free ≤50 vendors, enterprise above) model static rosters, not per-event rotating casts; venue CRMs carry no COI feature — https://www.trustlayer.io/resources/trustlayer-starter-free-compliance-tracking & https://www.everbridal.com/blogs/best-crm-for-wedding-venues — 2026-06-30
• Signal 3 (economic): ~35,829 US wedding venues; venues are the single largest revenue segment of a $65–100B wedding-services market — https://www.mmcginvest.com/post/the-u-s-wedding-venue-market-a-investment-thesis-for-2026-2030 & https://wedding.report/action/wedding_statistics/view/market/id/00/idtype/s/location/United_States/ — 2026-06-30 Category: Underserved niche

3. The opportunity

The job is shaped wrong for every existing tool. A venue doesn’t have a vendor list — it has an event calendar, and each event drags in 5–12 different vendors who will likely never return. The coordinator’s actual workflow per wedding:

1. Figure out which of this couple’s booked vendors are insurance-required under the venue’s rules (caterers/bartenders/rentals/DJ yes; calligrapher maybe not).
2. Email each vendor requesting a COI with the venue’s exact additional-insured wording, name, and address.
3. When the PDF comes back, eyeball whether it actually names the venue, hits the limits ($1M/$2M is the common bar), and — critically — covers the event date.
4. Chase the stragglers as the date approaches; decide whether to block load-in.
5. Repeat 30–60× a year.

Generic COI tools (TrustLayer, BCS, SmartCompliance) are built around a permanent vendor relationship and price/UX for risk teams managing hundreds of subs across states. They don’t think in “events,” don’t expire a cert against an event date, and their free tier evaporates the willingness to pay for a generic tracker. Carrier portals only see policies they underwrote. Venue CRMs ignore the problem entirely. The 10× is a tool that treats the event as the unit — point it at next Saturday’s wedding, it knows the booked vendors, fires the COI requests with the right wording, parses each returned cert, and turns the dashboard green only when every required vendor is verified-and-dated-valid for that event.

4. Target market

• Primary customer: Owner / operations manager / lead coordinator at an independent or small-group US wedding & event venue doing 20–120 events/year — barns, estates, vineyards, urban lofts, historic homes, country clubs. Not the Marriott; the owner-operated property that personally eats the liability.
• Why they buy, in their words: “It should be a non-negotiable policy for any paid vendor… it protects everyone involved.” The fear is concrete: a bartender over-pours, a guest falls, the caterer’s COI turns out to have lapsed two weeks before the date, and the venue — not the vendor — is the uninsured deep pocket in the lawsuit. One expired certificate can be a six-figure exposure.
• Rough TAM reasoning: ~35,829 US wedding venues + tens of thousands of non-wedding event venues (corporate, private-event spaces). Even 8,000 paying venues at ~$1,100 ACV ≈ $9M ceiling — comfortably past $5M, small enough that VCs skip it.
• Why now for them: The requirement is already universal and enforced; what’s new is that they’ve watched generic COI tools either go free-but-wrong-shaped or stay enterprise-and-overkill, leaving the event-shaped version unbuilt. They’re primed to recognize “this one’s actually for venues.”

5. Product sketch (MVP)

• Event-centric dashboard: a calendar of upcoming events; each shows a red/amber/green “clear to set” status that only goes green when every insurance-required vendor is verified for that date.
• One-click COI requests: pick the booked vendors, the tool emails each a branded request containing the venue’s exact additional-insured name/address/wording and an upload link — no account needed for the vendor.
• AI cert reading: vendor uploads any carrier’s COI PDF; the system extracts insured name, additional-insured language, GL limits, and policy effective/expiration dates, and flags mismatches (“venue not listed,” “expires 6 days before event,” “limit below $1M”).
• Date-aware expiry: a cert that’s valid today but lapses before the event is flagged amber, not green — the failure mode no generic tracker catches.
• Vendor memory: recognizes repeat vendors (the three caterers a venue uses constantly) and auto-pulls their last cert, re-checking it against the new event date.
• Rules per venue: owner sets which vendor types require insurance and the minimum limits; defaults shipped per common venue type.
• Load-in gate + audit trail: a shareable “cleared / not cleared” sheet for the day-of team and a timestamped record of every request, upload, and verification for the venue’s own liability file.

6. AI angle — what’s load-bearing

The load-bearing AI is reading arbitrary ACORD-25-style COI PDFs from any carrier and answering three questions: is this venue named as additional insured, are the limits met, and is the policy in force on this event date. That parsing is the whole product — strip it out and you’re back to a human squinting at PDFs, which is exactly the status quo. Vision-LLM document extraction is what makes “upload any cert, get a verified yes/no in seconds” possible and cheap today; it wasn’t reliably doable two years ago. The request-generation (correct additional-insured wording per venue) and the chase-the-stragglers nudges are automation glue, but the verification brain is genuinely AI-done work.

7. Localization angle (if any)

N/A — this is a US-first play. Additional-insured/COI conventions, the ACORD-25 form, and the venue-liability norm are US-specific; that specificity is the wedge, not a limitation. UK/AU/Canada have analogous public-liability norms and are a later port, but launching anywhere but the US first would dilute the “built for our paperwork” pitch.

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

• Pricing: flat SaaS by venue volume. $79/mo (≤40 events/yr), $129/mo (41–100), $199/mo for multi-property groups. No per-vendor metering — that’s the trap the free incumbents fall into; venues want a predictable number, not surprise vendor charges.
• ACV: ~$1,100/yr blended.
• Math to $1M ARR: ~910 venues × ~$1,100 ≈ $1.0M. Out of ~36K wedding venues, that’s a ~2.5% capture of just the wedding slice.
• Math to $5M ARR: ~4,500 venues, or ~3,000 venues plus an attach product (one-day vendor policy referral commissions — venues already broker ~$60 event policies for uninsured vendors — and a paid “venue audit-ready binder” export). Expansion comes from multi-property groups and from venues adding non-wedding corporate events to the same calendar.
• Expansion path: ACV grows via tier upgrades as event volume rises, multi-property seats, and referral revenue when an uninsured vendor buys a one-day policy through the in-app link.

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

• Scrape the venue directories. WeddingWire, The Knot, Peerspace, and Wedding Spot publicly list tens of thousands of venues with contact details and “vendor insurance required” language in their policies. Pull 2,000, send a 90-second Loom showing the coordinator’s own COI chase collapsed to one green dashboard, with their venue name pre-filled in the demo cert. Expect ~3–5% reply on a pain this specific.
• Venue-owner Facebook groups & forums. “Wedding Venue Owners,” WeddingWire/Weddingbee pro boards, and regional venue-owner groups are where this exact gripe already lives. Show up with the verified-COI checklist as a free lead magnet, convert to trial.
• Wedding-venue consultants & associations. A handful of well-known venue-business coaches (Venue RescueRx-type operators, state venue associations) sell to thousands of owner-operators. Rev-share an affiliate; their audience is the buyer.
• Insurance-adjacent partners. Event-insurance brokers (FLIP-style, Insurance Canopy) want venues to require COIs; co-market “require it, then verify it with CleartoSet” — they get more policies sold, we get qualified venue intros.

10. Build complexity — justification

Low. Standard web stack + an off-the-shelf vision-LLM for COI extraction + transactional email + a calendar/event data model. No marketplace, no two-sided cold start, no custom ML training — ACORD-25 is a semi-structured form a general model handles with good prompting and a verification rules layer. The only non-trivial work is the verification rules (date logic, additional-insured matching, limit thresholds) and tasteful handling of messy real-world PDFs. A 1–2 person team ships a credible v1 in ~8–10 weeks.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Document-management SaaS; we verify, we don’t issue insurance or give coverage advice.
Ethical — no harm / dark patterns	✅	Reduces real liability exposure; no dark patterns. Must avoid implying we guarantee coverage — position as verification, not advice.
Market exists (evidence above)	✅	Universal, enforced requirement across ~36K venues; verbatim owner quotes.
1–5 person team can build this	✅	1–2 people, ~8–10 weeks to v1.
Launchable with <$50K / ₹40L	✅	Off-the-shelf APIs; sub-$10K to launch.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	15/20	Recurring, real liability fear, felt 20–120×/yr. Capped below 17 because the workaround (free TrustLayer / manual email) is tolerable until the day a claim hits.
Demand evidence	15	11/15	Universal enforced requirement + verbatim owner quotes + forum threads. Docked because the complaints are about vendor resistance, not yet a loud “I’d pay for a tool” chorus.
Build feasibility	15	13/15	Off-the-shelf stack + vision-LLM. Only the verification rules + messy-PDF edge cases need care.
Distribution clarity	15	11/15	Named scrape-able directories, named FB groups, named consultant/broker partners. Conversion math is plausible but unproven.
Revenue mechanics	15	11/15	Clean flat pricing that dodges the free-incumbent trap; $1M needs only ~2.5% of wedding venues. Willingness-to-pay above $0 is the open question given TrustLayer’s free tier.
Time to first revenue	10	7/10	Self-serve trial → paid in 4–8 weeks; owner is the buyer, short cycle.
Defensibility	10	5/10	Execution + workflow lock-in (the venue’s vendor memory + audit trail compounds). Copyable by a focused competitor; a venue CRM could bolt it on in 12 months.
Total	100	73/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy (document-AI verification is the core), operations-heavy (venue GTM is relationship- and directory-driven, not pure self-serve SEO).

Key assumptions to validate (3–5)

1. Assumption: Venue owners will pay $79–199/mo for verification when TrustLayer’s tracker is free up to 50 vendors. How to test: put pricing in front of 30 owners in venue FB groups; measure trial-start and “would pay” rate. Kill signal if they say “I’ll just use the free one.”
2. Assumption: The event-date expiry and per-event framing is what they value (not generic storage). How to test: demo both framings; see which lands. If they shrug at the date logic, the differentiation is weak.
3. Assumption: Vision-LLM reliably extracts additional-insured + dates + limits from real-world COI PDFs at >95% on a 100-cert sample. How to test: collect 100 anonymized real COIs from early venues, benchmark extraction accuracy before scaling.
4. Assumption: Vendors will upload via a no-account email link without friction. How to test: run 20 real COI requests through the flow; measure completion rate.

Risk flags

1. Free-incumbent compression: TrustLayer’s free tier (and any venue CRM adding a basic COI upload) could anchor “this should be free.” Mitigation: win on event-date logic + venue-specific UX + audit trail, not on storage.
2. Platform/CRM dependency: Long-term value wants integration with Perfect Venue / Tripleseat / HoneyBook calendars; if they build native COI features, they’re the natural owner. Move fast, get loved by venues, become the obvious acquisition.
3. Liability positioning: If we over-claim (“you’re covered”), a missed edge case becomes our problem. Must stay strictly “we verify the documents you collected,” with clear disclaimers.

14. Structured verdict

Score:                  73/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder comfortable with document-AI, paired with someone who'll work venue-owner communities and consultant partnerships
Time to revenue:        6–10 weeks
Capital to launch:      $6–10K (≈₹5–8L)
Top 3 assumptions to validate first:
  1. Willingness to pay vs. free TrustLayer — 30-owner pricing test in venue FB groups
  2. Event-date / per-event framing is the differentiator — A/B demo two framings
  3. COI extraction ≥95% accuracy on 100 real-world certs before scaling
Kill criteria:
  - Abandon if <15% of 50 demoed venue owners start a trial
  - Abandon if COI extraction accuracy stays below 90% after tuning on 100 real certs
  - Abandon if a venue CRM ships a comparable native COI verifier before your v1

15. Next step — 1-week validation sprint

• Day 1–2: Pull 60 wedding-venue owners from WeddingWire/The Knot whose listed policies say “vendor insurance required.” Join 3 venue-owner Facebook groups.
• Day 3–4: Record one tight Loom: the manual COI chase vs. a green “clear to set” dashboard for next Saturday’s wedding, with the date-expiry catch highlighted. DM/email it to all 60 + post the free “COI verification checklist” lead magnet in the groups.
• Day 5: Decide. Go if ≥8 of 60 reply with interest and ≥4 say they’d pay ~$100/mo (vs. “I’ll use the free one”). No-go if the dominant reply is “we just use TrustLayer free” — that means the event-shaped differentiation isn’t worth a paid line item, and the idea needs a sharper wedge or a higher-liability adjacent vertical (corporate event venues, film-location rentals).

The result is falsifiable: a hard count of interested-and-would-pay owners out of 60, with an explicit free-incumbent objection rate as the kill signal.