Insurance · App Starter
Insurance Agency Template
A working agency management system — policy book, renewal pipeline, claims, commission tracking — generated into code you own.
Describe your book of business, and Dual7 generates this agency system around it: six connected entities, a renewal pipeline, and commission reconciliation, shipped as a real full-stack app. Your lines, your carriers, your workflows — in code you own, not another per-user platform fee eating your commission.
- 6 core entities
- Renewal pipeline
- Code you own
- Vibe + Governed modes
01 · Data model
What's inside: the data model
An agency runs on its book, and the book is a data model: who the client is, what's in force, when it expires, and what the carrier owes you. Six connected entities carry all of it, and every screen below reads from them.
| table | what it holds |
|---|---|
clients | Individuals and businesses with contacts, household and business relationships, and every policy across every line rolled up in one view. |
policies | The in-force record — policy number, carrier, line of business, premium, effective and expiration dates, and status through its term. |
carriers | The markets you write with — appointment details, commission schedules, underwriter and service contacts, and your book with each. |
claims | Loss events from first notice through resolution — adjuster, status, and outcome, linked to the policy and the client who called you first. |
renewals | Every upcoming expiration as a pipeline row — review, remarket, renew, or lost — so retention is worked, not watched. |
commissions | Expected versus received per policy per term, reconciled against carrier statements — the money the spreadsheet always loses track of. |
02 · Screens
Signature modules
Policy book
01The whole book, filterable by line, carrier, and expiration — with each client's household or business rolled up so cross-sell gaps are visible. The auto client with no umbrella policy is a query, not a hunch.
Renewal pipeline
02Expirations flow onto a board ninety days out and move through review, remarket, and bound stages. Retention becomes a managed pipeline with owners and dates — the difference between a book that compounds and one that leaks.
Claims tracking
03From first notice of loss to closed, with adjuster contacts and status against every policy. The agency isn't adjusting the claim, but the client calls you anyway — and the record means anyone who answers can speak to it.
Commission reconciliation
04Expected commission per policy per term, matched against carrier statements as they arrive. Shortfalls and missed payments surface as exceptions instead of vanishing into the deposit total — for most agencies this module funds the rest.
03 · Process
How it works
- 1You
Describe your book and lines
Tell Dual7 what you write — personal, commercial, benefits — which carriers you represent, and how your renewal process runs. Plain language is enough; the starter supplies the structure.
- 2Vibe mode
Generate and iterate in Vibe mode
Get the working system in minutes, then shape it conversationally: add a line of business, adjust the renewal stages, put a producer field on policies. Every change lands in real code you can review.
- 3Governed mode
Ship through the governed pipeline
When the office is ready to run on it, promote it through Dual7's approval gates to production — audit trail included, deployed on your infrastructure, your book in your database.
04 · Fit
Who the Insurance Agency starter is for
Independent agents outgrowing the spreadsheet
A few hundred policies fit in a workbook until the first missed renewal costs more than software ever would. This starter is the same information — clients, policies, expirations — with the renewal pipeline and commission match the spreadsheet can't do.
Agencies paying per user for a bloated AMS
Full agency-management platforms price per seat and ship features built for someone else's shop. Owning a system shaped to your actual workflow flips it: every CSR gets a login for the cost of a database row, and nothing you didn't ask for is in the way.
Niche and specialty program shops
If you write a specialty book — equine, cyber for dentists, contractor bonds — no vendor's object model fits. Here the schema is generated from your program: your risk fields, your carrier set, your renewal cadence, as first-class structure.
Principals who want the book to be an asset
At sale or perpetuation, the book's value depends on its records. A clean, queryable database you own — every client, policy, term, and commission — is diligence-ready in a way a decade of carrier portals and inbox archaeology never is.
05 · Yours
Customize it, own it
Make it yours
Make the vocabulary match your shop: rename entities, add the fields your lines require — vehicle schedules on auto policies, payroll and class codes on workers' comp, effective-date endorsement notes anywhere. In Vibe mode these are conversational edits that land as schema changes you can read.
Larger moves are ordinary work on an ordinary codebase: add a producer entity with splits feeding the commission module, build a certificate-of-insurance request flow for commercial clients, or import carrier statement files into reconciliation. The generated app has no runtime dependency on Dual7 — your team can edit it directly.
Why a starter, not a subscription
Agency platforms rent you access to your own book and charge by the seat, and the data export when you leave is famously the hardest feature to find. This starter inverts the deal: schema, screens, and rules are generated as source code in your repository, on your infrastructure. The book is the agency's asset — its system of record should be too.
The trade is stated plainly: you operate an app instead of subscribing to one. Dual7's governed pipeline makes that manageable — approval gates before changes touch production, an audit trail for E&O comfort, and regeneration when your process changes structurally.
Insurance Agency template — frequently asked questions
What does the insurance agency template include?
A working full-stack agency system generated into a codebase you own: six connected entities (clients, policies, carriers, claims, renewals, commissions), a policy book with cross-sell visibility, a renewal pipeline, claims tracking, and commission reconciliation against carrier statements.
Does it handle both personal and commercial lines?
Yes — line of business is a field on the policy, and each line can carry its own fields: drivers and vehicles for auto, locations and limits for property, class codes for comp. Because the schema is yours, a new program is an extension, not a workaround.
How does commission reconciliation work?
Each policy term carries expected commission from the carrier's schedule. As statements arrive, received amounts post against expectations, and unmatched or short rows surface as exceptions to chase. Import formats vary by carrier, and since you own the code, each importer is written once and kept.
Can it track renewals automatically?
Every policy's expiration generates a renewal row that enters the pipeline on your lead time — ninety days is the default. Rows carry an owner and a stage, so the Monday renewal meeting works a board instead of a printout of expirations.
Is this a replacement for a full AMS?
For many independent agencies, yes — it covers the book, renewals, claims visibility, and commissions, which is the daily 90%. Deep carrier connectivity like automated policy downloads is integration work you can add; the difference is you decide what's worth building instead of paying for everything.
What about E&O exposure and audit trails?
Every record change is logged with who and when, and the governed pipeline adds approval gates on changes to the system itself. Documentation of what was known and done, dated — which is what an E&O defense actually asks for.
Related
Dual7 App Starters
Build your Insurance Agency on your terms
A working agency management system — policy book, renewal pipeline, claims, commission tracking — generated into code you own. Describe your version to start — the output is a project you own.