This is written for people who've been on both sides — who've built things and who've had to evaluate teams that build things. Standard vendor evaluation advice misses too much. Here's what actually matters in the Mumbai context.
The market reality
Mumbai's tech corridor — BKC to Powai, with clusters in Andheri East and Lower Parel — houses everything from 5-person product studios to 2,000-person IT service firms. The market is mature enough that most firms can talk the talk. When you're shortlisting a software development company in Mumbai, technical depth is where real differentiation lives.
What to test in technical conversations
Architecture reasoning is the most reliable signal. Pick a project from their portfolio and ask how they'd approach it differently now. What database decisions would change? How would they handle the same scale requirements with current tooling? Teams that have genuinely shipped complex systems have opinions on this. Teams that haven't stay surface-level.
Ask specifically about:
- Schema design and migration strategy in live production systems
- API versioning and backward compatibility across client release cycles
- Observability — what does monitoring look like post-deployment?
- PII handling and data security, especially critical in fintech and healthtech
- Incident response — who gets called at 11pm, and what's the documented process?
The cloud question
Most serious Mumbai firms work across AWS and Azure. Ask which platform they'd recommend for your workload and why. If the answer doesn't involve follow-up questions about your latency requirements, team familiarity, or expected traffic — they're recommending what they know, not what fits you.
The handoff problem
This is specific enough to the Mumbai market to call out directly. A significant number of engagements end with code that works but isn't maintainable — no docs, no runbooks, no tests the internal team can operate. Ask explicitly: what does the repo look like at handoff? What can my team run on day one without calling you?
Good teams have a standard answer because handoff is built into their process. Teams that treat it as a future conversation are telling you it's not a priority.
IP and governance
Confirm before any contract: who owns the code and credentials from day one? Column-level access controls, audit logging, data lineage — designed in from the start or retrofitted on request? The answer to that second question reveals more about default engineering standards than any portfolio screenshot.
Top comments (0)