Worcester's Craft CMS enquiries usually mean one of two things: an install that's ticking over unpatched, or one that's genuinely broken with the developer who built it gone.
Karl's the person who works on it, always has. Craft CMS and ExpressionEngine are the only platforms Expression 37's ever touched, since 2007. Every job stays with him.
He checks the install properly before recommending anything. Depending on what he finds, that's a fix, an upgrade, or an ongoing retainer.
Where we typically come in:
- Manufacturers with technical, specification-heavy Craft sites, where content accuracy matters as much as how it looks.
- Food and agriculture businesses managing seasonal trade content and supplier information through Craft.
- Dealer or installer locator tools that need to stay accurate without constant manual maintenance.
- Businesses capturing trade or installer enquiries through HubSpot, an integration that needs the same care as the CMS itself.
- Owners who'd rather properly fix an existing site than pay for a rebuild that solves nothing underlying.
How a typical engagement starts:
The trigger is usually specific and practical: a locator tool returning bad results, a security scan flagging outdated plugins, or an enquiry form that's silently stopped sending emails. Karl reviews the actual codebase and Composer setup before quoting, and a good amount of that first work turns into ongoing monthly cover.
Common questions Worcester clients ask:
Does location matter for support like this?
Not really, no. Everything happens remotely, code review, deployments, fixes, and Worcester's close enough for the rare occasion a visit genuinely adds value.
Our content is mostly technical specifications, does that change how you'd handle the site?
It shifts the priority toward accuracy and searchability of that content over visual changes, and that's what drives how updates and fixes get approached.
We'd rather patch what we have than rebuild, is that a sensible option?
Often, yes. Most sites assumed to need a rebuild actually just need proper maintenance and an honest audit of the current install.
How far behind can we let our Craft version get before it's risky?
Security first, regardless of version. Beyond that, older installs run into plugins that have stopped being maintained, which is the real problem once an upgrade's genuinely needed.
Would you take on the enquiry form integration as well as the site itself?
Yes, it's usually built directly into the Craft templates, so treating it separately from the CMS tends to miss where issues actually originate.
How is pricing structured?
Fixed cost for scoped project work, monthly retainer for ongoing support, agreed before anything starts.
What's the right way to begin?
A short call about the site, its current Craft version, and what's prompting you to look into this now.
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.
