# Custom Software vs Off-the-Shelf: Which Is Right for Your Business?

> Custom software vs off-the-shelf compared on fit, three-year cost, ownership and risk, with a checklist for deciding what to buy, build or combine.

- URL: https://weaveward.com/blog/custom-software-vs-off-the-shelf
- Published: 2024-01-17
- Updated: 2024-01-17
- Category: Business Systems
- Tags: custom software, off-the-shelf software, build vs buy, business systems, total cost of ownership
- Author: Weaveward Team

The short answer to custom software vs off-the-shelf: buy a ready-made product when your process is standard and the product already covers most of it. Build custom software when the process is part of how you win customers, or when stitching several products together costs more, in money and daily friction, than one system designed around your workflow. Many growing companies end up with both: packaged software for commodity work such as accounting, and a custom layer for the operations that make them different.

The hard part is telling which of your processes are standard and which are not. Sales demos make every product look like a perfect fit, and every developer can make a custom build sound simple.

This guide compares the two options on the factors that matter after the demo is over: fit, total cost over three years, ownership, integration and risk. It ends with the questions business owners ask most often.

## What you are actually choosing between

The choice is rarely binary. There are three broad options, and each has a different cost shape.

### Off-the-shelf software

A ready-made product sold as a subscription (SaaS) or a license: cloud accounting, HR and payroll apps, point-of-sale systems, CRMs. You configure settings, but you cannot change how the product fundamentally works. A good local product also keeps up with Indonesian rules such as BPJS contributions and tax reporting formats, which saves you from tracking every regulation change yourself.

### Configurable platforms

ERP systems, low-code tools and platforms with add-on marketplaces sit in the middle. You get a standard core plus custom fields, workflows and extensions. Flexibility is higher, but heavy customization can make upgrades painful and usually requires a specialist partner.

### Custom software

A system designed and built around your process, by an in-house team or a software house. You decide every screen and rule, you can own the source code, and the system can connect to exactly the tools you use. In exchange, you pay for the build upfront and you are responsible for keeping it maintained.

| Factor | Off-the-shelf | Custom software |
|---|---|---|
| Time to start | Days to weeks | Usually months for the first release |
| Upfront cost | Low: setup, data import, training | Higher: discovery, design, development, testing |
| Ongoing cost | Subscription per user, outlet or module, rising as you grow | Hosting, maintenance and improvements, mostly independent of user count |
| Fit to your process | You adapt to the product | The product adapts to you |
| Integrations | Limited to the vendor's API and add-ons | Built for the systems you actually use |
| Ownership | Vendor owns the product; check that you can export your data | You can own code and data if the contract says so |
| Main risk | Price increases, removed features, product shutdown | Dependence on the builders unless documentation and handover are strong |

## When off-the-shelf is the right call

Off-the-shelf usually wins when most of these statements are true:

- The process works the same way in most companies in your industry, such as bookkeeping, payroll, basic invoicing or email
- The rules change often and the vendor tracks them for you, as with tax reporting and BPJS calculations
- You need something working this month, not next quarter
- Your team is small, and the per-user subscription stays affordable at the size you expect to reach
- The product covers most of your must-have requirements without workarounds
- Nobody inside the company could own a custom system after launch

A typical example is a 20-person trading company that needs accounting, payroll with BPJS deductions and tax invoice data for e-Faktur. There is little competitive advantage in custom accounting, and a mature local product will usually do that job better than a new build.

## When custom software pays off

Custom software earns its cost when several of these apply:

- The process is how you compete: tiered pricing for resellers, a unique dispatch or production flow, or a customer experience that competitors cannot copy by subscribing to the same app
- Your team runs on workarounds: exporting from one tool, fixing data in Excel, importing into another
- Subscription costs grow with every new user, outlet or warehouse, and the three-year total is approaching the cost of a build
- You need several channels in one flow: WhatsApp orders, Tokopedia and Shopee orders, QRIS or virtual account payments and your accounting software
- You need control over where data is stored and who can see it, for example to meet obligations under Indonesia's Personal Data Protection Law (UU PDP)
- Products for your niche are missing, designed around another country's rules, or hard for field staff to use in Bahasa Indonesia

Consider a distributor whose sales team visits hundreds of shops with tiered prices, credit limits and route plans. A generic CRM covers part of it, but a custom ordering app that checks each shop's credit limit and pushes confirmed orders straight to the warehouse can remove a whole layer of manual checking.

## The hybrid approach: buy the commodity, build the difference

You do not have to choose one approach for the whole company. A practical pattern is to buy the parts of the business that work like everyone else's, build the parts that do not, and connect them.

1. Keep a proven off-the-shelf product as the system of record for accounting and tax
2. Build a custom layer for the operational core, such as order management, field sales or production scheduling
3. Connect the two so confirmed orders create invoices automatically and payments flow back without retyping
4. Put reporting on top of both, so management sees one set of numbers

Before committing, check that every off-the-shelf product you keep has a documented API or a reliable import and export. A product that locks your data inside is the most expensive kind of cheap.

If you are still deciding which process deserves attention first, the five-step roadmap in our guide to [digital transformation for SMEs](/blog/what-is-digital-transformation-smes) is a good place to start.

## Compare the total cost over three years

The first invoice is a poor guide. Compare the total cost of ownership over the period you expect to use the system, which for core business software is often three years or more.

| Cost item | Off-the-shelf | Custom software |
|---|---|---|
| Licenses or subscriptions | Monthly, per user, outlet or module | None for your own code; some third-party services charge usage fees |
| Setup and data migration | Configuration and importing master data, sometimes by a paid partner | Part of the build or quoted separately |
| Customization and add-ons | Paid add-ons or partner work that may break on upgrades | Part of the build |
| Integrations | Connectors, middleware or manual exports | Built to your systems |
| Hosting | Included | Cloud or server costs |
| Maintenance and improvements | Included, but on the vendor's roadmap | Yearly budget; we plan on 15 to 20 percent of the build cost |
| Training and change management | Needed | Needed |

To see how the math works, take a hypothetical product priced at Rp 200,000 per user per month. For 100 users, that is Rp 20 million a month, or Rp 720 million over three years before add-ons. A custom system quoted at Rp 400 million, plus a maintenance budget of 15 to 20 percent of that per year, comes to roughly Rp 580 to 640 million over the same period.

In that example custom comes out lower, but only because of the user count. With 30 users, the subscription would total Rp 216 million over three years and buying would clearly win. None of these figures is a market benchmark; the point is to put both options in the same table using your real quotes and headcount plans.

## FAQ

### Is custom software only for large companies?

No, size matters less than how specific your process is. A 30-person company with an unusual production or distribution flow can benefit more from a focused custom system than a large company with standard needs. What small companies should avoid is building everything custom. Start with the one workflow where ready-made tools force the most workarounds, keep standard software for the rest, and expand only when the first system proves its value.

### Who owns the source code of custom software?

Whoever the contract says owns it, so never assume. Ask for the intellectual property in the source code, designs and documentation to transfer to your company on payment, and keep the code in a repository you control. Cloud accounts, domains and app store accounts should also be registered in your company's name. If the vendor reuses its own internal libraries, ask for a perpetual license to use them in your system.

### Can we start with off-the-shelf software and move to custom later?

Yes, and it is often a sensible path. Using a ready-made product first teaches you what you actually need, and its frustrations become a clear requirements list for the custom version. To keep that door open, choose products that let you export all your data in a usable format, avoid deep customizations you would have to rebuild, and keep master data such as product codes and customer IDs clean and consistent.

### How long does it take to build a custom business system?

It depends on scope. As a rough planning range for a team of three to four people, a focused system covering one core workflow often needs three to five months to reach a first production release, including discovery, design and testing. Systems with many user roles and integrations take longer and are best delivered in phases. Treat any estimate given before a proper discovery phase as a range, not a promise.

## How Weaveward can build this for you

Weaveward's [business systems service](/services/business-systems) starts by listing your processes and sorting them into buy, configure or build, with a three-year cost comparison based on your actual quotes and user numbers. Where custom makes sense, we design the workflow with the people who run it, build the first release around the process that causes the most friction, and connect it to the tools you keep, such as your accounting software, marketplaces and payment channels.

Each release is checked against agreed numbers, like order processing time or errors per week, before the scope grows. If you are weighing a subscription against a build right now, [talk to our team](/contact) and bring the quotes you already have.