Choosing a Software Development Company in Delhi NCR: A 12-Point Checklist

Choosing a software development company in Delhi NCR comes down to twelve checks you can finish in about a week: verify the legal entity, confirm who writes the code, get the IP assignment in writing, take ownership of the cloud and store accounts, test the handover plan, and ask how they will meet the DPDP deadline. Skip these and you inherit somebody else’s technical debt.

Search for a software development company in Delhi NCR and most of what comes back is a thinly disguised sales page. This one is a checklist you can run against any agency, including ours. Every item is something you can verify yourself, usually from a public government portal or from a clause in the contract you are about to sign. Nothing here requires you to be technical.

Work through it in order. Points 1 to 3 kill bad shortlists fast. Points 4 to 8 are the ones that cost money later if you get them wrong. Points 9 to 12 decide what your life looks like after go-live.

What “Delhi NCR” actually covers

The National Capital Region is not a city. As defined by the National Capital Region Planning Board, it covers the whole of the NCT of Delhi plus 24 districts spread across Haryana, Uttar Pradesh and Rajasthan, roughly 55,083 square kilometres in all. Gurugram, Noida, Faridabad and Ghaziabad sit inside it, but so do Meerut, Rewari, Karnal, Alwar and Bharatpur.

That matters for two practical reasons. First, a vendor who calls themselves local may be a three hour round trip away, which changes what “we will come to your office” is worth. Decide early whether you actually need on-site presence, or whether weekly video reviews and a shared board are enough. Most product work does not need the office visit.

Second, the vendor’s registered office decides which state’s stamp duty applies to your agreement and which courts hear a dispute if the jurisdiction clause is silent or badly drafted. A Noida entity and a Gurugram entity are in different states. Read the jurisdiction clause and make sure it names a specific city, not just “India”.

The 12-point checklist for choosing a software development company in Delhi NCR

1. Verify the entity before the first call

Ask for the CIN or LLPIN and the GSTIN, then check them yourself. Company and LLP master data is public on the MCA portal, and any GSTIN can be checked on the GST portal’s Search Taxpayer tool, which shows the legal name, registration date, status and constitution of business. Two things to look for: the trading name should match the registered entity you will be paying, and the GST registration should be active. If the invoice will come from a different entity than the one pitching you, ask why in writing.

2. Find out who will actually write your code

Plenty of firms sell you a senior team and staff the build with subcontractors you never meet. Ask three direct questions: are the developers on your payroll, will they be full time on this project, and can you meet them before signing. Then ask for the names to be written into the statement of work with a clause that substitutions need your approval. A vendor who will not name people is telling you something.

3. Ask to see a running product, not a deck

Portfolios are easy to fake. Live products are not. Ask for two or three apps you can download from the Play Store or App Store today and use as a real user, plus the case study behind one of them. Our Go Material construction materials marketplace is an example of what that looks like: a live buyer app, a supplier side, and a public write-up of what was built. If the marketplace model is what you are planning, the mechanics are covered in more depth in our post on building a two-sided marketplace.

4. Get the IP assignment in writing, with all four elements

This is the single most expensive clause to get wrong. Under the Copyright Act, 1957, an assignment of copyright must be in writing and signed, and section 19 requires it to identify the work and specify the rights assigned, the duration and the territorial extent. Section 19(5) sets the default duration at five years if the agreement is silent, and section 19(6) presumes the territory is India only. So a contract that just says “all IP belongs to the client” without those specifics can leave you with a five year licence limited to India rather than the worldwide, perpetual ownership you assumed you bought. Insist on explicit words: worldwide, perpetual, irrevocable, for all rights, in all media.

5. Own the accounts from day one

The code repository, the cloud account, the domain, the DNS, the Play Console and the App Store developer account should all be registered in your company’s name with your billing details, and the agency added as a collaborator. This costs nothing at the start and is painful to reverse later. If a vendor insists on holding your Play Console listing under their developer account, that is a lock-in mechanism, not a convenience.

6. Ask how they will meet the DPDP deadline

The Digital Personal Data Protection Rules were notified in November 2025 with a staggered commencement. The Data Protection Board provisions applied straight away, consent manager registration follows twelve months later, and the substantive obligations on data fiduciaries, covering notice and consent, security safeguards, breach reporting, and retention and erasure timelines, come into force eighteen months after notification, in May 2027. The government has described this explicitly as an eighteen month period for phased compliance.

You are the data fiduciary. Your development partner is your processor, and the Act requires that relationship to sit under a valid contract. Ask what the vendor’s plan is for consent capture, breach detection and notification, data retention and deletion, and processor agreements. A firm that has not read the Rules will say “we follow best practices” and change the subject.

7. Pin the engagement model and the price of a change

For the full twelve-month arithmetic, read staff augmentation vs fixed price: which costs less over 12 months.

Fixed scope, time and materials, and a dedicated team are three different risk profiles, compared in the table below. Whichever you pick, ask the question most buyers forget: what does a change request cost, who decides whether something is a change or a defect, and how quickly is it quoted. Get the hourly or per-sprint change rate written into the contract before you sign, not after you are committed. If you are still sizing the budget, our breakdown of what an MVP actually costs in India at each stage gives you a benchmark to argue from.

8. Check the tax mechanics on the invoice

Software development services are taxed at 18 percent GST, under SAC 998314 for software development and 998313 for IT consulting. Your quote should say clearly whether the number is inclusive or exclusive of GST, because 18 percent on a 30 lakh build is 5.4 lakh you either budgeted for or did not. On the other side, you deduct TDS: section 194J applies at 10 percent on professional services and 2 percent on technical services, with a threshold of ₹50,000 per financial year per category, and 20 percent if the vendor has not given a PAN. Agree in advance which rate applies to your engagement so the vendor is not surprised by a short payment.

9. Ask whether the vendor is a micro or small enterprise

This is the item almost nobody checks, and it is a tax risk that sits with you rather than the vendor. Section 43B(h) of the Income Tax Act, in force from 1 April 2024, allows a deduction for payments to a supplier registered as a micro or small enterprise under the MSMED Act, 2006 only in the year the payment is actually made, if you pay beyond the statutory limit. That limit is 45 days where there is a written agreement and 15 days where there is not. Medium enterprises and traders are outside it. Ask for the Udyam registration number, note the classification, and set your payment terms to match. A 90 day payment cycle with a micro enterprise vendor pushes your deduction into the next financial year.

10. Look at the QA and release process, not the QA promise

Ask to see the pipeline rather than hear about it. Concrete questions: is there a staging environment that mirrors production, what is covered by automated tests as opposed to manual checks, how long does a release take from merge to live, and what is the rollback procedure when a release breaks something on a Friday evening. Ask who signs off a release. If the answer is “the developer who wrote it”, that is a process gap.

11. Define handover and exit before you sign

Write the exit into the contract while everyone is still friendly. A workable handover clause covers: current source code in your repository, environment and deployment documentation, a runbook for common operational tasks, all credentials transferred and the vendor’s access revoked on a stated date, a named transition period with a rate attached, and a list of third party services with their accounts and renewal dates. Then test a small piece of it during the build. Ask for the deployment document at the halfway point. If it does not exist then, it will not exist at the end.

12. Read the support contract properly

Post-launch is where relationships sour. Get three definitions in writing. First, what counts as a defect covered under warranty versus a change you pay for, and for how long. Second, the response and resolution windows for each severity level, and what happens if they are missed. Third, who pays when iOS or Android ships a breaking OS update, or when a payment gateway deprecates an API. That last one is not hypothetical. It happens every year, and app maintenance costs are covered in our guide to mobile app development cost in India.

Engagement models compared

How to score your shortlist

Three vendors is the right number. More than that and you will not do the work properly on any of them. Run the same process on each:

1. Verify the entity, GSTIN and Udyam status before you spend an hour on a call. This alone usually removes one name.
2. Send all three the same one page brief and ask for a written approach, not a price. Compare what questions they ask you back. The good ones ask about your users and your constraints; the weak ones ask only about your budget.
3. Ask each to walk you through one live product they built, screen by screen, including something that went wrong and what they did about it.
4. Request the draft contract early, not after you have chosen. Read clauses 4, 5, 11 and 12 above before you fall in love with a proposal.
5. Score each vendor out of 12 on this checklist. Weight IP assignment, account ownership and handover double, because those are the ones you cannot fix later.
6. Call one reference the vendor did not hand you. Their case study pages and app store listings will tell you who their clients are.

Red flags when shortlisting a software development company in Delhi NCR

• A firm price before any discovery. A number quoted in the first call is either padded heavily or will grow through change requests. Neither is good for you.
• No named team. If you cannot get developer names into the statement of work, you do not know who is building your product.
• Reluctance to put IP assignment in the specific language of section 19. Vagueness here is rarely accidental.
• Accounts held in the vendor’s name. Play Console, cloud billing, domain registration. All three should be yours.
• No answer on DPDP. May 2027 is not far away for a product that handles customer data.
• A portfolio of screenshots with no live links. Ask for one thing you can install and use today.
• A quote that does not mention GST. It suggests either inexperience or a number that is about to grow by 18 percent.
• Pressure to sign this week for a discount. The discount is real, the deadline usually is not.

None of these is proof of a bad partner on its own. Two or three together is a pattern, and patterns are what you are looking for.

Your next step

Take this checklist to whoever is on your shortlist and ask them to answer it point by point in writing. A firm that gives you twelve straight answers has told you more about how they will behave over a nine month build than any proposal deck can. If you want a second opinion on a shortlist or a draft contract, or you want to talk through what your build actually needs, our custom software development team is happy to look at it with you. We are a software development company in Delhi NCR ourselves, so we are on the receiving end of this list too, which is rather the point of publishing it. Bring the questions, not the pitch.