Bengaluru has more web development companies than almost any city in India. That is good for price and bad for signal — portfolios look similar, everyone claims the same expertise, and the differences that matter are invisible until you are six weeks into a project that is going wrong.

These twelve questions surface those differences in a single conversation. For each, we have included the answer you want to hear and the answer that should worry you.

The twelve questions

1. Do I own the source code outright?

Good answer: "Yes, full ownership transfers on final payment, and it is written into the contract."
Worrying answer: Anything conditional, or a licence rather than ownership. Some agencies retain code so you cannot leave. This is the single most important question on the list.

2. Will I have a staging environment?

Good answer: "Yes, you review everything on a staging URL before it goes live."
Worrying answer: "We will just update the live site." That means every change is a live risk and there is no review step.

3. What happens if the developer on my project leaves?

Good answer: A description of documentation, code review, and version control that lets someone else pick it up.
Worrying answer: Vagueness. In a city with Bengaluru's attrition rates, this will happen on a long project.

4. Can I see a site you built two or more years ago?

Good answer: They show one, and it still works and loads fast.
Worrying answer: Only recent work. Anyone can make a site look good on launch day; durability is the real test.

5. How are change requests priced?

Good answer: A clear hourly rate or a defined revision allowance, agreed in writing.
Worrying answer: "Unlimited revisions." This is never true and becomes a dispute later.

6. What exactly does "SEO included" cover?

Good answer: Specifics — schema markup, meta structure, sitemap, Core Web Vitals targets, semantic HTML.
Worrying answer: "We will add keywords." That is not SEO; that is 2009.

7. How will the site perform on a mid-range Android phone on 4G?

Good answer: They mention performance budgets, image optimisation, and testing on real devices.
Worrying answer: They only discuss how it looks on a desktop. Most of your Indian traffic will be mobile.

8. Who writes the content?

Good answer: Clearly stated either way, with copywriting priced if they do it.
Worrying answer: Silence. Unwritten content is the most common cause of stalled launches.

9. What is the payment schedule?

Good answer: Milestone-based — typically 30–40% up front, the rest tied to deliverables.
Worrying answer: Full payment before work begins, which removes all their delivery risk and concentrates it on you.

10. Which technologies will you use, and why?

Good answer: A reasoned choice tied to your needs and your ability to maintain it.
Worrying answer: Buzzwords with no rationale, or a stack so exotic that only they can maintain it.

11. What happens after launch?

Good answer: A defined warranty period for bugs, plus optional maintenance priced transparently.
Worrying answer: "Contact us if there is a problem" — with no terms.

12. Can I speak to two clients directly?

Good answer: Yes, with contacts provided.
Worrying answer: Only written testimonials. Ask referees specifically: did it launch on time, and what happened when something broke?

If you only ask three: source code ownership, a two-year-old live reference site, and how change requests are priced. Those three alone filter out most of the problems.

Verifying claims yourself

You do not need to be technical to check most of this in ten minutes:

  • Run a site they built through Google PageSpeed Insights — a mobile score under 50 tells you performance is not part of their process.
  • Open one of their sites on your own phone and try to use the menu and contact form.
  • Check their company registration (CIN or GST) is real and matches the name on the contract.
  • View page source on a portfolio site and look for a JSON-LD schema block — its absence tells you how seriously they take SEO.
  • Search their company name alongside "review" and read past the first page.

Making quotes comparable

Most quote confusion is self-inflicted. Send every agency an identical brief stating: number of unique page designs, exact integrations, who supplies content, whether source code ownership transfers, and what post-launch support is included.

When every agency is quoting the same scope, the spread narrows — and the differences that remain finally tell you something real.

Ready to compare? Send us your brief, or read our Bengaluru website cost guide to calibrate what the numbers should look like.

Frequently asked questions

Ask who owns the source code, whether you get a staging environment, what happens if the assigned developer leaves, how change requests are priced, and to see a live site they built that is at least two years old. The answers to those five questions predict project outcomes better than any portfolio.
Check their CIN or GST registration, ask for two client references you can actually call, and inspect a live site they built — view the page source, run it through PageSpeed Insights, and check it on your phone. Real work holds up to inspection.
Almost never, but neither should you assume expensive means good. Normalise the quotes first by sending an identical brief, then judge on what each includes. The cheapest quote usually excludes something the others included.