🔒

This case study is private

Enter the password to view this project.

← All work
Case study 04

Giving enterprise clients full control over their own entities

FOCUS
Customer autonomy
YEAR
2024
ROLE
Lead Product Designer, with PM
New features creation overview
Overview slide: workshops, wireframing, and solution reporting.
OBJECTIVE

Give clients with multi-entity structures the autonomy to configure workflows, budgets and spending lines without routing everything through one central admin.

RESULT

16 accounts adopted the feature; one client went from 1 to 3 admins and 80 new entities created.

01 — Validate the problem
02 — Run client workshops
03 — Prototype & test
04 — Ship & track adoption

Context

Through LittleBig Connection's Customer Success team, a recurring signal kept surfacing: clients with multiple legal entities or subsidiaries depended on a single account administrator to set up workflows, budgets and spending lines for every entity. Veolia was the clearest case — 242 entities, one administrator. That created bottlenecks and capped how far the client could scale inside the platform on their own.

Discovery

1 — Client workshops

Sessions with other multi-entity clients, like Valeo, to understand how they actually structure entities and why so many existed in the first place.

2 — Existing screen analysis

Mapped which screens and permissions had to open up for the new role without compromising data isolation between entities.

One workshop finding stood out: of Valeo's 429 entities, only 93 had ever been used to create an RFP — roughly a quarter of the structure was active, the rest existed mostly to mirror the client's internal org chart rather than to do anything on the platform. That single insight reframed the problem: this wasn't just about admin workload, it was about entities multiplying faster than anyone could govern them.

Client workshop notes on entity onboarding, with real Valeo usage data
Workshop notes: how clients onboard and structure entities today, including the Valeo usage breakdown.
Full entity creation flow, from new legal entity to spending lines and workflows
The full entity creation flow we mapped — legal vs. organizational entities, spending lines, workflows and preferred suppliers.

User story → solution

"As an entity administrator, I want to manage my own workflows, budgets and spending lines without depending on the account's central administrator."

We translated that into a new role with permissions scoped per entity, and designed the full flow: an entity list, admin and owner assignment, and workflow/budget creation that can cascade down to sub-entities.

Entity settings: admin, owner, manager and operational roles
Per-entity settings: admin, owner, manager and operational roles, each scoped to that entity only.

Prototype and validation

We built a clickable prototype to walk selected clients through it before writing a single line of code: entity structure, workflow creation, and per-entity budgets.

Entity list with admin and owner roles assigned
Shipped: the entity list, with admin and owner roles assigned per entity and sub-entity.

Results

16
client accounts adopted the feature in the first quarter
1 → 3
admins for one key client, with 80 new entities created
significant drop in the central admin's configuration workload
Workflow and budget creation, problem, solution and impact