Craft CMS enquiries out of Luton tend to arrive in one of two states: an install left running unattended, or one that's stopped working with nobody around to explain it.
Karl's the only person who works on it, ever. He's specialised in Craft CMS and ExpressionEngine since 2007. No wider team, no account manager.
He checks the install properly before saying what it needs. That's usually a fix, a version upgrade, or an ongoing retainer.
What replaced Vauxhall as the thing Luton's economy actually runs on?
The airport, largely, anchoring a genuinely sizeable aviation and travel cluster, plus logistics firms making good use of the M1 and the airport's own freight capacity. Craft turns up regularly across that mix, often installed back when a business was considerably smaller and simply never revisited as things grew around it.
Karl picks up Luton sites wherever that's left them, a compatibility audit ahead of an upgrade, a full takeover of a codebase nobody currently understands, or ongoing support for firms who'd rather have someone actually watching things. The work starts with the site itself, never a description of it.
The install this usually turns out to be:
Something handling genuinely time-sensitive information, where a delay updating it is a real problem, not a minor annoyance. A logistics operation whose site connects into freight or scheduling systems set up years back and never written down anywhere. Bookings running through Stripe, or customer records synced to Salesforce, common enough here that they need the same ongoing care as the CMS itself. Left behind by a previous agency or freelancer who's simply not contactable anymore. And several major versions behind, where the real work in an upgrade is checking every plugin individually.
Common questions Luton clients ask:
How does this actually start?
With Karl reviewing the actual templates and plugins in use, since Luton handovers rarely arrive with documentation worth trusting. What usually prompts the first call is something concrete: time-sensitive content that failed to update correctly, a plugin that broke after a routine server change, or a decision the site's been running unsupported for too long.
Does it actually matter that support isn't local to Luton?
Not in any meaningful way. Everything runs remotely and holds up reliably. If a meeting in person's ever genuinely useful, Luton's easy enough to reach.
The developer who built this can't be reached, does that rule anything out?
Not at all, it comes up regularly. Working out what's genuinely custom against a modified plugin is step one, and that comes from reading the code properly, not assuming.
Honestly, how much risk does an old Craft version carry?
Less than most assume, taken alone. The core software tends to keep functioning fine. It's whatever plugins have been left unmaintained on top of it that eventually cause the actual problems.
What's the tangible benefit of ongoing support here?
Priority response the moment something breaks, proactive checks instead of silence between issues, and a developer who already knows your setup rather than starting from nothing every time.
Roughly what will this cost?
Entirely down to scope. 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.
