For a business that wants to own its site and has someone to maintain it, WordPress with a purchased theme is a legitimate choice. For a business that wants the design, copy, search and AI engineering done and delivered, and does not want to run a software stack, choose a custom build.
This is a different comparison from the hosted builders. WordPress is open-source software you install and own, and a purchased theme is a design template for it. The ownership problem that Squarespace and Wix have does not apply here. What does apply is the difference between buying a starting point and buying a finished, engineered site.
Unconventional Group's custom builds start at $3,000 one-time for ten to fifteen pages, with copy, SEO and AEO engineering, CRM-wired forms and full handover included, and a running cost of $50 a year afterwards.
Side by side
| Custom build (Unconventional Group) | WordPress + purchased theme | |
|---|---|---|
| Ownership | Domain, code, hosting and design in your name, every login handed over. | Yours: WordPress is open-source and self-hosted. The theme's licence terms apply to the theme itself. |
| Up-front cost | From $3,000 one-time (10–15 pages). Two-Day Website from $5,000 with SEO and AEO passes. | Theme licence plus hosting plus whoever configures it, designs around it and writes the content. Ranges widely. |
| Running cost | $50 a year for domain and hosting. Optional support $149 or $349 per month. | Hosting, domain, renewals on premium plugins and theme updates, plus the time or fee to keep everything patched. |
| Who writes the copy | Unconventional Group, from your intake brief and facts. | You, or a writer you hire. Themes ship with placeholder text. |
| SEO / AEO structure | One page per query family; one canonical Organization node with real prices; llms.txt; explicit AI-crawler permissions; redirect map. | Depends entirely on configuration. SEO plugins cover basics; multiple plugins often emit overlapping, conflicting markup. No llms.txt by default. |
| Mobile performance | Built at 375px first; LCP, CLS and INP budgeted against a mid-tier Android phone. | Depends on the theme and page builder. Heavy themes and stacked plugins are the usual cause of slow Core Web Vitals. |
| Speed to live | About two weeks typically; Two-Day Website live by end of day two when conditions are met. | As fast as the person configuring it; weeks is common once design and content are counted. |
| What happens when you leave | Nothing; the site is yours and runs for $50 a year. | Nothing; the site is yours. Maintenance responsibility stays with you. |
When a WordPress theme is the better choice
WordPress with a theme is the right call when the business has, or will hire, someone who is comfortable running it: applying updates, vetting plugins, keeping backups, and troubleshooting when a plugin update breaks the contact form. It is also the right call when the business needs something WordPress's ecosystem does unusually well, such as a large editorial blog, a membership area, or a specific plugin integration the business already depends on.
The ecosystem is the real strength. There is a plugin for nearly everything, hosting is available at every price, and thousands of developers can work on it. If a business values that flexibility and accepts the maintenance that comes with it, a theme is a reasonable place to start.
When a custom build is the better choice
A custom build is the right call when the business wants the outcome, not the platform.
The most common failure mode of a themed site is not the theme. It is that the theme is bought, the placeholder copy is half replaced, three SEO and schema plugins are installed and each emits its own Organization node with a slightly different phone number, the page builder loads a megabyte of scripts before the headline appears, and nobody decided which page should answer which question. The site exists and looks fine, and it is not doing the job.
A custom build starts from the other end: what the site needs to say, which page says it, how a machine reads it, and how fast it loads on a phone. The design is custom, the copy is written from the client's facts, the structured data is generated from one source so it cannot disagree with the page, the AI crawlers are explicitly allowed, and llms.txt states the business's facts in its own words. The client's team can update the content that changes often without a developer, which is a build requirement rather than an upsell.
The other difference is what "done" means. A themed site is done when the person configuring it stops. A custom build is scoped in writing before work starts, priced to that scope, and handed over with every login and a baseline measurement so the next measurement means something.
On price and results
The $3,000 floor covers a ten-to-fifteen-page build; page count beyond fifteen, integrations, content volume and migration with URLs preserved move it up, and the number is fixed before anything starts. Results are typical, not guaranteed: clients typically see movement in 14 to 90 days, measured against a baseline captured before the work starts.
