3. Feature-by-Feature Scrutiny (the Idea's Stated Features)
Categories:
- Table stakes (TS): customers expect it. It earns nothing, but its absence costs you.
- Differentiator (D): a real reason to choose you over the alternatives.
- Distraction (X): built but unlikely to move revenue or retention.
- Liability (L): creates support, compliance, legal or trust risk.
Some features sit in two buckets. The primary bucket comes first. Each is judged for the recommended buyer (event venues), with the as-described buyer noted where it differs.
3.1 Classification table
| # | Stated feature | Category | Reasoning |
|---|---|---|---|
| 1 | Collect COIs from vendors (request emails, upload link) | TS | BCS, TrustLayer and COI File all do this, the first two for free. It must exist. It wins nothing. For venues it becomes D only when collection runs on the event clock (T-30, T-14, T-7, T-3) and escalates to the host who hired the vendor. |
| 2 | Collect COIs from subcontractors | X for this wedge | Construction is Billy's, Jones's and myCOI's home. Subcontractor tracking pulls you into Procore and GC sales cycles. Leave it out. |
| 3 | Collect COIs from tenants | X / L | Residential renters insurance is handled by insurance programmes inside property systems, and is reportedly excluded from AppFolio's partner API. Commercial tenant tracking is covered by free tiers. Neither suits venues. |
| 4 | Read the certificate (AI extraction of carrier, policy numbers, limits, dates, holder) | TS | Already free in BCS and TrustLayer and in COI File at $39. Use an off-the-shelf model with a human confirm step, and cap the cost. Don't sell it as the product. |
| 5 | Check against required coverage: limits | TS | Every competitor compares limits against a template. Expected. |
| 6 | Check: additional insured | TS → D for venues, and L if promised | The certificate can say additional insured, but status comes from the endorsement. For venues, the check that matters is "is this venue, with its exact legal name, named for this event?" That's a D if done per event. It becomes L the moment the product implies the venue is insured. Always ask for the endorsement page, and say "the document states", never "you are covered". |
| 7 | Check: waiver of subrogation | TS | Standard requirement template field. Venues ask for it less often than GCs. Keep it as an option. |
| 8 | Chase gaps (automated deficiency notices) | TS → D for venues | BCS and TrustLayer send deficiency notices. The venue differentiator is chasing tied to the event date, copying the host, and showing the coordinator a single "ready / missing" line per event. |
| 9 | Audit trail | D | Everyone keeps history. The venue-specific version is an exportable pack per event: what was requested, received, flagged and overridden, and by whom. That's what a venue's insurer or lawyer asks for after an incident. |
| 10 | "Inside AppFolio or Buildium" (the catalog's wedge) | X | No API on AppFolio Core or Buildium Essential/Growth; Stack listing $25–50k a year; vendor insurance expiry already native in AppFolio (10). This is the single biggest reason the as-described version fails. |
| 11 | Self-serve under $200/mo | TS for venues / L as described | For venues, $79–149 flat is the core of the pitch. For small property managers it's a liability: BCS charges ~$57 for 60 vendors, and TrustLayer is free up to 50. |
| 12 | Broker channel (from the catalog's channel list) | X at first | illumend (Mar 2026) and Certificial (25,000+ agencies claimed) already work brokers. Revisit only after 50 paying venues, and then as a referral source, not a white-label product. |
| 13 | Yardi, AppFolio and Procore integrations (from the catalog's channel list) | X | Wrong buyer for venues. BCS already bundles Yardi, Procore and MRI at no cost. |
| 14 | Trade shows (property management and construction) | X | Wrong buyer. For venues, the equivalents are regional wedding and venue association events, and only after month 6. |
3.2 Scoreboard
| Category | Count | Features |
|---|---|---|
| Table stakes | 6 | Collection, AI reading, limits check, waiver check, self-serve pricing (venues), deficiency notices (base form) |
| Differentiator | 3 | Event-clock chasing with host escalation, per-event additional-insured check, per-event audit pack |
| Distraction | 6 | Subcontractors, tenants, inside AppFolio/Buildium, broker channel first, Yardi/AppFolio/Procore integrations, property and construction trade shows |
| Liability | 2 | Implied coverage from the AI check, cheap self-serve as described (price above free incumbents) |
About 20% of what was described is a reason to buy, and only once it's reshaped around the event. The rest is table stakes, a distraction or risk.
3.3 Feature bloat and "building to avoid selling": explicit call-outs
- Integrations first. AppFolio, Buildium, Yardi and Procore integrations feel like distribution. For this wedge they're months of work toward the wrong buyer.
- Perfecting AI extraction. Tuning ACORD 25 parsing is satisfying engineering. It's free elsewhere, and it teaches you nothing about whether venues pay.
- Policy-language analysis (reading full policies for exclusions, as Jones does). Impressive, expensive, and not what a venue coordinator needs on a Friday.
- Covering every requester type (vendors, subs, tenants) at once. That's how you end up competing with everyone.
3.4 What a disciplined v1 looks like
Keep: event list (date, space, host), requirement set per venue, vendor magic-link upload, AI read + human confirm, per-event checks (date, holder, limits, AI endorsement, liquor liability), event-clock chasing with host copy, ready/missing view, per-event audit pack. Defer: vendor profile reuse across venues (v1.5), booking-software sync (after 30 venues), host event-policy check (v1.5), multi-venue groups (month 9+). Cut: subcontractors, tenants, AppFolio/Buildium, broker white-label, ERP integrations, native mobile, full-policy analysis.