← All case studies
Case 02 · Insuraviews · Regulatory Intelligence

AI-Assisted Regulatory Intelligence Platform

Designing trust, explainability, and workflow continuity for complex analytical systems — turning a filing browser into a context-aware operational intelligence platform.

Embedded AI workflowsEvidence attributionWorkflow continuityConfidence scoringPlatform systems
Regulatory Intelligence · platform mapfilings · ai · monitoring · briefs
Filings layer
  • SERFF datasets
  • Inconsistent structures
  • Evolving requirements
Analyst workflows
  • Competitive intelligence
  • Precedent research
  • Pricing & rating analysis
AI layer
  • Embedded chat
  • Analytical lenses
  • Brief generation
  • Evidence attribution
Continuity systems
  • Persistent filters
  • Saved analyses
  • Monitoring & bookmarks
01 · Overview

From filing browser to context-aware operational intelligence.

Insurance regulatory filing analysis is inherently complex. Analysts and reviewers work across massive volumes of structured and semi-structured filing data while attempting to identify trends, pricing shifts, precedent, objection risk, and competitive positioning across evolving markets and jurisdictions.

Traditional filing tools often functioned more like static databases than operational intelligence systems. Users could search filings, but the operational workflows around them remained fragmented, repetitive, and cognitively heavy.

At Insuraviews, I helped shape an AI-assisted regulatory intelligence platform designed to transform filing analysis into a more scalable, context-aware operational workflow — focused on AI-assisted analytical workflows, operational trust systems, workflow continuity, and platform-level interaction patterns.

02 · Problem Ecosystem

Analysts weren't reading filings — they were running operations.

Users were navigating large SERFF-based datasets, inconsistent filing structures, evolving regulatory requirements, fragmented review workflows, and operational processes tied directly to business strategy and compliance analysis.

They were conducting ongoing competitive intelligence work, identifying regulatory precedent, analyzing pricing and rating factor trends, generating internal business intelligence, and making operational decisions tied to risk and market positioning.

Step 1
Search filing
Step 2
Manual extract
Step 3
Side research
Step 4
Personal notes
Step 5
Email findings
Lost analytical contextRepetitive lookupNo AI explainabilityFragmented workflows
Before — fragmented analytical processes and disconnected research flows

As the platform evolved from filing browser to analytical workspace, new platform-level questions emerged around navigation architecture, workflow continuity, persistent analytical context, AI explainability, trust in AI-generated insights, and scalable interaction systems across expanding workflows.

The challenge wasn't surfacing data more elegantly. It was designing a system that could support deep analytical work while maintaining trust, clarity, traceability, and operational continuity across increasingly AI-assisted workflows.

03 · Role

Workflow strategy, platform architecture, and AI interaction design.

I worked across workflow strategy, systems design, platform architecture, AI interaction design, and cross-functional product collaboration — helping evolve the platform from a filing retrieval experience into a context-aware operational intelligence system.

With product, engineering, and stakeholders, I structured AI-assisted analytical workflows, defined scalable interaction patterns, improved workflow continuity, reduced operational friction, and established more cohesive platform behaviors across expanding capabilities.

04 · AI Workflow Design & Trust

AI as an embedded operational layer, not a standalone chatbot.

The platform introduced AI-assisted Intelligence Brief generation capable of synthesizing filing information, surfacing trends, and supporting analytical research. Rather than treating AI as a standalone chatbot, the system was woven directly into user workflows.

Analytical lenses

AI behavior shifts based on user intent — pricing, precedent, objection risk.

Context-aware chat

Conversation inherits filters, selected filings, and current research state.

Brief generation

Synthesizes structured intelligence with cited evidence.

Evidence attribution

Every claim links back to its source filing line.

Confidence indicators

Communicates certainty, uncertainty, and inferred values.

Workflow continuity

AI outputs persist into bookmarks, monitoring, and saved analyses.

Embedded AI patterns across the analyst workflow

Because users were making compliance and business decisions based on platform outputs, workflows required explainability, auditability, operational trust, and clear visibility into how conclusions or inferred values were generated.

Source

Original filing line

Evidence

Pull-quoted excerpt

Inference

What the system deduced

Confidence

Certainty signal

Audit

Reviewable trail

The goal wasn't magic AI — it was AI-assisted workflows users could realistically trust inside operational decision-making.

Transparency stack
05 · Workflow Continuity & Platform Systems

Designing for the analyst who returns tomorrow.

As the platform expanded, workflow continuity became increasingly important. Users needed to maintain analytical context across workflows, preserve filtering and research states, monitor ongoing filing activity, revisit intelligence work over time, and move fluidly between filings, AI-generated analysis, reviewer history, and operational monitoring tools.

A large part of the work involved establishing scalable platform conventions around persistent filtering, contextual continuity, navigation systems, reusable interaction patterns, bookmarking and monitoring, and AI interaction consistency — shifting the focus from isolated screens to platform ecosystems.

Filing detail

Filters held

AI brief

Context inherited

Monitoring

Bookmarked & watched

Saved analysis

Resumed in one click

Continuity map — analyst moving across surfaces without losing context
06 · Systems & Organizational Complexity

A connective layer between engineering, product, UX, and the business.

The work required balancing user needs, regulatory complexity, operational trust, AI capabilities, platform scalability, and technical implementation realities.

Much of the complexity also lived organizationally — aligning stakeholders around evolving direction, translating ambiguous business requests into operational systems, coordinating across rapidly changing priorities, and helping establish scalable conventions as the platform matured. I frequently operated as a connective layer between engineering, product, UX, and business stakeholders, helping structure ambiguous initiatives into coherent platform capabilities and implementation-ready workflow systems.

07 · Outcomes & Impact

Cohesion, continuity, and trustworthy AI patterns.

More cohesive analytical workflows

Filing analysis stitched into a single operational surface.

Improved workflow continuity

Persistent filters, saved analyses, and monitoring across sessions.

Scalable AI interaction patterns

Lenses, embedded chat, and brief generation applied consistently.

Trust & transparency mechanisms

Evidence attribution, confidence signals, and audit visibility.

Reusable platform conventions

Navigation, filters, and interaction primitives standardized.

Reduced friction in analyst flows

Less repetitive lookup, more time on judgment work.

Beyond the product

The work also helped establish broader organizational thinking around:

AI operationalizationTrust systemsWorkflow orchestrationPlatform-level product architecture
08 · Reflections

AI is most valuable when embedded in real operational workflows.

This work reinforced my belief that AI product design becomes significantly more valuable when embedded into real operational workflows — not isolated as novelty functionality.

The most interesting problems were not visual design problems alone. They were systems problems: trust, workflow continuity, explainability, orchestration, and operational cognition. The experience deepened my interest in designing AI-assisted operational systems, context-aware product ecosystems, enterprise workflow platforms, and human-centered AI capable of supporting complex analytical decision-making at scale.