Insurance software development

Build around your underwriting edge.

Jaspar builds custom rating, underwriting and policy platforms for insurance businesses whose products, authorities and distribution do not fit off-the-shelf software.

Insurance firstRating, underwriting, quote/bind and policy work is the core practice.
Modelled on your productRates, states, coverages and authority modelled from your filings.
Integrates, not replacesRuns alongside the policy admin, CRM and payment systems you have.
Underwriting workbenchIllustrative interface concept
Commercial GL · New business Rate set FL 24.3 current
Submission Risk overview Eligibility Underwriting Rating Referral 1 Quote Documents

Atlas Roofing Contractors LLC

Sanford, FL · General Liability · Broker: Meridian Risk

Within authority
AppetitePreferred
Completeness94%
Rate versionFL 24.3
Roofing exposure$2,800,000Reviewed
Loss history2 in 5 yearsAcceptable
Subcontractors38%Referral check
Prior insuranceVerifiedClear
Indicated premium$18,420
Prepare quote

Insurance clients across Jaspar’s portfolio

Shield
BOZ
InsureMyRCFE
RPM
ERMA
One operating layer

From submission to policy service, without stitching the work together by hand.

Strong insurance platforms do not start with a dashboard. They start with the decisions, exceptions, calculations and handoffs that define the book. Jaspar maps those operating rules into a product system your teams can keep evolving.

01

Submission intake & triage

Email / portal intakeCompletenessAppetite

Structure incoming risk information, flag missing data, apply first-pass appetite rules and route the submission to the right queue before underwriting time is spent on it.

02

Risk assessment & underwriting

Conditional questionsAuthorityReferrals

Show the questions, evidence and rules that matter for this product and this state — with controlled exceptions, referral paths and review points instead of side conversations.

03

Rating & pricing

Rate tablesModifiersVersioning

Centralize premium logic, state variations, modifiers and effective dates so every quote can be traced back to the exact version of the logic that produced it.

04

Quote, bind & policy issue

Quote optionsApprovalsDocuments

Move approved risks into quote preparation, bind requests and policy documents without losing decision context between underwriting and operations.

05

Servicing, endorsements & renewals

EndorsementsCancellationRenewal

Keep post-bind change governed too: endorsements, reinstatements, cancellations, audits, inspections and renewals run on the same product foundation.

Abstract insurance workflow
Core platform capabilities

Your insurance logic should be reusable infrastructure.

Build the business rules once, expose them wherever the work happens, and keep the operating history visible to the people who have to explain it.

Platform overview
01

Rating & calculation engine

Premium calculations, rate tables, modifiers, eligibility, state logic, effective dates and version-controlled releases.

Explore rating & pricing
02

Underwriting workflows

Product-specific questions, authority thresholds, referrals, approvals, exception handling and operational queues.

Explore workflows
03

Quote & policy lifecycle

Broker quoting, quote options, bind, policy issue, endorsements, cancellations, reinstatements and renewals.

Explore lifecycle
04

Data & integrations

Connect policy administration, documents, e-signature, payments, CRM, third-party data and reporting.

Explore integrations
Product logic blueprintControlled change
01 / Rating

Rates & modifiers

Base rates, exposure bases, limits, deductibles, territories, class codes, credits and debits.

02 / Eligibility

Appetite & rules

Knock-outs, conditional questions, product eligibility and state or product differences.

03 / Authority

Referral controls

Authority thresholds, exception reasons, approvals, review steps and escalation paths.

04 / Governance

Versions & dates

Test scenarios, release history, audit trace and a clear split between draft and production logic.

Governance without slowing the business

Change the product without losing the history.

Insurance teams need to know what changed, when it changed, where it applies and which version priced a given risk. The platform should make those answers routine rather than investigative — for underwriting, for the carrier and for an audit.

See the rating architecture
Operating outcomes

What a better underwriting platform should make easier.

We do not publish invented percentage claims. The useful question is whether the system improves the mechanics that determine speed, consistency and control.

Speed

Fewer manual handoffs.

Less rekeying between intake, rating, referral and quote preparation.

Consistency

One product logic.

The same rates, eligibility and authority rules regardless of who is working the risk.

Control

Traceable decisions.

Versioned rules and recorded review points make decisions easier to explain and revisit.

Change

Products that can evolve.

State, rate and workflow changes move through a controlled release path instead of ad hoc edits.

Selected insurance work / Shield

Commercial contractor quoting for a multi-state MGA.

Shield is a contractor insurance MGA founded in 2004, writing GL, excess, workers’ compensation, inland marine, BOP and pollution liability for brokers nationwide through its own online rater.

Commercial GLBroker quotingUnderwritingMulti-state
Representative workflow / new quote
Risk stateFlorida
Class code91580
WorkflowUnderwriting
Rate versionCurrent
ReferralControlled
Policy stageQuote
Insurance portfolio

More than a single insurance engagement.

Jaspar’s public client list also includes BOZ, InsureMyRCFE, RPM, ERMA and other insurance-adjacent businesses.

  • BOZ — MGA for general and professional liability in elderly care
  • InsureMyRCFE — online quote and bind for California care facilities
  • RPM — workers’ compensation pay-as-you-go facilitation
  • ERMA — insurance and compliance services for small business
View customer work
Connected, not isolated

Fit into the systems the insurance business already runs on.

A custom underwriting layer does not need to become the system of record for everything. It sits where the work happens and connects to the platforms that already own policy, payment, document and enterprise data.

Policy adminQuote and policy data, issuance, policy status and servicing handoffs.
Insurance dataThird-party risk, loss history, geospatial and internal enrichment sources.
Documents & e-signApplications, forms, signatures and generated quote or policy packages.
PaymentsPremium collection, billing handoffs and finance-related integrations.
Jaspar underwriting & rating layerProduct logic, decision paths and operational history in one governed service.
Broker portalsSubmission, quote presentation, bind requests and document exchange.
CRM & serviceAccount context, tasks, communications and customer operations.
Identity & accessRoles, permissions, SSO and organization-level access controls.
ReportingOperational reporting, exports, data warehouse and downstream analytics.
Delivery with domain context

Make the rules, exceptions and release criteria explicit.

An insurance platform needs agreement on more than the happy path. We work through product rules, authority, data ownership and transaction scenarios so the implementation can be checked against the way your business actually operates.

Your insurance and compliance specialists retain ownership of product decisions and applicable requirements. Our role is to translate the agreed rules into testable software, make changes traceable and support the operational handover.

Discuss the scope
Insurance delivery blueprintAgreed around your needs
01 / Definition

Product & workflow model

Inputs, rates, eligibility, authority, referral paths and servicing scenarios documented together.

02 / Validation

Benchmark scenarios

Expected calculations, boundary cases and transaction examples agreed with domain reviewers.

03 / Integration

System boundaries

Data ownership, API contracts, permissions and exception handling defined for connected systems.

04 / Release

Controlled rollout

Versioned logic, acceptance criteria, release notes and operational guidance for the scoped solution.

How delivery works

From operating rules to a controlled insurance release.

The scope, review points and responsibilities are agreed with your team. Each stage produces something you can assess before the next step.

01

Map the insurance product

Review rating inputs, product variations, authority and the existing workflow. Identify the source documents, sample transactions and people who will validate the rules.

02

Define the first delivery scope

Agree what the new software owns, what stays in current systems and which integrations are required. Prioritize a usable product or workflow slice with explicit acceptance criteria.

03

Build against real scenarios

Implement the agreed logic and workflows, then check benchmark calculations, exceptions and transaction boundaries. Review results with the people accountable for the product.

04

Release & support change

Plan migration or rollout, establish the version and effective-date approach, and hand over operational knowledge. Future rule and workflow changes follow the agreed review path.

Common questions

A little clarity before we begin.

Scope, ownership, delivery and ongoing support — the details that help you decide how to move forward.

Can you start with a spreadsheet rater or a legacy platform?

Yes. A current rater, documented formula set or existing workflow is a useful starting point. We review its inputs, dependencies and known exceptions, then agree how the software should be validated. Unclear rules are resolved with your domain experts before they become implementation assumptions.

Do we need to replace our policy administration system?

Not necessarily. A rating engine, underwriting workflow or portal can sit alongside an existing system of record. We define data ownership and integration boundaries first, then recommend a phased scope that fits your operating model.

How are rating accuracy and product changes checked?

We use agreed benchmark quotes, boundary cases and transaction scenarios to validate the implementation. Rate versions, effective dates and change records make the release context explicit. Your designated product reviewers approve the business logic and expected outcomes.

Can a solution support several products or programs?

Yes, where this is part of the scope. We identify shared services and the rules that vary by product, program, state or carrier relationship. The goal is to reuse common foundations while keeping genuine product differences visible and maintainable.

How do you approach permissions and sensitive information?

We map user roles, access boundaries and data flows during discovery. Authentication, access controls, logging and information handling are designed around the agreed requirements and reviewed with your technical and compliance stakeholders. Specific assurance or certification needs are scoped explicitly.

What do you need to begin an insurance project?

A description of the operating problem, representative workflows and access to the right domain reviewers are enough for an initial discussion. During discovery, useful materials may include rate examples, product rules, referral scenarios and integration documentation, shared through an agreed channel.

Start with the operating model

Bring us the workflow that is hardest to change.

We map the product logic, underwriting handoffs, integrations and policy lifecycle around it — then define a practical path from the current process to a governed digital platform.

Discuss your platform See the platform All services

No obligation. A first call is usually a workflow review.