Case studies, websites, tenders and everyday content. Clear words that sound like your business and show what it can actually do, written by someone who asks.
Most construction firms we meet are sitting on a quiet pile of evidence — jobs delivered on time, problems solved on site, clients who would come back tomorrow. None of it is on the website. None of it is on LinkedIn. The case studies are two years out of date. The about page reads like a planning application.
We write the content that closes that gap. Case studies that lead with the problem and the result, not the photo carousel. Web copy that says what you do in one sentence. Tender narrative that sounds like the team who will deliver the job, not a marketing department. And social posts that actually look like they came from a contractor — because they did.
Written. Case studies, web copy, tenders, blogs. Case studies built around the problem you solved, not the photo gallery. Web pages that say what you do, who you do it for and why, in a sentence each. Tender narrative that sounds like the people who will deliver the job. Sector explainers and blog posts that earn slow, compounding search traffic over years.
Social. Posts that don’t sound corporate. LinkedIn and Instagram posts written from real jobs, not stock templates. A monthly content calendar built around what is actually happening on site that month. Captions for project photos. Case studies repurposed into multi-post breakdowns. The aim is steady visibility for the right audience, not viral.
Voice. Something you can hand to anyone. Every engagement starts with a short written tone-of-voice and audience guide. Two pages, plain English — so whoever writes for the firm next, whether that’s us, your office manager or a future agency, sounds like the same business.
The process is mostly listening, then writing. Two or three calls with the people who do the work — the estimator, the project manager, the founder, not the marketing person — because most of the good language already exists in the team, in the way they describe a job over a pint. Then the two-page voice document, which you sign off before anything else follows. Then first drafts in days rather than weeks, in plain prose, ready to mark up by reply: “this paragraph is too long”, “we don’t say infrastructure-led, we say civils”. Then it ships — onto the site, out on socials on a schedule, or handed to your bid team.
The useful details are usually already there: in the team, on the job and in the problems you solved. Bring them into the story.
The challenge. Your contribution. What changed.
Clarity before cleverness.Shape web pages and project stories around what the reader needs to know. Be specific about the work, and clear about the result.
The job, the people and the thinking behind it.
Useful, regular, recognisably you.Build posts and updates around what is happening in the business. Reuse the strongest project stories without making every post sound the same.
Relevant experience. A considered method. Clear evidence.
Write like the people doing the work.Capability narrative, project examples and a practical tone-of-voice guide. Clear language your team can keep using.
A conversation with the people who do the work is often the most useful starting point.
How we work together ↗Audience, tone and useful examples so the writing sounds like the same business.
Clear prose, shared early. Feedback in plain English and an agreed review process.
Website copy, project stories, tender sections or social posts, shaped for the agreed channel.
Content is a newer service line. The site and field notes show the writing approach; dedicated client stories will follow as the work develops.
A common starting point is a single rewrite: the homepage, the services page and two or three case studies. Three weeks of work, a noticeable lift in how the firm reads online, and a written tone-of-voice guide anyone on the team can keep extending. No retainer required.
For firms that want steady output, a monthly engagement typically produces one new case study, two longer-form pieces — sector explainers, opinion posts, tender-supporting essays — and a calendar of social posts built around what the business is actually doing that month. Slow, compounding, on-brand.
Where it matters most: the prose sections of a tender response. Capability narrative, project examples, social value statements, approach to delivery. Written like the team who will deliver it, not the bid template.
Content creation is a newer service line in 2026, so client case studies will arrive on the work page over the year. In the meantime, the writing you are reading now — this page, the rest of the site, the field notes — is the same hand. If the voice fits, the rest will.
Start with a homepage that no longer fits, a project worth documenting or a tender section that needs a clearer explanation.
Talk through a starting point ↗
Read the writing ↗Typical starter project, depending on the content and review process.
A one-off piece of work or a regular publishing rhythm.
A consistent approach your team can carry forward.
Send us the page, the project or the idea that deserves better words.