Most software projects in India do not fail because of technology. They fail because the scope was vague, the vendor disappeared after launch, or the client discovered too late that they did not own their own code. This checklist is what we would want any client to ask us — and any other vendor they are considering.
1. Ask for live, working examples — not just screenshots
A portfolio of logos and mock-ups proves little. Ask to see a product that is running in production, ideally one similar to yours, and ask what part of it the company actually built. Good partners can walk you through a live system and explain the trade-offs they made.
2. Verify the company is real
Check the registration on the MCA portal (CIN for a private limited company, LLPIN for an LLP), the GSTIN, and a physical address. A registered entity with a GST invoice gives you a contract party you can hold accountable.
3. Meet the people who will build your product
In many agencies the person who sells the project is not the person who builds it. Ask who the lead engineer will be and talk to them before you sign. You want direct access to the builder, not a relay through an account manager.
4. Insist on a written scope with milestones and acceptance criteria
A one-page quotation is not a scope. The proposal should list features, user roles, integrations, what is excluded, delivery milestones and how each milestone will be accepted. Vague scope is the single biggest source of disputes.
5. Pay by milestone, not all upfront
A reasonable structure is an advance followed by payments tied to delivered, working milestones. This keeps both sides aligned and limits your risk.
6. Make sure you will own the source code and IP
The contract should state that on final payment you receive the complete source code, database schema, deployment documentation and admin access to every account created for the project. Without this you are locked in.
7. Ask how you will see progress
Weekly demos on a staging link are far better than monthly status reports. If you can click through working software every week, problems surface early when they are cheap to fix.
8. Check the technology choices for the long term
Ask why a particular stack is recommended. Mainstream, well-supported technologies (for example React or Next.js, Node.js, PHP/Laravel, Flutter, PostgreSQL or MySQL) make it easier to hire developers later if you ever change vendors.
9. Ask about security basics
At minimum: HTTPS everywhere, role-based access, hashed passwords, no secrets in the code repository, regular backups and a plan for restoring them. Ask who will have access to production data.
10. Plan hosting, monitoring and backups before launch
Someone has to run the software after go-live. Clarify where it will be hosted, who pays for servers, how it will be monitored and how often backups are taken. A partner who can also host and maintain the system removes a common gap between “developed” and “actually running”.
11. Get the support and AMC terms in writing
Ask what is covered free after launch (bug fixes within a warranty period), and what an Annual Maintenance Contract includes — updates, security patches, small changes, response times.
12. Sign an NDA before sharing sensitive details
Any serious company will sign a Non-Disclosure Agreement before you share business plans, data or proprietary processes.
A quick scorecard
| Question | Good answer | Red flag |
|---|---|---|
| Can I see live work? | Walkthrough of a production system | Only mock-ups or logos |
| Who owns the code? | You, on final payment, in writing | “We licence it to you” |
| How is progress shown? | Weekly demos on staging | “We’ll show you at the end” |
| Who runs it after launch? | Clear hosting and AMC plan | “Your IT team can handle it” |
At FutureFist Tech Solutions LLP we work this way by default: NDA first, written scope and milestones, weekly demos, source code handover and optional hosting setup and AMC support. You can see examples in our case studies.
Frequently asked questions
What should I check before hiring a software development company in India?
Check live work samples, company registration (CIN or LLPIN and GSTIN), who will actually build the product, a written scope with milestones, milestone-based payments, source code and IP ownership, weekly demos, security practices, hosting and AMC terms, and an NDA.
Who should own the source code of custom software?
The client should. The contract should state that on final payment the client receives the full source code, database schema, documentation and admin access to every account created for the project.