Milton Keynes' Craft CMS enquiries tend to split two ways: an install running fine but neglected, or one that's genuinely gone wrong while whoever built it is unreachable.
Karl takes these on directly, no exceptions. Craft CMS and ExpressionEngine are the only platforms Expression 37's worked in since 2007. You go straight to him.
He reviews what's genuinely in the install before quoting anything. Depending on the outcome, that's a fix, an upgrade, or an ongoing retainer.
Why does infrastructure matter so much to a Milton Keynes site?
The town was planned around motorway access from the start, and that's exactly why distribution firms, corporate head offices, and a growing tech cluster all ended up based here. Plenty of the Craft installs supporting those businesses were built during a period when the platform was more commonly chosen locally, and haven't had a proper look since.
Expression 37 picks these up wherever they've ended up: a compatibility check ahead of an upgrade, taking over from a developer who's disappeared, or an ongoing arrangement for a business that wants someone actually keeping watch. Karl reads the real code first, before any number gets discussed.
Common questions Milton Keynes clients ask:
Our site publishes live scheduling or availability data, does that complicate things?
It raises the bar on testing, mainly. Anything time-sensitive needs its update path checked properly, because a delay there is a genuine operational problem, not a cosmetic one.
Is being physically based here actually necessary?
No, and given how many businesses in Milton Keynes already operate across several locations, that's rarely even raised as a concern. A visit's easy enough if one's ever genuinely useful.
The original developer's long gone, does that rule anything out?
Not at all, it's a familiar starting point. Someone has to open the codebase properly and work out what's genuinely bespoke, and that's exactly where this begins.
At what point does an old Craft version stop being trustworthy?
Rarely a clean cutoff. The platform itself tends not to fail on its own. It's whatever's been layered on top and left unmaintained, plugins, stale Composer dependencies, that actually causes problems.
What does an ongoing arrangement actually buy us?
Being first in line when something breaks, someone checking in before it becomes a fire rather than after, and never having to re-explain your own setup to a stranger.
What are we likely looking at cost-wise?
Entirely tied to scope. A defined job is one fixed number, agreed upfront. Ongoing work runs monthly. Nothing's quoted without knowing exactly what it covers.
Where this tends to matter:
A distribution or logistics business whose site shows live availability or scheduling, where stale data is a real operational cost rather than a minor annoyance. A corporate site whose content team has outgrown the structure it was originally built around. An install left behind when the agency or freelancer who built it wound down. A Salesforce or HubSpot connection that quietly broke and went unnoticed for weeks is a fairly common trigger for that first conversation. And a Craft version old enough that every plugin needs individually checking, Composer included, before an upgrade's attempted.
Ready to get started?
If your website is business-critical and needs a specialist who will take proper long-term ownership of it, get in touch. Karl will respond personally and give you an honest view of how we can help.
