A Southampton enquiry about ExpressionEngine support is usually one of two things: a site that's stable but overdue for attention, or one that's genuinely broken with the previous developer unresponsive.
Karl's who takes it on, on his own. He's specialised in ExpressionEngine and Craft CMS since starting Expression 37 in 2007. There's no account manager between you and him.
He works through the build first, always, before recommending anything. That's typically a fix, an upgrade, or an ongoing retainer.
Where this comes up most:
- Booking or reservation systems built on ExpressionEngine that need to survive a hard seasonal spike, not just average traffic.
- Sites handed over from an agency that's since stopped doing ExpressionEngine work, leaving support in name only.
- Installs several EE versions behind, where an upgrade means checking every add-on for compatibility rather than a routine update.
- Sites with Stripe, Salesforce, or HubSpot connections wired in by someone no longer around to explain how.
How engagements usually start:
Karl reads through the templates, add-ons, and any custom logic before quoting, since Southampton handovers rarely arrive with documentation worth trusting. Most clients get in touch after something specific happens: a booking flow that buckled under demand, an add-on that broke after a routine server update, or simply a decision that the site can't keep running unsupervised through another peak season. From there it's a scoped project or a retainer, priced upfront.
Common questions Southampton clients tend to ask:
Does it matter that you're not based in Southampton?
Not in practice. Everything, from code review to deployment, happens remotely, and it works well. Southampton is close enough that an in-person meeting is never a real obstacle if one's genuinely useful.
Our traffic is very seasonal, does that change what you'd recommend?
Yes, quite a bit. Sites with sharp seasonal peaks need load testing done in advance, not discovered live, along with hosting that can actually handle the spike and a support arrangement where someone answers if something breaks mid-peak.
Can you take over a site built by a developer who's no longer around?
Yes, regularly. The first step is always working out what's genuinely custom versus a modified add-on, which takes an actual read of the code rather than a guess from the front end.
How old can an ExpressionEngine install be before it's a real risk?
It varies more than people expect, some three-version-old sites are solid, some two-year-old ones are a mess. It comes down to what add-ons were bolted on and whether anyone's kept them current, not the EE version number by itself.
What's included in ongoing support?
Priority response when something breaks, proactive checks ahead of known busy periods, and a developer who already knows the site rather than starting from zero.
What will this cost?
Varies by scope. Standalone work carries a fixed project price. An ongoing arrangement is billed monthly at an agreed rate. Either way, you know the figure before saying yes.
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.
