How to buy custom software for a small business in India (2026)
Seven questions before the first rupee: the written scope, what you own from week one, weekly releases, where the rules live, and the full price.
The short answer: custom software is the most expensive thing a small business buys without seeing it first, so the contract has to do the seeing. Seven questions turn a promise into a contract: a written scope with the price and dates, the domain, accounts and data in your name from week one, a release you can click every week, a written ledger of the business rules, how your data is separated from other customers’, what happens when the developer is unavailable, and the full price including what comes after launch. Any developer who answers all seven in writing is one you can work with.
Disclosure: Brimpa builds custom software from Palanpur, Gujarat, starting at ₹29,999 (checked November 2026). These are the questions that make a project go well for both sides, and the answers Brimpa gives are on the service page.
What you need before you ask
- A one-page description of what the software has to do, for whom, and what you use today (paper, Excel, another system).
- The person at your business who will own it: the admin role, the backups, the user list.
- A budget range, even a rough one, so the developer can say early whether it fits.
Question 1: Can I have the scope in writing?
Screens, rules, what is excluded, the price and the dates, on paper, before any work starts. If a developer cannot write down what will be built, they cannot build it either; the writing is where the thinking happens. The scope should name the screens, list the business rules the software will enforce, say in plain words what is not included, and give one price and a date.
A good scope also says what happens when you change your mind. Changes inside the written scope should be part of the price. Changes outside it should get their own written note with their own price, before they are built.
Expected answer: a document, not a WhatsApp message. Red flag: “we will figure it out as we go”.
Question 2: What is in my name from week one?
Three things: the domain, the accounts the software runs on (the server, the email, any services it uses), and the data. Ask for the logins. A developer who will not put the accounts in your name is keeping a key to your business.
Then ask about the code. Custom software built for you should be yours when the scope says so. Licensed products are different: you get an account and your data, and the software stays the vendor’s. Both are fine; not knowing which you are buying is not.
Expected answer: “the domain, the server and the data are yours; here are the logins.” Red flag: the agency’s hosting account with no login for you.
Question 3: Will I get a release I can click every week?
A demo at the end is where surprises live. A release every week, on a staging address you can open on your phone, is where they get caught while they are cheap. Each release should come with a short note: what changed, who built it, what to look at. By the third week you should be clicking through real screens with your own data in them.
Expected answer: a staging address and a weekly note. Red flag: three months of silence and then a reveal.
Question 4: Where are the business rules written down?
Every business has rules nobody has written down. Which numbers must never repeat. Who may give a discount. What happens to an entry typed a day late. If the only place those rules exist is inside the code, the first bug fix in year two will quietly remove one, and nobody will notice until the accountant does.
Ask for a written ledger of the rules, numbered, kept with the project, updated when a rule changes. Brimpa’s products keep one, and more than one bug has been traced to a rule that was in the code but not yet in the ledger.
Expected answer: “there is a rules document and you can read it.” Red flag: “it is all in the code.”
Question 5: How is my data separated from other customers’?
Most modern business software runs as one installation serving many customers. That keeps the price down and it is a reasonable design, but it means your records and another business’s records share a database. Ask: does every record carry your account’s identity? Is every query filtered by it? Is that tested, or assumed? And can you be moved to your own installation later, as a choice rather than an emergency?
Expected answer: a specific mechanism, named, and a test. Red flag: “do not worry, it is secure.”
Question 6: What happens when you are unavailable?
Developers get sick, get busy, and sometimes disappear. The software should survive that. Ask for three things in the scope: documentation a new developer could read, backups you can restore yourself and have tried once, and a second person who knows the project.
Expected answer: “here is the handover document, here is how you restore a backup, here is the second contact.” Red flag: “only I know how this works.”
Question 7: What is the full price, including after launch?
The cheapest quote usually leaves out the parts that make software last: the rules written down, the weekly releases, the backups, the documentation, the thirty days of fixes after launch. Those are the parts you pay for twice if they are missing, once in the rebuild and once in the data you lose on the way.
For a sense of scale: a records or billing system for one small business in India, built properly, starts around thirty thousand rupees and goes up with the number of screens, the documents it prints and the rules it enforces (checked November 2026). A system that will serve many customers costs more because it has to be built that way from the first week.
Expected answer: one figure for the build, one for the thirty days after, one for the monthly care plan, and what you keep if you stop paying. Red flag: a price that only becomes clear once you depend on the software.
The seven questions as a sheet
| Question | Developer A | Developer B |
|---|---|---|
| 1. Written scope with price and dates | ||
| 2. Domain, accounts and data in my name | ||
| 3. A clickable release every week | ||
| 4. A written ledger of the rules | ||
| 5. How my data is separated, and the test | ||
| 6. Documentation, backups, a second contact | ||
| 7. Full price including after launch |
Check it worked
Three weeks after signing, you should have: the scope in your hand, the domain and accounts in your name, a staging address you have opened on your phone, and a first note of what changed. If any of the four is missing, raise it now, while it is cheap.
Questions people ask
Should I buy a ready-made product instead? If one fits, yes; it is faster and cheaper, and the seven questions still apply, especially 2, 5 and 7. Brimpa’s own Brimpa Care and Brimpa Gas are products that are set up per customer rather than built.
Is a mobile app necessary? Usually not. Software that runs in the browser works on a phone, a tablet and a computer with nothing to install, and costs far less than a native app in the app stores.
How long does custom software take? Six to twelve weeks for most business systems, released weekly, so you see it grow from the second week.
Brimpa’s answers to all seven are on the custom software page, and a scoping call starts on the contact page.