:quality(80))
From platform constraint to business capacity: what changes when the foundation is right
A platform stops being infrastructure the moment a routine content change needs an engineer. The update that should take an afternoon waits for a ticket, then a developer, then a slot in the next sprint, and lands three weeks later. Nobody decides this is acceptable. It becomes the way things work, and the team plans around it. That is the line between a platform that carries the business and one the business has to carry.
:quality(80))
The ceiling Service Apotheek hit
Service Apotheek is one of the largest pharmacy franchise organisations in the Netherlands, with more than 500 affiliated pharmacies serving tens of thousands of healthcare consumers daily. The platform was not failing in any visible way. It was just consistently, quietly insufficient. The CMS gave marketing too little room to move. Franchise personalisation, each pharmacy with its own pages and local identity, required workarounds that added maintenance overhead with every update. Aligning the website with the more advanced app meant bridging two systems that were never designed to share a foundation.
The platform had been built for what the business was. It had no capacity for what the business was becoming. That distinction, between a platform sized for the moment of launch and one built to carry the business forward, is where most platform decisions eventually break down.
What the rebuild was actually for
The rebuild was never about adding features. It changed how content and the teams who work with it every day relate to each other. The new platform decouples content from its presentation layer and connects it via API to each pharmacy's own data, with Umbraco as the CMS and a React and Next.js frontend. More than 100 pages were rebuilt from the information architecture up, structured around how healthcare consumers actually navigate decisions about prescriptions and repeat medication.
The goal was a platform marketers could run without waiting in a queue.
What the new foundation made routine
The platform now serves around 50,000 healthcare consumers daily. Performance and accessibility scores were strong from launch. Organic traffic for critical search terms has grown steadily, and Service Apotheek has reached top positions for the keywords that matter most to the business. Traffic held stable through the migration, the result of a deliberate content structure and redirect strategy, not luck.
Those are the numbers. What they represent in practice is a different kind of working day for the people closest to the content. Marketers update and publish without raising a ticket. Franchise pages are personalised locally without each instance requiring custom development. What used to be a project is now a normal action. The results came faster than the team expected. That happened because the rebuild was structural: when the foundation is right, the work that follows it compounds rather than accumulates.
The ceiling is a design decision, not a healthcare problem
The ceiling Service Apotheek hit is not specific to healthcare or franchises. It is the predictable outcome of a build optimised for launch rather than longevity. Content bound to its presentation layer, architecture designed for one channel, governance handled through workarounds: none of these is a maintenance problem. Each is a design decision that calcifies over time.
Half of the enterprises that already migrated are trying a new platform (State of CMS 2025, n=1,300). Most are not moving because the platform looks bad. They are moving because it stopped being capacity and became constraint. The question worth asking now, before the next rebuild, is whether your platform is built to carry what the business is becoming, or only what the business was.
Enterprise CMS & Digital Platform Insights
Insights on replatforming, CMS migration, and building scalable digital ecosystems.
:quality(50))
:quality(50))