Answer

How long does a custom WordPress theme take to build?

Four to six weeks for twelve pages and a blog on a custom block theme, about two for five pages on a tuned one. Built once, so later edits are patterns, not code.

Published September 22, 2026

A custom WordPress theme takes four to six weeks for a twelve-page site with a blog: a week of discovery, a week for the content model and design system, two to three weeks of templates, patterns and content, and a week of QA, performance and launch. A five-page site on a tuned block theme lands in about two.

Why does a custom theme take longer up front than a page builder?

Because the design system is built into the theme before any page exists. The colours, type scale, spacing and components live in theme.json and a set of block patterns, and the templates are written rather than composed. For the first two weeks there is little to look at.

The payback starts in week three. Once the system exists, pages are assembled from patterns in hours, every page agrees with every other page by construction, and a new page type is a template rather than a rebuild. A page builder front-loads the visible progress; a custom theme front-loads the thinking.

What do the six weeks contain?

The same four phases as every build, with more of the calendar spent in architecture and less in layout.

Week-by-week plan for a six-week custom WordPress theme build
Week	Phase	What gets done	What I need from you
1	Discovery	Goals, sitemap, a content inventory, integrations, what migrates from the old site. Ends with a scope and dated milestones.	The people who decide, in one session.
2	Architecture	The content model (which templates exist and what is editable on each), theme.json tokens for colour, type and spacing, the pattern list, the performance and accessibility budget.	Sign-off on the sitemap and design direction.
3–4	Build	Templates and block patterns; custom blocks only where core blocks cannot express the element; forms with delivery verified; integrations; content loaded as it arrives.	Final copy and images, page by page.
5	Launch prep	QA across devices, the performance pass, accessibility, metadata and schema, redirects from every old URL.	One review round with a named approver.
6	Launch & handoff	DNS cutover, monitoring on, pattern training and documentation for your team.	Account access: domain, hosting, analytics.

This is the same skeleton as every website timeline I run; what changes is where the weeks land.

How does the block editor change the calendar after launch?

It moves page changes from a developer's queue to your team's. Editors compose pages from the patterns the theme ships, the editor is the one WordPress core maintains, and updates come from core instead of from a builder vendor. Gutenberg is leaner and ages with WordPress; that is the argument for accepting the longer first two weeks.

It also changes what a future request costs. A new landing page is patterns; a new section type is a pattern; a new kind of content is a template. None of those reopen the build.

What stretches a custom theme build?

Custom blocks with interactive interfaces. Each one is a small application with its own editor UI, and each is a week that core blocks and a pattern would have made a day.
Design changes after templates are written. A revision in the design tool is hours; the same revision across built templates is days.
Migrating content out of a page builder, where every page is shortcodes rather than blocks.
A design delivered as static mockups with no system behind them, so the system has to be reverse-engineered before it can be built.
Content arriving after the milestone that needed it.

Custom theme or tuned theme: which timeline do you need?

A tuned block theme with five pages is about two weeks and is the right build for a business that needs a real website more than it needs a distinctive one. A custom-designed theme is the four-to-six week build for a site replacing a dated or template one, where the design is part of what the site has to say. If your marketers already live in a page builder, the Elementor timeline is the one to read. All three ship the same way: performance verified, forms tested, analytics wired, and the same scoping and milestone plan before work starts.

Decision record

Context: On a block-theme build, every element in the mockups raises the same question: a core block styled through theme.json, a pattern, or a custom block with its own editor interface.
Options considered: Build custom blocks for everything so the editor matches the mockups pixel for pixel
Use only core blocks and patterns, and bend the design to what they can do
Core blocks and patterns first, with custom blocks reserved for elements core genuinely cannot express
Decision: The third. Most of the design became patterns over core blocks; the handful of elements core could not express became custom blocks, each justified in writing.
Trade-off accepted: A few mockup details were simplified to what core blocks do well. In exchange the theme updates with WordPress core, the client's team can maintain it, and the build stayed inside its six weeks.

Questions

Can a custom WordPress theme be built in two weeks?

A five-page site on a performance-tuned block theme, yes. A custom-designed theme with its own design system, patterns and templates needs four to six weeks, because the system is built before the pages are.

Does a custom theme make the site faster?

Usually. A custom theme ships only the CSS and JavaScript the site needs, where a general-purpose theme ships for every site it might be used on. Speed is still a budget kept by discipline, not a property of the theme, so it is measured template by template during the build.

What does the handoff include?

The patterns your team composes pages from, a training session on the workflows you actually use, and written guides for them. The theme is documented so nothing about running the site depends on me being around.

How long does it take to move a page-builder site onto a custom theme?

It is a rebuild with a content migration inside it. The content has to be mapped out of the builder's shortcodes into blocks, which adds a week or more to the four-to-six-week build depending on how many pages carry it.

Related notes

More on web development

Related service: Web Development

Want this kind of engineering on your project?

Tall Karol takes on fractional and project-based engagements for startups and agencies.

Book a working session