Sunkey Insurance — Zywave integration dashboard

Context

Independent agencies often live in spreadsheets long after they have licensed modern rating and agency-management tools. The gap is not “more reports”—it is trustworthy pipelines that turn operational files into something systems and people can act on.

Overview

For Sunkey Insurance, Nightcoders built a path from structured spreadsheet import through validation to API interaction and an internal dashboard so staff could see consolidated status instead of re-opening the same workbook.

Challenge

Excel is flexible—which is why it becomes the shadow system of record. The project had to respect real-world files (headers drift, partial rows, human edits) without pretending a one-shot import solves governance forever.

Delivery approach

We implemented import handling with explicit error surfacing, server-side integration against the vendor surfaces Sunkey relied on, and dashboard UX oriented to operators—not executive chart theater. Assumptions about field mapping and source of truth were documented so the next change is a planned change.

Technical & operational notes

Patterns included idempotent writes where the API allowed, structured logging for support, and defensive handling when third-party endpoints or file formats shift—common in insurance stack work.

Scope & deliverables

• Spreadsheet import with validation and operator feedback
• API integration to Zywave-adjacent systems in scope
• Role-appropriate dashboard views
• Documentation of data lineage and failure behavior

Operational value

Internal visibility reduces duplicate entry and “who has the latest file?” friction; we describe mechanics and scope here rather than claiming quantified time savings we did not measure for publication.