How to choose a web development agency: 12 questions that expose the truth

To choose the right web agency, ask 12 questions across four areas: who owns the code after launch, how the project is scoped and priced, what technology stack they use and why, and what happens in the first 90 days after go-live. The agencies that answer these questions clearly and specifically are the ones worth working with. The ones that hedge or deflect are telling you something important.

To choose the right web agency, ask 12 questions across four areas: who owns the code after launch, how the project is scoped and priced, what technology stack they use and why, and what happens in the first 90 days after go-live. The agencies that answer these questions clearly and specifically are the ones worth working with. The ones that hedge or deflect are telling you something important.

Group 1: Ownership — who gets what after launch?

Question 1: Who owns the code after the project is done?

The correct answer: you do. All source code transfers to you at launch. If the agency says “it’s built on our platform” or “you’ll need us to make changes,” you are renting a website, not buying one. That rental relationship lasts as long as the site exists.

Question 2: What licenses are involved and do they continue after launch?

Some agencies build on premium plugins or page-builders that require ongoing license fees. Elementor Pro, certain theme frameworks, third-party form builders — these can add €100–500/year to your operating costs, forever. Ask for a complete list of third-party dependencies and their annual cost before you agree to the build.

Question 3: Will you give me all admin credentials and hosting access on launch day?

CMS admin, hosting control panel, domain registrar, analytics, email — everything. If any of these stay in the agency’s account “for convenience,” you have a dependency that limits your ability to switch providers or manage the site independently. The answer should be an unconditional yes.

Group 2: Process — how is the project scoped and run?

Question 4: Do you quote fixed price or hourly, and why?

A fixed price on a defined project protects you from overrun risk. The agency should be able to give you a number before you commit, and that number should not move unless you change the scope. An agency that only offers hourly for a project with clear deliverables is moving its estimation risk onto you.

Question 5: Who writes the content — us or you?

This is the most common silent scope gap in web projects. “We’ll reuse our old texts” is a sentence that turns a 2-week project into a 6-week one. If the agency writes conversion copy as part of the project, that is a genuine value-add. If it’s not included, both sides need to know before the build starts.

Question 6: What is your QA process before launch?

A serious answer includes: cross-browser testing, mobile testing on real devices, form submission testing, speed measurement (Core Web Vitals) and accessibility checks. A vague answer (“we test everything”) is a sign that QA is informal or absent.

Group 3: Technology — what are they actually building?

Question 7: Custom theme or page builder — and what are the trade-offs?

Ask directly. The agency should be able to explain what they use, why, and what the trade-offs are for your specific case. A custom hand-coded theme is faster, owned fully by you, and easier to maintain without ongoing license costs. A page builder is faster to build but ships bloat and creates a dependency.

Question 8: How do you handle Core Web Vitals?

LCP under 2.5 s, INP under 200 ms, CLS near zero — the agency should know these targets and have a process for hitting them. Ask what their last three projects scored on PageSpeed Insights. If they do not have an answer or the numbers are below 80, performance is not a priority in their process.

Question 9: How is the site structured for SEO at build time?

Not “do you do SEO” — that invites a marketing answer. Ask: are page titles and meta descriptions editable from the CMS? Is schema markup (Organization, BreadcrumbList, FAQPage) part of your default build? Do you set up canonical URLs and hreflang for multilingual sites? These are technical questions with yes/no answers.

Group 4: After launch — what happens next?

Question 10: What does support look like in the first 30 days after launch?

Bugs surface after launch. Real-world traffic reveals things a QA environment misses. The agency should have a defined window — typically 30 days — during which they fix bugs found in scope at no charge.

Question 11: What is the process if I need a change six months from now?

Ask for a concrete example: “if I need a new service page in six months, how does that work and what does it typically cost?” The answer tells you whether they have a support process or whether you are on your own after launch day.

Question 12: Can I talk to a recent client about their experience?

Not a written testimonial — a phone call or email thread with someone who has used them. Any agency confident in their work will say yes immediately. Hesitation here is a signal worth heeding.

Red flags that predict a bad project

• No prices on the website. “Contact us for pricing” on a standard project type means scope will expand to fill whatever budget you reveal.
• “All-inclusive” quotes without a line-item breakdown. If you cannot see what each element costs, you cannot compare quotes or identify what is missing.
• Portfolio with no live links or no named clients. If you cannot verify the work exists, the portfolio cannot be trusted.
• Design presented before discovery. Mockups from the first meeting means they drew something before understanding your goals.
• Urgency pressure. “This price is only valid until Friday” on a €3,000 project is a sales tactic, not a business reality.

Honestly: when you do not need an agency

If you are validating a new idea — building a quick landing page to see if anyone clicks — use Tilda, Webflow or Carrd. You need speed and low investment, not hand-crafted code. Hire an agency when the site needs to perform (organic search traffic, Core Web Vitals, schema), when integrations are involved, when buyers will research you, or when the site is a primary revenue channel.