Business
How to choose a web development company in India
What to ask, what the answers tell you, and the warning signs worth walking away from — written by an agency, which you should factor in.
Judge an agency on three things: whether they understand your business before proposing a solution, whether they will tell you something you do not want to hear, and what the contract says about code ownership and exit. Portfolio quality matters less than most buyers assume, because you cannot tell from a screenshot who actually did the work or what state the code is in.
Questions that reveal capability
Ask them to talk you out of something
Describe what you think you need and ask whether it is the right approach. An agency that agrees enthusiastically with every idea is selling, not advising. The most valuable supplier is the one who says a mobile app will not fix your retention problem, or that you do not need a custom build.
Ask who will actually do the work
Meeting a senior team during the pitch and being handed to juniors after signing is a well-worn pattern. Ask for the names, ask to speak to them, and ask what else they will be working on. Reluctance here is informative.
Ask what went wrong on their last project
Every project has problems. An agency that cannot name one is either inexperienced or not being straight with you. What you are listening for is whether they noticed, what they did, and whether they take responsibility.
Ask how they handle a change of direction mid-project
You will change your mind. The answer tells you whether they work in reviewable milestones or expect a specification frozen in month one and defended thereafter.
What to check in the contract
| Term | What you want | Warning sign |
|---|---|---|
| Code ownership | Yours on payment, in writing | Vague, or ownership retained |
| Repository | Your account from day one | Handed over at the end |
| Infrastructure | Your cloud and domain accounts | Held under agency accounts |
| Scope | Written, with exclusions stated | A price with no scope |
| Milestones | Reviewable deliverables | One payment, one delivery |
| Exit | Defined handover and documentation | Not mentioned |
| Maintenance | Priced separately and clearly | Assumed, unpriced |
The infrastructure point catches people out. If your domain, hosting and app store accounts are under an agency's control, moving away is painful and occasionally expensive. Own your accounts and grant access.
Warning signs
- Guaranteed Google rankings, or guaranteed AI recommendations — nobody can promise either
- A quote given before anyone has asked what your business does
- Portfolio work they cannot discuss in detail, which often means they did not do it
- Unwillingness to let you speak to the actual developers
- A price dramatically below everyone else, which is usually a scope misunderstanding you will pay for later
- No written scope, or scope described only in a proposal deck
- Claimed compliance certifications with nothing to produce
How to read a portfolio
Screenshots tell you almost nothing. A polished image may be a concept that never shipped, or work done by a designer who has since left.
More useful:
- Open the live sites. Are they still up? Are they fast? Test one on your phone.
- Ask what the business problem was and what the outcome was
- Ask which parts they built and which were subcontracted
- Ask for a reference from a client whose project had difficulties
That last request is the most revealing thing you can ask for.
On price
Development pricing in India varies enormously — by city, by seniority, by whether you are buying a team or a project, and by how much of the work is design versus engineering. Any published figure without that context is close to meaningless, which is why this article does not give you one.
What you can do is make quotes comparable. Give every agency the same written brief, ask each to state scope and exclusions explicitly, and compare like with like. Quotes that differ by a factor of three usually differ in what is included, not in value.
Be wary of the cheapest quote for the same reason you would be with any other trade: the shortfall is recovered somewhere, usually in change requests or in code somebody else has to fix.
The single best signal
How they behave before you have paid them anything. Do they ask about your business or talk about themselves? Do they answer the question asked? Do they tell you when something is a bad idea?
How a supplier behaves while trying to win the work is the best available evidence of how they will behave once they have it.