If you're looking for Craft CMS support in Woking, the install's usually in one of two states: running fine but ignored, with nobody keen to be the one who breaks it, or already causing problems while whoever built it has gone quiet.
That's Karl's job. He's only ever worked with Craft CMS and ExpressionEngine, since founding Expression 37 in 2007. Nobody else touches the work. You deal with him directly, not an account manager.
Karl checks what's actually in the install before recommending anything. From there it's typically a quick fix, a version upgrade, or bringing the site on as an ongoing retainer, depending on what it needs.
Where we typically come in:
- Engineering and technology companies with corporate Craft sites that need to stay polished and technically sound at the same time.
- Professional services firms serving local commuter-town clients, where quiet reliability matters more than flashy new features.
- Sites approaching a rebrand or corporate restructure, where the CMS needs auditing before visual changes go anywhere near it.
- Businesses feeding client or lead data into Salesforce, needing a developer comfortable on both sides of that connection.
- Owners who'd rather deal with a developer directly than go through an agency's account management process.
How a typical engagement starts:
A corporate trigger is common: an upcoming rebrand, a security review ahead of a compliance check, or a new marketing hire finding nobody can explain the site's current structure. Karl reviews the actual Craft install and Composer setup before quoting, and a good share of that initial work becomes an ongoing monthly retainer.
Common questions Woking clients ask:
Does it matter that you're not based in Woking?
Not really. Support runs remotely throughout, code review, deployments, ongoing fixes, and Woking's easily reachable for the rare occasion a face-to-face genuinely helps.
We've got a rebrand in the pipeline, should the CMS be reviewed first?
Usually worthwhile, yes. Auditing what's actually built before a rebrand touches templates and content means the technical foundation doesn't quietly undermine the new design.
Nobody here fully understands the site's structure anymore, is that unusual?
Not at all, particularly after a staff or agency change. Mapping what's genuinely there comes first, before anything else is touched.
How far behind on Craft is a real problem?
Security first, regardless of version. Beyond that, older installs run into plugins that have stopped being maintained, and that's the practical issue once an upgrade's due.
Is the Salesforce connection something you'd support as well as the CMS?
Yes, it's typically built directly into the Craft templates, so treating it apart from the site tends to miss where issues actually come from.
How's pricing worked out?
Fixed cost for scoped project work, monthly retainer for ongoing support, agreed before anything starts.
What's a sensible way to start?
A short call about the current site, its Craft version, and what's prompting the enquiry.
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.
