Wolverhampton enquiries about ExpressionEngine support usually come down to one of two situations: a site that's ageing quietly without incident, or one that's actively broken with the previous developer unresponsive.
Karl's the one you'd work with, and only Karl. He's built Expression 37 around ExpressionEngine and Craft CMS exclusively since 2007. There's no account manager in the picture.
Nothing gets recommended before he's gone through the build properly. What that shows decides whether it's a fix, an upgrade, or an ongoing retainer.
Where this tends to matter:
Manufacturers whose site publishes detailed spec sheets or catalogues that need to stay properly organised and searchable as the range grows. Businesses whose previous agency has quietly stopped supporting ExpressionEngine, leaving the install live but unmanaged in practice. Firms with Salesforce or HubSpot integrations into supplier or stock systems that were set up years ago and never documented. And sites several major EE versions old, where every installed add-on needs checking individually before touching an upgrade.
How engagements typically begin:
Karl reviews the templates, add-ons, and content structure before quoting anything, because these handovers tend to arrive with more institutional memory than actual documentation. Most people get in touch after something specific: a supplier feed that's stopped updating correctly, a security notice about an outdated add-on, or a decision that the site can't keep running without proper oversight. From there it's either a scoped project or a retainer, agreed upfront.
Common questions from Wolverhampton clients:
Does it matter that you're not based in Wolverhampton?
No, not for the actual work. Everything is handled remotely, from reviewing code to deploying changes, and it works well. Wolverhampton is close enough that a face-to-face conversation is never really an obstacle.
Our site feeds product data to a supplier or stock system, is that a common setup?
Very common around here given the manufacturing base. It needs mapping properly before any change touches the surrounding templates, so nothing quietly breaks further down the chain.
Can you pick up a site from a developer who's no longer contactable?
Yes, this comes up all the time. Getting a proper look at the code, sorting out what's a genuine custom build from a tweaked add-on, and writing down what wasn't documented the first time round.
What if our ExpressionEngine version is a long way behind?
That's common rather than unusual. The real work in an upgrade tends to be auditing which add-ons still function, not the version jump itself.
What's included with ongoing support?
You go to the front of the queue when something goes wrong, get checked on between problems rather than only after one shows up, and deal with someone who already knows your setup instead of explaining it fresh every time.
How much does this cost?
It's scope-dependent. Standalone work is a fixed quote. Continuing support runs as a flat monthly retainer. Either way, the figure is settled before work starts.
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.
