I run a small IT and digital marketing agency in Ranchi, and I have sat on both sides of the table: pitching for software projects and hiring outside developers. In my experience, most failed projects do not fail because the code was bad. They fail because the business and the developer never agreed on what was being built, who owned it, or what would happen after launch.
If you run a small business in India and plan to get custom software built, this is what I wish every client read first. It applies whether you hire locally, in a metro, or abroad.
Start by Defining Your Requirements
Before you speak to any vendor, write down what you need. A few pages in plain language are enough. Answer these questions:
- What problem are you solving, and for whom?
- Who will use the software? Staff, customers, field technicians, managers?
- What are the five or six things the software must do on day one?
- What can wait for a second phase?
- Does it need to connect with anything you already use, such as Tally, a payment gateway, WhatsApp or an existing website?
- What is your rough budget and your ideal launch date?
Separating "must have" from "nice to have" keeps the first version smaller and cheaper, and gives you a fair way to compare quotes. If two quotes differ widely, check whether both companies understood the same scope.
Fixed Price vs Time and Material
You will usually be offered one of two pricing models.
Fixed price means you agree on a defined scope and a set cost. It works well when your requirements are clear and unlikely to change. The risk is that every change after signing becomes a "change request" with extra cost, and some vendors pad the quote to protect themselves.
Time and material means you pay for the hours or days actually worked, usually at an agreed rate. It suits projects where you expect to learn and adjust as you go. The risk is that costs can grow if nobody is watching the scope.
For many small businesses, a mix works best. Fix the price for a clearly defined first version, then move to time and material for improvements later. Whichever model you choose, ask for payment to be linked to milestones you can actually see and test, not just to dates on a calendar.
Check Portfolios and Case Studies Properly
Almost every company has a portfolio page. The trick is to look past the screenshots. When you review past work, ask:
- Was this project similar to mine in size and type?
- What exactly did this company build? The whole system, or just the design?
- Can I see a live version or a demo?
- Can I speak to a past client?
A good case study explains the problem, the approach and the technology used. As one example from my own work, we wrote up a custom after-sales service management system we built for Seekoji Electric, which used Next.js, Node.js, Express and MongoDB, with JWT authentication and role-based access so different staff saw only what they needed. I mention it only to show the kind of detail you should expect. If a company cannot tell you what they used and why, be careful.
Ask Questions About the Tech Stack
You do not need to be a programmer to ask sensible questions. The goal is software that will not be hard to maintain or move later. Ask:
- Which languages and frameworks will you use, and why are they right for this project?
- Are these technologies widely used, so that another developer could take over if needed?
- Where will the software be hosted, and who pays for the hosting?
- How will you handle security, logins and user permissions?
- Will the software work well on mobile phones?
Be wary of anyone who insists on an obscure or in-house framework without a clear reason. Popular, well-documented tools make it much easier to find help in the future.
Make Sure You Own the Code and IP
This is the point small businesses most often overlook. If you are paying for custom software, your contract should clearly state that the source code, designs, database structure and related intellectual property belong to you once you have paid.
Also ask for practical access, not just legal ownership:
- The code should live in a repository, such as GitHub or GitLab, that you control or can be added to.
- Hosting, domain and cloud accounts should ideally be registered in your business name.
- You should receive all passwords, admin credentials and documentation at handover.
I have seen businesses locked out of their own software because a freelancer registered everything personally and then became unreachable.
NDAs and Contracts
If you are sharing business ideas, customer data or internal processes, it is reasonable to ask for a non-disclosure agreement before detailed discussions. Most professional companies will sign one without fuss.
The main contract should cover at least:
- The scope of work, ideally with your requirements document attached
- Milestones, deliverables and payment terms
- Ownership of code and IP
- How change requests are priced and approved
- Warranty or bug-fixing period after launch
- Confidentiality and handling of your data
- What happens if either side wants to end the project
If you are unsure about any clause, a lawyer's review costs far less than a dispute.
Communication and Timezone
Good communication matters as much as good coding. Before signing, find out:
- Who will be your single point of contact?
- How often will you get updates, and in what form?
- Which tools will be used, such as WhatsApp, email, Google Meet or a project board?
- Can you see progress regularly, for example a working demo every week or two?
Timezone matters too. A team in India shares your working hours, which makes quick calls easy. If you hire offshore, agree on overlapping meeting hours. You should also be able to discuss your needs in a language you are comfortable with.
Plan for Post-Launch Support
Software is never really finished at launch. Users will find bugs, phones and browsers will update, and you will want small changes. Ask each company:
- How long is the free bug-fixing period after launch?
- What does a support or maintenance plan include, and what does it cost?
- How fast will they respond to a critical problem?
- Who handles server updates, backups and security patches?
Get these answers in writing.
Red Flags to Watch For
Take these warning signs seriously:
- A quote given before they have understood your requirements
- A price far lower than every other quote, with no clear explanation
- Reluctance to put ownership of code in writing
- No real portfolio, or work they cannot explain in detail
- Pressure to pay most of the amount upfront
- Vague answers about who will actually work on your project
- No mention of testing, documentation or support
- Promises that sound too good, such as a complex app in a week
One red flag is not always a deal breaker, but two or three together usually are.
Local vs Metro vs Offshore Agencies
Local agencies in your own city or state can meet you in person, understand regional customers and often work at reasonable rates. Smaller cities now have capable teams, but check their experience carefully, because quality varies.
Metro agencies in places like Bengaluru, Mumbai, Delhi NCR or Pune may have larger teams and more specialists. They can also be more expensive, and a small project may not get their senior people's attention.
Offshore or foreign agencies can bring different experience, but timezone gaps, higher costs and less familiarity with Indian business practices, such as GST invoicing or local payment methods, can make things harder for a small Indian business.
Judge the team, not the location. A focused small team that understands your business can serve you better than a big name that treats your project as a minor account.
A Short Checklist
Before you sign, make sure you can tick these boxes:
- I have a written list of requirements, split into must have and later.
- I have compared at least two or three quotes for the same scope.
- I understand whether the price is fixed or time and material.
- I have seen real, relevant past work and ideally spoken to a past client.
- I know which technologies will be used and why.
- The contract says I own the code and IP after payment.
- Code, hosting and domain accounts will be in my control.
- An NDA is signed if I am sharing sensitive information.
- Payments are tied to milestones I can test.
- I know who my contact is and how often I will get updates.
- A bug-fixing period and support plan are agreed in writing.
Choosing a software development company is less about finding a perfect vendor and more about asking the right questions early.
Akhil Baraik is the founder of Crework Tech, an IT and digital marketing agency based in Ranchi, Jharkhand.
Top comments (0)