Wolverhampton's Craft CMS enquiries tend to split into two kinds: an install that's stable but untouched, or one that's genuinely gone wrong with nobody left to call.
Karl handles every one personally, no wider team involved. Craft CMS and ExpressionEngine are the only platforms Expression 37's touched since 2007. You deal with him, not an account manager.
He reviews what's genuinely in the install before recommending anything. That leads to a fix, a version upgrade, or an ongoing retainer.
Why does structured content matter more here than elsewhere?
Because so much of Wolverhampton's manufacturing base sits several tiers back in the automotive supply chain, component suppliers and precision engineering firms whose sites exist to hold accurate product and specification data, not to look pretty. Craft's a reasonable fit for that, and a fair number of local installs were originally built with exactly that job in mind.
Expression 37 picks these up in whatever state they've reached, a compatibility audit before touching anything, a full handover, or ongoing monthly support for a business that wants someone watching proactively rather than reacting after something's already broken. Karl reads the code before he'll put a number on anything.
Common questions from Wolverhampton clients:
Our stock feed connects into a supplier's system, does that add risk?
It's routine around here, not risky by itself, but it needs mapping properly before touching anything nearby. Skip that step and something further down the chain breaks quietly, usually without anyone noticing straight away.
Working with someone based elsewhere, does that actually function?
It does, fully. Nothing about reviewing code or shipping changes needs anyone physically present, and meeting in person is easy enough on the rare occasion it's genuinely called for.
What's involved in picking up a site nobody here understands anymore?
Reading the code properly, working out what's genuinely bespoke against a modified plugin, and writing down whatever the original build never bothered documenting.
Is a Craft version several releases behind a real concern?
It's common rather than alarming. Most of an upgrade's actual effort goes into checking which plugins still function and sorting Composer conflicts, not the version jump itself.
What does the ongoing side of things actually get us?
Front of the queue when something breaks, someone checking in between problems instead of only after one's reported, and a developer who already knows the setup rather than starting from a blank page.
Roughly what should we expect to pay?
Depends what's actually needed. A standalone job is a fixed number. Continuing support runs monthly at a flat rate. Either way, the figure's settled before anything starts.
Where this tends to matter:
Manufacturers with detailed spec sheets or catalogues that need proper organisation as the range keeps growing, not a folder of PDFs nobody can search. Businesses whose previous agency quietly stopped supporting Craft, leaving the install live but effectively abandoned. A Salesforce or HubSpot connection into a supplier or stock system, wired in years ago and never written down anywhere. Sites several major versions old, needing every plugin checked individually before an upgrade's anywhere near safe.
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.
