Craft CMS enquiries from Edinburgh tend to arrive in one of two states: an install that's ticking along neglected, or one that's genuinely broken while whoever built it is unreachable.
Karl handles every one of these personally. Craft CMS and ExpressionEngine are the only platforms Expression 37's ever worked in, since 2007. There's no handoff to anyone else.
Before he'll quote anything, the install gets a proper review. From there it's a fix, an upgrade, or an ongoing retainer, depending on what it needs.
Where we typically come in:
- Financial and legal sites where content structure matters, Craft's field and entry type system tends to get used properly here, which makes it worth maintaining properly too.
- Installs orphaned by an agency exit or rebrand, live but with nobody accountable for keeping them current.
- Festival and event booking systems that need to survive a short, intense traffic spike once a year without falling over.
- Sites pulling lead or enquiry data into Salesforce or HubSpot, where the integration usually breaks before the CMS does.
- Organisations who want direct access to whoever's actually doing the work, rather than a layer of account management in between.
How a typical engagement starts:
Enquiries usually follow a specific event: a Composer conflict blocking a security patch, a booking form buckling under festival-week load, or a new hire discovering nobody can explain a chunk of custom Twig logic. Karl reviews the install and its dependencies directly before quoting, and a good share of that initial work turns into an ongoing retainer once the immediate issue is resolved.
Common questions Edinburgh clients ask:
Do you need to be in Edinburgh to support us properly?
No, everything happens remotely by default, template work, deployments, server-side fixes. Edinburgh's within easy reach if an in-person meeting is ever genuinely useful, but it's rarely necessary in practice.
Can you pick up support after our agency has moved on?
That's a common starting point. Working out what's custom-built versus a standard plugin, and documenting it properly, comes first, before anything else changes.
Festival month is our busiest period by far, does that change how you'd approach our site?
It shifts the priority list in the run-up: booking flow testing, hosting headroom, and a support arrangement that responds fast if something breaks matter more than usual in the weeks before August.
What if we're stuck several major Craft versions behind?
Not unusual, particularly for sites that were set up early and left alone. The upgrade path itself is well trodden, the real work is checking plugin compatibility along the way.
We handle sensitive client and financial data, does that affect how you work?
It's factored in from the outset rather than bolted on afterwards, anything touching personal or financial data gets treated accordingly from the first review.
What's the pricing structure?
A fixed quote for scoped project work, a monthly retainer for anything ongoing, agreed before work starts either way.
How should we get started?
A short call about your current Craft version, what's built into the site, and what's actually prompting the enquiry. That's enough for an honest first assessment.
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.
