Custom Software Pricing in India: Fixed Price or Hourly?

Four things: how many different users the system has (admin, staff, customer, vendor), how many workflows each of them runs, what it must connect to (payments, WhatsApp, SMS, accounting, maps), and how much existing data has to move in. A booking system for one salon and a booking system for twenty branches look similar on a screenshot and differ by months of work.

Design polish matters less than people expect. Data rules matter more: who can see which record, what happens when a payment fails, what is kept for audit. Those rules are where custom software earns its keep — and where cheap quotes quietly cut corners.

A fixed price means the developer carries the risk of the work taking longer. That only works if the scope is specific enough to price: screens, user roles, fields, reports and integrations listed, plus what is explicitly not included.

If a fixed quote arrives after a ten-minute call, the risk has not disappeared — it comes back later as change requests. A good fixed quote should come with a written scope you can check line by line.

Hourly and monthly billing put the risk on you, but they suit products that are still being discovered — a startup MVP, an internal tool whose rules will change after the first month of use. The protection here is visibility: weekly demos, a shared task list and a working preview link you can click any time.

I quote a fixed price per project after a scoping call and, where useful, a free sample design. Websites start at ₹4,999 and redesigns at ₹2,000; custom software is quoted on its scope. Once a client commits, 30% is paid in advance and the rest is agreed with the client per project — and every website or app I build gets lifetime support and free bug fixing, as written in my terms.

Current examples of fixed-scope builds: a hotel management system with a public website for a dharamshala in Palitana (about 60% done), e-commerce with repair booking for a computer store in Ahmedabad, and a community matrimonial web app in Nadiad — all still being built, all priced as projects rather than by the hour.

Be careful with quotes that skip ownership (you should own the code, domain and data), skip hosting costs (servers and databases are a monthly cost of their own), or promise everything in a week. Equally, a quote that is ten times the others usually prices in a team of managers you will never talk to.

A scope you can price and check later lists, for each user role, the screens they see and the actions they take; the data each screen stores; the reports or exports needed; every outside service involved (payment gateway, SMS, WhatsApp, maps); what data moves from the old system; and what is explicitly out of scope for this version.

It also names the acceptance test: how you and the developer agree that a feature is done. “The office can add a student and the parent sees attendance the same day” is testable. “Smooth attendance module” is not.