Case study - Internal tooling · Entitlements unification
One place to configure every customer
A unified internal platform replacing a scatter of legacy tools for setting up contracts, offerings, and feature availability. I designed the end-to-end Client Configuration experience - a searchable customer directory, a six-step setup wizard, and a customer profile with full audit history - validated it with a working coded prototype, and handed it to development after all five usability test participants preferred it over the current tooling.
Overview
01
Context
A configuration model with real depth, and nowhere to put it.
Each customer buys a contract tier that determines which healthcare offerings their members receive - expert medical opinion, bariatric surgery, cancer care, trusted-partner programs. Every offering can be tuned further: bariatric surgery might be voluntary use for one customer and a mandatory consult for another, and eligibility can be limited to specific member groups.
Before this project, that configuration lived across multiple internal tools, personal notes, and slide decks acting as unofficial sources of truth. There was no reliable answer to "what does this customer actually have?" and no way to tell who changed a configuration, or when.
"Searching through a mountain of configurations."
The intended users - implementation, content, and sales teams - are non-developers, configuring all of this without engineering help.
02
The problem
Internal teams had no unified, reliable way to configure and audit a customer's entitlements - and no way to review the whole picture at once.
Setup meant stitching together contracts, toggles, eligibility rules, and partner settings across disconnected tools.
03
Constraints
Discovery
04
Research
Interviews with implementation managers, plus an audit of the existing tools and documentation.
Three insights that shaped the direction
05
Synthesis
Two core problems, in order of weight.
Fragmentation
No single place where a customer's configuration lives. Setup and lookup were spread across multiple tools and informal records - so there was no authoritative answer to "what does this customer have?", no audit trail, and configuration knowledge locked in individual heads.
Design response: one platform covering the full lifecycle - setup, overview, change history, deactivation.
Developer dependency
The people who own the configuration couldn't perform it. Implementation, content and sales teams knew what each customer should get, but changes routed through engineering. Every request became a ticket, every ticket a delay, and engineering time went to data entry instead of building.
Design response: a guided, self-serve flow safe enough for non-developers - stepped structure, per-step validation, incompatibility guards, and a mandatory review before anything publishes.
Not the core problem, but a prerequisite for a self-serve tool: if users configure entitlements without an engineer translating, the words on screen must mean the same thing to sales, implementation and the backing service. We restructured the draft glossary into a clean ladder, which then shaped the wizard's information architecture - contracts and attributes each got their own step because they are distinct domain concepts.
ContractOfferingAttributeEntitlement
Make the invisible contract visible - every entitlement decision should be inspectable, reviewable and traceable, by the people who own it.
Design
06
Process & iteration
Weekly crit and review with engineering throughout development.
Language as a collaboration tool
The glossary was built jointly with PM and engineering, with "replaces…" annotations to ease the transition. It kept UI and service responsibilities aligned as both moved.
Contract configuration depth
From a single contract to multiple contracts, group targeting (all members versus selected groups), per-group launch dates, and opt-out rules.
Rule complexity
Dedicated treatments for eligibility rules, incompatible offerings, and inline errors - the places where a wrong click has a real member consequence.
From setup tool to lifecycle tool
Later iterations added the customer profile: history, scheduled changes, and structured deactivation flows. The tool stopped being about day one and started being about year three.
The prototype as a communication artifact
Alongside the static designs I built a working prototype in Claude Code - real step navigation, toggle states, rule builder, validation. That made unmoderated remote testing possible and surfaced flow-level problems static frames can't. It also gave engineering an unambiguous behavioural reference: reviews happened against working interactions, not hypothetical descriptions.
07
Try the prototype
The coded prototype used in the usability study - six-step wizard, live validation, rule builder, and the Customer Overview.
08
Validation
Unmoderated study, 5 internal participants - the tool's real future users.
The scenario: set up a fictional customer, "SkyRoute Airlines", end to end - a Wayfinding Plus contract, expert medical opinion limited to specific employee groups and categories, one offering excluded, trusted partners with an age-based eligibility rule - then review the Customer Overview and audit log.
"I'm super excited to use this. It seems way more user friendly than current tools."
The step-by-step structure, contract selection, include and exclude toggles, and the Attributes step all tested well.
The study produced 6 flow recommendations and 11 design fixes - auto-save with draft mode, manual date entry, hover tooltips on rule chips, "select all" for partner programs, open-ended age ranges, customer archiving, an exportable overview - all folded into the designs before handoff.
Solution
09
Customer directory
A searchable list of every customer with their contracts, offerings and launch status - active, pre-launch, terminated, expiring - filterable by each. One glance answers "what does this customer have?"
10
Configure New Client
Six steps mapping one-to-one onto the domain model.
Craft details: autosave with a visible timestamp, and validation both on continue and at the final step.
11
Lifecycle management
The customer profile covers the full life of a configuration: change history, scheduled and planned future changes, individual end dates, notes, and structured deactivation - whole customer or per offering.
Impact
Outcomes & impact
12