Photo: Unsplash
Why the Company You Choose Matters More Than the Technology
Choosing the wrong software development company is the most expensive mistake an Indian business owner can make — it costs not just money but months of wasted time and missed business opportunities. I have consulted on rescue projects where businesses spent ₹15-25 lakhs with the wrong vendor and received unusable software — then had to spend another ₹12-18 lakhs rebuilding from scratch with a competent team. The total loss: ₹30-40 lakhs and 12-18 months.
The Indian software development market has over 50,000 registered companies and countless freelancers. Quotes for the same project can range from ₹3 lakhs to ₹35 lakhs. The cheapest quote is almost never the best choice, but the most expensive is not automatically the safest either. What matters is finding a team that understands your business domain, communicates clearly, follows proven development practices, and will be around to support the software after launch.
This guide gives you 10 specific questions to ask — and explains what good answers versus red-flag answers look like. Use this as your evaluation framework when interviewing potential development partners.
Evaluating Technical Capability and Portfolio
A software company's portfolio should demonstrate not just what they built, but that they can build something similar to what you need — and that those projects are still running successfully. Ask to see 3-5 live, working applications they have developed. Screenshots and demo videos are easy to fabricate; running production software is not. If they cannot show you live projects, that is a significant red flag.
Question 1: Can you show me 3 live applications you have built that are still in active use? Good answer: They share URLs or arrange demos of running applications with real data. Red flag: They only have screenshots, or their portfolio projects are all "under NDA" with no verifiable work.
Question 2: What technology stack do you recommend for my project, and why? Good answer: They recommend technologies based on your specific requirements — team size, expected scale, integration needs, maintenance considerations. They explain trade-offs. Red flag: They recommend whatever they are most comfortable with regardless of your needs, or they push trendy technologies without justification.
Question 3: How do you handle code quality and testing? Good answer: They describe specific practices — code reviews, automated testing, CI/CD pipelines, coding standards documentation. They can show you a sample test coverage report. Red flag: "We test thoroughly before delivery" with no specifics about how. Manual-only testing for any project above ₹10 lakhs is unacceptable — it means bugs will surface in production.
Communication, Process, and Project Management
Poor communication is the second most common reason software projects fail — right after unclear requirements. A technically brilliant team that communicates poorly will deliver something that does not match your expectations. Before signing any contract, evaluate how the company communicates during the sales process — that is your preview of how they will communicate during the project.
Question 4: Who will be my primary point of contact, and how often will we communicate? Good answer: You will have a dedicated project manager who provides weekly progress reports, is available for questions during business hours, and schedules regular demo sessions. Red flag: "You can email our team" with no specific person assigned, or the sales person disappears after contract signing and you are left talking to rotating developers.
Question 5: What project management methodology do you follow? Good answer: They describe a clear process — whether Agile/Scrum with 2-week sprints, or a structured waterfall approach for well-defined projects. They explain milestones, deliverables at each stage, and how you will review progress. Red flag: No clear methodology, or they claim "Agile" but cannot describe their sprint process, backlog management, or how they handle changing requirements.
Question 6: How do you handle change requests and scope changes? Good answer: They have a formal change request process — documented changes, impact assessment (time and cost), your approval before any work begins. Red flag: "We are flexible and accommodate changes" without a process. This means either they will say yes to everything and blow the budget, or they will resist all changes and deliver exactly the original spec even when it no longer matches your needs.
Understanding Pricing Models and Contract Terms
The pricing model you choose directly affects your risk exposure, budget predictability, and flexibility to adapt during development. There is no universally "best" model — the right choice depends on how well-defined your requirements are and how much you expect them to evolve.
Question 7: What pricing model do you recommend, and what is included in the price? Good answer: They recommend a model based on your project's characteristics and explain what is included (design, development, testing, deployment, documentation, training) and what is not (hosting, third-party API costs, post-launch maintenance). They provide a detailed breakdown, not just a lump sum. Red flag: A single number with no breakdown, or a quote that seems to include everything — hosting, maintenance, unlimited changes — for a suspiciously low price.
For Indian businesses, here is a pricing reality check: Junior developers cost ₹500-1,200/hour. Mid-level developers cost ₹1,200-2,500/hour. Senior developers and architects cost ₹2,500-5,000/hour. A project quoted at ₹5 lakhs that requires 6 months of work from 2 developers — do the math. At minimum market rates, that is at least ₹12-15 lakhs of developer time. If someone quotes ₹5 lakhs, either they are using extremely junior developers, cutting corners on testing and documentation, or planning to ask for "change order" fees later.
Question 8: What are the payment terms, and are payments tied to milestones? Good answer: Payments are milestone-based — 20% advance, then payments at design completion, first module delivery, testing completion, and final delivery. Each payment is triggered by your sign-off on deliverables. Red flag: More than 30% upfront, or payments tied to time rather than deliverables. If a company asks for 50% upfront on a ₹20 lakh project, you have very little leverage if things go wrong.
Red Flags That Should Make You Walk Away
After evaluating hundreds of software development proposals over 12 years, certain patterns consistently predict project failure. If you see two or more of these red flags, walk away regardless of how attractive the price seems.
No questions about your business. If the company jumps straight to quoting without deeply understanding your business workflows, they will build generic software that does not fit your actual needs. A good development partner asks more questions about your business than about the technology.
Unrealistic timelines. A company promising to build a complex business application in 4-6 weeks is either planning to deliver low-quality work or does not understand the scope. For reference: a well-built inventory management system with billing, reporting, and integrations takes 3-5 months minimum. Anyone promising it in 6 weeks is cutting critical corners.
No post-launch support plan. Software needs ongoing maintenance — bug fixes, security updates, feature additions, server management. If the company has no clear post-launch support offering, you will be stranded with software that gradually breaks as operating systems, browsers, and APIs evolve. Ask Question 9 and Question 10 specifically about this.
Question 9: What warranty and post-launch support do you provide? Good answer: Minimum 3-6 months warranty for bug fixes at no extra cost, plus clear AMC (Annual Maintenance Contract) options with defined response times and scope. Red flag: "We can discuss support later" or no warranty period.
Question 10: Who owns the source code, and how is it handed over? Good answer: You own all intellectual property. Source code is maintained in a repository you have access to throughout the project, with full handover at completion including documentation and deployment guides. Red flag: The company retains code ownership, charges for code handover, or does not use version control.
Your Due Diligence Checklist Before Signing
Before signing a contract with any software development company, complete this verification checklist — it takes 2-3 days but can save you lakhs.
Verify company registration: Check their GST registration on the GST portal and company incorporation on the MCA (Ministry of Corporate Affairs) website. Confirm the company has been operating for at least 2-3 years. Call at least 2 references from their client list — ask specifically about timeline adherence, budget accuracy, communication quality, and post-launch support responsiveness.
Review their online presence: Check Google reviews, Clutch.co profile, GlassDoor employee reviews (high employee turnover means your project will suffer from developer churn). Search for complaints or disputes. Ask for a sample contract and have your lawyer review it before signing. The ₹15,000-25,000 legal review fee is the cheapest insurance you can buy for a ₹15-30 lakh project.
Conduct a small paid trial: Before committing to the full project, consider engaging them for a small paid discovery phase (₹50,000-1,00,000) — requirements documentation, wireframes, and a technical architecture proposal. This gives you firsthand experience of their communication, quality, and work ethic before committing the full budget. If the discovery phase goes poorly, you have lost ₹50,000-1,00,000 instead of ₹15-30 lakhs.
Evaluate team stability: Ask who will be working on your project by name and role. Ask about the team's experience with similar projects. Inquire about their backup plan if a key developer leaves mid-project. Companies with high developer turnover pose a serious risk to project continuity and quality.
Frequently Asked Questions
How much should custom software development cost in India?
Custom software development in India typically ranges from ₹5-50 lakhs depending on complexity. A simple business application (inventory, billing, basic reporting) costs ₹5-12 lakhs. A mid-complexity system (multi-module ERP, CRM with integrations) runs ₹12-25 lakhs. Complex enterprise solutions (multi-tenant platforms, AI features, heavy integrations) cost ₹25-50+ lakhs. Be wary of quotes significantly below market — they usually mean corner-cutting on architecture, testing, or documentation that costs you more in maintenance later.
Should I hire a freelancer or a software company?
For projects under ₹8-10 lakhs with well-defined scope, an experienced freelancer can be cost-effective — you save on company overhead. For projects above ₹10 lakhs or with ongoing maintenance needs, a company provides team redundancy (your project does not stall if one person is unavailable), structured project management, and formal accountability. The key risk with freelancers is bus factor — if they become unavailable, your project stops entirely. With a company, another team member can continue.
What is the difference between fixed-price and time-and-materials contracts?
Fixed-price contracts set a total cost upfront — you pay ₹15 lakhs for the agreed deliverables regardless of how long it takes. This works well when requirements are crystal clear and unlikely to change. Time-and-materials (T&M) contracts charge for actual hours worked at agreed rates (₹1,500-4,000/hour for Indian developers). T&M works better when requirements will evolve, but requires more oversight. A hybrid approach — fixed price for Phase 1 with well-defined scope, then T&M for iterative improvements — often gives the best balance of budget certainty and flexibility.
How do I verify a software company's past work and claims?
Ask for 3-5 references from completed projects similar to yours — then actually call those references. Ask specific questions: Was it delivered on time? On budget? How was communication during the project? How responsive are they for post-launch support? Also request to see live, working applications they have built (not just screenshots in portfolios). Check their GitHub or code repositories if possible. Google their company name with keywords like "review" and "complaint." Verify their GST registration and company incorporation details on MCA portal.
What should a software development contract include?
Essential contract elements: detailed scope of work referencing the requirements document, milestone-based payment schedule (never pay more than 20-30% upfront), timeline with specific deliverable dates, intellectual property ownership clause (you must own all code), source code handover terms, warranty period (minimum 3-6 months post-launch bug fixes), confidentiality/NDA clause, change request process and pricing, acceptance testing criteria, and termination clause with code handover provisions. Have a lawyer review the contract — the ₹15,000-25,000 legal fee is negligible compared to the project cost.
Need Help Evaluating Software Development Companies?
I provide independent technical assessments of software development proposals — reviewing quotes, evaluating vendor capabilities, and identifying red flags before you commit. Get an unbiased second opinion that could save you lakhs.