WordPress Template vs. Custom Website: What Milwaukee Businesses Actually Get

What a WordPress theme actually is

WordPress is a content management system. It runs on a server, stores your content in a database, and uses a theme to control how everything looks. Themes range from free starter templates to premium commercial products sold for $49 to $200 on marketplaces like ThemeForest.

When a designer buys one of those themes, installs it, uploads your logo, and switches your colors, the result can look convincing. But the underlying architecture came from someone else. The code that runs on every page load, the CSS for components you will never use, the assumptions baked into the layout system: all of that is inherited from the original template author.

One auditor documented finding CSS classes named .dental-hero and .dentist-services still loading on an automotive business site. The theme started its life as a dental template. Nobody cleaned it up. Every page load carries that dead code.

That is not a disaster. It is a tradeoff. Understanding the tradeoff is what this guide is for.

What "built from scratch" means in practice

A genuinely custom site has no theme layer. The designer writes the HTML structure, the CSS, and the JavaScript for your specific site. No inherited component library. No theme author's assumptions about your navigation, your typography scale, or your layout system.

The output is leaner by default. There is no dental CSS loading on your HVAC site. There are no plugin dependencies for features the theme needed but you do not.

This approach costs more time. More time generally means more money. But the starting point is cleaner, the performance ceiling is higher, and the site does not carry another business's discarded architecture.

Modern frameworks like Next.js and Astro let a designer build a fast, custom site without the WordPress overhead. Codeable describes these architectures as producing faster performance "by default" compared to plugin-dependent WordPress builds.

How to spot a theme sold as custom

You do not need a developer to check this. A free tool at isitwp.com lets you enter any URL and see whether the site runs WordPress and which theme it is using.

Signs that a proposal is theme-based rather than custom:

• The proposal shows you a demo site rather than a wireframe or sketch of your specific structure.
• The quoted price is under $3,000 for a multi-page site with complex layout needs.
• The designer cannot describe what they will build specifically, only that they will "customize" it to your brand.
• The portfolio shows sites that look structurally similar to each other.

None of these are automatic disqualifiers. Theme-based work can be honest, well-executed, and appropriate for some budgets. The problem is when it is sold as something it is not.

The plugin problem

WordPress sites depend on plugins for most functionality beyond basic text and images. Contact forms, speed optimization, SEO settings, security, image compression, cookie notices: most of these require a plugin.

Plugins are not free in the real sense. Each one adds HTTP requests, database queries, and server-side processing. Each one has its own update schedule, its own author, and its own potential for conflicts with other plugins.

Patchstack's 2025 security research found that 96% of WordPress vulnerabilities come from plugins and themes, not from WordPress core. The platform itself is reasonably secure. The ecosystem around it introduces most of the risk.

That is not an argument against WordPress. It is an argument for knowing what you are buying into. A site built by someone who manages the plugin stack carefully is a different product than one built by someone who piles on plugins for convenience.

Platform lock-in: what you actually own

Lock-in is a spectrum, not a binary. Here is what it looks like at the worst end:

• Your site is built inside a proprietary page builder that stores content in its own format.
• Your designer retains admin credentials and manages the hosting account.
• Your content cannot be exported cleanly because the page builder has encoded it in its own database structure.
• Moving to a new designer or platform means rebuilding from scratch.

WordPress self-hosted sites are better than many on this scale. You own the content in a MySQL database. You can take that database and the files to another host. The migration is real work, but it is not impossible.

The variables are: who controls the hosting account, who holds the admin password, and whether the designer used a page builder that locks content to its format. Those are questions to ask before you sign, not after.

A note on placeholder pages

One thing worth flagging when reviewing any designer's portfolio: look at the live site, not just the screenshot.

Some designers show polished screenshots of sites that have not been fully built out. Placeholder text, empty service pages, contact forms that do not send anywhere. This is more common than it should be.

Ask for the URL and visit it yourself. Click through the navigation. Submit the contact form. If sections are unfinished on a site they are actively showing as portfolio work, that is information.

Questions to ask before you sign

These five will tell you most of what you need to know:

1. Will you show me a live site you built from scratch, not a demo or template preview?
2. Are you starting from a purchased theme, or designing this specifically for my business?
3. Who will own the domain, the hosting account, and the admin credentials when the project ends?
4. If I want to move to a different designer in two years, what does that process look like?
5. How many plugins are you planning to use, and which ones?

You are not looking for a specific answer on any of these. You are listening for whether the designer can answer them directly. Hesitation, deflection, or an inability to describe the technical approach in plain terms is the actual signal.

The honest tradeoffs

Theme-based WordPress sites are not inherently bad. They are faster to build and cheaper to produce. For a small business that needs a clean five-page site in four weeks and has a $3,000 budget, a well-executed theme build from a competent designer is a real option.

The problems start when:

• A theme build is sold at custom-build prices without disclosure.
• The plugin stack is not managed and the site accrues technical debt.
• The designer retains control of access credentials.
• The site's performance degrades because no one is watching it.

A custom build costs more because it takes more time. What you get in return is a site with no inherited architecture, a leaner starting point for performance, and no structural constraints from someone else's design decisions.

What I build and what it costs

I design and build the same site. There is no handoff between a designer and a separate developer. The thing I approved in the design phase is the thing I build in code, which means the direction does not get lost in translation.

I do not start from purchased themes. The sites I build are written for the specific business they are for. They run on a modern stack without WordPress overhead. They are set up so you own the domain, the hosting account, and every credential from day one.

The Starter package starts at $4,500, typical range $4,500 to $6,500. Growth projects run $8,500 to $15,000 depending on scope. Both include brand and site, not one at the expense of the other. Full pricing and what each package includes is at /packages.

I have about 15 years of design experience, including nearly five years doing product design at Dyson, and work for Milwaukee Tool and Kohl's. I am based in Milwaukee and I work directly with each client.

If you want a read on what your current site is actually doing, the free audit is the place to start.

Request a free site and visibility audit.