Quick Answer: What questions should I ask a web development company before hiring?
Ask a web development company how it handles ownership, security, accessibility, performance, and handover before money changes hands. In plain terms, the answers reveal whether you are buying an asset you control or renting a service you cannot leave. Agencies differ sharply: some build custom code you own outright, while others resell templates and retain the hosting account, and a few bundle maintenance contracts that quietly lock in renewal pricing. Compare the written scope, IP and repository ownership, data-processing terms, security baseline, real-user performance data, accessibility conformance, support SLA, and the documented exit process before you commit.
A short quiz before the contract

Here is a question worth sitting with: if your agency disappeared tomorrow, would you still own your website?
That single hypothetical exposes more about a web development company than a glossy portfolio ever will. Most buyers spend weeks comparing design mockups and almost no time asking who holds the domain registrar login, whether the code lives in a repository they can access, or what happens to their customer data if the relationship sours. Then they sign, and the answers arrive too late.
The questions below are the ones that actually change outcomes. They are not designed to trap anyone. Good agencies answer them without flinching, often before you ask. Weak ones get vague, change the subject, or promise things verbally that never appear in the contract. Treat every answer as provisional until it is written down.
Ownership and access questions
Start here, because everything else depends on it. Ask directly: who owns the source code, the design files, the domain name, the hosting account, and every third-party service connected to the build? The correct answer is that you do, transferred at handover, with credentials in your name.
A few follow-ups matter just as much:
- Will the code live in a repository under my organisation’s account, or yours?
- Which third-party accounts (analytics, email, payment, CMS) will be created in my name?
- What happens to my access if we stop working together?
- Can I get a full export of the site, database, and assets on request?
The trap here is subtle. An agency may hand over a working website but keep the domain registrar and hosting in its own name, billing you annually. That arrangement feels convenient until you want to move. Ask for a written handover checklist that names every credential and account, and confirm the transfer happens at final payment, not “when we get around to it.”
If your project involves customer-facing chat tools or AI features, ownership gets murkier still. The same discipline applies to evaluating those vendors, and a structured set of questions helps: AI chatbot security questions to ask before buying covers what to demand from any tool that touches your customer conversations.
Security and data protection questions
Security questions separate serious shops from hobbyists. Ask whether the agency follows a recognised baseline such as the OWASP Top 10 or the OWASP Application Security Verification Standard, and whether a penetration test is included before launch. If the answer is “we’ve never had a problem,” that is not a security posture; it is luck.
Data protection deserves equal weight. The GDPR has applied since 25 May 2018, and it governs how personal data is collected, stored, and shared. Ask three things: will the agency sign a data-processing agreement, who configures cookie consent and analytics, and where is data stored geographically? An agency that shrugs at the DPA question is telling you something important.
For sites handling payments, logins, or health information, go further. Request a written security scope covering TLS certificate management, HSTS, redirects from HTTP, patching cadence, and incident response. If you plan to outsource ongoing monitoring, the same scrutiny applies to that vendor, and this managed detection and response checklist walks through the questions worth asking before signing.
Practical tip: ask for a sample security questionnaire response from a past client project, with sensitive details redacted. Agencies that do this regularly will have one ready. Agencies that don’t will improvise, and improvisation is visible.
Accessibility questions most buyers forget
Accessibility is where well-meaning buyers get caught out. Ask whether the agency builds to WCAG 2.2 Level AA, the standard that became a W3C Recommendation on 5 October 2023, and whether it can produce an accessibility conformance report such as a VPAT.
Why does this matter commercially? Because in many markets it is now law, not charity. The European Accessibility Act (Directive (EU) 2019/882) applies from 28 June 2025 to many consumer-facing e-commerce and service businesses selling into the EU. In the UK, the Equality Act 2010 requires reasonable adjustments for disabled users of services, which guidance and case law treat as covering websites. Scope and thresholds vary, so verify your own situation, but the direction is unmistakable.
Ask the agency who owns remediation if accessibility issues surface after launch. The wrong answer is “that’s a content problem.” The right answer names a process, a timeline, and a cost.
Performance and technical quality questions
Every agency claims its sites are fast. Ask for real-user field data, not lab scores from a single test on a fast connection. The current Core Web Vitals metrics are Largest Contentful Paint, Interaction to Next Paint (which replaced First Input Delay in March 2024), and Cumulative Layout Shift. Request a before-and-after report from a comparable project.
Then probe the build itself:
| Question | Why it matters |
|---|---|
| Which CMS and why? | Determines long-term flexibility and upgrade risk |
| What third-party plugins or libraries are used? | Each one adds maintenance and licence obligations |
| Will you provide a licence list or software bill of materials? | GPL components can carry obligations you inherit |
| How is the site tested across browsers and devices? | Catches costly post-launch surprises |
| What is the deployment process? | Reveals whether changes are safe and reversible |
That licence question catches people out. If an agency builds on GPL-licensed themes or plugins, you may inherit obligations you never agreed to. Ask for a plain list of every component and its licence. It takes them ten minutes and saves you a legal headache.
Process, communication, and contract questions
Delivery failures are rarely technical. They are usually communication failures wearing a technical costume. Ask how often you will receive updates, who your single point of contact is, and what happens when scope changes mid-project.
Specific questions that produce useful answers:
- What is the payment schedule, and how much is tied to milestones rather than calendar dates?
- What is explicitly out of scope?
- Who tests the site before launch, and against what checklist?
- How do you handle change requests, and at what rate?
- Can I speak to two recent clients whose projects resembled mine?
That last one is the highest-value question on this entire list. References chosen by the agency will be positive, but listen for hesitation, for how quickly problems were resolved, and for whether the client would hire them again. A five-minute call beats a hundred portfolio screenshots.
If your project includes buying hardware or consumer products alongside the build, the same “ask before you commit” instinct applies elsewhere. Buyers researching physical goods often benefit from the kind of pre-purchase scrutiny found in this Rillabox review for buyers before ordering, and the underlying principle is identical: understand what you are actually getting before you pay.
Maintenance, support, and exit questions
Launch day is the start, not the finish. Ask for the support SLA in writing: response times, escalation paths, what counts as an emergency, and what falls outside the agreement. Vague promises like “we’re always here for you” are not an SLA.
Then ask the question agencies least like: what does leaving look like? Request a documented exit process covering credential transfer, documentation, training, and a reasonable notice period. An agency confident in its work will answer without defensiveness. One that gets prickly has told you what you needed to know.
Watch for bundled maintenance contracts with auto-renewal and steep exit fees. Ask whether maintenance is priced monthly or annually, what happens if you pause, and whether the rate is fixed or indexed.
How to compare proposals without getting fooled
Once you have answers from two or three agencies, compare them side by side rather than by gut feel. Score each on ownership clarity, security baseline, accessibility conformance, performance evidence, communication cadence, and exit terms.
| Factor | Weak answer | Strong answer |
|---|---|---|
| Code ownership | “We retain IP, you get a licence” | Full transfer at handover |
| Security | “We’ve never been hacked” | OWASP ASVS alignment plus pen test |
| Accessibility | “We add alt text” | WCAG 2.2 AA plus conformance report |
| Performance | Lab score screenshot | Real-user field data from a past project |
| Handover | “We’ll sort it out” | Written checklist with named credentials |
| Exit | Not discussed | Documented process and notice period |
A cheaper quote with weak answers on ownership and security is not cheaper. It is a deferred cost with interest.
Conclusion
Hiring a web development company is really an exercise in asking uncomfortable questions early, while you still have leverage. Ownership, security, accessibility, performance, communication, and exit terms are the six areas where projects quietly go wrong, and every one of them can be settled in a single conversation and a written contract.
The pattern across all of it is simple. Ask for specifics, ask for them in writing, and treat vague reassurance as a red flag rather than a comfort. Agencies that do good work are rarely offended by good questions; they tend to enjoy them. The ones that bristle have just saved you months of frustration. Ask the questions, compare the answers honestly, and sign only when the paperwork matches the promises.
FAQ
How many web development companies should I get quotes from?
Three is the practical sweet spot. Two gives you no tiebreaker, and four or more blurs into noise. Three lets you compare ownership terms, security posture, and pricing side by side while keeping the process manageable.
Should I choose the cheapest proposal?
Almost never on price alone. A low quote often reflects weaker ownership terms, thinner security work, or a maintenance contract designed to recover the difference later. Compare total cost of ownership over three years, not the headline number.
What should be in the contract about code ownership?
The contract should state plainly that all source code, design files, content, domain, and third-party accounts transfer to you at handover or final payment. It should also name the repository location and confirm credentials are created in your organisation’s name.
Do I need a separate maintenance agreement after launch?
Usually yes, but read it carefully. Look for response times, what is covered, whether renewal is automatic, and how you exit. A good maintenance agreement is a service; a bad one is a lock-in mechanism wearing a friendly name.
How do I check if an agency’s accessibility claims are real?
Ask for a conformance report such as a VPAT and a sample audit from a past project. Then request that accessibility testing be written into the scope, with a named owner for remediation. Claims without documentation are marketing.
What is a reasonable handover process at the end of a project?
A reasonable handover includes a written credential list, repository access, documentation, a training session, and a defined support window after launch. Ask for the checklist before signing so you know exactly what arrives on the final day.


