← All work Case study 03 Insurance · Regulated SaaS
03 /

CRM & relational databases

A customer, prospect and vendor management system — so a person’s history stops depending on whoever happened to handle their last case.

Role
Product designer — end to end
Industry
Insurance & claims · Regulated
Surface
Web platform, B2B multi-tenant
Scope
Data modelling, dashboards, permissions, retention
Customer dashboard — status, owner, next actions
Drop the image at assets/img/crm-databases-01.png
Context

Where this started

Records for each end customer tended to live individually across different systems and places, with no real way to see the full history of a customer’s life cycle.

That left the single source of truth resting on human organization, documentation discipline and clean hand-offs — three things that do not survive volume.

Problem

What needed to be true

A single customer could have dozens of cases, each living under a different case owner. Building a complete picture of that customer’s records — and knowing what follow-up was owed once cases closed — depended on going person by person.

Database schema setup for non-technical users
Follow-up automation builder
Challenges

The hard parts

  1. Migrating existing customer data into these database inputs
  2. Setting up dynamic follow-up automations conditioned by each customer’s data
  3. Organizing mass volumes of information for a given customer into a manageable, understandable dashboard experience
  4. A roles and permissions model enforcing privacy policy on customer data access
  5. A retention feature to clean databases based on conditions, driven by law and regulation
  6. Database creation and conditional-logic automation setup for non-technical users
Solution

What we built

A CRM-style database where you can create different types of customers, define their data points, and relate them to cases — and to the data living under those cases.

Each assigned customer got a dashboard view: what they have been up to, who is responsible for their current status and next tasks, a record of past cases and outcomes, and the automations set up for that customer type to follow up in future — either by the system, or by notifying a specific employee.

Retention rules
Drop the image at assets/img/crm-databases-04.png
Results

What changed

  • A centralized repository of every customer moving through the company — past, present and future
  • One organized record per customer, with full auditability
  • Direct relationships to everything else on the platform: cases, forms submitted, files uploaded
Contact

If you value clear design decisions, someone who builds a system instead of putting out the fire in front of them, who thinks in architecture and how a product scales, and who understands what the product owes the business — then

Let’s talk

Félix POS
Download résumé (PDF)