What Is Custom Software, and How Does It Differ from Off-the-Shelf?
What is custom software and how does it differ from an off-the-shelf package? We explain cost calculation, source code ownership and data export with examples.
- What Is Custom Software?
- What Is Off-the-Shelf Software?
- How Do Off-the-Shelf and Custom Software Differ?
- When Is Off-the-Shelf the Right Choice?
- How Do You Know You've Hit the Limits of a Package?
- How Do You Calculate the Total Cost?
- Who Keeps the Source Code and the Data?
- What Are the Risks of Building from Scratch, and How Do You Reduce Them?
- Is It Possible to Use Both Together?
- Are Low-Code Platforms an In-Between Option?
- What Determines the Price of Custom Software?
- How Do You Plan the Move from a Package to Your Own System?
- Ask Yourself Before You Decide
- What Should You Look for at the Quote Stage?
Custom software is software designed around the way a single business works and developed for that business alone. An off-the-shelf package, by contrast, is a solution where the same product is sold to thousands of companies at once and everyone uses similar screens. The choice is usually made by looking at the initial price tag. Yet the real difference shows up a few years later: in the total amount paid, in who holds the data, and in who you depend on the day you need a change.
What Is Custom Software?
What makes software custom is who it is written for. The developer first learns how the business takes orders, which rules it uses to calculate quotes, and who signs off on which approval. The screens and rules are built on that knowledge. The resulting system has no menus you will never open, and the rules specific to your business are not missing.
The scope can be small or large. A work order app written for a service company's field team fits this definition. So does an ERP that manages the entire flow from production to shipping. What they have in common is that the business using the software sets its direction. You decide what gets added, what changes and where the records are stored.
The concept is sometimes confused with the term proprietary software. That term describes licensed products whose source code is kept closed, and it covers most of the off-the-shelf packages on the market. What this article means is software produced for a single business.
What Is Off-the-Shelf Software?
The vendor develops these products by anticipating the common needs of a broad customer base. You buy it or subscribe, and after a short setup you start using it. Because the vendor spreads the development cost across thousands of customers, the entry price is low. On the market, these products come in quite different forms.
Boxed Software
These are programs installed on a computer or a company server, with a license bought once. An annual update fee is usually paid for new versions and regulatory changes. A large share of bookkeeping and accounting programs fall into this group. The records sit on your machine, and backing them up is your job.
Cloud Software Used by Subscription
In the industry it is known as SaaS. It opens in the browser, and you pay a monthly or annual fee per user. Servers, backups and updates are the vendor's responsibility, which is a real convenience for small teams. In return, your information is kept on the vendor's infrastructure, and the day you cancel the subscription, your access ends too.
Where Does Open Source Fit In?
Open-source products charge no license fee, and anyone can inspect the code. Still, they are not free of cost. Installation, hosting, updates and customization take effort, and that effort comes either from your team or from an outside contractor. Used as is, it is an off-the-shelf package. Once you have development done on top of it for your business, it becomes a hybrid model.
How Do Off-the-Shelf and Custom Software Differ?
The table below puts the two approaches side by side using the same criteria. No single row makes the decision on its own; which side weighs more varies from business to business.
| Criterion | Off-the-shelf package | Custom software |
|---|---|---|
| Getting started | Right after installation | Once analysis and development are complete |
| Initial payment | Low, license or subscription | High, project fee |
| Ongoing payment | Grows with the number of users | Maintenance and hosting, independent of user count |
| Business rules | As far as the package allows | Whatever the business's rules are |
| New features | Depend on the vendor's roadmap | Depend on your priorities |
| Integration | Limited to the connectors offered | Written for whichever system is needed |
| Where the data lives | Usually the vendor's servers | A server of your choice |
| Source code | Stays with the vendor; you get a right of use | Can be transferred to you by contract |
| Main risk | Price increases, the product changing direction | Project management, dependence on the developer |
Will Your Business Adapt to the Software, or the Software to Your Business?
Every package assumes a particular way of working. An order goes through these steps, the invoice is issued at this point, stock is deducted like this. If your way of working is close to that assumption, you won't have problems. If it isn't, you are left with two options. Either you change the way you work to fit the package, or you cover the steps the package can't handle with spreadsheets, email and paper. The second option looks harmless at first, but over time it creates a shadow process that runs outside the system.
With a system written from scratch, the direction is reversed. The rule is put on paper first, and the code is written to match it. The price of this is that you have to truly know your rules. For a business that cannot describe its own process, commissioning a system from scratch turns into an expensive experiment.
How Fast You Can Get Started
Here the off-the-shelf package is far ahead. Setup is short, training videos are ready, and the bugs other companies have been reporting for years have long since been fixed. A system written from scratch, on the other hand, takes time for analysis, design, development and testing. If you need a tool that works tomorrow morning, there is not much left to debate.
Who Controls Change Requests?
With a package, if you want a new feature, you fill out a request form. The vendor weighs that request against those from its other customers and adds it to the roadmap if it thinks it will bring in revenue. A need specific to your industry alone rarely rises to the top of that list.
With your own software, you keep the priority list. Changes naturally have a cost. But whether they get made does not depend on someone else's business plan.
When Is Off-the-Shelf the Right Choice?
Commissioning software from scratch is not sensible for every task. In some areas a ready-made product is both cheap and safe, and on top of that it brings the vendor's years of experience with it.
- Standard, regulation-driven work. Accounting, e-invoicing, e-ledgers and payroll follow the same rules at every business. When regulations change, the vendor sends the update to all of its customers at once. Tracking this in your own system is a constant burden.
- Businesses whose processes have not yet settled. At a newly founded company, the workflow changes many times in the first year. Having code written for a moving target means wasted effort. It is healthier to work with a package first and see what is missing.
- Small teams and common needs. For email, document sharing, task tracking or a simple appointment book, there are mature products on the market.
- Support work that doesn't set you apart. Running a process the same way everyone else does is no loss if it has nothing to do with why your customers choose you.
If one of these situations describes you, sticking with a package is the right decision. You save the development budget for where you truly stand apart.
How Do You Know You've Hit the Limits of a Package?
The need rarely appears overnight; it builds up through small signs. If you see several of the following at the same time, you have reached the package's limits.
- Exports are pulled from different programs for management reports, and someone merges them by hand every week.
- Your pricing varies by customer, quantity or payment terms, and because the package can't do that calculation, quotes are prepared in spreadsheets.
- An update sent by the vendor changed a screen you were used to, and the team took days to get back up to speed.
- Two programs you use don't talk to each other, and the same customer record is kept separately in two places.
- There is a screen you want to open to your customers or dealers, but the package only allows internal use.
- As headcount grows, the license bill grows faster than the revenue the work brings in.
A single item is no cause for alarm. Most packages cover one of these gaps with an add-on module or a small integration. When the signs pile up, however, the cost of patching approaches the cost of a new system. You can see examples of which business systems get written from scratch on our custom software development page.
How Do You Calculate the Total Cost?
Comparing the two options by the amount paid on day one is misleading. A package starts cheap and is paid every month. Your own system starts expensive and costs less afterwards. The right measure is the total cost of ownership, meaning the sum of all the money spent over the years the software is in use.
Costs That Surface Later with a Subscription
The list price is only the visible part of the bill. Add-on modules are charged separately. Advanced reports or integration connectors often require moving up to a higher plan. The per-user fee rises with every new employee. Annual price increases justified by exchange rates or inflation must also be taken into account. There are also costs that never appear on an invoice. The hours spent by staff doing by hand what the package can't do are not written on any bill, yet they are paid every month.
Costs That Surface Later with Your Own System
The project fee may look like a single item, but other expenses follow it. The server and domain renew every year. Security updates, backup checks and small fixes require a maintenance and support agreement. As your business changes you will want new features, and these are priced separately. Migrating old records and training staff should also go into the first year's budget.
How Do You Find the Break-Even Point?
Let's illustrate the method with a simple example; the figures are entirely hypothetical. Say 20 people use a cloud application that charges 900 TL per user per month. The monthly bill is 18,000 TL, and the annual total is 216,000 TL. After five years, even with no price increases at all, 1,080,000 TL will have been paid. If the team grows to 35 people, the annual total rises to 378,000 TL.
On the other side of the scale go the project fee in the quote, the annual maintenance fee and the hosting cost. The year in which the two totals meet is the break-even point. If that year comes before the end of the software's expected service life, your own system pulls ahead economically. If it comes later, the package is still more affordable. If you would like to see a clear figure for your own project, you can send us your requirements through the free quote form.
The calculation measures only money. The hours freed from manual work, fewer errors and faster quotes are hard to put into numbers, but they still have a place on the scale.
Who Keeps the Source Code and the Data?
Most comparison articles dismiss this topic in a single sentence. Yet this is what determines what you are left with on the day you want to part ways with the software.
With Off-the-Shelf Software You Get a Right of Use
A license or subscription is permission to use the software. The code belongs to the vendor, and the vendor decides the product's future. It can raise the price, remove a feature you like, or shut the product down entirely if the company changes hands. These things don't happen every day. Even so, reading the termination and price change clauses when you sign the contract takes a few minutes and can save you a great deal later.
With Commissioned Software, the Transfer Must Be in Writing
It is a common misconception that software you paid for automatically becomes yours. The Law on Intellectual and Artistic Works requires contracts concerning economic rights to be made in writing and the transferred rights to be listed one by one (Article 52). Delivering a copy of the program to you does not, unless otherwise agreed, mean the rights have been transferred either (Article 57). That is why the transfer of source code should appear as an explicit clause in the contract.
Alongside the right on paper, you also need actual access. You should be able to get into the repository where the code is kept with your own account, the deployment steps should be documented, and the server and domain accounts should be opened in your business's name. Without these, even if the rights are yours, moving the system to another team can take months. Getting a lawyer's opinion on the contract text is far cheaper than the cost of a dispute that might arise later.
Can You Export Your Data?
Programs change. Data stays. Ten years of customer history is worth far more than the program it happens to be kept in. Before committing to a package, ask in what format records can be exported. A button that just dumps the on-screen list into a spreadsheet is not enough. You also need to be able to take out related records, attached files and transaction history.
With your own system, the database sits on your server, so this question largely goes away. Even so, you should test at regular intervals that backups are being taken and that a backup can actually be restored.
KVKK and the Country Where Data Is Stored
Every business that processes customer or employee information is a data controller under Law No. 6698. Who made the software does not change that responsibility. When you use a cloud service whose servers are abroad, you are transferring personal data abroad. Article 9 of the law makes such transfers subject to certain conditions. An adequacy decision is required for the destination country; failing that, one of the appropriate safeguards comes into play, such as the standard contract published by the Board.
In practice, what you need to do before subscribing is ask the vendor which country its servers are in and what document it provides for the transfer. With your own software, you choose the location. Opting for one of the data centers in Turkey settles the matter from the start.
What Are the Risks of Building from Scratch, and How Do You Reduce Them?
Having a system built from scratch is less a purchase than a project. And projects can go over budget, run late, or even be abandoned halfway. Knowing the risks is the first step to shrinking them at the contract stage.
Scope Growing Along the Way
New ideas come up while development is under way. Each one looks innocent on its own, but together they double the schedule and the budget. The remedy is to have a scope document prepared before work begins, setting out point by point what each screen will do. Requests that come later go on a separate list, their cost is discussed and they are queued. We explained the logic of keeping the first version narrow in detail in our article What is an MVP.
Dependence on a Single Developer
If only one person knows the system, that person leaving locks up the business. Cleanly written code, documented deployment and a repository you have access to remove most of this dependence. Asking, when you get a quote, how the software would be handed over to another team also shows how much thought the other side has given the matter.
Screens Nobody Uses
The most expensive mistake is software that works but is never adopted. The cause is usually that the system was written around the process as the manager described it, while the actual practice on the ground is different. Talking during the analysis phase with the people who will use the program every day, and putting the first part in front of them early, lowers this risk. Phased delivery helps here too, because a misunderstood rule is noticed in the first weeks.
Is It Possible to Use Both Together?
It is, and for many businesses it is the most balanced solution. Standard work stays in the off-the-shelf package, a small system is written for the process that sets the business apart from its competitors, and the two are connected through an API.
In a typical setup, accounting and e-invoicing run in the existing program. Quote preparation, the field team's work orders or dealer orders, on the other hand, are brought together in a newly built panel. An approved order lands in the accounting program automatically, and nobody enters the same information twice. This way you leave regulatory compliance to the vendor and keep the area where you stand apart in your own hands.
The prerequisite for this setup is that the package opens a door to the outside. Before deciding, you check the vendor's documentation for which records can be read and written, whether the connection costs extra, and whether there is a limit on the number of requests. If there is no door, or it is very narrow, the hybrid model stays on paper. We covered the accounting and marketplace integrations commonly seen in Antalya on our Antalya software development page.
Are Low-Code Platforms an In-Between Option?
In recent years a third path has settled in between the two extremes. Low-code platforms let you build forms, tables and approval flows by dragging and dropping ready-made components. An employee with no programming knowledge can put together a simple internal app, such as leave requests or expense approvals, in a few days of work. The cost of trying it out is low.
The limit appears where the work gets complicated. Multi-step pricing rules, heavy data and two-way connections with external systems push these tools hard. In addition, the app you build cannot be moved off the platform, so the lock-in risk is the same as with an off-the-shelf package, and licensing is again per user. They are well suited to testing an idea and tidying up small internal processes. Before building the company's core workflow on one, you need to think about the way out.
What Determines the Price of Custom Software?
This is the question most often typed into search engines, and it has no single-figure answer. The price is calculated from the effort required. In the industry this effort is measured in person-days. One developer's working day equals one person-day, and the quote is the estimated number of days multiplied by the daily rate.
The number of days is determined by the number of screens, the variety of user roles, the external systems to be connected, the state of the old records to be migrated, and whether a mobile app is needed. That is why it is not surprising for one of two similar-looking projects to cost three times as much as the other. Ask for the line items to be listed separately in the quotes you compare. If the total is given in a single line, it becomes hard to understand what is included, and a quote that looks cheap can turn expensive later through additional invoices.
How Do You Plan the Move from a Package to Your Own System?
Once the decision is made, the most common mistake is trying to shut down the old program overnight. A healthy migration moves in stages and never leaves the business without a system for a single day.
Clean Up the Records First
In a program used for years, the same customer appears under several different spellings, discontinued products linger in the list, and half-finished orders have been forgotten. If this mess is moved over as it is, the new system loses trust from day one. Before the migration, you decide what will be moved and what will stay in the archive. It is tedious work. Skip it, and the price is steep.
Run Both Systems Side by Side for a While
The new software goes live with a single module, for example only quote preparation. While the team uses it, accounting and inventory carry on in the old program. Problems surface in a small area, get fixed, and then you move on to the next module. The parallel period feels like double work, so it should be kept short and its end condition written down in advance.
Cancel the Subscription Last
Do not end the old program's license until at least one full month-end close has been completed in the new system without problems. Also ask the vendor in advance how long read-only access to past records will remain open. For tax and audit reasons, you may need to look at old documents even years later.
Ask Yourself Before You Decide
Your answers to the questions below will clarify most of the picture before you talk to any vendors.
- Is this process directly tied to why customers choose you, or is it support work that runs the same way at every company?
- Can you write down the steps your current program cannot handle, and how many are there?
- How many hours of manual work are done each week for those steps?
- Where will your number of users be in the coming years, and what will the license bill be as a result?
- If you want to leave the package, can you export your records in full?
- In which country is the server holding your customer information?
- Has your process settled enough, or will it change again in six months?
If your answer to the first question is support work and to the last one is that it will change, you have strong grounds for sticking with a package. If the hours of manual work and the license bill are growing together, the scale tips the other way.
What Should You Look for at the Quote Stage?
If you have decided to have your own system built, the next task is finding the right contractor. Comparing prices alone is not enough. Whether a scope document will be written, which repository the code will be kept in, how interim deliveries will be approved and under what conditions bugs will be fixed after launch should all be clearly visible in the quote. We have compiled the questions that will help you in the meeting one by one in our guide to choosing an agency.
For businesses that are still unsure, there is one more middle path. An independent technical consulting engagement that reviews your current programs and workflow reveals which part really needs to be written before you commit a large budget. Often the answer is to tackle the single process that wastes the most time rather than having everything rebuilt from scratch.
These two approaches are not rivals but tools for different problems. Drawing on the maturity of a package for standard work, turning your own rules into code where you stand apart, and getting the two to talk to each other is the balance many businesses eventually arrive at.
Short answers
Is custom software always more expensive?
On day one, yes; in the long run, not always. For large teams paying per-user licenses, subscription fees accumulated over the years can exceed the project fee. For work with few users and standard needs, a package usually remains the more affordable option.
Can a small business have custom software built?
It can, as long as the scope is kept narrow. Instead of a system that covers the entire business, a small app written for the single process that takes the most time can be funded on a limited budget. Everything else carries on in the existing programs.
Who updates commissioned software?
With a package, updates come from the vendor automatically. With commissioned software, this work is handled by the development team under a maintenance agreement. Without an agreement, security patches and server updates are left unattended, so maintenance terms should be discussed together with the project contract.
How long does a software project from scratch take?
It depends on the scope; a single-screen tool and a multi-module system don't fit the same schedule. A reliable date can only be given once the scope document is written. Without that document, any timeline mentioned is no more than a guess.
Leave a comment
Your email will not be published. Your comment will appear once it is approved. KVKK Disclosure Text