Norwich's Craft CMS enquiries tend to split into two kinds: an install that's stable but untouched, or one that's genuinely broken with the developer who built it long gone.
Karl's who takes it on, always has. Craft CMS and ExpressionEngine are the only platforms Expression 37's ever worked in, since 2007. No account manager, just Karl.
He checks what's actually in the install before recommending anything. That leads to a fix, a version upgrade, or an ongoing retainer.
What does Aviva have to do with Norwich's Craft installs?
Not directly, but its long-standing presence has shaped an entire ecosystem around it, a genuinely large insurance and financial services base, a wider professional services scene, and lately a creative and tech pocket growing alongside both. Craft's picked up a reasonable share of that, usually chosen years back for exactly the kind of content-heavy corporate site this sector needs.
Karl works with Norwich businesses whose installs have simply aged past anyone paying attention, an audit and upgrade, a full handover from a developer who's moved on, or standing support for anyone who'd rather not deal with problems reactively. The codebase gets read properly first, every time.
The install this usually turns out to be:
Somewhere the content genuinely has to be accurate, an insurer or financial firm where uptime isn't optional, not a nice-to-have. A creative or agricultural business whose site has simply outgrown the structure it was built around. Occasionally a Salesforce or HubSpot connection running alongside the CMS that nobody's kept in sync properly. Left behind by a developer who's stopped supporting Craft work entirely. And several major versions old, needing every plugin's compatibility checked honestly rather than assumed.
Common questions Norwich clients ask:
What actually happens before you'll put a number on anything?
The real codebase gets reviewed, templates, plugins, however the content's evolved, because guessing scope from a description tends to be wrong in exactly the ways that end up mattering.
Is a developer outside Norwich a real limitation?
Barely comes up in practice. The whole process runs remotely and holds up fine, and Norwich is close enough that a visit's never genuinely difficult if one's actually warranted.
Our previous developer's stopped supporting the install, what now?
Common enough that it's routine. Someone reads the code properly, sorts what's genuinely bespoke from a modified plugin, and that's the whole first step.
Does an old Craft version put content accuracy at risk?
Rarely by itself. The platform tends to hold up. What actually needs attention is whatever's been bolted onto it and left unmaintained since launch.
What does a standing arrangement actually change?
Someone's watching before a fault becomes visible, not after. Response is faster when it counts. And it's the same developer each time, not a stranger relearning your setup.
What's this likely to cost?
A single job gets one fixed number, agreed upfront. Anything ongoing runs monthly. Nothing's committed until the scope's actually clear.
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.
