How to Choose a Web Development Company: 9 Questions That Sort Them Fast
Every agency homepage looks the same. These nine questions get you past the pitch and show you whether real engineers or a template reseller will build your site.
Every agency homepage looks the same. These nine questions get you past the pitch and show you whether real engineers or a template reseller will build your site. In this deep dive, we explore actionable strategies, real-world engineering blueprints, and future-proof patterns to elevate your digital operations.
- 1. "Who writes the code?"
- 2. "Show me something you built that is still running"
- 3. "What happens when something breaks at 2am?"
- 4. "Who owns the code, the domain and the accounts?"
- 5. "How will anyone find this site after launch?"
- 6. "What does the first 30 days after launch look like?"
- 7. "What will this cost me to run every month?"
- 8. "Can I see the real pages on my phone before I pay the final invoice?"
- 9. "What would you tell me not to build?"
- The pattern behind the answers
- What this looks like in practice
- Related Reading
Most web development companies look identical on paper. The same stock photos, the same words about being "passionate" and "results driven", the same three logos in the footer. Then you send five enquiries and get five quotes that differ by a factor of ten.
The difference is almost never the price. It is who actually does the work and what you own at the end.
I have been on both sides of this: as the developer clients hired, and as the person they called after a cheap build went wrong. These are the nine questions I would ask if I were buying, and what each answer really tells you.
1. "Who writes the code?"
Ask for the name of the person who will build your site, and whether they are on staff or subcontracted. Many companies sell the work and then hand it to a freelancer you never meet, keeping a margin on every invoice.
Good answer: a specific person, available on a call, who can explain their part of the build.
Bad answer: "our team", with nobody named. If no one can name the builder, no one is accountable.
2. "Show me something you built that is still running"
Portfolio screenshots are marketing. Live URLs are evidence. Open the site, use it on your phone, and check the date of the most recent blog post or product update.
Good answer: three to five live links, at least one older than two years and still maintained.
Bad answer: screenshots only, or links that redirect to a placeholder. Anyone can screenshot a template.
3. "What happens when something breaks at 2am?"
Websites break. Payment forms fail, certificates expire, a deploy takes the site down. What matters is who notices and how fast it comes back.
Good answer: monitoring, an alert to a real phone, and a stated response window.
Bad answer: "you can email us and we will look at it." That means nobody is watching.
4. "Who owns the code, the domain and the accounts?"
This one matters more than the price. Ask whether the code lives in your repository or theirs, whether the domain is registered in your name, and whether you get admin access to every service the site depends on.
Good answer: everything in your name from day one. You can leave whenever you want.
Bad answer: "we manage all that for you." That can mean your website is a hostage you rent. I wrote about why this gets expensive later in what custom web development in Chennai actually costs.
5. "How will anyone find this site after launch?"
A beautiful site nobody visits is an expensive business card. Ask what happens on the day after launch: indexing, sitemap submission, page speed, the pages that answer questions your buyers actually type.
Good answer: a specific plan with someone responsible for it.
Bad answer: "SEO is a separate service." Launch-day indexing is not a separate service, it is part of shipping. If your new site is already live and quiet, here is why a new website gets no traffic.
6. "What does the first 30 days after launch look like?"
Launch is not the end of a project. It is when real users find the things you could not predict: a form that sends to spam, a page nobody reads, a checkout step that loses buyers.
Good answer: a defined post-launch window with fixes included, and a plan to look at real analytics once there is traffic.
Bad answer: the invoice is the finish line. Every project needs a settling period, and it should be priced in.
7. "What will this cost me to run every month?"
Build cost is one number. The running cost is the one that surprises people: hosting, database, email service, third-party tools, maintenance. Ask for a monthly estimate in writing before you sign.
Good answer: a written range, and an honest note where usage could push it up.
Bad answer: "hosting is basically free." Sometimes true, but not when nobody has modelled your traffic.
8. "Can I see the real pages on my phone before I pay the final invoice?"
Ask to review the staging site on your own phone, mid-project, not on a shared screen at handover. Layout problems and slow pages show up on mobile data, not on a laptop on office wifi.
Good answer: a staging link, reviewed at agreed checkpoints.
Bad answer: one big reveal at the end. By then, changes cost extra.
9. "What would you tell me not to build?"
This is the question that separates a partner from an order taker. A good developer will push back on at least one thing you asked for, and explain what it costs you in time, money or conversion.
Good answer: an opinion, with a reason.
Bad answer: "Sure, we can build anything you want." Someone who never disagrees is not evaluating your project, they are quoting it.
The pattern behind the answers
You do not need to be technical to evaluate the replies. Listen for who is accountable, what you own, and whether the company has said no to anything. Teams that say no are the ones with standards.
The red flags, in one list:
- Nobody will name the person doing the work.
- No live sites, only screenshots.
- No answer on monitoring or uptime.
- Code and accounts stay in their name.
- SEO handed off as "a separate service".
- No post-launch window.
- No written monthly running cost.
- No staging review before final payment.
- Nobody ever disagrees with you.
Any single one can be survivable. Three together mean you should keep looking.
What this looks like in practice
A site is not a document you buy once. It is a system you will maintain, extend and depend on for enquiries. The cheapest quote is often the most expensive decision: rebuilding in eighteen months costs far more than the difference you saved, and a slow, under-built site bleeds customers the whole time it runs.
If you are comparing quotes right now, run these nine questions past each company in writing. The replies will sort them faster than any portfolio review, and it takes ten minutes.
Comparing quotes and want a straight second opinion? Message me on WhatsApp with two of the proposals and I will tell you which one is likely to bite you later. No pitch.
Related Reading
Get more insights like this
Join our list for practical automation, web engineering, and growth strategy — written by builders, for builders.
Manikandan S
Founder & Technical Lead at ZiyncFounder and technical lead at Ziync. I build high-performance websites and web applications for startups and mid-market teams: React, Next.js, Firebase. Based in Chennai, working with clients worldwide.