If you're looking for ExpressionEngine support in Woking, the site's probably in one of two states: quietly fine but unpatched, with nobody wanting to be the one who breaks it, or actively causing problems while the previous developer isn't responding.
That's where Karl comes in. He's only ever worked with ExpressionEngine and Craft CMS, since founding Expression 37 in 2007. Nobody else touches the work. You deal with him directly, not an account manager.
Karl goes through what's actually built into the site before recommending anything. After that it's usually a straightforward fix, a version upgrade, or an ongoing retainer, whatever the site needs.
Where we typically come in:
- Engineering and technology companies with corporate ExpressionEngine sites that need to stay polished and technically sound simultaneously.
- Professional services firms serving the local commuter-town market, where reliability matters more than flashy features.
- Sites facing a rebrand or corporate restructure, where the underlying CMS needs auditing before any visual changes are made.
- Businesses with Salesforce handling client or lead data fed from the site, needing someone across both the CMS and the integration.
- Owners who want direct developer access rather than working through an agency's account management layer.
How a typical engagement starts:
Woking enquiries often follow a corporate trigger, an upcoming rebrand, a security review ahead of a compliance audit, or simply a new marketing lead discovering nobody can explain the current site's structure. Karl reviews the actual codebase before quoting, and a fair share of that first work turns into an ongoing monthly retainer.
Common questions Woking clients ask:
Is it a problem that you're not based in Woking?
Not really, no. Support happens remotely throughout, code review, deployment, ongoing fixes, and Woking's easily reachable for the rare occasion an in-person meeting genuinely helps.
We've got a rebrand coming up, does the CMS need looking at first?
Usually, yes. It's worth auditing what's actually built into the site before a rebrand touches templates and content, so the technical foundation doesn't undermine the new look.
Nobody currently here fully understands our site's structure, is that common?
Very common, particularly after a staff or agency change. Mapping what's actually there comes first, before any changes are made.
How out of date can our EE version be before it's a genuine problem?
Security patching matters most regardless of version. Beyond that, older installs increasingly struggle to find maintained add-ons, which is the real issue at upgrade time.
Do you support the Salesforce integration as well as the CMS?
Yes, it's usually built directly into the ExpressionEngine templates, so treating it separately from the site tends to miss where issues actually surface.
What's the pricing structure?
Fixed cost for scoped project work, monthly retainer for ongoing support, agreed before anything starts.
What's the sensible first step?
A short call about the current site, its EE version, and what's prompting the enquiry 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.
