Edited in WordPress. Served as finished pages.
Your team works in the admin they already know. What visitors load is a set of pre-built files — fast, hard to attack, and cheap to host.
Less to maintain, less to defend, and no live server working on every single request. The trade is that the site changes in deliberate releases rather than constantly.
When static is right. When it is not.
It is an architecture, not a trend, and it genuinely does not suit every site. Here is the line, so you can rule it out in thirty seconds if it is not you.
- Load time shows up in your numbers
- You want dramatically less to patch and monitor
- The site changes in considered releases
- Your content is the same for every visitor
- You need live dashboards or user accounts
- Content changes per visitor or per login
- You run complex, real-time commerce
- Layouts get rearranged most weeks
Where it does not fit, we will say so and quote you the custom WordPress build instead. Talking someone out of the cheaper option is not a sales technique we have.
Who is publishing?
For brands whose layouts stay put and who would rather we handled publishing and content changes. The fastest route to launch, and the tightest control over how it looks.
For marketing teams publishing often who need full control without calling us. Structured WordPress editing, several editors, and a documented handover you can take elsewhere.
The bar is roughly how much of the publishing sits with your team. Visitors cannot tell the difference — this choice is about how you want to work.
The same standard, delivered differently.
- Pages served without running code or hitting a database for every visitor.
- Visitors never touch the content system, so the usual attack surface is not there.
- Simple hosting, lower running costs and fewer parts to understand later.
- The same strategy, design and accessibility work as any other build — only the delivery changes.
Useful answers, upfront.
Can we still edit the site ourselves?
Yes. Team-led builds keep a structured WordPress editing experience, and publishing those changes to the live site is one automated step.
Does publishing take longer?
There is a publish step, but it is automated. Small sites update in seconds; a large content library takes a little longer.
What happens to forms and search?
They run through focused, secure services rather than a public WordPress install. We choose the right ones during discovery.
How long, and what does it cost?
Two to four weeks for a focused site with settled brand and content; four to seven where your team is publishing, there are more templates, or a look is being designed alongside. Usually below a custom WordPress build — but we quote after reading the brief, because the content model decides the real scope, not the word ‘static’.
Tell us about the build.
We will tell you honestly whether static fits, which editing model makes sense, and what the project would involve.
Start a project