TSIB — proposal (working notes)
Where we are
- Apr 22, 2026 discovery established org-wide pain: Excel, silos, duplicate reports, long insurance cycles, regulatory caution.
- Dec 3, 2025 (Ian / Contextual / Brainforge) documented Ian’s lane: 90% E&S book, thousands of supplemental app variants, voice-to-form / map-to-carrier as a PoC direction.
- Explicit next step: TSIB homework = 3 use cases; Brainforge case studies; then a scoping conversation — not a finalized build proposal yet.
Suggested “proposal” deliverable (this week)
- Cover email to Ian + Peter (cc Andrew, Keon as appropriate): thank-you, 3 use case request restated, offer 1–2 Brainforge case study PDFs or links, propose agenda for May working session.
- 1–2 page options memo (internal or client-facing) with three columns: Use case (TBD from them) | Discovery / pilot shape | Ballpark size band (after internal sizing — do not over-specify).
- SOW only after use cases are written — or a Phase 0 discovery SOW (workshops, process mapping, security review) if they want paid structure before build.
Proof points to emphasize (from Apr call)
- Team-as-a-service: strategy through implementation; measurement from day one (usage, accuracy, cycle time).
- Embed in workflows (Teams, email) vs rip-and-replace.
- Honest culling: no AI for AI’s sake — regulatory and trust constraints front and center.
Tie-in to Dec 2025 (Ian-specific)
If one of the three use cases is intake / supplemental mapping, the Dec call is your source of truth for PoC data (Ian’s supplemental database). If TSIB picks finance / reporting consolidation or BD pipeline instead, pivot the story — don’t lock to Ian’s thread alone in the executive proposal.
Dependencies
- May meeting date confirmed (Ian).
- TSIB: 3 use cases in writing.
- Brainforge: curated 2–3 case studies (1 insurance-adjacent if available, 1 services automation, 1 data+AI measurement).