Choose a software development company in India by running 12 concrete checks before signing anything: verify at least 3 live portfolio projects, speak with 2 past clients, agree milestone payments (a 50/25/25 split is common), and get code ownership, support terms, and a named point of contact in writing. A vendor that resists any of these checks is telling you something.

India has thousands of software agencies, from two-person freelancer teams to firms with hundreds of engineers. Price quotes for the same brief can differ by 5x or more, and the cheapest and the most expensive quote are both frequently the wrong choice. This checklist is designed so that a non-technical founder or manager can separate serious engineering partners from resume-ware in one or two calls.

The 12-Point Checklist

1. Verify the portfolio, not the brochure

Anyone can paste screenshots into a slide deck. Ask for live URLs and app-store links, then actually open them. Sign up, place a test order, check whether the product still works. If a project is under NDA, that is legitimate — but a company where every single project is conveniently under NDA has no verifiable track record.

2. Talk to at least two past clients

Ask for reference contacts for projects similar to yours in size and domain. On the call, ask three things: Did the project ship on time? What happened when something broke after launch? Would you hire them again? The pause before the third answer tells you more than any case study.

3. Choose fixed price or time-and-materials deliberately

Neither model is universally better — they allocate risk differently. Fixed price suits a well-defined scope; time-and-materials (T&M) suits evolving products. The table below summarises the trade-off:

Factor	Fixed Price	Time & Materials
Best for	Clearly scoped websites, MVPs, defined platforms	Long-running products with changing requirements
Budget certainty	High — the price is agreed up front	Low — you pay for hours consumed
Flexibility to change scope	Low — changes go through change requests	High — reprioritise every sprint
Vendor's incentive	Finish efficiently (watch for corner-cutting)	Keep billing hours (watch for padding)
What you must do well	Freeze scope in a written document	Review timesheets and output weekly

For a first project with a new vendor, fixed price with a written scope is usually the safer starting point. You can move to T&M once trust is established.

4. Insist on milestone-based payments

Never pay 100% up front, and be suspicious of vendors who ask. A common, fair structure is 50% to start, 25% at a working demo, 25% at delivery — the structure we use ourselves. Each milestone should be tied to something you can see and test, not to calendar dates alone.

5. Get code ownership in writing

The contract should state plainly that on final payment, the source code, database, designs, and all intellectual property belong to you. Ask where the code will live during development — you should have access to the repository (GitHub, GitLab, or similar) from week one, not receive a zip file at the end.

6. Check who will actually write your code

Ask to meet the engineers assigned to your project, not just the sales lead. Some agencies subcontract work to freelancers without telling you, which usually shows up later as inconsistent quality and slow bug fixes. A direct question — "Will any part of this be subcontracted?" — belongs in every first call.

7. Agree a communication cadence before kickoff

Good vendors propose a rhythm without being asked: a weekly demo call, a shared task board you can open any time, and a named point of contact who answers within one business day. If getting a reply takes three follow-ups during the sales process, it will not improve after they have your advance.

8. Demand a written scope document before signing

A one-line quote ("Complete app development – ₹3,00,000") is a dispute waiting to happen. Before you pay anything, you should have a document listing every screen, user role, and integration that is included — and, just as importantly, a section stating what is excluded. Vague scope is the single most common cause of failed outsourced projects.

9. Read the post-launch support terms

Software needs care after go-live. Ask three questions: How long is the free bug-fix warranty after delivery? What does support cost after that? What are the response times? Get the answers into the contract. A 30–90 day warranty on defects is a reasonable industry norm; "we'll always be there for you" is not a term.

10. Keep hosting, domain, and accounts in your name

Your domain registrar, cloud hosting, app-store listings, and payment-gateway accounts should be created under your email and ownership, with the vendor added as a collaborator. Companies that insist on owning these accounts are building a lock-in, whether they intend to or not. Managed hosting from the vendor is fine — as an optional, cancellable service (ours, for reference, is ₹3,600 per month after a free first month).

11. Look at engineering practices, not just output

You do not need to read code to check the basics. Ask: Is all code in version control? Is there a staging environment where you can test before releases go live? Are database backups automated? How are passwords and API keys stored? Confident, specific answers indicate a real engineering culture; hand-waving indicates cowboy work.

12. Compare quotes on scope, not on price alone

When one quote is ₹80,000 and another is ₹2,40,000 for "the same" project, they are almost never the same project. Put the scope documents side by side: admin panel included? Payment integration? Testing on how many devices? Also confirm whether quotes include 18% GST — Indian vendors quote both ways, and it is a large surprise to discover at invoice time.

Red Flags That Should End the Conversation

• 100% advance payment or heavy discounts for paying everything up front.
• No written scope — "don't worry, we'll handle everything" is not a plan.
• Guaranteed rankings or downloads — nobody can guarantee first-page Google results or app installs, and firms that promise them are comfortable saying untrue things.
• Unwillingness to give repository access during development.
• Quotes that arrive within an hour of a complex brief — real estimation takes real analysis.
• No verifiable company identity — a registered Indian company can be checked on the MCA portal in minutes; a vendor with no legal entity leaves you with no recourse.

Questions to Ask on the First Call

• Which two projects in your portfolio are closest to mine? Can I speak to those clients?
• Who exactly will work on my project, and will any of it be subcontracted?
• What is your payment structure, and what do I receive at each milestone?
• What happens if I want to change scope midway?
• Who owns the code, and when do I get repository access?
• What is covered free after launch, for how long, and what does support cost after that?
• Is GST included in this quote?

Frequently Asked Questions

How much does it cost to hire a software development company in India?

Fixed-price projects at small and mid-sized Indian firms commonly range from ₹9,999–₹74,999 for an informative website, ₹21,000–₹1,50,000 for a CRM or business platform, ₹99,999–₹2,49,999 for a mobile app with an admin panel, and ₹2,49,999–₹5,99,999 for marketplaces and custom ERPs, plus 18% GST. Large enterprise consultancies charge several multiples of these bands.

Should I choose a big agency or a small development company?

For projects under roughly ₹25 lakh, small and mid-sized firms typically give you senior attention that large agencies reserve for their biggest accounts. Large firms make sense when you need dozens of engineers, formal compliance certifications, or global support coverage. Match the vendor's size to your project's size.

Is a 50% advance payment normal?

Yes — 40–50% to begin work is standard for fixed-price projects in India, because the vendor commits a team before seeing further money. What matters is that the remaining payments are tied to demonstrable milestones, such as 25% at a working demo and 25% at delivery.

How do I verify an Indian software company is legitimate?

Check the company on the Ministry of Corporate Affairs (MCA) portal using its CIN or name — you can see incorporation date and directors. Verify the office address, look for live portfolio projects, and speak with past clients. All of this takes under an hour and filters out most bad actors.

What if the company disappears after taking my advance?

This risk is exactly why the checklist exists: pay only a milestone at a time, contract with a registered legal entity, keep repository and account access from day one, and never let unpaid work exceed what you could afford to lose. With those controls, the worst case is losing one milestone, not the project.

Do I need a technical co-founder to manage an outsourced project?

No, but you do need discipline: a written scope, weekly demos you actually attend, and testing every milestone yourself. If the budget allows, a part-time technical advisor who reviews the vendor's work for a few hours a month is a worthwhile insurance policy.

Get a Scope and Quote You Can Compare

The fastest way to apply this checklist is to run a real vendor through it. Send us your requirement via our contact page and we will respond with a written scope, a milestone plan, and a fixed quote against our published pricing — the same documents this article tells you to demand from anyone you evaluate.