A Hull enquiry about ExpressionEngine support is usually one of two things: a site left running quietly for years, or one that's causing real trouble with the agency behind it no longer contactable.
Karl's the one who picks it up, every time. He's built Expression 37 around ExpressionEngine and Craft CMS alone, since 2007. There's no account manager between you and him.
He works through what's actually there before recommending anything. That's usually a fix, a version upgrade, or an ongoing retainer.
Who this tends to matter for:
Logistics and port-related businesses whose site needs to reflect current schedules, capacity, or availability accurately, where stale information isn't a cosmetic problem, it's an operational one. Creative and cultural organisations whose content volume has grown well past what the original site structure was built to handle. Firms whose previous developer has gone quiet, leaving a site nobody currently feels able to change. And installs old enough that every add-on needs a proper compatibility check before an upgrade goes anywhere near it. Firms with Salesforce or HubSpot feeding data in and out of the site need a developer who understands both ends of that connection, not just the CMS.
How a typical engagement starts:
Karl goes through the templates, add-ons, and content structure before quoting, since Hull handovers tend to come with assumptions rather than documentation. Most people get in touch after something concrete happens: information that's gone stale in a way that actually matters, a plugin that's stopped working after a routine update, or a decision the site needs proper ownership again. From there it's a defined project or a retainer, priced before anything starts.
Common questions Hull clients ask:
Is it a problem that you're not based in Hull?
Not really. The work happens remotely from start to finish, code review through to deployment, and it works well. Hull is close enough that an in-person conversation is never a real barrier if it's genuinely useful.
Our site needs to reflect live schedules or availability, does that change your approach?
It changes what gets tested most carefully. Anything time-sensitive needs a reliable way to update quickly and confidence that it's actually displaying correctly, rather than being treated as a minor content afterthought.
We inherited this from a developer who's no longer around, can you take it on?
Yes, this is a common starting point. Working out what's genuinely custom versus a modified add-on takes an actual look at the code, not a guess from the front end.
How far behind can an ExpressionEngine install get before it's a real risk?
It depends less on age than people assume. A well-kept older install can be safer than a newer one nobody's audited. Add-ons are where the actual risk tends to sit.
What does ongoing support actually include?
First priority when something breaks, regular checks so issues get caught early rather than after a visitor notices, and a developer who isn't starting from zero on every call.
What will this cost?
Depends entirely on the work involved. A single project carries a fixed cost. Retained support is billed monthly. You'll always know the number in advance.
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.
