Built so your team can edit it, your next developer can understand it, and updating a plugin doesn't take the site down.
They produce very different things to live with afterwards, and the cheapest to build is rarely the cheapest to own.
Bought theme, configured, plugins added for anything missing
Pages assembled visually with a builder plugin
Built for your design, with proper editing fields behind it
WordPress for content only, front end built separately
The question that decides this isn't budget, it's who maintains the site next year. If that's a marketing person who needs to add a page, a builder or a custom theme with good fields is right. If it's a development team, headless becomes reasonable. Choosing the technically impressive option and handing it to someone who can't use it is the most common mistake here.
Writing something bespoke is more fun and it's usually the wrong answer. Every line we write is a line you'll pay to maintain.
Use what exists
Forms, SEO, caching, backups, security
Solved problems with mature, maintained plugins. Building your own version of any of these is a waste of your money.
Anything a well-known plugin does properly
It's been tested by more people than we ever could, and it gets fixed when WordPress changes underneath it.
Payments and bookings
Especially anything touching money or data protection. Custom code here creates liability that isn't worth carrying.
Worth building
Your specific content types
Properties, courses, case studies, team members. A plugin that does this generically will always fit your business awkwardly.
Connections to your other systems
Your CRM, your stock system, your booking software. These are specific to you and there's rarely something off the shelf.
Replacing five plugins with one small piece of code
When plugins were installed for one feature each, a hundred lines can often remove all of them and speed the site up.
A rule we apply to ourselves: if a plugin does ninety percent of what you need, use it and live with the ten percent. Building the perfect version costs more than the gap is worth, and you inherit it forever. We'll tell you when we think that's the case even though the custom build would bill more.
Six things that decide whether a site is pleasant or painful to own two years from now.
Each editable part of a page gets its own labelled field, so your team fills in a form rather than fighting a page of formatted text.
WhyNobody can accidentally break a layout by pasting from a document.
Customisations sit where a theme update can't overwrite them, which is basic practice and is skipped surprisingly often.
WhyOtherwise updating the theme silently undoes months of changes.
Scripts and styles load on the pages that use them rather than everywhere, which is where most WordPress speed problems come from.
WhyCaching hides weight, it doesn't remove it.
A staging copy of the site where changes and updates get tried before they reach anyone real.
WhyA plugin conflict on staging is an afternoon. On live it's a phone call.
Limited login attempts, proper user roles, no shared administrator accounts, and backups that have actually been restored once to prove they work.
WhyMost WordPress hacks come through an outdated plugin or a weak password.
What was customised, why, which plugins matter and which are optional. Handed over as a document rather than living in someone's head.
WhyIt's what lets you work with someone else later without starting over.
Not a lot, and not never. Sites that get abandoned for two years are the ones that end up needing a rebuild.
Regularly
WordPress, plugins, and theme. Tested on staging first, since the occasional update does break something.
Always
Stored somewhere other than the site itself, and restored at least once so you know they're real rather than assumed.
Occasionally
Plugins nobody uses, old drafts, unused images, and stray database entries left behind by removed plugins.
Watching
A plugin whose developer stops updating it becomes a security problem quietly. Worth checking rather than discovering.
You don't have to buy this from us. Plenty of clients handle it internally or with their host, and that's fine as long as someone owns it. What causes trouble is everyone assuming someone else is doing it, which is the state most WordPress sites we inherit are in.
Your current site stays live throughout, so there's no gap where people can't reach you.
Content types, who edits what, and which other systems it has to connect to. This decides the approach more than the design does.
Hosting, staging, version control, and the theme structure. Boring, and it's what makes everything after it straightforward.
Templates built on staging where you can click through real pages rather than approving screenshots.
Redirects checked, tracking confirmed, then documentation and a walkthrough with whoever will be editing it.
For most business sites, yes. It's mature, you can hire for it anywhere, and you own everything rather than renting your site from a platform.
Where we'd point you elsewhere is a straightforward store, where Shopify handles more for you, or a site that's really an application rather than a website.
There's no number. Ten well-built plugins doing necessary things is healthier than four badly-built ones.
The better question is whether anyone can explain what each one is for. If nobody can, that's the actual problem rather than the count.
Usually, and we'd start by reviewing what's there and telling you honestly whether it's worth keeping.
Sometimes the answer is that rebuilding costs less than untangling. We'd rather say that than bill for months of working around someone else's decisions.
No, and that's deliberate. Standard WordPress practices, documented customisations, and code any competent developer can read.
Hosting, domain, and every account stay in your name throughout. If you want to move on, you take the site with you without needing our permission.
It depends on whether your team needs to create new page layouts, or just edit existing ones. Those are different needs and only the first justifies a builder.
For editing, structured fields are faster and safer. For building new pages freely, a builder earns its weight. We'd ask which you actually do before deciding.
We'll recommend based on your traffic and budget, and the account is set up in your name with you paying the host directly.
We don't resell hosting with a margin on top. It's a common arrangement and it means leaving your agency also means moving your site, which isn't a position we'd want you in.
Scoped from what the site has to do rather than quoted by page count. Pricing sits on the main web development page.
Related services
Thirty minutes on the approach, who'll be maintaining it, and what that means for how it should be built.
Or email hello@culmen.digital