InsurGrid Vendor Call — Pricing, API, and the Refresh Gap
Source: raw/meetings/notetaker/2026-08-17-meeting-with-insurgrid-16-01.json
Summary
First live vendor call in the insurance-vendor-diligence-tracker programme — until now every entry was built from public sources. manya-khanna (Customer Success, insurgrid, based in India) walked the team through pricing, the API tier for high-volume pulls, carrier coverage, the login/refresh model, the custom form builder, and downstream integrations. Guy introduced the team as founders from unicorn companies in stealth building an AI-native brokerage for SMBs — Guy CEO, Nizan CPO, Saar R&D. The call closes several standing open questions and contradicts one finding from the 2026-08-17 desk research, which is the most important outcome to carry forward.
Key takeaways
- Pricing, finally concrete. 19.99/mo per additional user. No tier cap on pulls under the standard plan. Enterprise volume runs on a separate API service agreement, with published tiers starting at ~500 pulls/month; anything approaching 100K pulls/month is custom-quoted by the CDO. No free trial — either a minimum API contract for testing, or 50% off the first month ($49.50) to evaluate the dashboard.
- Carrier counts from the vendor’s own mouth: ~300 personal, 120+ commercial. Any carrier offering online account services to its customers can be added on request. This conflicts with the desk-research finding recorded in insurance-vendor-diligence-tracker on 2026-08-17 that InsurGrid is “extraction/upload only — no commercial credential pull.” Manya’s account is that InsurGrid started commercial-first, found most commercial agencies lacked online accounts, and added document upload as a fallback alongside carrier connection — not that commercial connection doesn’t exist. Recorded as a conflict, not resolved: vendor CS vs. public FAQ. Close it against the API docs and the carrier list she is sending.
- The refresh gap is real and is the differentiator against canopy-connect. InsurGrid has no automatic ongoing refresh. A login opens a 15–20 minute window in which all available data is pulled; after that the window closes. Credentials are never stored, so there is no “remember me” — verifying that a policy is still in force a month later requires the customer to re-authenticate. Canopy markets auto-refresh; Manya’s counter is that an enterprise customer left for Canopy over exactly this feature and came back, citing reliability plus pricing, and that carrier-side authentication/security has made unattended refresh unreliable for everyone.
- Data persistence answered: pulled policy data stays on the dashboard indefinitely, until the account is deactivated — even though live carrier access expires with the session.
- Acquisition-phase usage is explicitly permitted. Guy asked directly whether using InsurGrid on prospects before they become clients — “connect and see where you’re overpaying” — creates a T&C problem. Answer: no. Pricing stays volume-based, and staging/testing-period discounts are routinely given to enterprise users pre-launch. This clears a real unknown for the check-up funnel in insurance-checkup-funnel-design.
- Custom intake forms are a bigger part of the product than the desk research showed. A form builder with unlimited questions, multiple field formats, custom welcome pages and producer branding (logo, headshot, name, “military-grade encryption” assurances) — and critically, a form can combine additional questions with the carrier login flow in one customer-facing step, so the producer gets dec pages and structured answers together. Manya’s framing: this “eliminated JotForm from their lives,” and form vendors can’t match it because they don’t do carrier login. Customers can also skip login entirely and upload documents.
- Reliability remains vendor self-report. “About 100%”; the missing ~1% is technical glitches or partial pulls (5 policies at a carrier, 3 returned), fixed manually when a user reports it. No completion-rate figure, no third-party corroboration.
- Integrations: AgencyZoom (AMS), TurboRater (Zywave), and PL Rating, activated from a settings tab with an agency key. Guy noted this could give indirect connectivity to bold-penguin rather than building it separately.
- Setup: 2–3 working days from signed contract and payment to a staging account with API and webhook testing plus developer support; monthly billing even under contract.
- Lineage: co-founder Chase Beach worked at canopy-connect before founding InsurGrid — the two products are near-siblings by design, which is consistent with the near-identical mechanism and helps explain the pricing-led differentiation.
Decisions
- None formally. The team stated it is comparing InsurGrid against canopy-connect and others this week before choosing the data-collection rail.
Action items
- guy-barkat — review InsurGrid’s documentation, pricing, and features and compare against canopy-connect before choosing the data-collection solution.
- manya-khanna (vendor) — send API and technical documentation, carrier lists, and integration details by email.
- manya-khanna (vendor) — prepare and send custom API pricing tiers including the projected 100K+/month pull scenario, plus a formal quotation.
Open questions
- Unresolved conflict: does InsurGrid do commercial credential pull, or commercial upload only? Vendor CS says 120+ commercial carriers; the public FAQ scoped carrier connection to personal lines. Resolve against the carrier list and API docs when they arrive.
- No completion/reliability number was given, and the internally inconsistent public carrier counts (150/350/450) were not raised on the call. Worth asking for a real figure before contracting.
- The 15–20 minute pull window is a hard architectural constraint on any “continuous portfolio ownership” product built on this rail — it means portfolio freshness is customer-initiated. How does that square with AX-INS-7’s “real continuity” claim?
- Canopy’s auto-refresh reliability is now contested by an interested party. Independent verification needed before treating either vendor’s account as fact.