How to Choose a Web Design Agency: 10 Questions Before a Quote

When choosing a web design agency, look at four things before price: who will own the site when it is finished, which steps and approvals the process will follow, whether the site will be delivered ready for search engines and accessibility standards, and who will look after it after launch. Ask the 10 questions below before you request a quote and get the answers in writing. Comparing quotes only makes sense after you have compared the answers.

Why ask questions before talking about price?

You can get two very different websites for the same price. In one, the domain sits in the agency's account, no measurement is set up and maintenance is not in the contract. In the other, everything is registered in your name, the site launches with measurable goals and it is still being updated a year later. A quote document usually does not show this difference; the right questions do.

These questions apply to corporate websites, single-page promotional sites and e-commerce projects alike. If you are building an online store, see our guide to choosing an e-commerce agency for extra topics such as payments, shipping and marketplace integration.

1. Who will own the site when it is finished?

Ask whether the domain, hosting account, content management panel and source code will be registered in your name. In some offers the site stays on the agency's closed platform, and if you want to leave you have to have everything rebuilt. The right answer is: the domain and accounts are opened in the company's name, code and content are handed over, and the agency continues only for maintenance and development under a contract.

2. What steps does the process have, and what will I see at each one?

A healthy project follows a clear order: discovery and content planning, design, development, testing and launch. Each step should have a concrete output: a sitemap and content list in discovery, screens for you to approve in design, a test address you can browse during development, and a checklist at launch. A team that cannot clearly name its steps and approval points will also struggle to keep the project on schedule.

3. Who will write the content, and where will images come from?

Web projects are delayed most often by content, not design. Will you provide the text, will the agency write it, or will you work on it together? If the agency writes it, ask plainly what information it will rely on and confirm it will not use unverifiable claims or references that do not exist. The same question applies to images: licensed stock photos, your own photo shoot or AI-generated images? Who keeps the license documents?

4. Will the site be delivered ready for search engines?

Ask for the following at handover: correct title and description tags for every page, a meaningful heading hierarchy, structured data describing your organization and services, a sitemap and robots file, and, if you are moving from an old site, redirects from the old addresses to the new ones. These should be part of the pre-launch checklist, not a package sold later.

Answer engines such as ChatGPT, Gemini and Perplexity also read websites and cite them as sources. Google states that there are no additional technical requirements to appear in its AI features; a page only needs to be indexed and eligible to be shown in search results. In other words, a solid SEO foundation serves both sides.

One warning: Google's own guide states clearly that no one can guarantee a number one ranking on Google. Be cautious with any quote that offers a "first page guarantee". If you plan to buy SEO as a separate service, the criteria in our guide to choosing an SEO agency will help.

5. What standard will be used to measure speed and mobile experience?

"The site will be fast" is not a sufficient answer. Ask which tool will be used, on which pages, and against which thresholds. Google's Core Web Vitals offer a good common language: according to web.dev, for a good experience the largest content element should load (LCP) within 2.5 seconds, the response to interaction (INP) should be 200 milliseconds or less, and layout shift (CLS) should be 0.1 or less. These values should be met for 75 percent of page loads, on mobile and desktop separately.

At the proposal stage, also discuss how image sizing, avoiding unnecessary plugins and caching will be handled.

6. Will the site be accessible?

In Turkey, Presidential Circular No. 2025/10, published in the Official Gazette on 21 June 2025, introduced an accessibility obligation for websites and mobile apps. Listed organizations such as public bodies, banks and private hospitals were given one year to comply, and e-commerce service providers covered by Law No. 6563 were given two years. Even if you are not in scope, a site that follows basic accessibility rules such as color contrast, keyboard navigation and form labels can be used by more people. Ask the agency which WCAG level it targets and how it tests for it.

7. Will the site talk to the systems behind it?

Will a customer who fills in a form end up in your CRM? Will an e-commerce order flow to accounting, the ERP and the courier? Is the booking calendar in sync with the team? Businesses that buy the website and the software behind it from separate teams often run into the problem of "systems that do not talk": data is entered twice and errors increase. Get the integration requirements written down in the discovery phase and add who is responsible to the contract.

8. Who will maintain the site after launch, and how fast will they respond?

Updates, security patches, backups and the response time in case of a fault should be written into the contract. Where are backups kept, how often are they taken, and has a restore ever been tested? Does maintenance include content updates, or only technical maintenance? These answers decide your total cost a year from now.

9. How will results be measured and reported?

A website is a sales channel, not a cost item. Which measurement will be set up: analytics, Search Console, form and phone conversions? When will the first report arrive, and how often after that? A quote that says nothing about measurement is not promising results either.

10. Can I browse your live references, and what does the price cover?

Ask for live addresses, not screenshots. Open the site on your phone, fill in the form and move between pages. If there is an example close to your sector, ask how content and integration were handled there.

On the price side, a transparent quote states scope and exclusions with the same clarity: number of pages, number of languages, content, images, integration, training and maintenance period. What happens when you ask for an extra page, an extra language or an extra round of revisions should be clear in advance.

In short: how should you compare the answers?

• Are ownership and accounts in the business's name?
• Are the process steps and approval points in writing?
• Are the SEO, speed and accessibility standards concrete in the quote?
• Are integration and maintenance responsibilities in the contract?
• Is the out-of-scope work clearly listed?

The quote with the most "yes" answers on this list usually brings fewer surprises overall, even if its price is a little higher. If you would like to ask us the same questions, we describe our process on our web design service page; our teams serve clients across Turkey and abroad from İstanbul and Dubai.