Bristol's Craft CMS enquiries tend to split two ways: an install that's stable but neglected, or one that's stopped working with nobody left to explain it.
Karl picks these up personally. Craft CMS and ExpressionEngine are the only two platforms Expression 37's touched since 2007. It's him on every job, not a wider team.
He reads the actual codebase before quoting anything. Most first engagements, once resolved, turn into an ongoing monthly retainer.
The kind of install this usually is:
A Bristol business where the website genuinely drives revenue, so downtime isn't a minor inconvenience. Often the previous agency has moved the client through account managers who never understood the actual build. Composer dependencies and plugins are frequently several major versions behind, sometimes with Stripe, Salesforce, or HubSpot wired in by whoever set it up originally, now long gone. What most of these clients want is one developer who actually understands their system, not a fresh face every time something needs doing.
What changes once Karl's involved:
Most first conversations start with something concrete: an upgrade that's been avoided for too long, an integration that's quietly broken, or a site left without proper support after an agency relationship fell apart. The goal from there is simple, to become the person who knows a Bristol client's Craft install better than anyone, so expert support is always one phone call away.
Common questions from Bristol clients:
Is remote-only support actually workable for a Bristol business?
Yes, consistently. For a specialist platform like Craft, direct access to the developer doing the work tends to beat going through a local agency, and on-site visits are almost never actually required.
Can an existing build from a previous developer be taken over?
Yes, this is one of the most typical starting points. Heavily customised templates and unusual plugin choices are handled regularly, always after properly understanding what's already there.
What if the install hasn't been touched in years?
Not unusual at all. Upgrading covers everything from auditing plugin compatibility to sorting Composer conflicts, with proper testing before anything goes live.
Do you maintain Stripe, Salesforce, or HubSpot connections too?
Yes, that's core to the work. Whether it's a payment gateway, a CRM sync, or a marketing platform link, it's supported alongside the Craft codebase, not treated as a separate job.
How is the cost worked out?
Defined work like an audit or upgrade is a fixed project price. Ongoing support is a monthly retainer. Either way, the number is settled before work starts.
What's the response if something breaks urgently?
Retainer clients get priority handling. Without one, critical issues are still usually dealt with quickly, but that consistent priority is specifically what a retainer buys.
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.
