Custom software

Off-the-Shelf Software or Custom Development? A Process-by-Process Decision Guide

admin 7 min read

This question is usually asked from the wrong place. “Off-the-shelf package or custom software?” is not a question that can be answered as a whole, because a business has ten different processes and the answer is different for each one. A ready-made program may be the right choice for your accounting while the same answer is wrong for your dealer order flow. This article does not push you to one side; it explains how to make the decision process by process.

First, be clear about which process you are talking about

Trying to decide under a broad heading like “business software” is the most expensive mistake. Instead, separate the processes one by one and ask these three questions for each:

  • Does this process set you apart from your competitors? If it is tied to the reason customers choose you, custom development can be justified. If it is a job everyone does the same way, a ready-made product is enough.
  • How close is this process to the industry standard? Issuing invoices is standard. Your made-to-measure production pricing probably is not.
  • How often does this process change? In a flow that changes often, being able to make the change on your own priority matters.

When you answer these three questions separately for each process, you will see that most of the list is solved with ready-made products and a small but critical part with custom development.

Comparing the two routes

Off-the-shelf package / subscription Custom software
Shape of the cost Low start, ongoing subscription High start, then hosting and maintenance
Cost growth Increases with number of users or transaction volume Does not increase directly with number of users
Going live As long as setup and data migration take Analysis and development time required
Fit with your process You adapt to the product The product adapts to your flow
Speed of change Depends on the vendor’s roadmap You set the priority, but every change is work
Bugs and updates Vendor is responsible Depends on your maintenance agreement
Knowledge base The product has documentation and a community The number of people who know the system is limited
Dependency On the vendor’s pricing, feature and continuity decisions On the development company and the code handover terms
Exit Can you export your data? Are code and data handover written into the contract?

The last row of the table is the one looked at least at decision time and the one that hurts most later. On both routes, ask this question: if I want to end this relationship, in what state do my data and my business come back to me?

When is an off-the-shelf package the right choice?

  • If your process is close to the industry standard.
  • If you need to start quickly; a ready-made product can be used today.
  • If your budget does not allow a development investment.
  • If you are not sure whether your need is permanent. Trying a ready-made product and giving it up is cheap.
  • If your team is small; a per-user fee is not a problem with few users.

Before choosing a ready-made product, test the trial version with your real data and on a real working day. In promotional videos every product seems to solve your job; the difference shows in how it handles your exceptions.

When is custom development justified?

  • If ready-made products do not cover a significant part of your processes and the missing part is critical to the business.
  • If data is constantly being carried by hand between several systems. You can check whether you have reached the limits of Excel with the signs in our article on job tracking software instead of Excel.
  • If user permissions, pricing or the approval flow are based on rules specific to you.
  • If “for now” workarounds have piled up in the ready-made product: side tables, second files, notebooks.
  • If the subscription cost is approaching the development investment as your user count grows.
  • If the service you offer your customers is itself intertwined with software.

None of these items requires custom development on its own. If several of them come together and the business is growing, it is worth a conversation. We explained how to proceed on our custom software development page.

For most businesses the right answer is: both

In practice the approach that works most often is not trying to build a single system, but continuing to use ready-made products and developing only the part that is specific to you. Keeping accounting in a ready-made program and having an order tracking panel built that connects to it; using a ready-made e-commerce platform and developing the dealer-specific pricing and order flow separately — we covered the latter in detail in our dealer order portal article.

The advantage of this approach is clear: the development scope shrinks, the risk drops, the result comes sooner. Its only condition is that the ready-made product offers an interface to the outside (an API). Check this technical feasibility before deciding — products that do not offer one make the hybrid approach difficult.

How do you compare the total cost?

When putting the two routes side by side, comparing a one-off fee with a monthly fee is misleading. Instead, choose a fixed period — three or five years — and add up the same items for both routes:

  • Initial fee (setup or development)
  • Annual subscription or hosting + maintenance
  • How these items change with the projected growth in your number of users
  • Data migration and training
  • Required integrations and any additional module fees
  • The time cost of the work done by hand today — how much of it remains on each route?

The last item is usually left out of the calculation, and it is usually the largest. How many people, how many hours a week, on which repetitive task? A comparison made without working out this number is incomplete.

We cannot say the result will always come out in favour of custom software; most of the time it does not. The aim is to make the decision with numbers.

Frequently asked questions

Is custom software always more expensive?

At the start, almost always yes. What happens in the long run depends on your number of users, how fast the subscriptions increase and the volume of manual work. Calculate this with your own numbers, not as a general rule.

Will custom software integrate with my existing programs?

Not always. Integration depends on that program offering an API to the outside and on access permissions. Technical feasibility needs to be examined at the start of the project; where it is not possible, alternatives such as file transfer are considered.

Can I move from a ready-made product to custom software later?

You can, but the only thing that will make it easier is being able to export your data. Checking the data export option when choosing a ready-made product gives you room to manoeuvre later.

If I have custom software built, do I own the code?

This is a matter written into the contract and it varies from company to company. In some agreements the code is handed over; in others a right of use is granted. Clarify in writing which one applies.

Does custom software make sense for small businesses?

For a system covering the entire process, generally not. A narrowly scoped tool that solves a single bottleneck can make sense for small businesses too. It is possible to start with a narrower scope.

Let’s talk through your own processes

The most useful thing to do before making this decision is to write down which task takes how much of your time today. Tell us your current flow and the programs you use; let’s work out together which part is solved with a ready-made product and which with development. You can look at our custom software development page and get in touch — we work in English or Turkish. We collected the questions to ask when choosing a company in our choosing a software company article.

Let’s work together

Have a project in mind? Let’s build it properly.

WhatsApp