Before you hire a web agency, the most critical questions to ask concern ownership, scope, delivery timeline, revision rights, and support after handover. Signing with an agency that won't give you clear, written answers to these questions significantly raises your risk of running into surprise costs mid-project or ending up with a half-finished site. Below we've listed 15 questions you can ask before accepting a quote, why each one matters, and examples of good versus bad answers.
These questions matter especially if this is your first time commissioning a website; sorting out which answer actually offers real assurance, amid technical terms and vague promises, takes experience. If you're a small boutique store owner who has never had a website built before, for instance, an agency's jargon can easily win you over; the questions below are designed to cut through that jargon and reveal the real commitment underneath.
1. Once the site is live, who will own the domain name and hosting?
This question matters because some agencies deliberately register the domain name and hosting account under their own name; if you later want to switch agencies, you can find yourself locked out of your own site. Good answer: 'The domain and hosting will be registered in your name; we'll only take management access.' Bad answer: 'It's more practical if we keep hold of that, you don't need to worry about it.'
2. Will the source code and design files be handed over to me once the project is finished?
This question matters because without the code and design files, no other team can take over your site; you'd be stuck with the original agency even for the smallest change. Good answer: 'Once the project fee is paid in full, all source code and files are delivered to you under the contract.' Bad answer: 'The code is our know-how, we don't share it.'
3. Exactly how many pages and which features are included in the scope?
This question matters because the word 'website' on its own specifies no scope at all; a 5-page brochure site and a 20-page corporate portal cannot be built for the same price. Good answer: 'The quote lists 8 pages in total: home, about us, 4 service pages, a blog setup, and a contact page.' Bad answer: 'We'll build a standard site, and add whatever you need along the way.'
4. How long will delivery take, and what exactly is included in that timeframe?
This question matters because a vague range like '3-4 weeks' doesn't tell you whether the time you'll spend delivering your own content is included in that schedule. A typical corporate site project takes 4-6 weeks if content and images are delivered on time. Good answer: 'From contract signing, we'll be live within 5 weeks if your content reaches us within 2 weeks.' Bad answer: 'It'll be done soon, don't worry about it.'
5. How many revision rounds do I get, and how does extra billing work after that?
This question matters because a promise of unlimited revisions is usually unrealistic and can drag a project out indefinitely; a clear number of rounds protects both sides. Good answer: '2 revision rounds are included at the design stage; anything after that is billed hourly.' Bad answer: 'Change it as many times as you like, there's no limit.'
6. Are basic SEO settings included in the quote?
This question matters because the technical SEO fundamentals (title tags, a sitemap, fast loading) should be part of the build itself, not a service tacked on afterward. Good answer: 'Title and description tags, a sitemap, and basic speed optimization are included in the build; ongoing monthly SEO work is a separate service.' Bad answer: 'SEO is a separate job, we'll talk about it later.' If you're curious how a full SEO process actually works, take a look at our article what is SEO and how does it work.
7. How will the site be tested on mobile devices?
This question matters because the majority of visits now come from phones; sites that look great on desktop but break on mobile are still a common problem. Good answer: 'We manually test across different screen sizes (phone, tablet, desktop) and send you a screen recording.' Bad answer: 'The system automatically adapts, separate testing isn't necessary.' To dig deeper into this topic, read our article on responsive web design.
8. Is there a concrete target for site speed?
This question matters because 'it'll be fast' isn't measurable; speed directly affects both the user experience and search rankings. Good answer: 'We aim for a green score on core mobile speed metrics, and we measure and report it before launch.' Bad answer: 'We use modern code, so it'll be fast anyway.' You'll find detailed measurement methods in our article on website speed and Core Web Vitals.
9. How will data protection and cookie compliance be handled?
This question matters because any site with a contact form, cookies, or a newsletter signup falls under data protection law (such as GDPR in the EU or Türkiye's KVKK) and needs a privacy notice and a proper consent mechanism. Good answer: 'A privacy notice template and a cookie consent banner are included in the build; we prepare the legal text together with you.' Bad answer: 'We never really thought about that, it's probably not needed.'
10. Is maintenance a separately billed service after launch?
This question matters because software updates, security patches, and small content changes all need ongoing attention; a site left unmaintained becomes vulnerable to security issues or breakage within a couple of years. Good answer: 'The first 3 months of support are free; after that we have a monthly maintenance package, though your own team can also manage it if you prefer.' Bad answer: 'Our job ends once we deliver.'
11. Do you provide training on using the content management panel?
This question matters because having to call the agency for even a small text change after handover costs you both time and money. Good answer: 'We provide a 1-hour screen-share training session at handover, plus a written user guide.' Bad answer: 'The panel is very simple, you'll figure it out yourself.'
12. What situations could lead to extra costs?
This question matters because if items like 'an extra page,' 'an additional integration,' or 'an out-of-scope revision' aren't defined upfront, you can end up with unexpected invoices at the end of the project. Good answer: 'Any request outside what's stated in the quote gets priced and sent to you for approval before it's carried out.' Bad answer: 'Extras usually don't come up, and if they do, we'll agree on something reasonable.'
13. How does the payment plan work?
This question matters because a project requiring full payment upfront puts you at risk, while one paid entirely at the end can be unsustainable for the agency; a balanced plan protects both sides. Good answer: 'The contract splits payment as 40% upfront, 30% at design approval, 30% at delivery.' Bad answer: 'We'll give you a discount if you pay it all upfront.'
14. What happens if the project is left unfinished?
This question matters because agencies can sometimes close down or their project team can change; whether the work completed up to that point belongs to you needs to be settled in advance. Good answer: 'The contract has a termination clause; the work and files completed up to that point are handed over to you in proportion to what's been paid.' Bad answer: 'That won't happen, you don't need to worry about it.'
15. Have you built a similar project before, and can you provide references?
This question matters because a team that has already solved needs specific to your industry (an appointment system, inventory tracking, a multilingual setup) starts you off on the right path from day one. Good answer: 'You can call these three references, I'll share their numbers.' Bad answer: 'Our references are confidential, but trust us.'
Extra Questions Specific to Your Industry
While the 15 questions above apply to every business, some industries call for additional questions. These extra questions show whether the quote actually reflects your project's specific needs.
- For e-commerce businesses: Is payment gateway integration, shipping carrier integration, and inventory sync included in the quote? Without these three integrations, an e-commerce site is essentially non-functional.
- For clinics and appointment-based businesses: Will the online booking system integrate with your existing calendar or patient records software, or will a separate system be set up?
- For service businesses: Where will the quote-request form deliver the submitter's information - email, a CRM, WhatsApp?
Ask these industry-specific questions the same way: request a written answer. Choose an agency that clearly describes which system it will integrate with and how, rather than a generic 'we can integrate that.'
Two Bonus Questions: Critical but Easy to Overlook
16. Will I have access to the site's analytics and traffic data myself?
This question matters because if data like visitor numbers, which pages get attention, and where your traffic comes from isn't kept in your own analytics account, you lose all of that historical data the moment you switch agencies. Good answer: 'We set up the analytics account under your name, and we log in with manager-level access.' Bad answer: 'We'll send you reports, there's no need for an account.'
17. After launch, will I be able to make small changes myself, like updating prices or service descriptions?
This question matters because having to call the agency for every small text change wastes time and can lead to being charged extra even for minor edits. Good answer: 'You can update fields like text and prices yourself through the content management panel; only changes involving code stay with us.' Bad answer: 'The panel is complicated, just leave every change to us.'
How Should You Use These Questions?
Rather than firing off all these questions in a single sitting, take short notes at your first meeting and get the answers confirmed in writing (by email or message). A verbal answer is worthless if a dispute arises later; written confirmation protects both you and the agency. The pattern of which questions get clear answers and which get vague ones is itself the most reliable signal about the project.
A practical method: write your questions and the answers you get into a simple table, marking each one as 'clear and written,' 'clear but verbal,' or 'vague.' If the 'vague' column fills up by the end of the conversation, make sure to ask for further clarification before proceeding with that agency, or talk to another one as well. This simple habit keeps your decision grounded in concrete evidence rather than gut feeling.
Once you've found an agency that answers your questions clearly and puts the scope in writing, the next step is evaluating the quote itself. We walk through how to compare an incoming quote line by line in our article how to evaluate a website proposal; if you want to see the full agency selection process, take a look at our guide how to choose a web design agency.
Conclusion: The Right Questions Are the Foundation of the Right Project
The questions you ask before commissioning a website eliminate most of the surprises you'd otherwise run into later in the project. A quote where you can't get clear answers on ownership, scope, timeline, revisions, and support is risky no matter how attractive the price looks.
At Welda, we start every project by giving clear, written answers to these exact questions. To talk through your questions and pin down the right scope for your project, take a look at our web design and development service, and get in touch with us for a free initial consultation.