The first software decision a company faces is usually: "Surely there is a ready-made product for this?" Usually there is. Accounting, email, HR, customer tracking, project management: each has dozens of products sold by monthly subscription.
Even so, a good share of the projects that reach us come from companies that used a SaaS product for a while and hit its limits. The reverse happens too: companies that commissioned custom software, carried its maintenance for years, and eventually asked "could we have handed this to a subscription?"
This article explains when each side is right.
When the off-the-shelf product clearly wins
If most of the following apply, buy the product and close the topic:
- The process does not differentiate you. Issuing invoices, running payroll, scheduling meetings. Invoicing better than your competitor does not win you customers.
- The process is standard in your industry. The product was written for thousands of companies doing the same work. Your exceptions are usually their exceptions too, and the product already handles them.
- You need to start now. You can sign up and use it the same day. The first version of custom software takes months at best.
- The team is small and the budget uncertain. A monthly subscription is a predictable expense. Custom software carries hosting and maintenance costs even after development ends.
- Regulation changes often. In areas such as e-invoicing, tax reporting or data protection, the vendor tracks the changes on your behalf.
Notice that "price" is not on this list by itself. The ready-made product is not always cheaper; we will get to that.
When custom software wins
If two or more of these apply, custom development is worth discussing:
- The process is your competitive advantage. Getting a quote to the customer faster than anyone, pricing orders with your own logic, running a field team your own way. A ready-made product forces you to work "like everyone else".
- It sits between several systems. You need a layer that moves data between ERP, e-commerce, logistics and accounting. Ready-made integrations are usually limited to "the five most common systems".
- The subscription grows with headcount. Per-user pricing is negligible for a team of 10 and a budget line for a team of 300.
- The data has to stay with you. Industry regulation, a customer contract or company policy requires data to be held in a specific place.
- The product roadmap does not match your needs. If you have heard "that feature is in the next release" three times, it is probably not coming.
Comparing the cost properly
Most comparisons are done wrong because the two sides count different items. The product's monthly fee is placed next to the custom software's development cost, and custom software always loses.
The honest comparison is five-year total cost. Both sides have these items:
| Item | Off-the-shelf SaaS | Custom software |
|---|---|---|
| Start | Setup, data migration, training | Analysis, development, data migration |
| Annual fixed | Subscription (per user and module) | Hosting, maintenance, security updates |
| Growth | Each new user and module adds cost | New users are usually free; new features need development |
| Integration | Built-in connectors free, custom ones extra work | Designed in from the start, easy to add later |
| Exit | Data export, migration project | The code is yours, no lasting dependency |
Two items are often left out. The first is the cost of bending your workflow to the product: changing a process the team is used to, moving data between two products by hand, work that cannot be done "because the system does not allow it". This never shows on an invoice, but it is paid every month.
The second is the cost of ownership in custom software: the software needs an owner. Someone who collects bug reports, prioritises updates and talks to the development team. Without that person, the software turns within a few years into the legacy system nobody wants to touch.
The third option: a product plus a thin custom layer
Most decisions are not binary. The successful setup we see most often is a ready-made product for the core job, with a thin custom layer on top that carries what makes the company different.
Examples:
- An off-the-shelf accounting package, with the company's own quote and order screens on top. Invoices come out of the product; the pricing logic belongs to the company.
- An off-the-shelf e-commerce platform, with a warehouse and logistics integration on top. The store runs on the product; the order flow is built around the company.
- An off-the-shelf CRM, with a small mobile app for the field team on top. The data lives in the product; the field experience is the company's own.
In this setup the custom software stays small, so it is cheap to maintain, and the product does its own job. The one condition is that the product exposes a proper API. When choosing a product, ask that question first.
Questions that settle the decision
Answer in order:
- Does this process make us different in the customer's eyes? If not, buy the product.
- Is there a ready-made product for this in our industry, and does it offer an API? If so, try it first.
- Which side has the lower five-year total cost, including workflow adaptation and user growth?
- Will the custom software have an owner inside the company?
- If we ever need to leave the product, can we take our data with us?
If most answers point to the product, do not commission custom software. If a few point to custom, start with a thin layer and grow it.
Conclusion
There is no general answer to "buy or build", but for a specific company the answer usually emerges in an afternoon. Asking the right questions is enough.
If you would like to work through this decision together, the discovery call is free. Saying "you do not need custom software" is part of that conversation when it applies. You can reach us through the contact page.
