During the audit, the picture sharpened. The screens were indeed cold and corporate, but that was not the root cause. The real issue was the structure of the journeys.

The app was designed like a back-office. It stacked screens without following the actual journey of a parent inside Wepartum. Vital information for each step was not surfaced, the user had to figure out where they stood at every login, friction kept building up.

Repainting the UI would have treated the surface, not the cause. I raised the finding with the Wepartum team. We agreed to expand the scope, from graphic redesign to product redesign.

Before any production development, I built a simulation engine. A high-fidelity interactive prototype, coded with Claude Code, powered by mock data. It plays back the seven states, their transitions, their edge cases.

Concretely, the Wepartum team could click through the demo and test, for instance, what a parent sees when returning after their meeting with Constance, or how the app reacts when documents are still incomplete. Every scenario replayable, every state controllable.

The engine served to arbitrate in meetings on concrete material, not wireframes. And more importantly, Wepartum reused that structure to refactor its production workflow. The prototype did not stay a validation deliverable, it became an architecture blueprint.

46 screens derived, all from the same source of truth. Zero conditional logic in the rendering, the journey drives the interface.

At each state of the journey, the app answers three questions the parent is asking : where I am, what's coming, and what has already been done for me.

The home screen surfaces the vital information of the moment first. A simulation ready to review, an appointment to confirm, a candidate to meet. Everything else recedes. The parent doesn't dig through a menu, the app pushes the useful action.

Administrative work is pre-chewed wherever possible. Costs per childcare type are calculated in advance. CESU pre-financing activates with one tap. Candidate profiles arrive pre-filtered and sorted by Constance, with her notes, and a favorite tag when she has one.

The design system exists to serve this mechanic. Five semantic colors (aubergine for CTAs, blush for empathy, olive for validation, peach for waiting, lilac for discovery) that give a status at a glance. An editorial voice, Constance's, that speaks short and direct, with no HR jargon. A Fraunces typeface to soften the register.

But color was never the point. The point is that at 2:17 PM between two meetings, the parent opens the app and knows in two seconds what to do.

V2 delivered. A B2B2C app that follows the parent through every step, seven states mapped, 46 screens derived, an aubergine and fruit-named design system, an editorial voice carried by Constance.

The simulation engine allowed each journey to be validated on concrete material before production, and served as an architecture blueprint for the refactor of Wepartum's technical workflow.

Where the V1 just validated an administrative file, the V2 supports a parent through a decision that matters.