WordPress vs a custom-built website

For most small organizations, WordPress is the right answer and custom is a word that adds several thousand dollars without changing anything a visitor can see. Custom earns its price when the site has to be extremely fast under real traffic, has to do something no plugin does, handles sensitive information, or is honestly an application wearing a website costume.

That is the short version. The longer version matters because the word custom is used to mean three completely different things, and the person quoting you $18,000 and the person quoting you $6,500 may both be saying custom while describing different products.

I have built on both sides of this for 14 years from one office in Edina. I have also talked people out of custom builds more often than I have sold them.

What does custom actually mean?

Three things, and they are not close to each other in cost or consequence.

1. A custom theme on WordPress. The site runs WordPress. The design is drawn from scratch and coded into a theme built for your organization, rather than a $59 theme from a marketplace. You still get the WordPress admin, WordPress plugins, and WordPress updates. This is what most agencies mean when they say custom WordPress, and it is what most quotes in the $3,500 to $9,000 range describe.

2. A custom CMS. Somebody writes both the website and the tool you use to edit it. This was common in 2009 and is now, with rare exceptions, a bad idea for a small organization. You are the only customer of that software. When the developer moves on, nobody else knows how it works, and there is no community writing security patches for it.

3. A fully hand-built site or application. No off-the-shelf CMS running the public pages. The site is built with a modern framework such as Astro, Next.js, or Eleventy and either published as static files or run as an application with its own database, accounts, and logic. This is what people picture when they say custom, and it is where the real trade-offs live.

Ask any agency which of the three they are quoting. If the answer is vague, that is the answer.

How do WordPress and custom compare on the things that matter?

	WordPress (theme or page builder)	WordPress with a custom theme	Fully hand-built (static or app)
Typical build cost	$1,800-$3,500	$3,500-$9,000	$9,000-$25,000 for a site; $12,000-$60,000 as an application
Build time	2-4 weeks	4-8 weeks	8-16 weeks, longer for applications
Page speed	Adequate to poor. Page builders add weight	Good if the theme is disciplined	Excellent. Static pages are hard to beat
Security surface	Largest. Every plugin is a door	Smaller. Fewer plugins by design	Smallest for static. No database to attack
Editing experience	Best. Familiar to millions of people	Best, with guardrails on layout	Weakest unless you add a CMS layer, which costs more
Flexibility	Whatever a plugin already does	Wide, with some framework limits	Unlimited, at engineering rates
Hosting	$10-$50/mo	$10-$50/mo	Often free to $20/mo for static; more for an app
Ongoing maintenance	$75-$600/mo care plan, effectively required	$75-$600/mo	Little to none for static; real cost for an app
Developer availability	Enormous. Anyone can pick it up	Large	Smaller pool, higher hourly rate
Longevity	5-8 years with maintenance	5-8 years	8+ years for static; apps age like software

Two rows in that table decide most projects. Editing experience decides whether the site stays current. Ongoing maintenance decides what it costs you in year three.

When is WordPress the right choice?

WordPress wins in four situations, and they cover the majority of the organizations we talk to.

When the site is content-heavy. If you publish news, sermons, program updates, staff bios, board minutes, or a real blog, you want a proper editor and a media library. A masjid posting prayer times and Friday reminders every week, or a nonprofit publishing program news, is a WordPress site. Mosque websites and nonprofit websites usually fall here.

When a non-technical person will maintain it. This is the one that matters most and gets discussed least. The office manager who updates your staff page has probably used WordPress somewhere before. She has probably never used a git-based content workflow, and she should not have to.

When the budget is genuinely tight. At $2,500 total, custom is not on the menu. WordPress with a well-chosen theme and a careful setup beats a stretched custom build every time.

When the functionality already exists as a plugin. Event calendars, donation forms, membership areas, multilingual content, job listings, appointment booking. Somebody already solved these and has been fixing bugs in them for a decade. Paying an agency to rebuild a working plugin is how budgets die.

WordPress runs a very large share of the web, which is a real advantage. It means your next developer will already know it, and it means the plugin you need probably exists. That is not a small thing when you are a five-person nonprofit and your web person just moved to Chicago.

When is a custom build actually worth it?

Five cases, and they are narrower than the sales pitch suggests.

Performance is critical. If people arrive on phones over poor connections, or you run paid ads where every second of load time costs you conversions, a static build is meaningfully faster. Google treats loading speed as a ranking signal and recommends a largest contentful paint under 2.5 seconds, which is achievable on WordPress and nearly automatic on a static site. If speed is your current problem, read why your website is slow before you assume a rebuild is the fix.

The functionality is unusual. A scheduling engine that matches caregivers to shifts. A grant portal with reviewer roles. An intake form that scores responses and routes them. No plugin does your specific thing, and bending three plugins into a shape they resist costs more than building it. That work sits in web app development, not web design.

Traffic is very high. WordPress at high traffic needs caching layers, a CDN, and a hosting bill that grows. Static files at high traffic need a CDN and almost nothing else.

The context is security-sensitive. If the site touches protected health information, client records, or anything you would be embarrassed to see in a breach notice, a smaller attack surface is worth money. Most WordPress vulnerabilities disclosed each year live in plugins and themes rather than in WordPress core, so fewer moving parts is a real defense.

It is actually an application. If users log in, see different things, and change data, you do not have a website with features. You have software with a marketing page attached. Price it as software.

What about Astro, Next.js, and Eleventy?

Modern static site generators produce plain HTML files at build time. There is no database answering requests, no PHP executing on every page view, and nothing to patch at 2am. The result is very fast, very cheap to host, and very hard to hack, because there is nothing running to attack.

The honest trade-off is editing. Out of the box, updating a static site means editing text files and pushing to a repository. That is fine for a developer and unusable for a program director.

The fix is a headless CMS. You attach an editing tool such as Sanity, Contentful, Prismic, or a hosted WordPress instance running in headless mode, and the static site pulls content from it at build time. Editors get a friendly interface, visitors get static speed. It works well and it costs more: a meaningful chunk of extra setup on top of the build, plus a monthly fee for the CMS itself.

The second trade-off is preview time. On WordPress you hit update and the change is live. On a static build the site rebuilds first, which takes anywhere from ten seconds to a few minutes. Nobody minds this once it is explained. Everybody minds it when it is a surprise.

	Static build, no CMS	Static build with a headless CMS	WordPress
Who can edit	Developers only	Anyone	Anyone
Time from edit to live	Minutes, after a commit	10 seconds to a few minutes	Instant
Extra setup cost	None	Added setup time plus a monthly CMS fee	None
Best fit	Sites that rarely change	Content-heavy sites that need speed	Almost everything else

Where I would tell you not to spend the money

If you are a home care agency, a small law practice, a therapy clinic, or a five-location contractor, and your website is 12 to 25 pages of information plus a contact form, a custom build is a waste of your budget. Nothing about your visitor’s experience improves. You will pay roughly double, wait twice as long, and end up with a site that fewer people in town can maintain.

Take the difference and spend it on things that actually move the needle: a real photographer, someone who writes your service pages properly, and a year of local SEO. A $4,500 WordPress site with excellent photography and honest copy beats a $14,000 custom site with stock images and three paragraphs of filler. I have watched that comparison play out enough times to say it plainly, and I say it even when the bigger number would have been our invoice.

The exception is the organization whose site is already generating real revenue and is already slow. Then the math changes, and it changes fast.

What does TayoPro build on?

All of it, deliberately. We work in WordPress, Squarespace, Wix, Shopify, and WooCommerce, and we build fully custom when the project calls for it. This site runs on Astro, because it is a marketing site I update myself and I care about it loading instantly.

Most of the work we publish is on platforms the client can maintain without calling us. That is not modesty, it is what keeps a site alive. A site nobody can update goes stale in about eight months, and a stale site with 2023 staff photos and a dead phone number does more damage than an ugly one.

Our published pricing reflects the split. A business website at $3,500 to $9,000 is usually WordPress with a custom theme. An advanced website at $9,000 to $25,000 may be either, depending on what it has to do. A web application or portal at $12,000 to $60,000 is always custom, because there is nothing else it could be. Everything sits on your own domain and your own hosting account, which matters more than the platform - see do you actually own your website for how to check.

So how do I decide?

Answer four questions honestly.

Who updates this on a Tuesday afternoon? If the answer is a staff member with other responsibilities, choose WordPress or a static build with a headless CMS. If the answer is a developer, or nobody, static is fine.

How often does the content change? Weekly means you need a real editor. Twice a year means the editing tool barely matters.

Does anything on the site need to remember a user? Logins, accounts, saved records, dashboards. If yes, you are shopping for an application, and the web app comparison is a better starting point than this article.

What is the total budget over three years, not three months? WordPress costs less to build and more to keep. Static costs more to build and almost nothing to keep. Over five years those lines cross for some organizations and never cross for others. The Minnesota cost breakdown in how much a website costs here has the running numbers.

If you already have a WordPress site and are considering the jump, do not start with the platform. Start with what is failing. Slow, insecure, unmaintainable, or unable to do a specific thing are four different problems with four different fixes, and only the last one reliably requires a rebuild. Moving to a new platform without losing rankings is its own project with its own budget.

Talk it through

If you are weighing a WordPress build against a custom one and the quotes are far apart, send me both. I can usually tell you within a few minutes whether they are describing the same product, and whether the expensive one is buying you anything you will use.

Reach us at info@tayopro.com or (612) 293-0636. We are in Edina and we work with organizations across the Twin Cities, greater Minnesota, and beyond.