Start with what you already have
Before evaluating anything new, list the tools the business already pays for. In most Indian SMEs that includes an accounting package (Tally or Zoho Books), Google Workspace or Microsoft 365, WhatsApp Business, a payment gateway, and often a CRM or HR tool that is only partly used. A surprising share of “we need new software” requests are solved by configuring a module in a tool that is already licensed.
Write down, for the workflow in question: who does it, how often, where the data lives today, and what breaks. That one paragraph is the input to everything below.
Three questions that decide most cases
- Is this workflow the same as every other business of our type, or is it how we compete? Payroll, invoicing, and basic CRM are commodities — buy. A pricing engine, a scheduling rule set, or a customer process that is genuinely yours may justify building.
- How much data moves between systems? If the workflow is mostly one team entering and viewing records, a no-code tool is often enough. If it must pull from your accounting system, push to a payment gateway, and notify customers, integration capability matters more than the interface — and custom or a strong low-code platform becomes more attractive.
- Who will own it in two years? A no-code app built by an enthusiastic manager who then leaves is a liability. A custom system with no maintenance arrangement is worse. Decide the owner before the tool.
The three options, honestly
| Off-the-shelf (buy) | No-code / low-code | Custom build | |
|---|---|---|---|
| Time to first use | Days | Days to weeks | Weeks to months |
| Fit to your process | You adapt to it | Moderate; limits appear at edges | Exact, if scoped well |
| Integration | Only what the vendor offers | Connectors; custom API work is limited | Anything with an API |
| Ongoing cost | Per-user subscription, rises with headcount | Subscription plus platform limits | Hosting plus a maintenance arrangement |
| Main risk | Process bent to fit the tool | Hitting a ceiling; single-person dependency | Scope creep; abandoned by the vendor |
| Best for | Commodity functions | Internal trackers, approvals, simple portals | Differentiating workflows, heavy integration, scale |
Compare cost over three years, not at purchase
Subscription software looks cheap per month and expensive by year three, especially as the team grows. Custom software looks expensive upfront and cheap afterwards — if maintenance is budgeted. A fair comparison puts all three on the same three-year line:
- Licences or subscriptions × expected users × 36 months, including likely tier upgrades.
- Implementation and configuration — internal time counts.
- Integration work — often the largest hidden line for off-the-shelf tools.
- Maintenance for custom software: budget a realistic annual figure for fixes, dependency updates, and small changes, rather than assuming zero.
- Exit cost — how hard is it to get your data out and move? Ask this before signing anything.
We deliberately do not quote prices here; custom development costs in India vary widely with scope, team, and quality expectations. What matters is that any quote you receive is for a fixed, written scope with the first version small enough to be in use within a few weeks.
Warning signs in either direction
- A vendor who cannot show you the workflow running end-to-end with your kind of data before you sign.
- A custom quote with no phase one, no acceptance criteria, and no maintenance terms.
- A no-code build that already has workarounds for the workarounds.
- Any option that requires the whole company to change how it works on day one.
- Nobody named as the internal owner.
A sensible default
Buy for commodity functions. Use no-code for internal trackers and approvals where the process is stable and simple. Build only where the workflow is genuinely yours, integration is heavy, or the tools have run out — and start with the smallest version that removes the most manual work.
The decision is rarely permanent. Many businesses run a no-code version for a year, learn what the process actually needs, and then commission a custom build with far better requirements than they could have written on day one.
Trying to decide what to build?
Our IT consulting engagements start with a workflow review and end with a clear recommendation — buy, configure, or build — along with a scoped plan. If the honest answer is “use the tool you already pay for,” that is what we will tell you.