Southampton's Craft CMS enquiries generally split two ways: an install running fine but neglected, or one that's stopped working with nobody left to explain it.
Karl deals with it directly, every time. Craft CMS and ExpressionEngine are the only two platforms Expression 37's worked in, since 2007. It's him on every job, not a team.
Before quoting anything, he checks the install itself. Depending on what's found, that's a fix, an upgrade, or an ongoing retainer.
Why does a Southampton booking site need different treatment to most?
Because of the pattern: quiet for weeks, then hit hard the moment a cruise line announces its next season's sailings. That calm-then-spike rhythm runs right through Southampton's port, maritime, and cruise-linked businesses, and it's exactly the kind of load an under-maintained Craft install handles badly. A site that's coasted fine all year can fall over in the one week it actually mattered.
Expression 37 works with Southampton businesses to get ahead of that pattern rather than react to it: auditing what's running now, fixing anything fragile well before the next peak, and taking on ongoing support for firms who'd rather not discover a problem live. Karl reviews the actual templates and plugins directly before quoting.
Where this tends to matter:
- Booking or reservation systems on Craft that need to survive a genuine seasonal spike, not just handle average traffic comfortably.
- Installs handed over from a developer who's since stopped doing Craft work, leaving support in name only.
- Setups several major versions behind, where an upgrade means auditing every plugin's compatibility and untangling Composer conflicts, not a routine bump.
- Sites with Stripe, Salesforce, or HubSpot connections wired in by someone no longer around to explain how.
Common questions Southampton clients ask:
What actually happens before you'll quote anything?
Karl goes through the templates, plugins, and any custom logic first, since Southampton handovers rarely come with documentation worth relying on. Most people get in touch after something specific: a booking flow that buckled under demand, a plugin that broke after a routine update, or a decision the site can't run unsupervised through another peak season.
Does it matter that you're not local to Southampton?
Not in practice. Everything happens remotely and works reliably. Southampton's close enough that an in-person meeting is never a real obstacle if one's genuinely useful.
Given how seasonal our traffic is, what would you actually recommend?
Load testing done well ahead of the peak, not discovered live. Hosting that can genuinely absorb the spike. And a support arrangement where someone actually answers if something breaks mid-peak, rather than a ticket queue.
Can you take on a Craft build from a developer who's disappeared?
Regularly, yes. The first job is separating what's genuinely custom from a modified plugin, which only comes from actually reading the code.
Is there an age where a Craft install becomes a real risk?
Less than people expect, and it varies more than a simple rule would suggest. What was bolted onto the install, and whether it's been kept current, matters far more than the version number by itself.
What's the deal with pricing?
Standalone work is a fixed project price. An ongoing arrangement runs 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.
