Step 4 of 4 · Software and systems

When custom software makes sense for a small business

Most small businesses don't need custom software. Here are the signs that you might, the cheaper steps to try first, and how to brief a developer fairly.

Most small businesses don't need custom software: a ready-made tool, a spreadsheet or a shared form covers the job for far less money. Custom makes sense when you've tried two or three tools properly and each one fights the way your business actually earns, and the time or money lost is large and steady. Even then, build the smallest piece that fixes the problem first.

Why it matters

Custom software costs more than the first bill. Someone has to fix bugs, update it when phones change and add features as you grow, for as long as you use it. A ready-made tool spreads that cost across thousands of businesses; custom puts it all on you. That's why it should be the last option, not the first.

Months of real trading give you proof of how you really work. If you've trialled ready-made tools with real data and they kept forcing workarounds, you can describe exactly what's missing. That description is what makes custom software affordable and useful instead of a long, open-ended project.

A note on who's writing this: our studio builds custom software, so we have a reason to recommend it. We'd still rather you didn't pay for it unless the signs below clearly apply.

How to do it

Work down this list in order. Stop at the first step that solves the problem.

  1. Check the signs honestly

    Custom software is worth considering when most of these are true: you've tried at least two ready-made tools for a week or more and each needed daily workarounds; the way you work is part of why customers choose you (a special order flow, pricing by weight and cut, multi-stage job tracking); staff retype the same data into two or three tools or spreadsheets; and the problem costs many hours a week, every week. If your process still changes every month, wait; you'd be paying to build something you'll redesign.

  2. Try configuring what you have

    Many tools have settings, custom fields, templates or add-ons that owners never open. Ask the vendor's support directly: "Can your tool do this?" with a concrete example. Sometimes the answer is yes, and it costs nothing extra.

  3. Try a spreadsheet and a form

    Google Sheets with a simple form for staff to fill in on their phones handles a surprising amount: job tracking, daily checklists, order intake, attendance. It's free, you control it and anyone can change it. If this works for six months, you may never need more. If it breaks under volume, you've written the specification for custom software without meaning to.

  4. Consider connecting tools instead of replacing them

    If the pain is retyping between two tools that each work well, a small connection between them can be cheaper than a whole new system: for example, orders from a form landing in your billing tool, or a WhatsApp Business message going out when a job is marked ready. This is a smaller, cheaper piece of custom work.

  5. If custom is the answer, write the brief yourself first

    Describe the process step by step, who does each step, on which device, and what information they need. List the three or four screens you can picture and the reports you want. Include your time-wasting list and what you learned from the trials. A clear brief is the biggest single control you have over price.

  6. Ask for terms that protect you

    Ask for a fixed price for a first small version, delivered in a few weeks, rather than an open-ended hourly project. Make sure the code and your data belong to you, the app runs on hosting in your business's name, and you get the source code and login details at handover. Agree in writing what yearly maintenance costs and covers. If it will store customer phone numbers or other personal details, ask how it handles consent and deletion under the Digital Personal Data Protection Act.

Ballparks that vary widely by scope and developer. Get written quotes.
OptionRough costFits when
Settings in a ready-made toolUsually freeThe tool almost fits
Spreadsheet and phone formFreeLow volume, process still settling
Connecting two toolsLow, often one-timeEach tool works; retyping is the pain
Small custom appOften from a lakh or two, plus yearly upkeepProcess is stable, unusual and costly to work around

If you've worked through this list and custom still looks right, you can see the kinds of systems our studio builds for small businesses. Get at least one other quote as well.

Your result

A clear decision: stay with ready-made, use a sheet, connect tools, or build. If build, a one-page brief.

Problem: ________ | hours lost a week: ____
Tools tried: 1) ____ 2) ____ | why each failed: ____
Settings or add-ons checked? y/n
Spreadsheet + form tried? y/n | result: ____
Decision: ready-made / sheet / connect / custom
If custom: must-do screens ____ | who uses it ____ | devices ____
Ownership of code and data agreed? y/n | yearly upkeep ₹____

Fill it in on your checklist, next to this topic. It stays in this browser.

Time and cost

Time
A few hours to work through the options. If you build, a small first version often takes weeks rather than months; anything quoted as many months for a single shop deserves a second look.
Cost
Free for the first three options in most cases. A small custom app commonly starts at a lakh or two and rises with scope, plus yearly maintenance. These are wide ballparks; ask for written quotes.

Ballparks to verify: prices and fees change by city and over time, so check current rates before you budget.

Common mistakes

  • Building before trialling

    Without trying ready-made tools, you don't know what's missing, so you pay to rebuild features you could have rented cheaply.

  • A big first version

    A big first version takes longer, costs more and is harder to change. Fix the single costliest problem first and add later.

  • Not owning the code or the hosting

    If the developer disappears and the app runs on their account, you can lose the software and your data. Get it in writing.

  • Forgetting upkeep

    Phones update and needs change. Budget for maintenance every year, or the app slowly stops working.

Go deeper

The playbooks are written for one business each. Start with the full playbook or find yours.

Questions people ask

Is custom software only for big companies?

No, but it fits a small business only when the process is unusual and stable. A single shop with a common way of working is almost always better served by ready-made tools.

Can I build it myself with a no-code tool?

For simple forms, lists and reports, yes, and it's a good way to learn what you need. Watch the monthly fees as users grow, and keep an export of your data.

What if I open a second outlet later?

Tell the developer now, so the data can hold more than one location. For billing across outlets, see one billing system for all outlets.

← All business basics

Menu

Read

Ask an expert Ask an expertFree, real peopleHub
Ask an expert