A typical Exeter enquiry about ExpressionEngine support involves a site in one of two states: fine but neglected for years, or genuinely broken with the previous developer no longer answering.
Karl's the one who picks it up. Expression 37 has stuck to ExpressionEngine and Craft CMS only, since Karl founded it in 2007. Every job's handled by him directly, not passed along.
He works through the site properly before recommending anything. Usually that's a fix, a version upgrade, or bringing it on as an ongoing retainer.
Where we typically come in:
- Tourism and visitor-facing businesses whose site sees genuine seasonal swings, where a slow booking flow during peak season has a direct commercial cost.
- Financial and insurance firms where content accuracy and consistent uptime matter more than most, not just as a nice-to-have.
- Businesses running Salesforce alongside the CMS, needing someone who understands both halves of that connection.
- Sites several major ExpressionEngine versions behind, where an honest upgrade means checking every add-on's compatibility individually.
How a typical engagement starts:
Nothing gets quoted until Karl's been through the templates and add-ons directly, since these handovers rarely come with anything resembling documentation. Most people get in touch after something concrete: a booking system that struggled during a peak weekend, a security notice nobody's acted on, or a decision the site can't keep running unsupervised. From there it's a fixed-scope project or an ongoing arrangement, agreed before work starts.
Common questions Exeter clients ask:
Does it matter that you're not based in Exeter?
It doesn't affect the work. Deployment, code review, everything happens remotely, and Exeter's rail connections make an occasional visit painless if one's ever actually needed.
Our traffic swings hard by season, is that unusual?
Not here. It's the norm for anything tourism-adjacent. It needs stable hosting and a properly tested booking flow well before the season starts, not a scramble once it's underway.
Can you take over a site the previous developer's walked away from?
That's a normal starting point, not an unusual one. The first job is always working out what's custom-built versus an off-the-shelf add-on that's been modified, and that only comes from reading the code.
Is an old ExpressionEngine version something to worry about?
On its own, rarely. What actually goes wrong is almost always an add-on left to rot, not the core platform itself, so that's the first thing an audit looks at.
Do you handle the Salesforce integration too, or just the CMS?
It's covered as part of the same work. Splitting the CMS from an integration wired straight into its templates rarely reflects how the two actually function together.
What's the likely cost?
A fixed price for defined work like an audit or upgrade, agreed before anything starts. Ongoing support is billed monthly at a rate set in advance.
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.
