CONSTRUCTION AND REAL ESTATE
WEB DESIGN.
Construction company web design, real estate sites and the sales software around them, for firms whose work is visual, technical and hard to explain in a deck. Built so marketing publishes without a developer, and so a demo still runs where there is no signal.
THE WORK IS VISUAL.
THE SITE RARELY IS.
Point clouds, captures and models, presented as bullet points.
-
Years of disorderly growth
The architecture stopped matching how the company sells three reorganisations ago, and every rebuild risks the rankings that bring most of the enquiries.
-
Marketing waits on development
Services, locations, projects and case studies all need a technical ticket to publish, so the site is always a quarter behind the business.
-
The demo happens where there is no WiFi
On a stand or a jobsite, anything that needs the internet fails exactly when it matters most.
WHAT A CONSTRUCTION BUILD
ACTUALLY NEEDS.
A site the team runs alone
Services, industries, locations, projects, resources and events each get their own content type, template and fields, plus a component library the team assembles new pages from with no design or development step.
Multi location and franchise sites
A location is an entry with fields, not a page somebody maintains. Everywhere it should show up, a map, a finder, a service page, it shows up on its own. We have run this with 93 franchise locations on one site.
Migrations that keep the rankings
Old URLs mapped against new, redirects shipped with the site, metadata and semantic structure rebuilt to carry the authority across. The archive comes too, back as far as it goes.
Sales tools that work offline
Installable desktop apps holding explorable 3D models, point clouds and deviation analysis, updating themselves when there is a connection and working fully when there is not, contact capture included.
THE SAME TEAM,
WHICHEVER ONE YOU NEED.
FROM SITEMAP
TO HANDOVER.
Five steps, ending with the keys in your team's hands.
- 01 Architecture How the company sells today, turned into a structure.
- 02 System Components and content types, designed against the brand.
- 03 Build Templates, fields and relationships, all editable.
- 04 Migrate URLs, redirects, archive and measurement, planned in advance.
- 05 Handover Your team publishing without us, which is the point.
THE TOOLS
BEHIND THE BUILD.
Built on what the systems in your sector can actually talk to.
-
-
-
-
-
-
-
-
-
-
- Core Web Vitals
WHAT CONSTRUCTION CLIENTS
ASK FIRST.
The questions that come up on almost every first call.
It moves with how much of the company has to live on the site: the services, the locations, the project archive and whether any of it has to be migrated. A single-office contractor and a firm with 93 locations are not the same build. We scope first and quote a fixed number, which is a slower answer than a price list and a more useful one.
Yes, and it is the part we plan first. Old URLs are mapped against new ones before anything is designed, the redirects ship with the site and not after it, and the semantic structure is rebuilt to carry the authority across. On the last one of these the site kept every ranking it started with and search clicks were above average the day after the cutover.
That is the deliverable. Every entity the business publishes gets its own content type and editable fields, and pages are assembled from a component library. On the last two builds that meant 17 content types and 94 reusable components, and publishing a service or a location became a job of minutes.
They need to be content, not pages. A location is an entry with fields, and everywhere it should appear, a map, a finder, a service page, it appears automatically. We have run this with 93 franchise locations on one site.
Yes. We ship installable desktop apps for Mac and Windows that hold the models, point clouds and video documentation locally, so the demo runs with no connection at all. They update themselves in the background whenever there is one, and the contact form captures offline and syncs on reconnect.
It has to, and we check it instead of assuming it. On the last rebuild six forms kept posting to the same Account Engagement handlers, with tracking and analytics carried across on the same identifiers so the reporting history did not restart at launch.
Still have a question? Let's talk
WE WORK IN
OTHER ROOMS TOO.
The pattern changes by sector. The standard does not.
View all industries
TELL US WHAT
YOU ARE BUILDING.
We will come back with a structure your own team can publish into.