WordPress Design and Development Agencies: The Three Builds, and the Handover That Decides If You Can Leave

The expensive decision on a WordPress project is not which agency you hire. It is which of three builds you are buying: a commercial theme configured for you, a page builder site assembled in a visual editor, or a custom theme with blocks written for your content. The three take very different amounts of work, they leave different people able to change the site afterwards, and they age in different ways. Settle the build first, because two quotes for two different builds are not comparable, however similar the cover page looks.

The three builds behind every WordPress quote

Whatever the proposal calls it, it is one of these.

Build	What the agency actually does	Who can change it afterwards	What it depends on in three years
Commercial theme, configured	Buys a theme, imports its demo layouts, replaces the text and photos, sets colours and fonts, installs the plugins the theme expects	Anyone, inside the layouts the theme already ships	The theme author still shipping updates, and the plugins bundled with it still being maintained
Page builder site	Builds each page in a visual editor such as Elementor, Divi, Bricks or Beaver Builder, usually on a light starter theme	Anyone willing to learn that builder, and nobody who is not	An active licence for the builder, and the builder itself, because the pages need it to render
Custom theme with custom blocks	Writes a theme, then builds blocks and fields for your content types so each block has a fixed shape and style	Editors, inside the blocks they are given, with far less chance of breaking a page	A developer on call, and the code sitting in a repository you control

These are not three price points on one scale. They are three different quantities of labour, which is why a pile of WordPress quotes for one brief spreads wider than quotes for the same brief on a closed platform. Our page on what a web build costs by scope carries the US bands by project size, so this one stays on the part that is specific to WordPress.

Five questions that pick the build for you

• How often will the site change? A site that gains a page a week needs an editing experience somebody will use. A site that changes twice a year does not justify paying for one.
• Who will do that changing? Name the person. For an office manager who has never edited a website, a builder interface and a custom block set are two very different days.
• How many layouts do you really need? Most sites run on five or six: home, service, landing, listing, article, contact. Agencies quote per page, so price per layout instead and the number usually falls.
• Does anything have to connect? A booking system, a CRM, a stock feed or a payment gateway moves the job from configuration to development, whichever build you pick.
• How long is this site meant to last? A three year site and an eight year site deserve different answers, and owning the code only starts to pay on the longer one.

If those answers all come out small, a WordPress agency may be more than the job needs. One experienced freelancer configuring a well supported commercial theme is the right purchase for a great many small sites. An agency earns its fee when there are several content types, an integration, or a group of people who will all be editing.

Page builder lock in, described plainly

A page builder keeps your layout in its own format inside the post record. Switch the plugin off and the pages do not fall back to plain content, they render as shortcodes or unstyled markup. That is what lock in means here, and it has three consequences worth putting in the contract.

• The licence is a running cost. Pro versions are sold annually and the payment buys updates. Let it lapse and the site keeps working while falling behind on security fixes.
• Rebuilding is the exit, not exporting. Moving to a different builder, or to core blocks, means rebuilding the pages. Budget for that when you choose, not when you leave.
• Core blocks are the conservative option. Content made with the block editor that ships with WordPress is stored as HTML, so it stays readable even if every other decision is reversed later.

None of that makes a builder the wrong choice. It makes it a named dependency. Ask which builder, who holds the licence, and what happens if the plugin changes hands.

The handover list, in WordPress terms

This is the part that decides whether you are tied to the agency. Get all of it before the final invoice is paid, and check each line yourself.

• An Administrator account in your name, on an email address you control. Not a shared login, and not one the agency can remove.
• The hosting account and the domain registrar in your company's name, with the card in your name. If the agency resells hosting, get the plan, the price and the cost of leaving in writing.
• Licence keys for every paid item: theme, builder, forms, custom fields, caching, any premium add on. In your name, with renewal dates listed.
• The theme and any custom plugin in a repository you can access. A child theme is normal, but you need both halves documented.
• A full export, database plus uploads folder, taken after launch and stored somewhere that is not the agency's laptop.
• A list of custom post types, taxonomies and field groups and what each is for. Without it the next developer spends a billable week reading the database.
• A staging site, or instructions for making one, so updates are tested before they reach the live site.
• No agency plugin that has to stay installed for the site to work. If there is one, it belongs in the handover as code.

The test before final payment: could a different developer take the site over using nothing but this list?

Making the site genuinely editable by your own team

An editable site is a build decision, not a training problem. Give your team fixed shapes to fill rather than a blank canvas with full styling control, because a blank canvas is how sites drift. Four things do most of the work: block patterns for the layouts you repeat, template parts for the header and footer, named fields for content that must always be present, and the Editor role rather than Administrator for everyone who only writes. Ask for a short written note on adding each page type, before handover. Search settings are a separate conversation, and the plugin and indexing decisions sit on our WordPress SEO page.

What a WordPress buyer still needs settled

Should the agency use a page builder or write a custom theme?

A builder suits a site with many one off layouts and a team who want to arrange pages themselves. A custom theme with blocks suits repeating content types, a defined design system and a longer life. Watch how much of the design depends on the builder, because that is how much depends on the plugin staying alive.

Who should hold the plugin licences?

You should, in your company's name. Agencies often buy developer licences covering many client sites, which is legitimate and cheaper, but the key is theirs. Agree in writing what happens when the relationship ends: either the licence transfers, or you buy your own and the agency installs it.

How much maintenance does a WordPress site actually need?

Core, theme and plugin updates on a cycle, tested on staging first; a PHP version check once a year; offsite backups with a restore somebody has actually tried; and a log of what changed. Price it as a line item with a stated response time, and keep the right to do the work yourself.

Can another agency take over a page builder site?

Yes, and it happens constantly. The new agency needs the licence, the hosting and admin access, and it will charge to learn a structure somebody else designed. Pages built in a builder it does not use are the part it will quote to rebuild, so get that quote before you move.

What should I check on launch day?

That you can log in as Administrator and change a headline; that form submissions arrive in your inbox and not the agency's; that hosting and licence receipts carry your name; that a backup exists somewhere other than the live server; and that search engine visibility is switched on, because leaving it off is the most common reason a new site is missing from Google.

The part of the build that decides what an assistant can quote

A WordPress page is text in a database rendered by a theme, and the theme decides what anything reading the page can see. That matters more than it used to, because buyers now ask ChatGPT, Gemini or Perplexity who builds sites in their category, and those answers are assembled from text. Builds that load the important facts into hero images, sliders, closed accordions and icon captions leave very little to work with, because the prices, the service names and the service area have all become pixels. Put the facts in real text inside the blocks and a WordPress build reads as well as any other. AI Knows Us puts a buyer's question to ChatGPT, Gemini and Perplexity and reports back the pages each one read to answer it, which is how you find out whether a new build made it: aiknowsus.com.