Introduction

Lanark’s website no longer matched the depth and reliability of their work. Buyers struggled to see what Lanark actually delivers across planning, procurement, warehousing, transport and customer service. Content was thin, proof was missing, and updates took too much effort. Internally, adding pages or publishing proof meant workarounds instead of steady growth.

Operating in a high-stakes environment, Lanark needs clarity and trust at every step of the buyer journey. The previous site didn’t support that. Key domains were buried, messages overlapped, and there was no clear path from interest to action.

Our role

Strategy, UX, UI, Webflow build, CMS setup, SEO basics, and training. Scope expanded along the way, so extra page types shipped before launch. The goal stayed the same: clear offers, real proof, and a platform the team can run without friction.

Approach

Structure first. Services were mapped into clear “Domains,” with paths for different readers: quick scans for first-time visitors, deeper detail for evaluators. Content quality led the way, case studies and useful insights over filler. Once the model held, the system moved into a calm, readable design that scales without rework.

The solution

UX & structure

The site centres on Lanark’s domains and an end-to-end story that ties them together. Crosslinks connect domains to related cases and insights, so buyers can move from context to proof in a few clicks. CTA's stay consistent and clear.

Design system

A compact Figma library—headers, cards, proof modules, CTA sections, content blocks—mirrors 1:1 in Webflow components. New pages assemble from these parts, keeping speed high and design drift low.

Webflow development

Component-based build with a clean class system and tuned responsiveness across breakpoints. As scope grew, new page types reused existing components. No one-offs. Maintainable, predictable, and ready for future sections.

CMS & content management

Webflow CMS powers domains/services, case studies, insights, team and reviews. Collections are interlinked: domain pages surface relevant cases and posts automatically; cases point back to the domain they prove. Editors get clear fields and inline guidance, so publishing is quick, safe and consistent.

SEO & performance

Logical URLs, semantic headings and structured meta fields. Images and assets optimised. Redirects aligned where needed. The foundation is clean, fast and ready for targeted landing pages as content scales.

Analytics, tracking & flows

Tracking implemented across key journeys. Forms routed to the right owners with confirmations in place. The setup supports ongoing measurement without extra dev work.

Launch, training & support

Training focused on the essentials editors need week to week. We covered how to create a new case and connect it to the right domain/services, how to use component blocks to assemble new pages or extend existing ones, and how to set the basics for SEO (titles, descriptions, alt text).

Results & impact

The site now matches the work Lanark delivers. Buyers can see what Lanark does, and real proof to back it up. The team owns the platform and ships content without waiting on a developer. As the library of cases and insights grows, we expect the compounding effects: clearer story, more trust, smoother evaluations, and a site that supports growth instead of slowing it down.