Brighton's Craft CMS enquiries mostly split two ways, an install holding up fine but under-maintained, or one where something's already gone wrong.
Karl's the only person you'll deal with on this, no account manager, no wider team. Expression 37 has stuck to Craft CMS and ExpressionEngine only, since starting in 2007.
The install gets a proper look before he says what's needed. That could mean a fix, a version upgrade, or an ongoing retainer.
Why do so many good Brighton builds end up orphaned?
Because the city has one of the densest clusters of digital agencies outside London, and agencies here close, pivot, or switch platforms constantly. A well-built Craft site doesn't stop working when that happens, it just stops having anyone who remembers how it's put together. A surprising number of genuinely solid installs from Brighton studios are still running quietly with no one left to call about them.
Expression 37 picks those up: an audit and upgrade for something that's drifted, a full takeover when the original agency's vanished, or a standing retainer for a business that wants a specialist who isn't going anywhere next. Karl reads the actual codebase before quoting, every time.
Common questions Brighton clients ask:
Our agency's shut down, is picking this up realistic?
Very realistic, it happens often enough here that it's practically routine. The code gets read properly first, sorted into what's genuinely bespoke versus a stock plugin, regardless of how the previous agency left things.
With so many developers already in Brighton, why go remote?
Because most of the industry here already works that way. Review, deployment, testing, handled identically whether someone's five minutes away or two hundred miles, and it works.
Weekends and summer bring a real traffic spike, is that worth flagging?
Worth flagging and worth acting on. Sites with sharp peaks need their hosting and heavier pages tested well ahead of the busy stretch, not discovered live once it's too late to fix quietly.
How old does a Craft install need to be before it's genuinely a problem?
Older than people generally think. The platform itself rarely misbehaves. It's the plugins and Composer dependencies built up around it, left unattended, that eventually cause the trouble.
What's the actual value of a retainer here?
Priority the moment something breaks, proactive checks instead of silence between problems, and continuity, the same developer each time rather than starting fresh.
Roughly what does this cost?
A one-off piece of work, audit or fix, gets a fixed quote. Anything ongoing runs monthly. Either way you'll know the number before committing.
Where this tends to matter:
A business whose agency's closed, rebranded, or quietly walked away from Craft work, leaving a site that's technically sound but practically unsupported. A tourism or hospitality site with a sharp seasonal pull around weekends and summer. Somewhere with Stripe, HubSpot, or a booking system wired straight into Craft by a developer who's no longer contactable. And an install several major versions behind, where the real work is a proper plugin-by-plugin compatibility pass.
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.
