A lot of what comes in from Derby is the same underlying issue: an ExpressionEngine site that's kept running for years without anyone actually checking on it, until something finally gives.
That's Karl's job, and only Karl's. Expression 37's been ExpressionEngine and Craft CMS exclusively since 2007. There's no wider team or account manager in between.
He works through the codebase properly before saying what it needs. That usually comes down to a fix, a version upgrade, or bringing the site on as a retainer.
Where this tends to matter most:
Engineering and manufacturing firms whose site holds a large, growing library of technical documents or product data that needs to stay genuinely searchable, not just present. Businesses whose previous developer or agency is no longer contactable, leaving an install that works today but that nobody feels confident touching. Sites running Stripe, Salesforce, or HubSpot integrations set up years ago by someone no longer around to explain them. And installs old enough that an upgrade means checking every add-on individually rather than a routine update.
How engagements usually start:
Before quoting anything, Karl reviews the templates, the add-ons, and however the content structure has grown over time, since Derby sites in this category often carry years of accumulated content that was never properly organised. Most clients get in touch after something specific prompts it: search results that stopped making sense, a security notice about an outdated add-on, or a decision that the site needs proper ownership again after drifting for too long. From there it's a scoped project or a retainer, priced upfront.
Common questions Derby clients tend to ask:
Does it matter that you're not based in Derby?
Not for the work itself. Code review, deployment, testing, all handled remotely and it works well in practice. Derby is close enough that an in-person conversation is never a real barrier when one's genuinely useful.
Our site has years of accumulated technical documents, does that complicate things?
It changes what needs attention rather than complicating it. A large content library needs a proper structure and working search, so people can find the specific document or spec sheet they need, rather than an archive that's grown faster than anyone's kept it organised.
Can you take over a site built by a developer no longer around?
Yes, regularly. The first job is separating what's genuinely custom from a modified add-on, and that only comes from actually reading the code, not guessing from the front end.
How old can an ExpressionEngine install get before it's genuinely risky?
Longer than most expect, and that's usually fine on its own. The core rarely breaks by itself. Problems tend to trace back to add-ons that stopped being updated long before anyone noticed.
What does ongoing support include?
Quicker response on anything urgent, periodic reviews so problems get caught before they're visible to visitors, and a developer already familiar with the site rather than starting from nothing.
What will this cost?
Comes down to scope. A one-off job is priced as a fixed sum. Ongoing support runs as a monthly retainer. You'll know the number before anything is agreed.
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.
