20 Essential Questions to Ask Before Hiring a Web Development Agency

Choosing the right web development agency is one of the most important business decisions you'll make. The wrong choice can mean months of frustration, wasted budget, and a website that doesn't serve your goals. The right questions upfront save you from all of that.

Here are 20 questions every business should ask — and what good answers look like.

Before You Start: Evaluating the Agency

Before diving into project-specific questions, take time to evaluate the agency itself. Review their portfolio, read case studies, check online reviews, and ask for references. A few things to look for:

Portfolio quality: Do their past projects match the quality and style you're looking for? More importantly, do they show range — or does every site look the same? A good agency adapts to each client's brand, not the other way around.

Relevant experience: Have they worked with businesses similar to yours in size, industry, or complexity? An agency that specializes in e-commerce may not be the best fit for a B2B service company, and vice versa.

Communication style: How responsive are they during the sales process? If they take a week to respond to your inquiry email, expect similar communication during the project. The sales phase is when they're trying to impress you — it only goes downhill from there if communication is already lacking.

Team size and structure: Understand who will actually be working on your project. Some agencies use the senior team for sales pitches and hand the work to junior staff. Ask directly: "Who will be designing and developing my site, and can I meet them?"

Costs & Ownership

1. How much will the website cost, and what are the payment terms?

A professional agency should provide a detailed proposal with a clear scope of work and pricing. Look for milestone-based payments (e.g., 50% upfront, 25% at design approval, 25% at launch) rather than full payment upfront. The proposal should itemize what's included at each phase so you understand exactly what you're paying for.

Good answers include a written scope of work, clear deliverables for each phase, and a defined process for handling changes that fall outside the original scope. Every additional feature or change should require a formal change order with an agreed-upon cost and timeline impact.

*Red flag:* Vague pricing with no written scope of work. "It depends" without a framework for determining cost. Verbal agreements with nothing in writing.

2. Are there any ongoing or hidden costs?

Ask specifically about hosting, domain renewals, premium plugin licenses, SSL certificates, maintenance fees, email hosting, stock photography, and third-party SaaS subscriptions. A trustworthy agency is transparent about the total cost of ownership — not just the build cost, but what it costs to keep the site running month over month.

Request a complete list of recurring costs you'll be responsible for after launch. Add them up and factor them into your annual budget. A $30,000 website with $500/month in recurring costs has a true first-year cost of $36,000.

*Red flag:* "We'll figure that out later." Any reluctance to discuss ongoing costs upfront is a sign that you'll be surprised later.

3. Who owns the website and its assets once it's launched?

You should own everything — custom code, design files, content, and domain — after final payment. Ensure this is documented in the contract with a Work for Hire clause or explicit IP transfer. The agency may retain ownership of their proprietary frameworks, tools, or libraries — that's reasonable as long as your site can function independently without them.

Make sure your domain is registered under your own account, not the agency's. Same for hosting, analytics, and any third-party accounts. If the relationship ends, you should be able to walk away with full access to everything without needing the agency's cooperation.

*Red flag:* The agency retains ownership of the code or locks you into proprietary systems. They host your domain under their account. You can't access your own analytics or hosting without going through them.

Timeline & Process

4. How long will it take to build and launch the website?

Expect honest timelines: 6–8 weeks for simple sites, 8–16+ weeks for complex projects. An agency that promises a custom site in two weeks is cutting corners — likely using a template and calling it custom, skipping QA, or delivering a site that needs significant fixes after launch.

Timelines should include buffer for client review periods, content preparation, and unforeseen complications. Ask about their track record: "Of your last 10 projects, how many launched on schedule?" Honest agencies will acknowledge that delays happen (often due to client content or feedback delays) and explain how they manage them.

*Red flag:* Unrealistically short timelines without a clear explanation. No mention of client responsibilities or review periods in the timeline.

5. What is your step-by-step process?

Look for a structured process: discovery, wireframing, design, development, QA, and launch. Each phase should have clear deliverables and approval points. Ask to see an example project timeline or Gantt chart. The process should include defined moments where you review and approve work before the next phase begins.

A mature process also includes a defined change request procedure. "What happens when we realize mid-development that we need a feature we didn't plan for?" The answer should involve a documented change order, revised scope, and adjusted timeline — not ad hoc additions that create confusion and budget overruns.

*Red flag:* No documented process or unclear phases. "We just start building and figure it out as we go."

6. What do you need from me before we start?

You'll typically need to provide brand assets (logos in multiple formats, brand colors with hex codes, approved fonts), written content or a detailed content plan, high-resolution images or a photography budget, access to existing hosting and domain accounts, and credentials for third-party tools that need integration.

A good agency will send you a detailed content and asset checklist with deadlines. They understand that their ability to stay on schedule depends on your preparedness, and they'll be proactive about setting expectations.

*Red flag:* They don't ask for anything and start building without understanding your business. They have no content checklist or asset requirements.

7. Who will be my main point of contact, and how often will we communicate?

You should have a single point of contact — usually a project manager or the lead designer/developer — and regular check-ins (weekly at minimum). Ask about their preferred communication tools (email, Slack, project management platform) and response times. Understand who is available when, and how emergencies are handled.

Also ask about the approval process: "When I need to sign off on a design, how does that work? Is there a formal approval step, or is it ad hoc?" Formal approval steps prevent miscommunication and ensure everyone is aligned before moving forward.

*Red flag:* No dedicated contact or unclear communication expectations. "Just email the team inbox."

Design & User Experience

8. Will the site be custom-built or based on a pre-existing template?

Neither is inherently wrong, but you should know which approach is being used. Custom builds offer more flexibility, uniqueness, and performance. Template-based builds are faster and more affordable but less differentiated. The important thing is honesty — you should know exactly what you're getting.

If the agency uses templates, ask which template marketplace or theme they source from and what level of customization is included. If they build custom, ask to see examples of their custom work and understand their design process.

*Red flag:* Claiming a site is "custom" when it's actually a modified template. This is surprisingly common and is one of the most frequent complaints from clients who realize after the fact that their "custom" site uses the same theme as thousands of others.

9. How do you ensure the website is fully mobile-responsive?

Over 60% of web traffic comes from mobile devices, and Google uses mobile-first indexing. Your agency should design mobile-first and test across multiple devices and screen sizes. Ask specifically about their testing process: which devices and browsers do they test on? Do they use real devices or just browser simulators?

A thorough agency tests on current iPhone and Android devices, multiple tablet sizes, and a range of desktop screen resolutions. They should also test on varying connection speeds (3G, 4G, broadband) since mobile users are often on slower, less reliable connections.

*Red flag:* "We check it on an iPhone and it looks fine." Only testing on one device or relying solely on browser resizing.

10. How many rounds of design revisions are included?

Most contracts include 2–3 revision rounds. Know what's included and what additional revisions will cost so there are no surprises. A revision round should be clearly defined: the agency presents a design, you provide consolidated feedback within a specified timeframe, and they implement the changes.

Ask about the feedback process: "How should we submit feedback? Is there a specific format or tool you prefer?" Agencies that use design collaboration tools (like Figma comments) get more precise, actionable feedback than agencies that rely on email threads.

*Red flag:* Unlimited revisions (sounds nice, but usually means no clear process and no incentive to get it right) or zero revisions included. Either extreme signals a process problem.

11. Do you ensure the website meets accessibility standards (ADA/WCAG)?

Look for agencies that understand WCAG 2.1 AA compliance: keyboard navigation, screen reader compatibility, color contrast, alt text, proper heading structure, focus management, and form labeling. Ask about their testing methodology — do they use automated tools, manual testing, or both?

Accessibility isn't a checkbox — it's a design and development discipline that needs to be considered at every stage. Retrofitting accessibility onto a finished site is significantly more expensive than building it in from the start. Ask the agency how accessibility factors into their design process, not just their development process.

*Red flag:* "What's WCAG?" or "We can add that later."

Technology & Development

12. What CMS do you use, and why?

The answer should be based on your needs, not just the agency's preference. WordPress, headless CMS platforms, or custom solutions each have trade-offs. The agency should explain why their recommendation fits your specific situation — considering your team's technical comfort level, your content update frequency, your performance requirements, and your budget.

Ask follow-up questions: "What are the downsides of this CMS for our use case? What would make you recommend a different platform?" An agency that only knows one platform will recommend that platform regardless of fit. An agency with broad experience will match the technology to your requirements.

*Red flag:* "We use [platform] for everything" without considering your specific requirements. No willingness to discuss alternatives or trade-offs.

13. Can you integrate the site with my existing software?

Discuss your CRM, email marketing tools, booking systems, payment gateways, accounting software, and any other platforms your business relies on. Integration complexity varies significantly — connecting a Mailchimp form is very different from building a real-time sync with Salesforce.

Provide a complete list of tools and ask the agency to identify which integrations are straightforward, which require custom development, and which might present challenges. Each integration should be documented in the scope of work with clear expectations about data flow, error handling, and ongoing maintenance.

*Red flag:* Dismissing integrations as trivial without understanding the specifics. "Oh, we can hook that up in a day." Complex integrations often surface unexpected edge cases that take time to resolve.

14. How do you handle website security?

At minimum: SSL certificates, regular software updates, firewall protection, automated backups stored off-server, and access control with two-factor authentication. Agencies using headless CMS architectures get additional security benefits from the separated frontend/backend.

Ask about their security incident response process: "If our site is compromised, what steps do you take and how quickly?" Also ask about their track record: "Have any of your client sites ever been hacked? What happened and how was it resolved?" Transparency about past incidents (and how they were handled) is a sign of maturity.

*Red flag:* Security isn't mentioned until you ask about it. No documented security practices. No backup and recovery plan.

15. How easy will it be for my business to scale or add new features later?

A well-architected site should accommodate new pages, features, and integrations without requiring a rebuild. Ask about the codebase's modularity, documentation, and whether future developers can work with it. A site built with standard technologies (React, Next.js, standard APIs) is portable. A site built on a proprietary platform is not.

Also ask about performance scaling: "If our traffic doubles in six months, what changes (if any) would be needed?" The answer should involve hosting and caching configuration, not a rebuild.

*Red flag:* Proprietary systems that only the original agency can modify. No documentation. Code that isn't version-controlled (stored in Git).

SEO & Analytics

16. Is technical SEO included in the build?

Clean URLs, meta tags, heading hierarchy, image alt text, XML sitemaps, robots.txt configuration, canonical tags, structured data, and page speed optimization should all be part of a professional build. This isn't an add-on — it's a baseline.

Ask for specifics: "What Core Web Vitals targets do you build to? How do you handle structured data? Will you set up and verify Google Search Console?" These aren't unreasonable requests — they're standard deliverables for any agency that takes SEO seriously.

*Red flag:* "SEO is a separate service" for basic on-page optimization. If they're charging extra for meta tags and alt text, find a different agency.

17. How do you ensure fast page load speeds?

Look for specifics: image optimization (format, compression, lazy loading, responsive sizes), code splitting, server-side rendering, CDN usage, browser caching, and font loading strategies. Ask about their Core Web Vitals targets — a good agency should be targeting green scores (LCP under 2.5s, INP under 200ms, CLS under 0.1) on every project.

Performance should be a design constraint, not an afterthought. Ask how performance considerations affect their design decisions — for example, do they limit the use of heavy animations or autoplay video based on performance impact?

*Red flag:* "We'll optimize it after launch." Performance retrofitting is expensive and often limited by architectural decisions that were already made.

18. Will you set up Google Analytics and tracking pixels before launch?

GA4, Google Search Console, and any advertising pixels (Facebook, LinkedIn) should be configured and verified before the site goes live. Without this, you'll have no data from day one. The first days and weeks of a new site launch are valuable for establishing baselines.

Ask about conversion tracking specifically: "Will you set up goals/events for our key actions (form submissions, phone calls, downloads)?" And ask about data ownership: "Will the analytics accounts be under our Google account, or yours?"

*Red flag:* Analytics setup isn't part of the project scope. The agency sets up analytics under their own account and only shares reports.

Post-Launch & Support

19. Will you train my team on how to update content?

You should receive training — either live, recorded, or documented — on how to manage your CMS, update content, and handle basic tasks independently. Training should be customized to your team's technical comfort level, not a generic walkthrough.

Ask about the scope: "How many training sessions are included? Will they be recorded? Will you provide written documentation?" Also ask about ongoing support for CMS questions: "If my team has a question six months from now about how to do something in the CMS, can we contact you?"

*Red flag:* "Just Google it" or no training offered. An agency that doesn't train your team is setting you up for dependency — you'll have to pay them for every content update.

20. Do you offer ongoing maintenance and support packages?

Ask about what's included (updates, backups, monitoring, development hours), response times for emergencies, pricing tiers, and contract terms. Month-to-month plans offer more flexibility than annual commitments, though annual plans sometimes come with a discount.

Understand the boundaries: what's covered under maintenance versus what's a separate project. Ask for a sample monthly report so you can see what kind of visibility you'll have into the work being done.

*Red flag:* No post-launch support available, or the site can only be maintained by the original agency due to proprietary technology or undocumented code.

Bonus: Questions to Ask Yourself

Before talking to any agency, make sure you can answer these questions:

The Bottom Line

The best agencies welcome these questions. Transparency, clear communication, and a structured process are signs of a professional partner who will deliver a website that serves your business for years. If an agency gets defensive or evasive when you ask tough questions, that tells you everything you need to know.

At BeClearDesign, we answer all of these questions in our first conversation — because we believe an informed client makes the best collaborator. The best projects happen when both sides communicate openly, understand the process, and trust each other to deliver.