Hiring a team

How to choose a web development company: 10 questions to ask

Ten questions to ask before you hire a web development company, from live work and code ownership to written scope and support.

By Coding LoadingUpdated First published

To choose a web development company, ask ten questions before you sign: show me live work, where are your independent reviews, who will do the work, what is your process, will I get a written scope, how do you handle changes, who owns the code, how will we communicate, what happens after launch, and can I speak to past clients. Listen to how they answer as closely as to what they say.

The wrong choice costs more than the invoice: time spent managing a struggling project, money spent fixing poor code, and months a competitor uses to move ahead. Most of that is avoidable.

1. Can you show me live sites you have built?

Screenshots prove little. A live site can be tested. Ask for a few live projects similar in scope to yours, then open them on your phone and on a computer. Run one through PageSpeed Insights. A company that cannot show fast, well-built live work is telling you something.

2. Where can I read independent reviews?

Testimonials on a company’s own site are easy to write. Look for reviews on independent platforms, such as Google, Clutch or industry directories, that mention communication, deadlines and support, not just design. Notice how the company responds to criticism; a thoughtful reply to a bad review says more than a page of perfect ones.

3. Who exactly will work on my project?

Ask who will handle design, front-end development, back-end development and testing, and whether any of it is outsourced. You want to know who is doing the work, not a promise that “our experienced team” will handle it.

4. What does your process look like, step by step?

A company with a real process can describe it clearly: discovery, design you approve before building starts, development with regular demos, testing, launch and handover. If the answer jumps from “we scope it” to “we build it”, the missing middle is where projects go wrong.

5. Will I get a written scope before work begins?

A written scope protects both sides. It should list the pages or features, the technology, the milestones, what is excluded, and the price tied to each deliverable. Never start without one, however much you trust the people.

6. How do you handle changes during the project?

Requirements change. A professional company has a change process: new work is described, priced and approved before it starts. Without one, changes pile up quietly until a surprise invoice or a project that drifted from the brief.

7. Who owns the code and the accounts?

The answer should be you: the code, the design files, the domain, the hosting, the analytics and every service account. Some companies keep ownership, charge license fees or build on platforms that lock you in. Get ownership confirmed in writing.

8. How will we communicate?

Agree on it before you start: who your main contact is, how often you get updates, how quickly questions are answered, and which tools you will use. The way a company communicates while selling is the best preview of how it will communicate while building.

9. What does support look like after launch?

Every site needs care after launch: browser and platform updates, security patches, small fixes and changes. Ask what is included after launch, for how long, and what ongoing support costs. A company with no clear answer treats launch as the end of its job.

10. Can I speak to past clients?

A confident company will connect you with clients whose projects were similar to yours. Ask them about communication, how problems were handled, whether deadlines held and whether they would hire the company again.

One more thing: notice how they sell

Beyond the questions, pay attention to the conversation. Do they ask about your goals before pitching? Do they tell you honestly when something is not worth building? Do they explain trade-offs, or promise that everything is possible? A good web development company acts like a partner from the first call.

Prepare before you ask

You will get better answers if you bring a short brief: what the business does, who the site is for, what it must do, what it connects to, and when you need it. Our guide to what a web app costs shows what to include, and if you are weighing a company against an individual, read app development company vs freelancer.

Questions people ask

What should I look for in a web development company?

Live work you can test, independent reviews, a named team, a clear step-by-step process, a written scope before work starts, a formal way to handle changes, full ownership of the code for you, regular communication, defined support after launch, and references you can call.

What questions should I ask a web developer before hiring?

Ask to see live sites, who will do the work, how their process runs, whether you get a written scope, how changes are priced, who owns the code, how they communicate, what happens after launch and whether you can speak to past clients.

What are red flags when hiring a web development company?

No live examples, starting work without a written scope, vague answers about who does the work, unclear ownership of code or accounts, no change process, guaranteed results, and slow or evasive communication during the sales process.

Should I choose the cheapest web development quote?

Only if it covers the same scope. Quotes often differ because they include different things, such as design, testing, content or support. Compare each quote line by line against one written scope.