This is one of the first real questions in any website project, and most answers online come from people who only sell one of the two. We build both. Here is the honest version: what each thing is, what each genuinely costs, and the handful of questions about your business that decide it.
What WordPress actually is
WordPress is free software, first released in 2003, installed on a web server — a rented computer that answers requests from visitors. It keeps your content in a database, a structured filing system. When somebody visits, the server looks up the content, runs code to assemble the page, and sends the result. More websites run on WordPress than on any other content management system.
Two things get bolted on: a theme, which controls how the site looks, and plugins — small add-on programs that each do one job. Contact forms. Backups. Booking. A store.
Worth clearing up: WordPress.com is a paid hosting service; WordPress.org is the free software you install anywhere you like. Same name, different products. Almost every agency-built business site is the second kind, and that is what this article means.
What "static" or custom-built actually means
A static site is built ahead of time. Your pages exist as finished files and the server just hands the file over — no database lookup, no code running while the visitor waits. It is the difference between a restaurant cooking your order and a bakery handing you a loaf already on the shelf.
Static does not mean "a brochure that never changes," and it does not mean "no features." A static site can have working contact forms, a filterable menu, an interactive delivery-zone checker. What it does not do is rebuild the page from a database on every visit.
Custom-built is broader and often means more: a purpose-made application — an order form with your specific rules, a booking system, a therapy-practice intake form. That is a different animal from a static brochure site. Be precise with your builder about which you are buying.
What WordPress is genuinely good at
You can change things yourself
This is why WordPress won. A grocery owner can log in, change a price, swap a photo, add a page about Yom Tov hours, and publish — at 11pm, without calling anybody. For a business whose site changes weekly, that alone can justify everything on the cost side.
The plugin ecosystem
The official directory holds tens of thousands of free plugins, with a large commercial market on top. Appointment booking, multilingual pages, membership areas, event calendars, invoicing — something exists. It may not be great, but it installs in ten minutes rather than taking ten days to build.
WooCommerce, for stores that need a real store
WooCommerce is the free store plugin most WordPress sites use. It handles what gets tedious fast: product variations (a sefer in three bindings), inventory counts, coupons, tax rules, shipping zones, order emails, refunds, customer accounts. With 400 products, or staff marking orders fulfilled, you get an enormous amount of finished work for free.
Anyone can take it over
If your developer becomes unreachable, thousands of people can pick up a WordPress site. Someone can pick up a custom site too, but the pool is smaller. If continuity worries you, WordPress is the conservative choice.
What WordPress actually costs
- Hosting. Cheap shared hosting runs roughly $5–$15 a month. Managed WordPress hosting, which handles updates and caching for you, more commonly runs $20–$50 a month and up. Read the renewal price, not the signup price.
- Plugin licenses. Serious plugins are annual subscriptions, commonly $50–$300 a year each. Four of them is real money. A lapsed license usually keeps working but stops getting updates — exactly the wrong thing to let happen.
- Maintenance. Someone applies updates, checks nothing broke, keeps backups. Retainer or your own time, it is not optional.
The update treadmill
Core, theme, and every plugin release updates independently. Security patches need applying promptly. Feature updates occasionally break something — a layout shifts, a form stops sending. WordPress can install many updates automatically, which lowers the risk of falling months behind and raises the risk of waking up to a changed site. Either way somebody has to look.
On security: the large majority of WordPress compromises come through vulnerable plugins and themes, not through WordPress itself. Core has a serious security team. The plugin somebody installed in 2019 and abandoned is the problem. Every plugin is another author you are trusting.
Sprawl and slowdown
WordPress sites degrade predictably. Year one is clean. By year three there are twenty-two plugins, four doing nothing, each loading its own styling and scripts on every page whether that page uses them or not. Add a drag-and-drop page builder, and photos uploaded straight off a phone at 4,000 pixels wide, and pages get heavy.
Speed is commercial, not cosmetic. Google's loading-speed measure, Largest Contentful Paint, treats 2.5 seconds as the threshold for "good," and page experience factors into ranking. More to the point, a slow store loses carts — see site speed for online stores. None of this is inevitable: a disciplined site with eight plugins, compressed images, and caching is fast. It stays fast because somebody enforces discipline, and discipline is a service you pay for.
Where a static or custom site wins
- Speed. No database query, no code to run before the page is sent. Static files are also easy to serve from a CDN — a network of servers in many cities keeping a copy near your visitors. A well-built static page arriving well under a second is normal, not an achievement.
- Security surface. No admin login to attack, no plugin vulnerabilities, no database to inject. Not invulnerable — your domain registrar and hosting accounts still matter — but the list of things that can go wrong is dramatically shorter.
- Hosting cost. Services like Cloudflare Pages, Netlify, and GitHub Pages have free tiers that comfortably cover a small business's traffic, HTTPS certificate included. Many static sites cost the owner nothing to host; the domain, typically $10–$20 a year, is the only recurring bill.
- It holds up under a rush. A pre-Pesach surge, or the motzei Shabbos wave that hits a grocery site all at once, is exactly the load that flattens a cheap shared-hosting WordPress install.
- It does not rot. Leave a static site alone for three years and it works. Leave a WordPress site alone for three years and you have a security incident waiting.
Where a static site loses
The honest answer is short and important: a non-technical owner cannot restructure the site themselves. Without an editing layer, changing a price means emailing your developer. So does adding a page. If your builder is responsive and changes are occasional, that is fine — arguably better, since someone competent reviews every change. If you need to move fast and often, it is a daily irritation.
Second, everything is built rather than installed. A feature that is a $79 plugin in WordPress may be two days of custom work. For a booking system with ordinary rules, WordPress is usually cheaper. For a booking system with your rules, custom is often cheaper, because you are not fighting a plugin's assumptions.
The middle grounds
A static site with a lightweight editing layer
Keep the static site — fast, cheap, hard to break — and add a simple browser-based editor on top. The owner logs in, sees plain form fields ("store hours," "this week's specials," "product photo"), saves, and the site rebuilds itself within a minute or two. Tools that do this include Pages CMS, Decap CMS, Sveltia CMS and TinaCMS.
The trade-off is precise: you can edit what was set up as editable, and nothing else. You can change the words on the specials page. You cannot invent a new page layout. For most owners that is the right amount of power — enough to stay current, not enough to break the design.
A custom application for a real workflow
When the business logic is unusual, custom is the cheap option, not the luxury one. Delivery pricing that depends on the customer's zip code. Orders that cut off before Shabbos and reopen at a set time. A food-assistance application with eligibility questions. These run as small applications on serverless hosting — you do not rent a server, you pay per use, and at small-business volumes that is often pennies. Ordering around Shabbos and Yom Tov has more edge cases than owners expect; see taking online orders around Shabbos and Yom Tov.
Headless WordPress and hosted platforms
Headless WordPress runs WordPress as the back-office editor and publishes a static front end from it. It works, but it means maintaining two systems instead of one, and under a few hundred pages it usually adds cost without value. Be skeptical if it is proposed for a neighborhood store.
Shopify, Squarespace and Wix are a legitimate fourth answer for a straightforward store. Monthly fee, no server, no plugin to get hacked through. In exchange you accept their limits, their checkout, their payment terms, and you cannot take the site with you. Entry plans have generally sat in the range of roughly $16–$40 a month — check current pricing, it moves. For unusual delivery rules or Hebrew right-to-left pages, they fight you more than they help.
What actually determines the answer
- Who edits, and how often? Changes most weeks means you need a content management layer. Changes three times a year means static with no editor is fine and cheaper.
- Do you sell online, and how? There is a large gap between "customers submit an order and we call them back" and "customers pay by card, pick a delivery window, get a receipt." The first is a form on a static site. The second is a store.
- How many products, and how do they change? Under roughly 25–30 stable items, a static catalog is very manageable. Above that — or with variations, stock counts, constant price changes — WooCommerce or a hosted platform is the sane choice.
- Is there a workflow with real rules? Booking, applications, delivery zones, quoting, order cutoffs. The more your rules differ from everybody else's, the more custom wins.
- Who owns this in year three? The most expensive websites we see were not built wrong. Nobody owned them after launch.
| Business | Usual fit | Why |
|---|---|---|
| Plumber, contractor, one-page service business | Static | Content barely changes; speed and near-zero cost win |
| Therapist, coach, medical biller | Static with an editing layer | Few pages, occasional updates, forms that must stay private |
| Caterer | Either | Depends how often menus and galleries change |
| Kosher grocery or butcher with delivery | WooCommerce, or a custom ordering app | Large changing catalog, or delivery rules no plugin handles |
| Seforim store | WooCommerce | Hundreds of titles, variations, search and filtering |
| Travel agency | Static plus a custom request form | No cart; the value is a well-built inquiry workflow |
| ABA or therapy provider | Static or light CMS | Informational; hiring and intake pages change occasionally |
Migrating from one to the other
Nothing "converts." A migration is a rebuild with the content carried across.
WordPress to static is easier for content — text and images come out cleanly. The work is whatever was interactive: forms need a new home, search needs rebuilding, a store needs replacing entirely. A brochure site is often a week or two. A store is a full project.
Static to WordPress means building a theme matching your design and moving pages in one at a time. No shortcut. Budget close to a new build, though settled design decisions save real time.
What breaks
- URLs. The one that actually costs money. If
/catering-menubecomes/services/catering-menu, every search result and posted link now hits a dead page. The fix is a 301 redirect — a permanent forwarding instruction from the old address to the new. List every current page before you start and map them all. Skipping this is how businesses quietly lose search traffic after a redesign. - Order history and customer accounts. Products migrate reasonably well. Past orders and saved accounts frequently do not. Keep the old store readable for a period — New York requires sales tax records be retained for at least three years.
- Email. Changing where the website is hosted does not have to affect your email, but it can if settings are moved carelessly. Get it in writing that mail records are being left alone.
- Recurring payments. Subscriptions and saved cards generally do not transfer between systems. If you have them, raise it on day one.
The part nobody wants to say
For a large share of small local businesses, either choice works, and the platform is not your risk. The builder is.
A well-built WordPress site with restrained plugin use and real maintenance will serve a grocery for a decade. A well-built static site will do the same for a plumber. A badly built version of either will be slow, insecure, impossible to hand over, and quietly costing you customers. That difference is not technological, so interview for it. Ask any builder, including us:
- Is the domain registered in my name, with my email on the account?
- Do I have the hosting login, or only you?
- If I hire someone else in two years, what exactly do I hand them?
- What does year two cost, itemized — hosting, licenses, maintenance?
- What happens when something breaks on a Friday afternoon?
A builder who answers those clearly will do fine work on either platform. One who gets vague will not, whichever they recommend. If you want a straight recommendation for your situation, tell us what the business does and who will update the site — that is most of the answer. You can describe the project here, and if you are working out a budget, see what a website should cost.
The short version
- WordPress fits when the owner edits often, when you have a real catalog, or when you want the widest pool of people able to take over. Its cost is hosting, licenses, and permanent maintenance — not the software.
- Static or custom fits when the site changes rarely, speed matters, hosting should cost almost nothing, and your rules are unusual enough that plugins fight you.
- The middle ground is real. A static site with a small editing layer gives most owners the control they actually use, without the maintenance they do not want.
- Decide with five questions: who edits and how often, do you sell online, how many products, is there a custom workflow, who owns this in year three.
- Migration is a rebuild. The expensive part is redirecting old page addresses so you keep your search traffic.
- Judge the builder, not the platform. Own your domain, hold your own hosting login, get year-two costs in writing before you sign.