Colchester's Craft enquiries tend to involve an install that was properly built once, then handed the bare minimum of attention for years afterward.
Karl fills that gap personally. Craft CMS and ExpressionEngine are all Expression 37's ever done, since 2007, and it's always Karl on the work.
Karl won't recommend anything until he's actually reviewed what's there. Usually that ends up being a fix, a version upgrade, or an ongoing retainer.
Why does Britain's oldest town have so many orphaned sites?
A garrison presence, a growing university population, and a retail and hospitality sector that all lean on websites nobody's necessarily kept a close eye on. A fair number of those sites were built on Craft during a period when the town's digital economy was expanding quickly, and have run largely unsupervised since.
Expression 37 supports Colchester businesses in that position: a developer who's stopped returning calls, an install several major versions behind, or a site with bespoke functionality nobody currently understands. Karl reviews the actual codebase before quoting, rather than guessing from outside.
Common questions Colchester clients ask:
What's the actual starting point for an engagement?
Karl goes through the templates and plugins directly before anything's quoted, since these handovers rarely arrive with documentation worth relying on. Most people get in touch after something specific: an integration that's stopped syncing, a security notice nobody's acted on, or a decision the site can't keep running unsupervised.
Being a fair distance from Colchester, does that create friction?
Very little. The garrison and university links mean plenty of local businesses already deal with people outside the immediate area, and remote support fits that pattern without anyone noticing much difference.
Can this be picked up from a previous agency that's walked away?
Yes, and it's a familiar shape of job here specifically. The templates get opened, the plugins get audited, and only then does anyone talk about what happens next.
Is an old Craft version something we should worry about?
On its own, rarely. Most of the actual risk sits with plugins nobody's revisited in years rather than the platform version itself.
What tangibly changes once there's a retainer in place?
The site stops being something that only gets attention when it breaks. Regular checks catch problems early, and response on anything urgent moves to the front of the queue.
What's the likely cost?
A single job carries one fixed number, settled before it starts. Ongoing support runs monthly. Either way, nothing's agreed until the scope's actually clear.
Where this tends to matter:
A retailer or hospitality business whose trading periods genuinely stretch the site, not the quiet weeks either side of them. Somewhere with HubSpot or a CRM wired in by whoever built the site, long since gone, leaving the connection a mystery to everyone currently involved. An install that's technically live but effectively unwatched, the previous developer having quietly stopped taking Craft work at some point. And a version old enough that a proper upgrade means going through every plugin individually rather than trusting a version bump alone.
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.
