The Book Importer
Move a brokerage's entire book of business into Plansight in one process
Move a brokerage's entire book of business into Plansight in one process
A brokerage's book already exists. It sits in plan documents, in an agency management system, in spreadsheets. The Book Importer reads whatever they have, converts it into one neutral format, and lands it in Plansight as real employer groups with real plans: who the carrier is, what the rates are, and what the plan attributes are. One conversion pipeline, several source adapters, a whole book at a time.
The same five stages regardless of where the data starts.
A document library, an agency management system API, or a spreadsheet.
AdaptersOpen Plan classifies and extracts every document into structured facts.
Exists todayClaude normalizes those facts into the neutral Employer Book format.
To buildPlansight's existing conversion layer turns the Book into live plans.
Exists todayLow confidence rows go to a review queue. A sample is hand-checked.
To buildWhy two of the five stages are already built
Open Plan is the document reader Plansight has been teaching for years, and V1 already ships the layer that converts Open Plan output into live plan data. That same reading and verification runs in the plan builder today, a plan at a time. The Book Importer is not a new extraction engine. It is a converter and a landing path wrapped around a pipeline that already runs in production, so the pipeline can take a whole book without a person sorting the documents first.
Same plan, three altitudes. The client version carries no internal economics.
The build. Every stage with real endpoints, file paths, and line numbers, verified against today's V1 master. Includes the V1 constraints that will bite, the phases with effort, and the dead ends not to retry.
The BrokerageBuilder-specific plan. What their API actually holds, field-by-field maps to V1 at employer and plan level, the finding that documents have no plan association, and why we send an agent instead of building a connector.
The bet, the economics, the timeline, and the decisions already made. What it costs to run, what it replaces, what is blocked and who unblocks it. Ends with three specific asks.
How a customer's data gets into Plansight with the least lift on their team. Built around the division of labor. No pricing, no margins, no internal systems named.
Research and mapping complete. Nothing built yet.
Naming discipline
Three different Zywave and Vertafore products get confused constantly, and mixing them up in front of a customer is expensive. BrokerageBuilder is Zywave's agency management system, the one this importer's API adapter targets. BenefitPoint is Vertafore's, and it is a separate existing Plansight integration. C64 is Zywave's quoting tool. They are not interchangeable.
Source of record: the working documents live in the Plansight Brain vault under
BrokerageBuilder Integration/, with the API reference and OpenAPI spec in
~/Documents/Zywave/. This site is the shareable read of that plan, not a replacement for it.
V1 claims on these pages were verified against master at a8e7f76c89 on August 10, 2026. Re-check line numbers before writing code against them.