Industrialise the public site
32 page types and 165 reusable components, connected to a headless CMS so that marketing can publish without a code release.
CASE STUDY / 01ANONYMISED ASSIGNMENT
Automotive retail · franchise networkNational automotive marketplace
A network of around 90 branches, a marketplace in 7 languages and 14 country versions, and the whole system connecting catalogue, acquisition, CRM, distribution, invoicing and cloud operations.
DURATION2 years
ROLEArchitecture, development, operations
TEAMUp to 9 people
STATUSIn production
THE CONTEXT WE FOUNDUnderstand the system
Understand the system
before transforming it.
The public site and the business tools ran on a single server, with manual releases. The real catalogue was almost invisible to search engines, enquiries landed in a generic mailbox, and there was neither a standby site nor any monitoring.
WHAT WAS DONEFrom diagnosis.
From diagnosis.
To production.
The scope describes the decisions and the work actually carried out, without naming the organisation involved.
Produce the catalogue at scale
The sitemap is rebuilt every night from production, split by type, country and branch, then checked against control pages before publishing.
Fix performance and SEO at the source
Caching placed on the data that is genuinely expensive, five families of 404s removed and 349,874 duplicate addresses redirected.
Build the acquisition chain
Collection, normalisation, a 0-to-100 score, territorial assignment, traced consent and idempotent delivery to the CRM.
Connect the network operations
Lead / Contact / Deal / Customer CRM, distribution to portals, branch back office, indicators, invoicing and compliance.
Change the foundation without interrupting the business
Migration to Kubernetes, four environments including a replicated standby site, versioned configuration and purpose-built monitoring.
MEASURED RESULTSFacts.
Facts.
Not a logo.
TECHNOLOGIES IN PRODUCTION
The foundation actually used.
Next.jsReactTypeScriptSymfonyPHP 8StrapiMySQLPostgreSQLRedisRabbitMQKubernetesTraefikGitHub ActionsS3 / R2Playwrightk6
Clients, brands, domains, addresses and identifying details are not published. The figures come from the logs, databases, clusters, repositories and control reports provided for these assignments. Security incidents are described without any reproducible exploitation path.
OTHER CASE STUDIESTwo other systems.
Two other systems.
Two other sets of constraints.
02Public sector · national portal
Public service portal
A national portal where users follow sensitive administrative procedures, made of several generations of front end, a business API, a CMS, an SSO and a Kubernetes cluster.
5 yearsMigration under way
Read the full case study ↗
03Digital marketing · lead generation
White-label acquisition platform
An acquisition platform, dozens of landing pages and white-label sites that collect and then distribute qualified enquiries to partners.
8 yearsIn production
Read the full case study ↗A critical system to build or to take over?
Describe the context, the existing systems and the expected result. We will propose the right level of intervention.