Most advice on choosing a software company says the same three things: look at the portfolio, read the reviews, compare the prices. None of that is wrong, but it does not tell you how to compare three proposals that describe different scopes, different teams and different payment terms.
This guide gives you a process you can run in a few weeks. Write a short brief, confirm that each company is a real, registered business, score every vendor on the same criteria, and make sure the right paperwork exists before you pay anything. It ends with the red flags that should stop a deal.
Quick answer: Choose a custom software development company by comparing vendors against your own written brief, not their sales decks. Verify the business through its GSTIN and company records, then score each vendor on how well it understood your problem, verifiable past work, the actual team, a written scope with milestones, IP and code-access terms, security practice and support. Sign only when all of it is in writing.
Write a one-page brief before you call anyone
A vendor can only quote what you describe. If you describe the project differently on each call, you will get quotes you cannot compare. Spend an hour writing one page and send the same page to every company on your shortlist.
- The problem: what is slow, manual or error-prone today, in plain words.
- Users and roles: who will use the software, from the owner to branch staff, and what each person must or must not see.
- Must-have workflows: the three to five processes the first version has to handle.
- Integrations: Tally, a payment gateway, WhatsApp, a biometric device or an existing database.
- Constraints: a deadline, a budget range and where the data must be hosted.
Our guide on writing a software requirements document covers this in more detail. A good company will ask questions that sharpen your brief. A company that sends a quote without asking any is guessing.
Confirm the company is what it says it is
In India you can check the basic facts about a vendor for free, in a few minutes, before you share anything sensitive.
- GST registration: ask for the GSTIN and look it up with the taxpayer search on the GST portal. The legal name there should match the name on the proposal and the contract. If your business is GST-registered, a proper tax invoice from a registered supplier is what lets you claim input tax credit, subject to the usual conditions.
- Company records: for a private limited company or an LLP, the company master data on the MCA portal shows whether it is active, when it was incorporated and who its directors are.
- Who signs: the contract should name the same legal entity, with the same GSTIN, that will invoice you. A brand name on its own is not a contracting party.
- Where they work: an office address you could visit and a named project lead you can call. Remote work is fine. Anonymity is not.
Score every vendor on the same criteria
After the discovery calls, fill in one scorecard per company. The weights matter: a polished portfolio should count for less than proof that the vendor understood your problem. Adjust the weights to suit your project, but fix them before you look at the prices.
| Criterion | What good looks like | Suggested weight |
|---|---|---|
| Understanding of your problem | They restate the problem in their own words, ask about edge cases and suggest what to leave out of the first version. | 25 |
| Relevant, verifiable past work | Projects of similar complexity, a live demo or a past client you can speak to. | 15 |
| The team you will work with | A named project lead and developers, and you have met at least the lead before signing. | 15 |
| Written scope and milestones | A specification with deliverables, acceptance criteria and a payment tied to each milestone. | 15 |
| Code, IP and access terms | Full assignment of source code and IP, with repositories and cloud accounts in your name. | 15 |
| Security practice | Role-based access, secure coding against the OWASP Top 10 and testing before go-live. | 10 |
| Support after go-live | A warranty period for defects and a separate, priced support plan. | 5 |
Score each row from 1 to 5, multiply by the weight and add up the total. Bring price in only after this step: as a tie-breaker between vendors who score close to each other, or as a reason to ask the cheaper vendor what it left out. The OWASP Top 10 is a useful reference when you ask how a vendor writes secure code.
Questions to ask on the discovery call
- Who exactly will work on my project, and can I speak to the lead developer before we sign?
- What will I receive before the first milestone payment?
- How do you handle a change in scope halfway through, and how is it priced?
- Where does the code live during the project, and who has admin access to it?
- How do you test for security before go-live, and will I get a written report?
- What happens to my project if a key developer leaves your company?
- Can I speak to two clients whose projects were similar to mine?
- What does support cost after the warranty period, and what does it cover?
Write the answers down while you listen. Vague answers to the second, fourth and sixth questions are the ones most likely to cost you money later.
The paperwork to have before you pay
A handshake and a quotation PDF are not enough for software that will run part of your business. Before the first payment, you should have:
- A mutual NDA: signed before you share customer data, pricing or process details.
- A written specification: what will be built, what is out of scope and the assumptions behind the price.
- A milestone plan: each milestone with a deliverable you can test, acceptance criteria and the payment linked to it.
- An IP assignment clause: source code, database schema, documentation and design files assigned to your company on payment. A licence to use the software is not the same as owning it.
- Access terms: the code repository, domain, hosting and third-party accounts registered in your company's name, with the vendor added as a user.
- GST invoices: one for each milestone, from the same legal entity that signed the contract.
If budget is still an open question, our breakdown of custom software development cost in India explains what moves a quote up or down.
Red flags that should end the conversation
- A firm quote after a short call: a fixed price with no questions asked means the vendor priced a template, not your project.
- Vague IP language: wording such as "the client may use the software" instead of a clear assignment of the source code.
- Code only in the vendor's account: if you cannot see the repository during the project, you may not get it at the end.
- The sales team disappears: the people who pitched are not the people who build, and you never meet the developers.
- Most of the money before any deliverable: an advance is normal. Paying most of the price before you see working software is not.
- No change process: every project changes. A vendor with no written way to price changes will argue about them later.
- Promises nobody can keep: anyone who commits to a delivery date before discovery, or promises business results from software alone, is selling, not planning.
How EthicsComputer can help
EthicsComputer has built software for Indian businesses from its head office in Rohtak since 2018, and is GST registered, MSME registered and ISO/IEC 27001:2022 certified. Every project starts with a mutual NDA and a written specification, moves through milestone sign-offs and ends with full source code and IP handover. Custom software development and MVP projects start from ₹45,000 for a modern frontend and secure backend, role-based access, REST APIs and webhooks, database design and full source-code handover, built in 2–4 week sprints. If you are still at the idea stage, read how to build an MVP for a startup first.
Comparing software companies for your project?
Send us your one-page brief and we will come back with our questions, then a written scope and a milestone-based quote.
About the author
Vinay Grover founded EthicsComputer in Rohtak, Haryana in 2018 and leads its cybersecurity, software and AI work for clients across India and abroad. EthicsComputer is ISO 9001, ISO/IEC 27001 and ISO 20000-1 certified.
