AMS integration in diligence — beyond the spreadsheet export.

The diligence document a buyer trusts least should be the spreadsheet export — because it's produced by the seller, and a seller produces the version that flatters the book. The fix is direct, read-only access to the agency's management system during diligence, which lets the buyer query the source rather than accept a curated summary. It's faster, it's more trustworthy, and it pre-maps the post-close migration that otherwise leaks commission — three reasons it belongs in a streamlined diligence.

§ 01 · Four export failure modesWhy the spreadsheet lies.

The spreadsheet export fails four ways, and each hides something a buyer needs. The numbers don't tie — commission totals diverge across the P&L, the producer schedule, the carrier report, and premium times rate, and a reconciliation gap is a finding. Detail gets smoothed — aggregating policy to producer to book to P&L hides specific-account risk, so a reported "91% retention" can mask the loss of the two largest accounts. Data gets curated — the seller highlights "representative" data and quietly excludes departed producers and lost large accounts. And the timing is wrong — last quarter's export rather than the current state. None of these is necessarily deception; they're the natural product of a seller assembling their own numbers. Direct access removes the seller as the intermediary, which is what makes the data trustworthy.

§ 02 · Five components of direct accessHow integration works safely.

Direct access is only acceptable to a seller if it's controlled, which is what the five components provide. The seller authorizes and authenticates the access (a token-based or similar grant they control), the access is scoped by table or view and by disclosure stage (so the buyer sees only what the current stage permits), both sides see a visible audit trail of what was queried, the access is read-only by default (write access belongs in post-close migration, not diligence), and there's a termination mechanism the seller controls — revocable at will and auto-revoking on deal termination, end of exclusivity, or a calendar date. Built this way, direct access gives the buyer source-of-truth data without giving up the seller's control or violating the staged-disclosure protocol — the same staging discipline covered in staged disclosure enforces the boundary here.

§ 03 · Eight trustworthy metricsAnd the leakage benchmark.

Direct access makes eight diligence metrics meaningfully more trustworthy than any export: policy-level commission by producer (attribution becomes unambiguous), retention cohorts by account size and tenure, the renewal-versus-new commission decomposition, carrier concentration with granularity (premium, commission, contingency, by producer, by line), customer concentration with specificity (which single customer is 4% of commission, their tenure, their producer, their trend), E&O claim exposure cross-referenced by line and producer, agency-bill versus direct-bill composition (which drives the trust-account math), and endorsement and mid-term change patterns (invisible at the P&L level, fully visible at the system level). Beyond trust, direct access pays a post-close dividend: it cuts the 5%–15% of commission typically lost in the 12 months after a poorly-executed data migration, because pre-close access means the schema is already mapped (migration is incremental, not from-scratch), the data exceptions are already known (orphaned policies, duplicate records, producer codes that don't tie to names), and commission continuity has been pre-tested (the first three months of post-close commission flow simulated before cut-over). The tech-debt read that pairs with this is in AMS due diligence.

§ 04 · The staging fit and the objectionsMaking it work for both sides.

Direct access and staged disclosure intersect cleanly: aggregated and anonymized data flows in stages 1–2 (the buyer sees that the top-5 customer is 4% of commission, not who), and identified customer data only unlocks at the stage-4 closing threshold, with scoped permissions enforcing the boundary. Three common seller objections each have a counter. "The data isn't clean enough" → the buyer finds the debt either way, and direct access enables collaborative remediation rather than adversarial negotiation. "I don't want the buyer seeing customer-level detail" → staged disclosure with scoped permissions is the structural answer. And "our system doesn't support integration" → the fallback (structured imports, reporting views, guided exports) must be predictable, documented, and auditable. The seller-side bar that makes any of this happen is the authorization experience: a one-click flow, clear permissioning, visible scope, and an obvious revocation control — because an integration that's easy for the buyer but painful for the seller is one the seller won't authorize, which means no integration at all. The reverse-diligence packet this integration data feeds is in reverse due diligence.

◆