Dundee's Craft CMS enquiries tend to split into two kinds: an install that's stable but untouched for years, or one that's genuinely gone wrong with nobody left to call.
Karl takes these on personally, always has. Expression 37's worked in nothing but Craft CMS and ExpressionEngine since 2007. You deal with him directly, not a team.
Before quoting anything, he checks the install itself. What comes out of that is a fix, a version upgrade, or an ongoing retainer.
Where we typically come in:
- Games studios and creative agencies whose Craft site was built fast during a launch push and hasn't been touched since.
- University-linked research groups and life sciences teams running content-heavy sites carrying real funding and publication detail.
- Installs left behind by a departed founder or developer, live and functioning but genuinely unexplained to anyone currently around.
- Organisations routing investor or enquiry contact through HubSpot connected directly to Craft, which needs looking after alongside the CMS itself.
- Small teams who want direct developer access, not a ticket queue that adds a layer of delay.
How a typical engagement starts:
The usual trigger is a new team member finding a Craft install nobody can explain, a security review flagging outdated plugins, or a HubSpot form that's stopped submitting without anyone noticing for a while. Karl reviews the actual codebase and Composer setup before quoting, and a good share of that first work becomes ongoing retainer support.
Common questions Dundee clients ask:
Is remote support genuinely enough for us?
Yes, it covers everything in practice, deployments, template work, ongoing fixes. Dundee's reachable enough for an in-person meeting on the rare occasion it's genuinely useful.
The person who originally built our site has left, can you take it on cold?
Often, and it's a familiar way for Dundee clients to reach us. Working out what's custom-built versus standard plugin functionality comes first, before anything else changes.
We're a small studio with no dedicated IT support, is that a problem?
Not remotely. A lot of clients here are exactly that, a capable small team without spare capacity to manage a CMS properly, which is exactly the gap this kind of support closes.
How far behind on Craft versions is genuinely risky?
Security matters most regardless of version number. Beyond that, older installs run into plugins that have stopped being maintained, which becomes the real problem at upgrade time.
We collect investor or funding enquiries through HubSpot, is that in scope?
Yes, that integration is usually built directly into Craft's templates rather than kept apart from the CMS, so it needs the same level of attention.
How is pricing worked out?
Fixed cost for defined project work, monthly retainer for ongoing cover, agreed upfront either way.
What's the right way to start?
A short call about what's currently built, your Craft version, and what's actually prompting the enquiry.
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.
