A restaurant chain owner in Bopal came to us last year after his third failed website in four years. Every agency he'd hired looked good on paper. Nice portfolio, decent Google reviews, a polished sales pitch. And every single one left him with a slow website, no idea who owned the code, and a WhatsApp number that stopped replying two months after launch.

He wasn't careless. He'd done what every blog tells you to do: check the portfolio, read the reviews, compare quotes. The problem is that advice, repeated everywhere, doesn't actually filter out bad vendors anymore. Every agency in Ahmedabad has a decent-looking portfolio now. Reviews can be requested from happy clients right after launch, before anyone finds out what maintenance actually looks like.

So here's what we'd tell a friend who asked us this, not what sounds good in a blog post.

Why the Standard Advice Stopped Working

"Check their portfolio" tells you they can build a website. It tells you nothing about what happens after you sign the contract. "Read Google reviews" tells you about the sales experience, since most reviews get collected at delivery, not six months in when the real test starts. "Compare quotes" just tells you who's willing to charge less, not who's cutting corners to hit that number.

None of this is bad advice exactly. It's just surface level, and in a market as crowded as Ahmedabad's IT sector, surface level doesn't separate anyone from anyone else.

What Actually Tells You Something

Ask who writes your code, specifically. Not "do you have a team," ask if the same developers who scope the project actually build it, or if it gets handed off to freelancers or subcontractors you'll never talk to. A lot of agencies sell in-house expertise and deliver outsourced work. There's nothing wrong with subcontracting if it's disclosed, but you deserve to know before you sign, not after something breaks and nobody can explain the code.

Ask for one reference you can actually call. Not a testimonial on their website, an actual phone number of a client from eight or ten months ago, past the honeymoon period. A company confident in their post-launch support will give you this without hesitation. One that goes quiet on this request is telling you something.

Ask what happens to the code and credentials if you leave. This sounds paranoid until it happens to you. Some agencies build on proprietary platforms or keep hosting and domain access under their own accounts, quietly making it expensive or technically difficult to switch vendors later. Before you sign anything, get it in writing: you own the code, the domain, and the hosting credentials, full stop.

Ask how they handle scope changes, before you need to. Every project changes shape once you start. The difference between a good agency and a bad one shows up here, not in the initial pitch. Do they have a clear process for scoping changes and pricing them, or does "just one more feature" quietly turn into months of unpaid delays and resentment on both sides?

Look at how they talk about timelines. If every question gets a "yes, definitely, no problem" without any pushback or clarifying questions, that's a sales answer, not a technical one. A team that actually understands the work will ask you things back, about your existing systems, your timeline flexibility, what "done" looks like to you specifically.

Red Flags Worth Walking Away From

A few patterns that, in our experience, reliably predict a bad outcome:

• Asking for full payment upfront before any milestone is delivered
• No written scope document, everything agreed over WhatsApp or phone calls
• Quotes dramatically lower than every other agency you've spoken to, often a sign of corners being cut on testing, security, or support
• Reluctance to put IP ownership and code handover terms in the contract
• No clear point of contact after the project manager who sold you the deal disappears post-signing

None of these alone is a dealbreaker, but two or more together is a pattern, not a coincidence.

A Better Way to Compare Vendors

Instead of comparing portfolios side by side, try asking the same three questions to every agency you're evaluating and comparing the answers directly:

• Who exactly will be working on my project, and can I meet them before I sign?
• What does support look like in month six, not week one, and what's included versus billed separately?
• If I'm not happy with the direction after the first milestone, what's the exit process?

The answers will tell you far more than any portfolio scroll ever could.

Where We Stand on This

At Zestra, we've picked up more than a few projects from businesses who got burned exactly the way described above. It shaped how we structure our own web development and mobile app development engagements: clear written scope before work starts, code and credentials that belong to you from day one, and a support process that doesn't disappear once the invoice is paid.

Evaluating Vendors Right Now? Get a Second Opinion.

If you're currently evaluating vendors and want a second opinion on a quote or a contract before you sign anything, reach out to us. We're happy to tell you honestly what to watch for, even if you don't end up working with us.

Talk to Our Team