A Plymouth enquiry about ExpressionEngine support is usually one of two things: a site that's held up fine but ignored, or one that's genuinely broken with nobody left to call about it.
Karl's who picks it up, first call to final fix. He's kept Expression 37 to ExpressionEngine and Craft CMS only, since 2007. There's no handoff to anyone else.
He goes through the site properly before saying what it needs. Depending on what turns up, that's a fix, an upgrade, or an ongoing retainer.
The kind of work that comes up:
Tourism and visitor-facing sites where seasonal traffic swings hard between winter and the summer holiday period, and where a slow or broken site during July costs real bookings. Maritime and marine supply businesses whose site needs to hold technical specification content properly, not just marketing copy. Sites left behind when a freelancer or small agency stopped trading, with no clear record of what add-ons are installed or why. And installs several ExpressionEngine versions old enough that an upgrade needs a proper compatibility pass across every add-on first. Tourism operators taking bookings through Stripe, or marine suppliers running Salesforce alongside their site, need a developer who treats the integration as part of the system, not an afterthought.
How this usually plays out:
Before any quote, Karl goes through the templates and installed add-ons directly, since Plymouth handovers rarely arrive with anything resembling proper documentation. Most people get in touch after something specific: a summer traffic spike that exposed how fragile the hosting setup actually was, a plugin that quietly broke after a server update, or simply the realisation nobody currently understands how the site works. From there it's either a fixed-scope project or an ongoing arrangement, priced before anything begins.
Common questions Plymouth clients ask:
Is it an issue that you're not in Plymouth?
Not really. The work is entirely remote, code review through to going live, and it holds up fine. If a call or an in-person chat is genuinely useful at any point, Plymouth isn't difficult to reach.
Our traffic is heavily seasonal, does that affect your recommendations?
Yes. A site that coasts through winter and gets hammered every summer needs its hosting and its slower pages checked well before the season starts, not after something's already gone wrong on a Saturday in August.
The previous developer isn't around anymore, can you still take this on?
Yes, this is a common situation. Working out what's actually installed, what's custom, and what's simply been forgotten about takes a proper look at the code rather than a guess.
How old can an ExpressionEngine site get before it's a genuine risk?
Older than most people think. The core software itself tends to keep working, it's the unmaintained add-ons riding on top of it that eventually cause problems.
What's the difference between a one-off project and a retainer?
A project is scoped and priced upfront for a specific piece of work. A retainer is ongoing monthly support with priority response, useful if you'd rather have someone watching the site than call someone new every time something breaks.
How do we get started?
A short conversation about the site's current state and what's prompting the enquiry. That's enough to give you an honest view of what's actually involved.
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.
