An AMS for independent P&C agencies

If your agency writes P&C business, services it directly, issues certificates and gets paid on commission statements you have to check, the system was designed around your day.

That shape has specific consequences. The policy lifecycle, ACORD forms, certificates of insurance and commission reconciliation are the product rather than modules bolted onto a contact database. Renewal work opens on its own at 90, 60 and 45 days because missing a renewal is the failure mode that actually costs an independent agency money. And the whole book lives in one place because the alternative — a spreadsheet for commissions, a folder for certificates, an inbox for requests — is the arrangement most agencies are trying to leave.

The same system serves a single desk and a multi-office agency. What changes is how work routes, not which product you bought.

A single desk runs renewals from one queue. A split desk gives producers and servicers their own queues and routes renewal work by producer. Departments let commercial, personal and benefits hold separate books while automations carry 90 / 60 / 45 across all of them. A multi-office agency shares one book of business instead of running four systems, so every desk reads the same record.

Moving between these shapes is a configuration change. Agencies grow into the next one without a migration, which is the point of putting them on one page.

Roles and permissions are granular, so what each person can reach is a decision the agency makes rather than a limitation of the software.

• Producers work their pipeline and their book, and see the renewals coming due on their own policies over the next 60 days.
• Servicers handle endorsements, certificates and client requests against policies that stay connected to everything else.
• Administrators configure the agency, manage users and permissions, and own the commission and import workflows.
• Owners see the whole book across desks, departments or offices without assembling it from separate systems first.

In larger agencies this is also what lets departments or offices hold their own books inside one shared system: access is evaluated per record, so separation does not require separate installations.

NowCerts transfers over a direct API connection. Applied Epic, AMS360 and HawkSoft come across by CSV export and field mapping, and so do spreadsheets and any other system that exports CSV.

The part that decides whether a switch succeeds is what happens after the upload. Documents are identified by type, dates and names and carrier codes are normalized into one shape, documents are matched to their policy and policies to their client, and gaps or conflicts are surfaced rather than dropped. Nobody retypes a book by hand — that is the single most common reason an AMS migration stalls partway and never finishes.

Agencies arriving from spreadsheets and email rather than a competing AMS use the same path. There is no requirement to already be on a system.

Agency Nexus is not built for carriers, MGAs running their own underwriting platforms, or agencies whose book is primarily life and health rather than P&C.

It is also not a quoting engine or a rater. It manages the book — policies, documents, certificates, renewals and commissions — and expects rating to happen where it already happens. An agency that mainly wants comparative quoting and does not have a servicing and commission problem will get less out of it than an agency drowning in renewals and statements.

Agencies that also run a benefits department can hold that book in the system, but P&C is what the workflows are shaped for, and it would be dishonest to imply otherwise.