In short
- A typical "custom WordPress site" is a theme, a page builder and thirty plugins assembled by someone else. You are paying for assembly.
- The real cost is monthly: updates, security, a maintenance plan, plugin licenses, and the hours when something breaks.
- WordPress is the right choice for content-heavy sites with several editors, and for sites that already work.
- A custom site built as software has nothing to update, no plugin to break in through, and loads in a fraction of the time.
- The decision comes down to what the site costs you per year, in dollars and in babysitting.
Fourteen updates available
The email arrives on a Tuesday. Fourteen plugin updates are available. The owner clicks update all, because that is what the last developer said to do, and eleven go fine. The twelfth breaks the contact form. Nobody notices for nine days, because the form fails quietly and the leads it would have sent simply do not arrive. The form spam piece is a cousin of this story. Every WordPress owner has one.
WordPress is a machine with moving parts. That is not an insult; it is a description. A theme, a page builder, plugins for forms, SEO, caching, security, backups, galleries and sliders, each written by a different company, each updated on its own schedule, each able to break the others. The machine works when someone is minding it. It fails when nobody is.
This guide is the business decision: what the machine costs you, when it is worth keeping, and what the alternative is. The WordPress versus Next.js explainer covers the technical side, how each one is built and served. Read that for the how. This one is the whether.
What a "custom WordPress site" usually is
Here is a habit of the web industry worth naming. A shop quotes a custom WordPress site. What gets built is a purchased theme, a page builder such as Elementor or Divi laid over it, and twenty to forty plugins to supply everything the theme and builder do not. The shop's work is picking the parts and dragging them into place. It is assembly, not building, and there is nothing wrong with assembly as long as it is priced as assembly.
The trouble is the stack that results. Each layer adds code the page has to load, a license to renew, and an update that can break the layer below it.
The layers of a typical WordPress site
| Layer | What it is | What it costs you |
|---|---|---|
| WordPress core | The publishing engine | Free; updated several times a year |
| Theme | The starting design, bought or free | Roughly $60–$100 a year for a premium theme, and the same look as everyone else who bought it |
| Page builder | A drag-and-drop editor laid over the theme | A yearly license and the heaviest code on the page |
| Plugins | Forms, SEO, caching, security, backups, sliders, galleries | Several licenses a year; the most common source of breaks and break-ins |
| Hosting | The server running all of it | About $20–$100 a month for hosting that keeps it acceptably fast |
| Maintenance plan | Someone minding the machine | About $50–$300 a month, or your own hours |
Nothing in the table is custom. A well-built WordPress site is possible, with a lean theme and a handful of plugins, and a careful shop will build one. It is rare, and it is not what most owners have. Most have the stack above, and the stack is why the site is slow, why it breaks, and why it costs what it costs each year.
The bill that arrives every month
Maintenance. WordPress cannot be left alone. Core, theme and plugins need updating, backups need checking, and something needs testing after each update. Owners either pay for a maintenance plan, do it themselves, or do nothing and pay later. The maintenance cost guide prices each choice; a hosting and maintenance plan is the sane version of paying.
Security. WordPress is the most-attacked platform on the web for the plain reason that it is the most common one. The attacks come through plugins, almost always an outdated one. A hacked site means malware removal, a warning on Google, and days of lost calls. The risk is manageable with discipline. It is never zero.
Speed. A page builder loads its whole toolkit on every page. Add a slider, a form plugin, a security plugin, tracking scripts and a theme built for every possible layout, and a page that should weigh a few hundred kilobytes weighs several megabytes. On a phone that is seconds. WordPress optimization can claw back a good deal of it; it cannot make a builder page load like a page built to be light, and the speed guide shows what the difference is worth.
Plugins that stop being maintained. A plugin's author moves on. Nothing announces it. A year later a core update breaks it and the feature it provided is gone. Fixing WordPress plugins is a whole line of work for the same reason a tow truck is.
When WordPress is the right call
It often is, and a guide that said otherwise would be selling you something.
- You publish a lot and several people write. A magazine, an association, a firm with forty attorneys posting articles. The editor and the user roles are built for this, and no custom site beats it without becoming WordPress.
- The site works. Fast enough on a phone, ranks, produces calls, and someone competent minds it. Do not replace a working site because a guide made an argument. Fix the parts that need fixing.
- You need a specific plugin ecosystem. Membership sites, course platforms, directories, a WooCommerce store that already runs. The plugin exists and does the job; rebuilding it would cost more than tolerating the stack.
- Your team already knows it. Familiarity is worth real money. If your staff can update pages without help, that is a feature.
- The budget is this year's, and it is small. A lean WordPress site from a careful shop is a real option and can be financed at 0% like any other project.
If you are staying, stay well: a lean theme, as few plugins as the site can survive with, real hosting, a maintenance plan and a speed pass. That is a different site from the one most owners have, and it is a reasonable place to spend money.
The custom alternative
The alternative is a site built as software rather than assembled from parts. At DataCram that means Next.js: the pages are built once and served as fast static files from servers near the visitor, and only the parts that need to change, a menu, a blog, a review feed, are wired to a simple editor. There is no plugin stack because the features are written for the site. There is no theme because the design is the site. There is nothing to update on Tuesday.
The full argument runs long. The business version fits in a table.
| WordPress, typical stack | Custom site, Next.js | |
|---|---|---|
| Up-front cost | Lower; often $2,000–$8,000 for an assembled site | Higher; typically $6,000–$20,000 |
| Monthly cost | Hosting plus a maintenance plan plus licenses | Hosting, often under $50; maintenance optional |
| What breaks | Plugins, after updates | Very little; there are no moving parts to update |
| Security exposure | Every plugin is a door | Small; on most sites there is no admin panel to attack |
| Speed on a phone | Amber to red without serious work | Green, by construction |
| Editing | A full editor for everything | A simple editor for what you actually change |
| Ownership | Yours, with dependencies on a dozen vendors | Yours, outright |
Ranges are general; the [custom cost guide](/guides/website-cost/custom-website-cost) breaks the higher number down.
The honest trade: more money once, less money and less babysitting every month after, and a site that does what it was built to do. For a business that gets its customers from the site, the second and third of those pay for the first. The WordPress decline analysis has the numbers on where the platform is heading.
Making the call
- 1
Add up last year.
Hosting, maintenance, licenses, developer hours for fixes, and your own hours. Most owners are surprised by the number.
- 2
Test the site on a phone, over cellular.
Count seconds to the headline. Run Google's speed test. If it is red on mobile, the site is costing you calls you cannot see, and the free audit will show how many.
- 3
List what you would change if you could.
The feature the plugin does badly, the page that looks like the template, the form that spams you. If the list is short, fix the site. If it is long, that list is the brief for the replacement.
- 4
Decide: keep and fix, or replace.
Keep if it works and the list is short; a speed pass and a plugin cleanup are fixed-price jobs. Replace if the yearly cost plus the list plus the speed adds up to more than a build. Replacing WordPress is a known process with redirects and no lost rankings.
- 5
Whichever you choose, own it.
Domain in your name, hosting in your name, backups you can reach. The honest math guide makes the same point about every platform.
WordPress is not expensive to buy. It is expensive to own. Do the math on owning it.
Find out what your site is actually doing.
A free audit scores your site on speed, mobile, SEO and security, and lists the fixes in order of what they are worth. Delivered as a PDF to your inbox.
Want an honest answer on building it yourself?
Tell us where you are and we will tell you, plainly, whether a builder will do the job or whether it is time for a real one. No pitch, and you keep the answer.
Which of these sounds like you? (pick any)
Questions people ask
Straight answers
For a content-heavy site with several editors, or a site that already works and is well maintained, yes. For a small business site whose job is to load fast on a phone and turn searches into calls, a custom build usually costs less per year once maintenance, security and lost speed are counted, and it has no plugin stack to break.
Almost always the stack: a page builder that loads its whole toolkit on every page, a theme built for every layout, a dozen plugins each adding scripts, and images that were never compressed. Optimization can recover a lot of it. It cannot make a builder page as light as a page built to be light, which is the ceiling of the platform.
Roughly $50 to $300 a month for a plan that handles updates, backups, security and monitoring, plus hosting and a few plugin licenses a year, plus the hours when something breaks anyway. A site that is not maintained costs nothing until it is hacked or breaks, and then it costs a great deal in one week.
A custom WordPress site is usually a purchased theme, a page builder and a set of plugins arranged for you. A custom website is built as software for your business: the design is the code, the features are written rather than installed, and there is no stack to update. The first is cheaper to buy. The second is cheaper and faster to own.
Yes. The content moves, each page is rebuilt on the new platform, and every old address is permanently redirected to its replacement so rankings and links carry over. The new site is usually faster, which helps rankings from then on. A short dip in the first week or two is normal and recovers.
Fix it if it mostly works, the list of things you would change is short, and the yearly cost is reasonable; a speed pass and a plugin cleanup are fixed-price jobs. Replace it if it is slow on a phone, breaks regularly, blocks features you need, or costs more per year in maintenance and lost calls than a new site would over three years.
Where to go from here