A Luton enquiry about ExpressionEngine support usually looks like one of two things: a site that's stable but overdue for attention, or one that's actively broken with the agency behind it long gone.
Karl deals with it personally, every time. Expression 37's only ever worked in ExpressionEngine and Craft CMS, since Karl started it in 2007. It's him on every job, not a team.
Nothing gets recommended before the build's been properly reviewed. Depending on what turns up, that's a fix, an upgrade, or an ongoing retainer.
Where this tends to matter:
Travel and aviation-related businesses whose site needs to handle time-sensitive information reliably, where a delay in updating something is a genuine problem, not a minor inconvenience. Logistics firms whose site connects into freight or scheduling systems set up years ago and never documented. Sites left behind by a previous agency or freelancer no longer contactable. And ExpressionEngine installs several major versions old, where the real work in an upgrade is checking every add-on individually. Bookings processed through Stripe, or customer data synced to Salesforce, are common enough here that they need the same ongoing attention as the CMS itself.
How this tends to start:
Nothing gets quoted until Karl's actually reviewed the templates and add-ons in use, since Luton handovers rarely arrive with documentation worth trusting. Most people reach out after something specific: time-sensitive content that's failed to update correctly, a plugin that broke after a routine server change, or a decision that the site's been running unsupported for too long. From there it's a defined project or a retainer, priced before work starts.
Common questions Luton clients ask:
Does it matter that you're not based in Luton?
Not really. The work happens remotely from start to finish, and it's reliable. If an in-person meeting is genuinely useful at some point, Luton's easy enough to reach.
Our site needs to reflect time-sensitive information accurately, is that a common issue?
Common enough given the travel sector here. It needs a reliable update mechanism and proper testing, since a delay or an error in something time-sensitive has real consequences beyond a cosmetic one.
Can you take over a site the original developer's no longer around for?
Yes, regularly. Working out what's genuinely custom versus a modified add-on is always step one, and that needs an actual read of the code, not an assumption.
How risky is an old ExpressionEngine version, honestly?
Less risky than people assume, in isolation. The core software tends to keep working. It's whatever add-ons have been left unmaintained on top of it that eventually cause problems.
What do we actually get with ongoing support?
Priority response when something breaks, proactive checks instead of silence between issues, and a developer who already knows your setup rather than starting from nothing.
What's the cost likely to be?
Depends on scope entirely. A one-off audit or fix is a fixed price. Ongoing support runs monthly. Either way you'll know the figure before agreeing to anything.
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.
