Eficiens · CCMO Mutuelle

At a glance

• Industrialized a proof of concept: from zero to over 1,050 automated tests, 85% of PHP lines covered
• Lightweight DDD, ports & adapters on 7 third-party clients, mocked to work off-VPN
• Full journey: 4-step quote, 7-step subscription, payment and OTP e-signature
• Pixel-perfect, responsive and accessible Figma integration (WCAG 2.1 AA audit) on a Twig UX design system
• Business integrations: pricing, XML/PDF document generation, CRM, DMS, Brevo emails, e-signature and bank payment

Paris-based digital agency. Assignment at CCMO Mutuelle, a French multi-industry health insurer based in Beauvais: redesign and production launch of the online sales journey, from quote to contract signature.

Context

Sole developer on the application, working directly with the client’s project-management support team, IT department and marketing team, under the supervision of an Eficiens project manager.

Starting point (February 2026 audit): a working but non-industrializable Symfony proof of concept — no tests at all, exposed admin back office, hard-coded secrets, monolithic controllers, a UI that neither matched the mockups nor was responsive, and a Lighthouse score of 56/100.

Goal: deliver a production-ready application — tested, secured, accessible and matching the mockups — covering the whole journey, from anonymous quote to contract signature.

Stack: PHP 8.2 / Symfony 7.4, Twig and Twig UX components, Doctrine ORM, Messenger, MariaDB, Webpack Encore, Docker, GitLab CI, Figma mockups.

Achievements

• Industrialized the proof of concept: full security hardening (secrets moved out of the code, encryption of sensitive session data, dependency injection, rate limiting) and a GitLab CI pipeline with scheduled Composer and npm dependency audits
• Test strategy: 952 PHPUnit tests (2,576 assertions, unit and BDD) and 105 Jest tests, all green; critical front-end validation rules (phone, dates, fields) 100% covered, French social security number 93%, IBAN 75%
• Lightweight DDD architecture: Domain / Application / Infrastructure layers, port interfaces on each of the 7 third-party clients (pricing, document generation, CRM, DMS, signature, payment, mailer), backed by mock implementations to develop without VPN access to the client’s systems
• 4-step quote flow: people to cover, coverage needs, contact details, plan comparison with real-time pricing and a personalized study sent by email
• 7-step subscription flow: beneficiaries, contract, summary, bank details with BIC/IBAN validation, supporting documents, first premium payment and electronic signature by one-time code
• XML/PDF document generation: seven document templates (membership form, SEPA mandate, termination mandate, advice sheet, personalized study) produced by typed XML builders and validated against reference fixtures
• Journey resumption: signed 256-bit token paired with a one-time code, delayed reminder through Brevo cancelled on subscription, scheduled purge of expired tokens, brute-force protection and per-IP quota
• Pixel-perfect Figma integration: design system of reusable Twig UX components (buttons, fields, date picker, toggles, collapsible blocks, step bar), responsive from mobile to desktop
• Accessibility: WCAG 2.1 AA audit of the funnel, keyboard, focus and label compliance, and documented contrast issues escalated to the client’s design team
• Performance: HTTP caching, image compression (main visual down from 17 MB to 369 KB), fonts and lazy loading of third-party widgets; Lighthouse score from 56 to 71

Results

• PHP line coverage raised from 0 to 85% (5,135 of 6,035 lines) in seven months; uncovered code is concentrated in internal tools never exposed to customers
• Lighthouse score from 56 to 71/100 and main content (LCP) displayed 2 s faster, the rest being down to the client’s third-party widgets
• Full journey working end to end, from anonymous quote to electronic signature: a non-deployable proof of concept turned into a production-ready application
• Development independent of the client’s systems: all 7 third-party services can be simulated, so work is no longer blocked by the VPN or by undelivered APIs
• A codebase others can take over: explicit layers, swappable third-party clients and operations documentation