SlateSight

For independent life insurance agencies

Your commissions, reconciled to the cent.

SlateSight runs the whole agency — clients, policies, carrier statements, commission splits and upline overrides — on one system that agrees with the carrier before you pay anybody.

Request a demoSee what it does

Built for life insurance agencies — purpose-built, not a general CRM with insurance bolted on.

Illustrative example — invented data

American Amicable · September 202614 rows · $4,182.60
  • Delgado, Maria — AA-4471092First year · writing no. 88214 · D. ReyesMatched$612.40
  • Whitfield, Curtis — AA-4468810Renewal · writing no. 88214 · D. ReyesMatched$48.15
  • Okafor, Ruth — AA-4402255Renumbered from AA-4391187 · confirm before postingNeeds review$531.00
  • Unmatched row 12No policy on file for writing no. 90177Exception$204.90
12 matched · 1 needs review · 1 exceptionNothing posts until the queue is clear — $4,182.60
An illustration of a carrier statement being reconciled. Every agent, client, policy number and amount shown is invented for this example.
  • Every agency gets its own database. Not a shared table with a filter.
  • Posted entries never change. Corrections reverse and repost.
  • No rates in code. Your schedules, your levels.

The platform

Four systems most agencies run separately — in one place, agreeing with each other.

A CRM that doesn’t know your commission schedule. A spreadsheet that doesn’t know your carrier statement. A statement nobody has time to check. SlateSight closes that loop.

  • Clients and policies

    Households, policies, calls and lead assignment, with every record owned by a named agent.

    • Household view — spouses and dependants together
    • Policy status from application through in force
    • Call logging and lead pool distribution

  • Commission calculation

    Your carrier schedules and agent levels, applied exactly — first year, renewal, advance and as-earned.

    • Upline overrides from your own reporting lines
    • Chargebacks when a policy lapses in the advance period
    • Splits that preserve the total to the cent

  • Carrier statements

    Upload the statement, map its columns once, and every statement afterwards matches itself.

    • Rows matched to policy and writing number
    • An exception queue for whatever doesn’t match
    • Nothing reaches the ledger until you approve it

  • Agency operations

    Who works here, what they can see, and what they’re owed — without a spreadsheet.

    • Roles and permissions you configure, not ones we chose
    • Reporting lines that drive override calculation
    • Payout periods built from the posted ledger

Underwriting decision support

Which carrier is most likely to approve this client — before you take the application.

Enter age, state, height and weight, tobacco use, medications and conditions. SlateSight ranks the carriers you actually write, reads each carrier’s own underwriting guide, and tells the agent why in one line.

An estimate for your agents — never a decision, and never shown to a client. Health answers are used for the ranking and are never stored.

  • Royal NeighborsControlled diabetes accepted at this ageBest chance
  • Mutual of OmahaLevel benefit — build within tableGood chance
  • American AmicableCardiac event inside 24 months — likely ratedNeeds check
  • Baltimore LifeNo published rules for this product yetNot evaluated
Illustrative example — invented data: a made-up applicant, not a real client, and not a carrier’s decision.

Reporting

Report on any of it — and every number traces back to a posted entry.

Production, commissions earned against commissions paid, chargeback exposure, reconciliation status, exception ageing, lead conversion, call activity, and which carrier actually approved the case against the one the tool expected.

Agent
Their own book — policies written, commission earned, what’s still pending.
Manager
Their team’s production and the overrides it generates.
Owner
The whole agency, by carrier, agent, product or period.

Scope is enforced on the server — an agent isn’t shown a filtered view of everyone else’s numbers, they’re never sent them.

Illustrative example — invented data

Production by agent — September 2026
Production by agent, September 2026 (Illustrative example — invented data)
AgentPoliciesAnnualised premiumCommission
D. Reyes18$41,280$33,024
M. Santos14$29,940$23,952
T. Boyd9$18,615$14,892
3 agents41$89,835$71,868

Drawn from the same posted ledger the payouts are built from — not a separate total someone maintains.

Illustrative example — invented data: the agents and amounts are made up for this page.

Isolation by design

One agency’s book is never one query away from another’s.

Most multi-tenant software keeps every customer in shared tables and filters by an agency column. One missing filter exposes everyone. SlateSight gives each agency its own database, and access is resolved on the server from who you are — never from anything the browser sends.

Separate databases

One per agency, provisioned at onboarding

  • Agency AIts own database — nothing sharedIsolated
  • Agency BIts own database entirelyIsolated
  • Platform recordsAccounts and billing only — no client dataSeparate
Illustrative example — invented data: “Agency A” and “Agency B” are labels, not customers.

Get in touch

See it against your own carriers.

Tell us which carriers you write and how your overrides work, and we’ll show you SlateSight reconciling a statement you recognise.

Your message is emailed to our team and is not stored on this website. We reply to the address you give.