Before you begin
Have one real account, one real producer workflow, and one target line of business ready. Prudens works best when you implement against an actual operating process instead of trying to configure everything at once.
- Choose the source systems and record owners that will define the first data schema.
- Prepare representative accounts, policies, documents, carrier guidance, and forms.
- Choose one implementation owner and one workflow to measure from intake to completion.
Start with the structure of the AMS. Define how Prudens should represent accounts, contacts, policies, activities, documents, submissions, and the relationships between them before importing live records.
What to configure
- Define the account, contact, policy, activity, document, and submission records your team needs.
- Map required fields, relationships, statuses, and ownership rules to the way your agency operates.
- Decide which records are authoritative before any sync or automation is enabled.
What good looks like
- One account provides the context needed for service, quoting, proposal, and submission work.
- Required data is clear enough that users do not create duplicate or incomplete records.
- Every team knows which system owns edits for each record type.
NowCerts sync is designed to work out of the box. Open Settings, select NowCerts Sync, enter the connection details, and activate it. Prudens will automatically sync your NowCerts data into the AMS every day.
Turn on the default sync
- Open Prudens Settings and choose NowCerts Sync.
- Enter your NowCerts connection details and select Enable Sync.
- Leave the default daily schedule enabled so Prudens keeps current data flowing automatically.
What Prudens handles
- Prudens imports and updates the connected NowCerts data automatically.
- Your team works from the synchronized accounts, contacts, policies, and related records in Prudens.
- After the first sync, spot-check a few records and review any connection or sync status messages.
Configure the working experience around the roles that use Prudens. The goal is not to expose every capability at once, but to make the right records, actions, and views obvious for producers, service teams, and operations.
Shape the workspace
- Choose the navigation, record views, statuses, and actions each role needs first.
- Make account context, documents, activities, and current work visible without unnecessary clicks.
- Keep the initial workspace focused on the target line of business and rollout team.
Test with real work
- Walk through service, quote, proposal, and submission tasks with representative accounts.
- Remove screens or actions that create duplicate entry or unclear ownership.
- Capture feedback before standardizing the layout for the wider team.
With the data and workspace ready, enable AI where it removes repetitive work and define the workflows that control how work moves. Start with assistance and approvals before allowing autonomous execution.
Assistants
Routing
Approvals
Realtime
Enable deliberately
- Choose one high-volume use case, such as intake, service questions, or document preparation.
- Define prompts, data access, escalation rules, and the human approval point.
- Monitor assistant behavior with live data before expanding its scope.
Build the workflow
- Document the trigger, required inputs, next action, owner, and completion signal.
- Keep exceptions and handoffs visible so automation never hides unfinished work.
- Test the workflow from intake through its final record update.
Configure the market and document layer after your data model and workflow rules are stable. Carrier appetite, submission requirements, and forms should guide the work rather than become manual lookup tasks.
Configure the market
- Load carrier appetite, eligibility notes, markets, and submission requirements.
- Define how risks are matched and when a user must confirm the carrier decision.
- Keep carrier guidance current and visible alongside the account and submission context.
Configure the documents
- Map forms and required fields to the data already held in Prudens.
- Test ACORD and supporting document generation with real submission examples.
- Separate required human review from fields that can be completed automatically.
Now connect the configured pieces into repeatable AMS operations. Implement one end-to-end workflow, measure it, and add automation only where the data, decision, and approval path are already clear.
Intake
Forms
Submissions
Human Review
- Start with a complete path from intake and carrier appetite through forms, submission, and record updates.
- Use APIs, assistants, MCP tools, or scheduled jobs only after the workflow succeeds with human review.
- Track completion, exceptions, handoff time, and manual rework so the next automation has a measurable target.
Operating model
How to roll this out without creating noise
First 2 weeks
- One data schema and one controlled sync.
- One role-based UI configuration.
- One AI-assisted workflow with a human approval point.
- One carrier, form, and automation path for the target line of business.
Metrics to watch
- Sync accuracy and time to find complete account context.
- Time from intake to a reviewed AI-assisted output.
- Carrier and form submission completion rate.
- Exception volume, approval time, and manual rework.