Skip to content
Guide

How to choose a web development company: 12 questions worth asking

By the Vertex Stacks team · 7 min read · Updated

Most web projects go wrong for ordinary reasons: unclear scope, slow communication, surprise costs, or a site that nobody maintains after launch. The right questions, asked early, expose most of these problems before you have signed anything.

Use these questions with every company you talk to, including us. A good partner will be glad you asked.

Questions about the work

  • Can I see work similar to what I need, and can I talk to someone it was built for? Be wary of portfolios you cannot verify.
  • Who will actually build my project, and will I be able to talk to them directly?
  • What technology will you use, and why is it right for my project rather than just for you?
  • How do you handle design: do I see and approve it before development starts?

Questions about money and scope

  • What exactly is included, and what would count as extra? Ask for it in writing.
  • How is the price built: fixed price, time and materials, or a monthly plan? What are the trade-offs of each for this project?
  • What happens if the scope changes halfway through?
  • Are there ongoing costs I should expect, such as hosting, licences, domain renewals or maintenance?

Beware of a quote that is far below the others. Either the scope is different from what you think, or corners will be cut somewhere you cannot see yet.

Questions about quality and risk

  • How do you test before launch, and what does your launch checklist cover?
  • How is security handled: login protection, secrets, backups and rate limiting?
  • Will the site meet basic accessibility, performance and search engine standards by default?
  • Who owns the code, the design files, the domain and the accounts when the project ends? You should own your own work.

Questions about life after launch

  • Who fixes bugs after launch, how quickly, and is that included for a period?
  • Do you offer maintenance and updates, and what do they cover?
  • If we part ways, can another team take over without starting from scratch? Clean, documented code makes that possible.

Red flags

  • Guaranteed number-one rankings. No honest company can promise that.
  • Pressure to sign today, or discounts that disappear tomorrow.
  • No written scope, and answers that stay vague when you ask for specifics.
  • Reluctance to let you own the accounts, code or domain.
  • Reviews or case studies that cannot be traced back to real clients.

What a good first conversation looks like

In the first call or email exchange, notice who asks the questions. A good partner wants to understand your customers, your goals and your constraints before talking about technology or price. If you are handed a quote within minutes of describing your idea, the quote is a guess.

You should also come away knowing what the next step is, who is responsible for it, and roughly when you will hear back. Clear next steps early are the best predictor of clear communication later.

Before you sign

  • Read the scope line by line and ask what is not included.
  • Confirm the payment schedule is tied to delivered milestones, not only to dates.
  • Agree how changes are requested, estimated and approved.
  • Ask for the launch checklist, the testing approach and the handover plan in writing.
  • Make sure you will own the domain, hosting and database accounts from day one, or have them transferred at handover.

How to compare proposals fairly

Line the proposals up against the same list: what is built, who builds it, what it costs, what happens after launch, and who owns what. The cheapest proposal is rarely the cheapest project, and the most polished pitch is not the same as the best delivery. Choose the partner whose questions about your business were the best.