How to Choose a WordPress Development Agency: 12 Questions to Ask Before You Sign
If you want to know how to choose a WordPress development agency, here is the compressed version: pick the team that can show you the code behind their portfolio, explain in plain language how your site will still be fast and secure two years from now, and put scope, price and the post-launch guarantee in writing before you sign. Everything else — awards, office size, the length of the proposal — is noise.
The reason this matters is that WordPress is both the easiest platform to build on and the easiest to build badly on. Two agencies can quote the same price for the same sitemap and deliver sites that differ by a factor of ten in load time, maintenance cost and how often your marketing team has to open a support ticket. The difference is not visible in a design mock-up. It is visible in the answers to twelve questions.
This guide gives you those twelve questions, grouped into engineering, process, commercial terms and life after launch, with the answer you should expect to hear from a serious WordPress development partner and the answer that should make you walk away. It ends with a comparison of the three kinds of provider you will meet and a short list of red flags.
Before you start: decide what you are actually buying
Most agency selections go wrong before the first call because the buyer has not separated three different purchases: a design, a build, and a relationship. A brilliant design studio can hand you a Figma file that no WordPress developer can implement without a page builder and forty plugins. A cheap build shop can implement anything, badly. And the relationship — who answers the phone when checkout breaks on a Friday — is the part most contracts forget.
Write down, in one page, what the site has to do for the business (leads per month, demo bookings, orders, a sales cycle you want to shorten), what it must integrate with, and who on your team will be editing it every week. That page is the brief. Every question below is easier to score when you have it. Our process page shows how we turn that brief into a fixed scope before any design starts.
How to choose a WordPress development agency: the engineering questions
1. Can we see the code, not just the screenshots?
Ask for a link to a live site they built and open it in Chrome DevTools. Look at the page source. You are checking for a custom theme with a small number of stylesheets and scripts, rather than a marketplace theme with a page builder and dozens of plugin assets loading on every page. Ask whether they will show you a repository from a comparable project under NDA. An agency proud of its engineering will say yes without hesitation.
Good answer: “Here is a staging link, here is the repo, here is the theme’s block directory.” Bad answer: “Our sites are built on a premium theme we customise for each client.”
2. What is your architecture for keeping components isolated?
This is the question that predicts whether your marketing team will be able to change the site without breaking it. In a well-engineered WordPress site, every section — hero, pricing table, testimonial carousel — is a self-contained block with its own markup, styles and script, registered through block.json and loading its assets only on pages where it appears. Change the pricing block and nothing else moves.
In a poorly engineered site, one global stylesheet and a page builder mean every edit risks side effects elsewhere. We explain the approach in detail in our guide to modular WordPress block architecture. If the agency cannot describe something similar, expect to be calling them for every change.
3. What Core Web Vitals do you commit to, and on which device?
Google’s Core Web Vitals thresholds are public: Largest Contentful Paint at or under 2.5 seconds, Interaction to Next Paint at or under 200 milliseconds, Cumulative Layout Shift at or under 0.1. The important qualifier is “on mobile”, because mobile Lighthouse runs on a throttled connection and a slow CPU, and it is where the majority of your traffic is. An agency that only quotes desktop scores is quoting the easy number.
Ask what happens if the launched homepage does not meet the target. We put it in the contract: Lighthouse mobile 90 or better on the launch homepage, or we keep working at no charge. If a prospective agency will not attach a number to their speed promise, treat the promise as decorative. Our Core Web Vitals guide for marketing teams will help you understand the metrics well enough to hold them to it.
4. How do you handle security, and what does “secure at launch” mean?
You want to hear specifics: a web application firewall, two-factor authentication on all admin accounts, file editing disabled in wp-config.php, least-privilege user roles, automatic updates on a staging-first workflow, a plugin policy that limits the count and vets each one’s maintenance history, and a vulnerability scan (WPScan or equivalent) with zero critical findings at launch. Ask who receives the alert when a plugin you use gets a CVE.
Vague answers (“we use a security plugin”) mean security has been delegated to a plugin’s default settings. That is how most WordPress breaches start.
The process questions
5. Who exactly will work on our project, and how senior are they?
Agencies sell with their best people and deliver with whoever is available. Ask for names, roles and years of experience for the strategist, designer and lead developer who will be on your project, and ask whether any of the work is subcontracted. A senior-only team is more expensive per hour and cheaper per project, because senior developers do not build the same feature three times.
6. What does the timeline look like week by week, and what do you need from us?
A credible agency will give you a phased plan with named deliverables and client checkpoints: discovery and content audit, wireframes, design, build, QA and launch. For a typical 8–12 page marketing site that is five to seven weeks. For a WooCommerce or multilingual platform, ten to fourteen. Be suspicious of anything much shorter unless the scope is genuinely a single page, and of anything vague (“depends on feedback cycles”), which is usually code for no plan.
Also ask what they need from you and when. Most delays on agency projects are caused by late content and slow approvals. A good partner will tell you that up front and structure the schedule around it.
7. How do you handle SEO during a redesign or migration?
If you already have organic traffic, the redesign is the riskiest thing you will do to it this year. The agency should describe a URL inventory, a one-to-one redirect map, preservation of title tags, meta descriptions and structured data, staging blocked from indexing, and a post-launch crawl to catch 404s. If they say “we will install an SEO plugin”, they have not done this before. Our 31-step WordPress website redesign checklist is the standard we hold ourselves to; ask any agency to walk you through theirs.
8. What is your response time when something breaks?
Get this in writing, with hours. “We respond within four business hours during your business day” is a commitment. “We are always available” is not. Ask which time zones they cover; an agency in Central Europe serving US clients should be explicit about overlap with US Eastern hours.
Want a second opinion on the site you have now? Drop your URL and a senior strategist will record a free 15-minute teardown of its speed, structure and conversion leaks — within 48 hours.
The commercial questions
9. Is the price fixed, and what exactly is in scope?
Hourly billing puts all the risk on you. Fixed-scope pricing puts the risk on the agency, which is where it belongs, because they are the ones who can estimate the work. The trade-off is that fixed scope requires a precise scope document: pages, templates, blocks, integrations, content migration volume, languages, and the number of revision rounds. Read it. Anything not listed is a change order.
For orientation, a custom-designed, custom-built WordPress marketing site of 8–12 pages from a senior team in the US or EU typically lands in the high four to low five figures; e-commerce and multilingual platforms run higher. Our own pricing is published for exactly this reason: a Growth Site from $18,000, a Platform from $45,000. We wrote a full breakdown in how much a custom WordPress website costs so you can benchmark any quote.
10. Who owns the code, the design files and the accounts?
The answer must be “you”, in the contract, for everything: theme code, custom plugins, design source files, the hosting account, the domain, and every third-party licence purchased for the project. Some agencies retain ownership of a “framework” they reuse across clients and license it to you. That is a lock-in mechanism. If you leave, you cannot take the site with you.
11. What is your guarantee, and what happens after launch?
A guarantee tells you what an agency is confident about. Ours is simple: Lighthouse mobile 90+ on the launch homepage or we keep working free, zero critical WPScan findings at launch, and 30 days of post-launch care included. Whatever the agency offers, check that it has a measurable trigger and a defined remedy. “Satisfaction guaranteed” has neither.
Then ask about ongoing care. Updates, backups, uptime monitoring, security scanning and a monthly block of development hours are what a real care plan contains. We covered what should be included in WordPress maintenance plans explained. If the agency has no maintenance offering at all, ask who they expect to look after the site.
12. Can we talk to two clients from the last twelve months?
Not the testimonial page. Two recent clients, on a call, chosen by you from their portfolio. Ask those clients three things: did the site launch on time and on budget, how fast did the agency respond when something went wrong, and can your marketing team edit the site without a developer. The third question is the one agencies least like to be judged on.
Freelancer vs generalist agency vs WordPress specialist
You will meet three kinds of provider. Each is right for some projects and wrong for others.
| Criterion | Freelancer | Generalist digital agency | WordPress specialist studio |
|---|---|---|---|
| Typical project fit | Small sites, fixes, single landing pages | Brand-led projects where the CMS is secondary | Growth and platform sites where performance and maintainability matter |
| Engineering depth | Varies widely; depends on the individual | Often outsourced or junior; page builders common | Custom block themes, performance and security as standard |
| Bus factor | One person | Team, but WordPress may not be their core skill | Team with WordPress as the core skill |
| Speed and CWV commitment | Rarely contractual | Rarely contractual | Should be contractual |
| Price band (8–12 page site) | Low four figures to low five | Mid five figures and up, design-weighted | High four to mid five figures, engineering-weighted |
| Ownership and lock-in | Usually clean | Check for proprietary frameworks | Should be clean; verify in contract |
| Post-launch support | Ad hoc | Retainer, often expensive | Structured care plans |
A representative pattern we see in teardowns: a mid-market company hires a generalist agency for a beautiful rebrand, the site launches on a page builder with a mobile Lighthouse score in the 30s, and eighteen months later they hire a specialist to rebuild it on a proper architecture. The second project costs about as much as the first. Knowing how to choose a WordPress development agency at the start would have cost one project, not two.
Red flags that should end the conversation
- They cannot name the theme architecture. If the answer to “custom theme or page builder?” is evasive, it is a page builder.
- No staging environment. Editing production directly is not a workflow; it is an incident waiting to happen.
- Speed is described as a “plugin we install”. Caching plugins help; they do not fix a bloated front end.
- The proposal is a template. If your company name is the only thing that changed, so is the site.
- Hosting is bundled and not transferable. You should be able to move hosts without the agency’s permission.
- They promise rankings. No one controls Google. An agency can promise a technically sound, fast, crawlable site; that is all.
- Unlimited revisions. Sounds generous, signals that scope and schedule are not managed.
How to choose a WordPress development agency with a scoring sheet
Take the twelve questions into every call and score each answer from 0 to 3: 0 for evasive or absent, 1 for generic, 2 for specific, 3 for specific and backed by evidence (a link, a document, a contract clause). A serious WordPress development agency should score 28 or higher out of 36. Weight questions 2, 3, 9 and 10 double if your marketing team will be editing the site weekly or if organic traffic is a meaningful revenue channel.
The purpose of scoring is not precision; it is to stop the decision being made on the strength of the design deck. Design can be evaluated in ten minutes. Engineering, process and commercial terms are what you live with for three to five years, and they are what these questions surface.
If you would like to see how we answer all twelve, our WordPress design and development service page lays out the architecture, the guarantee and the team, and our work shows the results.
Key takeaways
- How to choose a WordPress development agency comes down to engineering, process and commercial terms, not the design deck; a mock-up tells you nothing about speed, security or maintainability.
- Ask to see code and a repository. A custom block theme with isolated components is what lets your team edit the site without a developer.
- Demand a contractual Core Web Vitals commitment on mobile, with a remedy if it is missed.
- Fixed-scope pricing with a precise scope document beats hourly billing; you should own all code, files and accounts outright.
- Speak to two clients from the last year and ask whether they can edit the site themselves.
- Score every agency against the same twelve questions so the decision is comparable, not emotional.
The lowest-risk way to evaluate any agency, including us, is a small fixed-scope engagement. Our 7-Day Homepage Sprint delivers a fully built, Core Web Vitals-green homepage in one week for a fixed $4,900, credited toward a full build if you continue within 60 days. You see the code, the speed and the working relationship before committing to anything larger.
Frequently asked questions
Look for a custom block-based theme rather than a page builder, a contractual Core Web Vitals commitment on mobile, a documented security process, a senior named team, fixed-scope pricing with a precise scope document, full ownership of code and accounts, and a structured post-launch care plan.
For a custom-designed 8 to 12 page marketing site from a senior US or EU team, expect the high four to low five figures. E-commerce, membership and multilingual platforms typically start in the mid five figures. Hourly rates vary widely, which is why fixed-scope quotes are easier to compare.
A freelancer suits small sites, fixes and single landing pages. For a growth or platform site where speed, security and maintainability matter, a specialist WordPress studio with a senior team and a guarantee is the lower-risk choice, and generalist agencies are best when brand work outweighs the CMS.
Ask to see code from a live project, how they isolate components, what Core Web Vitals they commit to on mobile, how they handle security and SEO during a migration, who will work on the project, their response time, whether the price is fixed, who owns the code, what the guarantee is, and whether you can speak to recent clients.
Evasive answers about theme architecture, no staging environment, speed described only as a plugin, templated proposals, non-transferable bundled hosting, promised search rankings and unlimited revisions are all signs to walk away.