The platform

Not a wrapper. A stack we built and run.

When we build AI for your agency, it doesn't sit on a hobby server. It runs on the same layers that carry InsurEco's own insurance products — each with one job, and each already in production.

01

PolicyOS and the portal where people work

The workspace every person on the platform uses. It adapts to who you are — a producer sees their deals, an account manager their queue, an owner their reports. Tickets, pages, tables, forms and sites live here, and Jefferson works inside it with you. The pages on this site are portal pages.

02

Jefferson (JCI) what the AI knows

Jefferson Context Intelligence: a knowledge graph of your relationships, mail, meetings and commitments, with search that understands meaning. It is served over MCP, so Claude, Cursor and our own chat all reach the same memory — with Bio-ID sign-in, and admins deciding which tools each person gets.

03

Chaac what the AI does

Our AI factory. Give it a task and it produces a plan first — steps, risks, questions — for a person to approve or change. Only then do its agents execute, and every result is tested before it's accepted. Chaac builds our own software, and it's what drives chaacBots in carrier portals.

04

Governance what the AI may do

In insurance an agent without rules is a liability. Rules say what data an AI may read and what actions it may take; approval gates hold anything that binds, pays or sends to a client until a person says yes; and every action is logged — who asked, what was decided, who approved.

05

Tawa where it runs

The platform everything deploys to. Sign-in, databases, nightly backups, metering by the call, a tamper-evident audit trail, uptime monitoring and custom domains come with every service. A custom MCP we build for you is one more service on it — with the same controls as our payments products.

06

The insurance products already live

PolicyPay for premium finance and collection, RaterSpot for rating, and the rest of the PolicyEco line. Commissions reconciles carrier statements for you: upload them as CSV, Excel or PDF, and every line is checked against what you expected, with short, missing and over-paid commissions flagged. Producers are paid on what actually came in, with a statement each and 1099 totals at year end. It's the work that takes most agencies 40 to 80 hours a month. When your AI needs to quote, collect or issue, it can plug into rails that already carry real premium.

What that means for you

The boring parts are already done

  • Your data stays yours

    Scoped to your agency, never used to train a model that leaves your environment, and portable to a box in your office.

  • A person approves what matters

    Plans before actions, approval gates before anything binds, pays or sends, and a record of who said yes.

  • You pay for what runs

    Usage is metered by the call, so a quiet month costs less than a busy one and you can see exactly where it went.

  • It works with the AI you use

    MCP means Claude, Cursor and Jefferson all reach your tools. You're not locked into one chat window.

First step

See what this stack would do for your agency

The $500 assessment maps your work and prices the first build, and your $500 fee comes off that build.