When a business compares software, the conversation usually starts and ends with one number: the monthly subscription, or the quoted fee to build it. That number matters, but it is rarely the whole bill. Owners who budget only for the headline price often feel, six months in, that the software has become more expensive than promised, even when nobody has done anything dishonest.

This article walks through the costs that tend to be missed, so you can compare a ready-made product and a custom build on equal terms. We have not put rupee figures on anything, because they vary too much between businesses. The aim is to give you a checklist and a method.

Think in three years, not one invoice

A subscription that looks cheap per month and a custom build that looks expensive upfront are not comparable until you put them on the same timeline. The most useful habit is to estimate the total cost over three years for each option you are considering.

A simple structure works well:

  • One-time costs: everything you pay once to get started.
  • Recurring costs: everything you pay monthly or yearly to keep it running.
  • Internal costs: the staff time you will spend, even though no invoice arrives for it.
  • Exit costs: what it would take to leave if the software stops fitting.

Add these up for each option. The ranking often changes once you do.

One-time costs beyond the licence or build fee

Setup and configuration

Ready-made software rarely works exactly as your business does. Invoice formats, approval steps, tax settings, user roles and reports all need to be set up. Ask whether setup is included or charged separately, and who does it.

Data migration

Moving customer lists, stock records, opening balances and past transactions from spreadsheets or older systems takes real effort. Cleaning the data first is often the larger part of the work. Ask the vendor what they handle and what your team must prepare.

Integrations

If the software needs to talk to your accounting package, payment gateway, e-commerce store or GST filing tools, find out whether those connections are built in, available as paid add-ons, or need custom work. This is one of the most common sources of surprise charges.

Training

Even simple software needs a short training period. If you have several branches or shifts, one session will not be enough. Budget for repeat sessions and for new hires who join later.

Recurring costs people forget

  • Per-user pricing. A plan that suits five users can become expensive at twenty-five. Check what counts as a user, and whether occasional users such as field staff or accountants need full seats.
  • Hosting and storage. With custom software, someone pays for servers or cloud services. With ready-made products, extra storage or higher usage tiers may cost more as you grow.
  • Support and maintenance. Find out what support is included, what the response times are, and what happens after the first year. For custom software, ask whether bug fixes and security updates are covered or billed by the hour.
  • Third-party fees. SMS, WhatsApp messaging, email delivery, payment gateway charges, maps and e-signature services are often billed separately by the provider. They scale with usage.
  • Upgrades. Mobile operating systems, browsers and government portals change. Software that is not updated slowly stops working properly.

Also check how GST applies. If your business is registered, you may be able to claim input credit on software charges, which changes your real cost. Confirm this with your chartered accountant rather than assuming.

The cost of your team's time

This is the cost that never appears on a quote, and it is often the largest. Someone in your business will need to answer the vendor's questions, test the software, correct mistakes, and train colleagues. For the first few weeks, work may slow down while people learn a new routine, or you may run old and new systems side by side.

Plan for this honestly:

  1. Name one person as the internal owner of the project, and free up part of their week.
  2. Decide how long you will run the old and new methods in parallel.
  3. Expect a temporary dip in speed and decide in advance that it is acceptable.

A cheaper product that demands more of your team's time may cost more in practice than a pricier one that is easier to adopt.

Exit costs: the ones you hope never to pay

It is uncomfortable to plan for leaving software before you have started using it, but it is sensible. Three questions are worth asking up front:

  • Can I export all my data? Ask for the formats, and whether the export includes history, attachments and documents, not just current records.
  • Who owns the code? For custom software, the contract should say clearly whether you receive the source code and under what terms.
  • What happens if the vendor stops operating? A good answer involves documentation, access to your data and a clear handover process.

Lock-in is not always bad. A tightly integrated product can be worth it. The risk is in not knowing the price of leaving.

A simple way to compare two options

Make a short table in a spreadsheet, one column per option, with these rows:

  1. Upfront fee (licence or build)
  2. Setup and configuration
  3. Data migration
  4. Integrations
  5. Training
  6. Yearly recurring cost, multiplied by three
  7. Third-party usage fees, estimated at your current volumes
  8. Support and maintenance, multiplied by three
  9. Internal staff time, estimated in days
  10. Likely cost of leaving

Where you do not know a number, write down what you would ask the vendor and leave the cell flagged. A blank cell is useful information: it shows where the quote is vague.

Questions to ask before you sign

  • What is included in the price, and what is not?
  • What will it cost if I double my users, branches or transaction volume?
  • Which charges are billed by other providers, and how do they scale?
  • What does support cover, and for how long?
  • Can I get all of my data out, in a usable format, whenever I want?
  • What would you expect to change in the first year, and how is that priced?

A vendor who answers these plainly is usually one you can work with. If answers are evasive, treat that as part of the price.

The point of all this

The goal is not to find the cheapest software. It is to avoid being surprised, so you can decide with the full picture and keep the project on track after the contract is signed. If you are weighing a custom build against a ready-made product and want a second opinion on the costs, you can reach the team through Native Software and we will help you think it through.