Choosing a WordPress agency in 2026: what actually matters

#Choosing a WordPress agency in 2026: what actually matters

#Why most comparisons start in the wrong place

A typical selection process looks like this: Google search, browse five websites, fill in three contact forms, compare quotes, decide on price. The problem is not the sequence but what is missing before it: a written definition of what is actually being commissioned.

Without a brief, you are not comparing quotes - you are comparing moods. Agency A prices a leaner website because it did not understand your product architecture. Agency B prices a more thorough one because it looked closely. The comparison now tells you that A is cheaper - when in fact B simply read more carefully. This is the most expensive mistake in the whole process, and it happens before the first sales call.

The second systematic error: comparisons are decided on criteria that stop mattering the day the site launches. The portfolio shows the ten best screenshots from five years; it does not show whether the agency answers the phone after launch, whether it runs maintenance as a real business line, or whether it will hand over the code at all. All three questions predict your satisfaction better than any redesign ever will.

The third error is the mirror image: comparisons that run on price alone punish careful agencies. Whoever prices staging environments, code reviews, GDPR processes and documentation into a quote will visibly land above the agency that skips all of it. If you only see the price, you reward the omission. The checklist in this article exists to make those omissions visible.

#The checklist: eight criteria for the comparison

The following eight points work as an interview guide and as a quote checklist. Print them out, note each agency’s answer against each point, and at the end you will have something solid instead of three pretty PDF decks.

#1. Scope: what exactly is being delivered?

Before you request quotes, write a short brief yourself - one page is enough. Which pages exist, which features must survive or be created, which languages, which systems need integrating (ERP, CRM, newsletter), who supplies content and imagery, where the deadline pressure is real and where it is not.

A good agency asks follow-up questions about this document and says openly what it has not yet seen or cannot deliver. An agency that returns a fixed-price quote for a multi-week project within 24 hours, without a single follow-up question, has not calculated - it has guessed. The bill arrives later as a change request, and change requests are the number one reason website budgets collapse mid-project.

Make the point verifiable for both sides: “Changes to scope are agreed in writing with price and schedule impact.” If an agency refuses that clause, it is not a detail - it is an announcement that change requests are the business model.

#2. Staffing: who actually works on your project?

Agencies primarily sell continuity - but continuity only exists if you know who delivers it. Ask for the names and seniority of the people on your project: who is the responsible senior developer, who does design, who handles maintenance after launch?

Legitimate answers name people, roles and rate bands. A common and legitimate pattern: one senior developer leads and reviews, one or two juniors handle documented routine tasks. A warning pattern is different: the quote promises “a team of specialists” and staffing is decided “subject to availability” only after signature. Subject to availability usually means, in practice: whichever developer currently has nothing else to do.

Also ask about the bus factor: if your lead developer resigns, who else knows the code? An agency with a documented workflow, code reviews and version control answers that question comfortably. An agency built on one person dodges it - and that dependency is exactly what you would be buying.

#3. Performance: targets with numbers instead of slogans

“We build fast websites” is not a statement you can compare on. Every agency says it. The point becomes comparable only with concrete targets: which Core Web Vitals (LCP, INP, CLS) should realistically be reached on which device class, how will they be measured, and what happens if the targets are missed after launch with real content and real plugins?

An experienced agency knows the limits of these metrics and tells you which of them sit on your side of the fence: oversized hero images from marketing, third-party tracking that eats your load time, a booking widget you insist on keeping. A less serious agency promises benchmarks that are unreachable on your configuration and then discusses “tolerated deviations” after launch.

Put it in the quote: performance targets, the measurement method (for example a lab test on a defined test page plus field measurement after four weeks with real traffic) and a remediation commitment within the warranty period.

#4. Security: process beats promises

Weak agencies answer security questions with adverbs (“highly secure”, “state of the art”); strong agencies answer with processes. Ask about five concrete things: the update policy for WordPress core, themes and plugins; how access is managed (passwords, 2FA, individual accounts instead of shared admin logins); whether staging environments exist and whether updates are tested there before production; how backups are structured (frequency, retention, separate storage location, restore testing); and how the agency reacts to an active compromise - who is informed when, and who decides about downtime.

One point deserves special attention because it is almost never checked in comparisons: the plugin strategy. Ask how the agency thinks about plugins. Good answers sound like “as few as possible, every plugin has a documented purpose, no functionality spread across seven overlapping plugins.” Bad answers sound like “we’ll figure that out.” Every additional plugin is a second update topic, a second security topic and a second compatibility risk - permanently, not just on launch day.

#5. Maintenance: what happens after launch?

Most regret in the WordPress world does not happen on launch day but in the year after: the agency is busy with new projects, updates get postponed, and six months later the site is outdated and the gap between “built then” and “maintained now” is so large that no new agency will take it over without a fresh discovery phase.

So treat the maintenance path as its own criterion, whether or not you plan to buy it: Does the agency offer maintenance as a contract with defined deliverables (update cycles, backups, monitoring, security response), with response times as a contractual quantity rather than an intention? What does maintenance involve qualitatively? And what happens if you buy maintenance elsewhere or take it in-house: is there a documented handover, admin access, a list of plugins and custom code?

For what a good maintenance contract contains, see our own page on WordPress website maintenance - regardless of whom you hire: an agency without a maintenance path and without a handover concept builds you an object nobody wants to touch in eighteen months.

#6. Contract, currency and consumer rights

The contract is the only document that remains when everything else is disputed. Four checkpoints:

Ownership and handover. You are buying work product, not renting a platform. The code, the designs and the content belong to you after full payment - including the rights to custom development (custom plugins, blocks, themes). An agency that releases code only for an extra fee, or not at all, has not built a sellable product; it has built a dependency.

Invoicing and currency. For European clients, invoicing in euro with a SEPA payment route is the comfortable baseline: no exchange-rate exposure, no expensive cross-border payment fees, clean VAT treatment. When hiring across borders, an EU contracting party invoicing in EUR is what you should expect and demand.

Consumer and withdrawal rights. If you commission as a small business or consumer, EU-wide consumer law applies: withdrawal information for distance contracts, clear rules on partially delivered work, transparent cancellation terms. Ask the agency how it handles this - the answer tells you whether you are dealing with a serious EU contractor or a letterbox operation.

Warranty and remediation. What happens to defects that surface after launch? Serious agencies cleanly separate warranty (fixing defects in the delivered scope), maintenance (ongoing care) and change requests (new scope). Whoever lumps all three together either misunderstood the scope or plans to bill every follow-up question.

#7. Communication: cadence and written-first working

Projects fail less often on technology than on unspoken expectations. So ask about the communication rhythm: weekly written status reports or ad-hoc emails? Who is your contact person, and who deputises during holidays? How long does a reply to a normal request realistically take - and what about escalating problems?

For cross-border engagements - a Polish, Austrian or Swiss agency serving a Western European client - there is a simple test: clear, complete written communication in the agreed contract language must already work during the pitch phase. An agency that answers incompletely while trying to win your business will show the same weakness under project stress, only more expensively.

Written-first is also the legally sound expectation: scope changes, schedule shifts and approvals belong in writing. An agency that holds calls and then sends a written summary is the comfortable case. An agency that makes important agreements only verbally is building a dispute for you, with the burden of proof on your side.

#8. IP, ownership and the dependency question

This overlaps with the contract but goes further: do not just ask what the contract says - ask what technically happens if you switch agencies tomorrow. Can you get a full backup of the site including database and media library without having to ask the agency for a favour? Is the hosting registered in your name or the agency’s? Who owns the domains? Are premium plugins licensed to your company or to the agency?

The answers reveal whether you are buying a supplier or a dependency. Neither is automatically wrong - dependency you know about and choose deliberately is a business decision. Dependency you discover during a dispute is a trap. Serious agencies can produce an “exit documentation” on request: a list of credentials, licences, hosting accounts and custom code. If an agency does not know the term or pushes back on it, you have learned something more valuable than any portfolio impression.

#Cross-border must-haves when hiring inside Europe

The eight criteria above apply everywhere. Four points deserve extra attention when you compare agencies across European borders - and they separate agencies that genuinely serve international clients from those that treat “international” as a brochure word.

#GDPR and data processing

Ask every agency for three things: a data processing agreement under Article 28 GDPR that the agency offers as a processor; the hosting locations (EU hosting is the clean solution for most European mid-market companies); and how it handles third-country tools (US tracking, US CDN, US form providers) that it deploys by default. An agency with cross-border experience has ready answers and documents for all three. An agency that needs to “check with legal” during the project will learn on your invoice.

#Accessibility: build it in, not on top

Whether or not your site falls under the EU Accessibility Act or national implementations such as Germany’s Barrierefreiheitsstärkungsgesetz, the direction of travel is unmistakable: accessibility requirements are spreading, enforcement is maturing, and a site built accessible from day one costs once - a site retrofitted later costs twice. Ask the agency where it stands: are contrast, keyboard operation, focus handling and semantic HTML built in from the start? Do they have experience with WCAG conformance checks? An agency that treats accessibility as “a paid special request” has missed where the market is going.

#Euro contracts and payment route

Expect invoices in EUR, SEPA transfer, clean VAT details, and - for Swiss engagements - the usual adjustments to local tax handling. Check this before signing, especially with non-EU or cross-border partners: Is invoicing in EUR? How is VAT handled (reverse charge for EU partners)? Is there an EU bank route that accepts SEPA transfers without extra fees? These questions sound mundane, but they reliably filter out agencies that have never genuinely operated across borders.

#Written communication as a working style

European mid-market clients generally run written-heavy workflows: quotes, minutes, approvals, follow-ups. That is not a stylistic preference; it is risk management. Ask the agency explicitly how it documents commitments. The right answer contains the word “written” and a tool (email, project tool, minutes). The wrong answer contains the word “phone”.

#The price question: think structurally, read the details

How much does a WordPress project actually cost? The honest answer: it depends on scope, staffing, migration load and maintenance needs - and the spread between agencies comes overwhelmingly from those factors, not from “cheap versus quality”. The structural logic: agencies in high-wage Western European markets price in office costs and long sales paths; offshore agencies price in lower wage levels, but leave communication, legal coverage and handover risk with you unless the contract says otherwise. The smart comparison does not ask “who is cheapest” but “which price components does this quote rest on, and which of them can I verify?”

We deliberately publish no numbers in this article, because they move with the market and the engagement - our current price structure is documented transparently on the WordPress pricing page. Use pages like that as a benchmark for the structure of the quotes you receive: if your quote shows no comparable components, you know what to ask next.

#Red flags: five warning signs

One warning sign in first contact does not make the other criteria obsolete - but one is enough for a very pointed follow-up question, and two are enough to walk away.

1. Guaranteed rankings. “We guarantee you first place on Google” is not a service commitment; it is a breach of basic market literacy. Nobody can guarantee rankings, because nobody controls the algorithm or your competition. An agency that makes such promises should not be trusted with a website whose visibility matters to you.

2. No maintenance path. The agency sells the launch brilliantly, but asked about maintenance, updates and security response afterwards, it offers a shrug or a “let’s discuss that later”. In practice that means: you inherit a website with no named owner - and in eighteen months you finance the next full rebuild.

3. Plugin pile-ups as a strategy. When the agency’s answer to every requirement is another premium plugin - page builder plus forms plugin plus popup plugin plus optimisation plugin plus security plugin - you are not buying a solution, you are buying a stack of future update conflicts. Ask about the strategy behind it and the honest answer is usually missing: custom development competence is absent, and every plugin purchase is a commitment to deferral.

4. No staging environment. Updates, new plugins and editor training belong on a test environment, not on the live site. An agency without a staging workflow will eventually push a plugin update straight to production - and that day you pay for the downtime a staging environment would have prevented.

5. Unclear ownership. Hosting, domain, plugins and code sit in the agency’s name, and the answer to what gets handed over on a switch stays vague. That need not be fraud - often it is simply a business model that makes leaving expensive. But it is your risk, and it grows with every project month.

#Ten questions and what a good answer sounds like

Ask these ten points in the second round - after the first quote, before the signature. Write the answers down verbatim; you will need them when you decide between two agencies.

1. “Who exactly will work on my project, and in what role?” A good answer names people, roles and bands: “Ms X leads the project, Mr Y is the responsible senior developer, two juniors handle documented subtasks under review.” A bad answer sounds like “our experienced team” and describes no people.

2. “What is your update and security process in detail?” Good: update cycles, staging tests before production, individually assigned admin accounts with 2FA, backup frequency and restore testing, a named contact in an incident. Bad: “We work to the highest security standards.”

3. “How many plugins do you use, and why?” Good: “As few as necessary, every plugin has a documented purpose, and functionality we can build cleanly ourselves, we build ourselves.” Bad: a list of ten plugins plus the note that this is all “standard”.

4. “What happens if the performance targets are missed?” Good: a named measurement method, concrete target values for defined checkpoints and a remediation commitment inside the warranty. Bad: “Our sites are always fast.”

5. “What does a handover look like if we part ways in two years?” Good: the agency describes an exit documentation unprompted - a credentials list, licences in the client’s name, code handover, database export, a short handover session with your next agency. Bad: visible irritation at the question itself.

6. “How do you document scope changes?” Good: “Every change is confirmed in writing with price and schedule impact before it is implemented.” Bad: “We’ll sort that out as we go” - meaning: verbally, unmeasurable, unprovable in a dispute.

7. “How do you ensure GDPR compliance?” Good: the agency produces a data processing agreement, names EU hosting locations, knows the third-country issues with common tools and clarifies the split between you as controller and it as processor. Bad: “We take care of data protection.”

8. “Can you build accessible websites, and what does that mean concretely?” Good: contrast, keyboard operation, focus handling, semantic HTML, experience with WCAG audits - plus an honest assessment of how much of that belongs in your project. Bad: “Yes, sure” without a single concrete example.

9. “What does your status report look like, and how often does it come?” Good: weekly and written, with completed items, open items, risks and the next step; a named contact and a deputy. Bad: “We’ll get in touch when there’s something to report.”

10. “What belongs to us in the contract, and what to you?” Good: after full payment, code, design and content including the rights to custom work transfer to the client; licences run in the client’s name. Bad: “We keep that flexible” - flexibility here is a synonym for dependency.

A note on applying these: the questions are built so that good answers are concrete and bad answers are general. That is no accident - concreteness costs nothing, but it requires knowledge, and knowledge requires experience. An agency that answers ten questions concretely has lived through those situations. An agency that answers ten questions generally has lived through something else: a great many sales meetings.

#When a Polish agency with a European focus fits - and when it does not

We are ourselves a Polish agency with a European focus and have run this model for years, so we can be more honest here than any neutral guide: there are cases where our model is the right choice, and cases where we would advise against it ourselves.

Our model fits when:

• Written communication carries the project. We work remotely from Gdynia, Poland, and communicate in German and English - in writing, completely, with a written reply usually within one business day. If your organisation already runs project communication over text (email, tickets, documentation), you lose nothing to the distance.
• Euro invoicing and the EU legal framework matter. We invoice in EUR with SEPA payment, operate under EU consumer law including withdrawal rights and consent forms, and GDPR compliance is standard for us, not a special request.
• Senior quality at reliable terms is the goal. The wage structure in Poland lets us assign senior developers where Western European agencies must price the same staffing significantly higher because of their cost base - with the same tooling, the same review standards and the same documentation discipline. How we handle requirements in specific markets, we describe on our pages for WordPress development in Poland, Vienna and Austria and Zurich and Switzerland.

Our model does not fit when:

• Regular on-site presence is required. Workshops in your meeting room, on-site training, spontaneous walkthroughs: this is where an agency in your city is objectively better than any remote partner. We travel for multi-day workshops - but if you expect weekly presence, we are not the right model.
• Your project needs local legal advice. We build sites that implement GDPR processes cleanly in technology. We are not a law firm. If you need binding legal advice on data protection, employment or contract law, you need a lawyer - not an agency, from any country.
• Your site tolerates no hours of downtime. We work remotely with defined response times, but if your business model needs minute-level application response guarantees, look at a provider that can contractually guarantee 24/7 on-call coverage - and budget accordingly.

Either way: ask. Describe your project through the contact form and you will usually receive a written reply within one business day with the next steps - and if we are not the right model for your case, we will tell you that too. A selection process in which an agency disqualifies itself honestly is a good selection process.

#The summary as a table

The whole checklist at a glance - qualitative, without prices, because prices without scope and staffing are meaningless:

#Next step

If you have several quotes on the table and are considering us as one of the candidates: describe your project through the contact form - you will usually receive a written reply within one business day, with concrete answers and, if we are not a fit, an honest decline with a reason.