Darlington enquiries about ExpressionEngine support usually mean one of two things: a site that's stable but hasn't been looked at properly in years, or one that's already broken with nobody answering the phone about it.
Karl deals with all of it personally. Expression 37 has worked in ExpressionEngine and Craft CMS only, since Karl set the company up in 2007. Every job stays with him, not a handed-off account manager.
Nothing gets quoted until Karl's gone through the actual build. From there it's typically a fix, an upgrade, or a retainer, depending on what the site needs.
Where we typically come in:
- Manufacturers with trade or export-facing sites where product data and pricing information needs to stay accurate and available.
- Organisations with public sector or accessibility obligations, where content structure and compliance matter as much as appearance.
- Long-established local businesses on older EE installs that predate anyone currently working there.
- Businesses running Stripe for trade or retail payments directly through ExpressionEngine, needing someone who understands both the CMS and the integration.
- Teams who'd rather deal with one developer than a rotating account management team at an external agency.
How a typical engagement starts:
Darlington enquiries often follow a specific prompt: an accessibility audit flagging issues on a public-facing site, a trade customer reporting outdated pricing information, or simply a new hire discovering nobody understands how the site actually works. Karl reviews the real codebase before quoting, and a fair number of those reviews turn into a standing monthly retainer.
Common questions Darlington clients ask:
Do you need to be based in Darlington for this to work properly?
No, support happens remotely from start to finish, code changes, deployments, ongoing fixes. Darlington's reachable enough for the rare occasion an in-person meeting genuinely helps.
We have accessibility requirements to meet, does that change how you'd approach the site?
Yes, content structure, markup, and testing get handled with that specifically in mind, rather than treated as a separate concern bolted on afterwards.
Nobody currently on staff built or understands the site, is that a common starting point?
Very common, particularly for long-established businesses. The first step is properly mapping what's actually there before anything gets changed.
How out of date can our EE install be before it's a genuine problem?
Security patching matters most regardless of version. Beyond that, older installs increasingly struggle to find maintained add-ons, which is usually the bigger issue once an upgrade's actually needed.
Do you support the payment integration too, or just the site itself?
Both. Payment processing is usually built directly into the ExpressionEngine templates, so treating it separately from the CMS tends to miss where issues actually come from.
What's the pricing structure?
Fixed cost for scoped project work, monthly retainer for anything ongoing. Agreed before work starts either way.
What should the first conversation cover?
The current site, its EE version, and whatever's prompting the enquiry now. That's enough for an honest first view.
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.
