Heron runs inside Revit, Rhino, ArchiCAD and SketchUp, so the site had to read as an instrument rather than a brochure from the first frame.

The preloader replaces the progress bar with a drawing in progress. A red datum line moves up an architectural elevation carrying the percentage value, and the building is drawn in line by line as loading completes. Supporting information sits in the margins in the same register: live cursor coordinates, a project spec card covering type, founding year, focus and location, and a numbered system boot sequence.

Functionally it covers asset loading for the interactive hero, so the drag-to-reveal behaviour responds immediately once the page lands. Editorially it sets the frame before a single line of marketing copy appears.

A client shouldn’t have to learn Webflow just to publish their next case study.

On a recent build, I spent a lot of time on the CMS: setting up reusable blocks and the logic that lets the team update content without rebuilding pages.

The tricky part is deciding how much control to give them. Too little, and every update becomes a request. Too much, and they’re suddenly responsible for the layout.

I want them to open the CMS, know what to do, and get on with their day. There’s a fair amount of work behind making that feel simple.

The CMS thinking here is spot on: the best handoff is the one that gives a client confidence without exposing all the complexity underneath.