Lincoln's ExpressionEngine enquiries typically boil down to one of two things: a site running quietly out of date, or one that's stopped behaving properly with the previous developer unreachable.
Karl's the one who takes it on, always has. He's worked in ExpressionEngine and Craft CMS only, since founding Expression 37 in 2007. You speak to him directly, never an account manager.
He goes through the build properly before recommending anything. What that shows decides whether it's a fix, an upgrade, or an ongoing retainer.
Where we typically come in:
- Agricultural and agri-tech businesses with dealer catalogues or trade information built on ExpressionEngine.
- Engineering firms whose site was built for a specific technical purpose years ago and left running since.
- University departments and research groups needing content structures that hold up to genuine scrutiny.
- Businesses with Stripe handling trade or equipment sales through the site, needing someone across both the CMS and the payment flow.
- Teams that inherited a site rather than commissioned it and want it properly explained before taking responsibility for it.
How a typical engagement starts:
Lincoln enquiries often come from someone new to a role discovering a site nobody around them can explain, or a specific issue: a dealer catalogue with wrong pricing, a security scan flagging an outdated install. Karl audits the actual codebase before quoting, and a fair number of those audits turn into ongoing monthly support.
Common questions Lincoln clients ask:
Does it matter that you're not based in Lincoln?
Not in practice, no. Support runs remotely from code review through to deployment, and Lincoln's reachable enough for the rare occasion a visit genuinely helps.
Nobody currently here knows how the site was actually built, is that unusual?
Not for Lincoln, no. A lot of sites here were built years ago by someone no longer around, and mapping what's genuinely there is a routine first step.
Our content needs to hold up to real academic or technical scrutiny, does that change your approach?
Yes, structure and accuracy get treated with extra care where content carries genuine institutional or technical weight, rather than being handled like a standard marketing page.
How out of date can our EE install be before it's a real problem?
Security patching matters most regardless of version. Beyond that, older installs increasingly struggle to find maintained add-ons, which becomes the real issue at upgrade time.
Do you handle the payment side of our dealer or trade site too?
Yes, it's usually built directly into the templates, so proper support covers both the CMS and the payment flow together.
What's the pricing structure?
Fixed cost for scoped project work, monthly retainer for ongoing cover, agreed before anything starts.
What's a sensible first step?
A short call about the site, its EE version, and what's prompting you to look into support 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.
