Status: Delivered. Described from our own delivery records. Client identity, brand and commercial terms are withheld. Figures, where given, cover the period stated and nothing beyond it.
Context
A group of related companies, each with its own web presence: a site, a blog, event announcements and forms through which customers make contact.
Each had been built and was being maintained on its own terms.
The problem
- Every company's site was managed separately, so a change to a shared pattern had to be made several times.
- Publishing an event or a post required knowing which system that company used.
- Customer engagement forms fed into different places, so enquiries were handled inconsistently.
- Infrastructure cost scaled with the number of sites rather than with traffic.
What we built
A shared content-management system
Covering the group's sites, blogs, event updates and engagement forms, with each company retaining its own identity.
Shared delivery pipelines
So publishing and deployment work the same way regardless of which company's content is moving.
Shared serverless infrastructure
So cost tracks actual usage rather than the number of sites standing.
How we delivered it
- 1
Audit the existing estate
What each company runs, what is genuinely different, and what only appears different.
- 2
Design the shared model
Around the real differences, not the accidental ones.
- 3
Build the platform and pipelines
With one company as the pilot.
- 4
Migrate site by site
Each with its own content and its own switch-over.
- 5
Hand over publishing
To each company's own team.
How it was phased
Indicative phasing for work of this shape. Actual duration varies with data quality, access and decision speed.
What the client keeps
- The platform and its source
- Infrastructure definitions in their own repository
- Delivery pipelines
- The content model
- Per-company publishing documentation