Most Craft CMS enquiries from Slough involve an install in one of two states: stable but ignored, or genuinely broken with whoever built it long gone.
Karl handles it personally, start to finish. Craft CMS and ExpressionEngine are the only platforms Expression 37's touched since 2007. No wider team, no account manager.
The install gets a proper review before anything's quoted. That's usually a fix, a version upgrade, or an ongoing retainer.
Where we typically come in:
- Logistics and distribution operations running order or dispatch systems on Craft that genuinely can't tolerate unplanned downtime.
- Dealer and supplier portals built for one specific internal process years ago, now poorly understood by current staff.
- Sites tied into wider Heathrow-adjacent supply chains, where business-hours uptime has consequences beyond the site itself.
- Businesses running Stripe or custom order logic through Craft Commerce, an area that breaks more often than people expect.
- Teams who want reliability, not a redesign pitch attached to every support ticket.
How a typical engagement starts:
The trigger is usually operational: a dealer portal that's stopped syncing stock, a Composer conflict blocking a needed patch, or simply nobody left who understands how the original build works. Karl reviews the live install before quoting anything, and these functional, business-critical sites tend to move onto a steady monthly retainer rather than staying one-off.
Common questions Slough clients ask:
Our site is internal-facing, not customer-facing, does that change your approach?
It shifts priorities rather than process, uptime and quiet reliability matter more here than visual polish, which is exactly what internal portals and dispatch systems actually need.
We don't have anyone in-house who understands the build anymore, is that unusual?
Not at all, it's the normal starting point. Mapping what's genuinely custom against what's standard plugin functionality comes first, before any change is made.
The site handles live stock and dispatch data, how carefully is that treated?
Very carefully. Anything feeding operational data gets tested thoroughly before it reaches production, since a broken sync causes problems well past the website itself.
How far behind on Craft is genuinely risky?
Security is the immediate concern regardless of version. After that, older installs tend to run into plugins that have stopped being maintained, which is the real blocker come upgrade time.
Is order processing through Craft Commerce something you support directly?
Yes, it's usually built right into the templates rather than existing as a separate system, so it needs the same attention as the rest of the site.
How do you price this kind of work?
Fixed cost for defined project work, monthly retainer for ongoing cover, agreed before anything starts either way.
What's a good first step?
A short call about what the site actually handles day to day, its current Craft version, and what's prompting the enquiry now.
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.
