How to Choose a WordPress Development Agency: 12 Questions to Ask Before You Sign

Choosing the wrong WordPress development agency is an expensive mistake.

Not just in money — though a failed project can easily cost $15,000–$50,000 in wasted fees, rebuilds, and lost time. The deeper cost is ownership disputes, disappearing contractors, and the discovery that the “senior developer” on your project was a junior freelancer with limited supervision. By the time you realize something is wrong, you’re six months in and the budget is gone.

This guide is written for buyers who are at the decision stage. You’ve already done your research. You have a shortlist. Now you need a framework for separating the agencies that will deliver from the ones that will leave you worse off than before you started.

These 12 questions — asked directly, before you sign anything — give you that framework.

Why the Vetting Stage Is Where Projects Are Won or Lost

Most clients evaluate agencies on two criteria: price and portfolio. Both matter, but neither is sufficient.

Price tells you the cost of the engagement, not the cost of the project. An agency at $8,000 that delivers 60% of what you need and disappears after launch is more expensive than one at $15,000 that delivers everything and supports you for a year post-launch.

Portfolio tells you what an agency has done, not how they work, who does the work, or what happens when things go wrong. A portfolio of beautiful sites can mask a process that doesn’t survive contact with a real client project.

The 12 questions below are designed to surface what a portfolio and a price sheet cannot.

Question 1: Can I See Examples of WordPress Projects Similar to Mine?

Every agency shows their best work. Ask specifically for examples that match your project type, complexity, and industry — not their most visually impressive launch.

What to look for (green flags):

• Portfolio examples that closely match your scope (e.g., if you need WooCommerce + custom booking, ask to see e-commerce projects with third-party integrations)
• Willingness to walk you through a project rather than just show screenshots
• Case studies that describe the problem, not just the solution — what was the client’s challenge? How did they solve it?

Red flags:

• A portfolio full of brochure sites when you need a complex application
• No examples in your industry (not a dealbreaker, but notable)
• Resistance to explaining the technical approach behind past work
• Portfolios without client references attached

Go deeper: ask for a 15-minute walkthrough of one relevant project. How the agency explains past work — what they’re proud of, what they’d do differently — tells you more than the screenshots.

Question 2: What Is Your Development Process?

A professional agency has a defined process from discovery through launch. The specific steps matter less than whether the process exists and whether the agency can articulate it clearly.

A solid process typically includes:

1. Discovery / requirements — structured intake to define scope, goals, and technical requirements before any design or development begins
2. Design — wireframes and visual mockups approved before development starts (not the other way around)
3. Development — staged delivery with milestones, not a single “here’s the whole site” handoff at the end
4. QA — dedicated testing phase against documented acceptance criteria, not just “the developer checked it works”
5. Launch — planned deployment with rollback capability
6. Post-launch — a defined support period and handoff documentation

Green flags: They can describe each phase, what you’ll receive at each milestone, and what your responsibilities are as the client.

Red flags: Vague process descriptions (“we build it and you review it”), no defined milestones, or a process that skips discovery and goes straight to design. Projects that skip discovery almost always expand in scope and budget.

For reference on what a professionally managed development project should look like, our post on how to choose a web development partner covers the engagement model in more detail.

Question 3: Who Will Actually Work on My Project?

This is the single most important operational question you can ask. The answer you get from the sales conversation is often not the answer to who actually builds your site.

Ask explicitly:

• “Who are the specific people who will work on my project?”
• “Is this a dedicated team or a pooled resource model?”
• “What is the seniority level of the developers assigned to my project?”
• “Will I have the opportunity to meet them before we start?”

Green flags: The agency introduces you to the actual developers or team lead before the contract is signed. They can describe team members’ specific experience. They have a dedicated team model where you have a consistent point of contact throughout the project.

Red flags: “We assign the best people available” (translation: whoever isn’t busy). Inability or reluctance to introduce the team before signing. Heavy reliance on subcontractors or freelancers without clear quality oversight.

If continuity is important to you — especially for complex or long-running projects — ask about the dedicated development team model specifically. This structures the engagement so you have named, consistent developers working exclusively or primarily on your project.

Question 4: How Do You Handle Communication and Project Updates?

Communication failures kill projects. Not technical incompetence — communication gaps that let small misalignments grow into expensive misunderstandings.

What a good communication structure looks like:

• A single point of contact (project manager or lead developer) for all client communication
• Defined update cadence (weekly status calls, bi-weekly demos, etc.)
• Shared project management tool where you can see task progress without chasing emails
• Clear escalation path if issues arise
• Response time SLA for non-urgent and urgent communications

Questions to ask:

• “What project management tools do you use?”
• “How often will I receive updates without asking for them?”
• “What’s your response time SLA?”
• “Who do I contact if my main contact is unavailable?”

Green flags: They already use a structured PM tool (Jira, Linear, Notion, Basecamp) and can invite you to the project board. They have proactive, not reactive, communication built into their process.

Red flags: “We’ll keep you updated by email.” No defined update cadence. The salesperson is also the project manager with no handoff process.

Question 5: What Is Your Pricing Model — Fixed, Hourly, or Retainer?

There’s no universally right answer here, but understanding the model’s implications protects you from scope disputes and billing surprises.

Fixed-price projects are best when requirements are fully defined upfront. You pay an agreed amount for an agreed deliverable. The risk: if your requirements change (and they usually do), every change is a change order with a negotiated price. Fixed-price works well for well-scoped, stable projects.

Hourly/time-and-materials is appropriate when the scope is genuinely uncertain. You pay for time regardless of output. The risk: without careful project management, hourly engagements can balloon. The upside: you can adjust scope without formal change orders.

Retainer/monthly is the right model for ongoing development, maintenance, and feature work. You commit to a monthly capacity and the agency delivers against a prioritized backlog. Best for long-term engagements where you’re continuously building.

What to ask:

• “How do you handle scope changes under a fixed-price model?”
• “What are typical reasons projects exceed the estimated budget?”
• “What’s included in and excluded from the quoted price?”

Green flag: They walk you through common scope-change scenarios and how each would be priced. Transparency here predicts behavior when the inevitable scope question arises mid-project.

Red flag: A very low fixed price with no clear scope documentation to back it up. Low prices for complex projects almost always mean either scope restrictions you’ll hit mid-project, or an agency relying on change orders for profitability.

Question 6: Do I Get Full Ownership of All Code and Assets?

This question should be in every agency contract. In practice, it sometimes isn’t.

What full ownership means:

• You own the source code, not just a license to use it
• You can move development to another agency without the original agency’s permission
• You can modify, extend, or redistribute the code
• Design assets, style guides, and documentation belong to you

What to watch for:

• Agencies that retain licensing rights to “their” code frameworks or components
• Contracts that grant you a license to use the code rather than full ownership
• Staging environments or repositories hosted on agency accounts that aren’t transferred at handoff

Practical step: Ask for the specific contract language on IP ownership before signing. If it’s not clear, ask for it to be made explicit. This is non-negotiable.

Question 7: What NDAs and Confidentiality Protections Do You Offer?

If your project involves proprietary business logic, unreleased product features, customer data, or competitive information, confidentiality matters.

What to cover in an NDA:

• What information is considered confidential
• How long confidentiality obligations last (perpetual for source code; time-limited for other information is standard)
• Whether the agency can name you as a client or show your project in their portfolio (you may want to restrict this)
• How confidential information is stored and who on the agency’s team has access

Green flag: The agency has a standard NDA they offer and can adjust specific clauses. They’re familiar with mutual NDAs.

Red flag: Resistance to signing an NDA, or NDAs that are so broad or poorly worded they aren’t enforceable.

Question 8: How Do You Handle Bugs and Revisions Post-Launch?

Every launch has issues. The difference between a good agency and a bad one is often what happens in the 30–90 days after launch.

What to establish clearly:

• How long is the warranty/guarantee period (the window where bugs are fixed at no charge)?
• What qualifies as a “bug” vs a “new feature request”?
• What is the response time for critical issues (site down, checkout broken)?
• What is the response time for non-critical issues?

Green flag: A written post-launch support policy with defined SLAs and a clear distinction between warranty work and paid change requests. At WebHelp Agency, our standard engagement includes a post-launch support period with defined response times before transitioning to a maintenance retainer.

Red flag: Verbal assurances of “we’ll take care of you” with nothing in writing. No defined warranty period. No critical incident response process.

Question 9: What Does Ongoing Support and Maintenance Look Like?

A launched WordPress site is not a finished product. It requires regular updates, security patches, performance monitoring, and occasional development work.

Questions to ask:

• “Do you offer ongoing maintenance services after the project is complete?”
• “What does your maintenance package include?”
• “How do you handle WordPress core, plugin, and theme updates?”
• “What’s your process for security incidents?”

Agencies that don’t offer maintenance often build sites, collect payment, and move on — leaving you to find ongoing support elsewhere. Agencies that offer structured maintenance typically build with maintainability in mind, because they know they’ll be the ones maintaining it.

For context on what comprehensive WordPress maintenance should cover, our post on WordPress maintenance tasks and best practices is a useful reference before these conversations.

Our WordPress site maintenance service includes core and plugin updates, uptime monitoring, security scanning, performance checks, and a monthly development hours allocation for minor updates.

Question 10: What Are Your Security Practices?

Security is not optional. WordPress powers over 43% of all websites on the internet (W3Techs, 2025) and is a consistent target for automated attacks. A site built with poor security hygiene is a liability from day one.

Ask specifically:

• “Do you conduct code reviews for security vulnerabilities?”
• “How do you handle user input sanitization and output escaping?”
• “Do you use parameterized queries to prevent SQL injection?”
• “Is penetration testing included in the scope or available as an add-on?”
• “What’s your process for a security incident after launch?”

Green flags: The developers can explain their security approach in technical terms (sanitization, escaping, nonce verification, capability checks). They follow the WordPress security checklist principles as standard practice, not an add-on.

Red flags: Vague answers like “we follow best practices.” No ability to explain specific security measures. No post-launch security monitoring offering.

Question 11: Can You Provide Client References or Case Studies?

Portfolios are curated. References are unfiltered.

How to approach references:

• Ask for 2–3 client references for projects similar to yours
• Contact them directly — don’t rely on the agency to facilitate
• Ask specifically: “Was the project delivered on time and on budget?” “Were there any significant issues — and how did the agency handle them?” “Would you hire them again?”
• Check agency reviews on Clutch and Upwork before shortlisting — these platforms carry verified client reviews that are harder to curate than a portfolio

What to look for in case studies:

• Specific results (not “we improved their site” but “organic traffic increased 40% in 6 months after the rebuild”)
• Honest acknowledgment of challenges and how they were resolved
• Client quotes that feel authentic, not PR-polished

Green flag: The agency proactively offers references before you ask. References respond enthusiastically and without prompting.

Red flag: “References available on request” that never materialize. References who give vague, non-specific answers.

Question 12: What Makes Your Agency Different from the Other 500 WordPress Agencies?

This is the honest question. There are thousands of WordPress agencies. The differentiators that actually matter:

• Specialization — do they specialize in your industry, your tech stack, or your project type? A generalist WordPress agency can handle most things; a specialist builds faster and with fewer mistakes on what they know deeply.
• Team depth — can they handle your project without being at capacity? What happens if your project manager gets sick?
• Communication quality — everything you’ve observed in this vetting process is a data point. An agency that responds promptly, communicates clearly, and asks smart questions during the sales process will do the same during the project.
• Ownership alignment — are they trying to sell you what you need, or what they’re comfortable building?

There’s no universally right answer to what makes an agency worth choosing. The right answer is specific to your project, your communication style, and your risk tolerance. But the question surfaces how clearly they understand their own strengths — and agencies that give vague answers here often have vague self-awareness about their limitations.

How to Compare Proposals Side by Side

Once you have proposals from 2–3 agencies, use this framework:

The cheapest proposal is rarely the right choice. The proposal with the clearest scope, the most direct answers to the 12 questions above, and the most credible references is almost always the better investment.

What a Good Engagement Contract Should Include

Before you sign, confirm the contract covers:

• Full project scope — detailed enough that “what’s included” is unambiguous
• Payment milestones — tied to deliverables, not calendar dates
• IP ownership clause — you own all code and assets outright upon full payment
• Change request process — how scope changes are requested, approved, and priced
• Timeline with milestones — not just a start and end date
• Warranty period — duration and what it covers
• Termination clauses — what happens if either party terminates mid-project
• NDA — if applicable, signed before project details are shared

For further reading on due diligence before hiring a web development partner, see our guides on how to hire a WordPress developer for your website and the benefits of working with a web development agency.

Frequently Asked Questions

Work With a WordPress Agency That Has Straight Answers to All 12 Questions

At WebHelp Agency, we’re a WordPress development team based in Ukraine, working with businesses and digital agencies across North America and Europe. We build custom WordPress sites, plugins, and integrations — with dedicated team models available for ongoing engagements.

We can walk you through our process, introduce you to your team lead before you sign, provide client references, and give you a detailed scope document before any contract is in place. No vague answers, no portfolio bait-and-switch.

See how we approach custom WordPress development →

Explore our custom WordPress development service →

You might also find useful:

• How to choose a web design agency — broader evaluation criteria for design-focused engagements
• Hiring WordPress developers: what to look for — if you’re considering in-house hiring alongside agency options

The 12 Questions: Quick Reference Checklist

Print this before your next agency call.

• Partner
• Web Development Agency
• WordPress