Craft CMS enquiries out of Guildford usually involve one of two situations: an install running fine but neglected, or one that's genuinely broken while nobody's left to call.
Karl takes these on directly. He's worked only in Craft CMS and ExpressionEngine since Expression 37 started in 2007. Every job stays with him, not a wider team.
The install gets a proper look before anything's quoted. That's usually a fix, a version upgrade, or an ongoing retainer.
Surrey's tech corridor, and what it means for Craft support
A research park and a university feed a steady stream of growing software and engineering firms in Guildford, alongside an affluent professional services base commuting into London. A good number of those companies run Craft installs that were built properly at the start and have since been left to run themselves.
Karl works with Guildford businesses whose install has reached that point: a founder or early hire who understood the tech has moved on, several major versions behind, or a developer who's stopped taking on Craft work. Nothing gets quoted without reading the actual codebase first.
Common questions Guildford clients ask:
What actually happens before a number gets discussed?
The codebase gets opened up properly, templates and plugins both, since guessing scope from a description tends to be exactly how quotes end up wrong. A CRM sync that's quietly stopped working, or a decision the install can't run unsupervised any longer, usually prompts that first conversation.
Is being outside Guildford's immediate area a real limitation?
Barely. The rail link into London means a visit's easy enough on the rare occasion it's genuinely useful, but very little of the actual work depends on it.
Our site's outgrown what it was built for, is that common here?
Very common, especially with fast-growing tech firms. It needs a structure that can actually take the weight, not one stretched past what it was designed for.
Can an install be taken over from a developer who's moved on?
Yes, routine work. Establishing what's genuinely custom versus a modified plugin comes first, based on an actual read of the code.
Is an old Craft version a real concern?
On its own, not particularly. Trouble tends to come from whatever's been plugged into it and forgotten about, more than the platform version itself.
Do you handle the Salesforce or HubSpot integration too, or just the CMS?
Both, as one piece of work. Those connections are usually wired directly into the templates, so treating the CMS and the integration as separate problems tends to be where things get missed.
Where we typically come in:
A growing tech or engineering firm whose site was fine for five people and isn't anymore, now stretched well past what it was designed to hold. A company running Salesforce or HubSpot for sales and marketing, that connection deserving the same standard of care as the CMS itself. An install left behind entirely when whoever understood it left the company, with nobody currently confident enough to touch it. And a Craft version several major releases old, where an honest upgrade means a proper plugin-by-plugin pass and resolving whatever Composer's built up.
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.
