Custom Information System or Off-the-Shelf Solution? How to Decide
A custom information system is software developed precisely around one company's processes, unlike an off-the-shelf (boxed) system that sells the same product to thousands of customers. It pays to build custom what sets your company apart from the competition, or processes that an off-the-shelf system can only be bent to fit expensively and awkwardly. Accounting, payroll or email, on the other hand, are almost always better off-the-shelf. The right answer is therefore often not "either/or" but a combination: off-the-shelf systems for standard operations and your own system where nothing ready-made fits.
In this article we show when a custom system pays off and when it doesn't, how to decide using specific criteria, how development works, what it costs and how it's paid for, what the risks are and what the contract must include so you're not dependent on one vendor forever.
Key takeaways
- Build custom what is specific to your company or a competitive advantage. Take standard operations (accounting, payroll) off-the-shelf.
- Besides choosing between off-the-shelf and custom, there's a third way: your own system built on a platform that provides the admin, API and permissions out of the box.
- Compare the total costs over 3–5 years: per-user licenses versus development and maintenance.
- Secure a license to modify, the source code and documentation in the contract. Without them, you depend on the vendor.
Table of contents
- What is a custom information system
- Three paths: off-the-shelf, customized or custom-built
- When a custom system pays off and when it doesn't
- Decision criteria in a table
- The third way: your own system on a ready-made platform
- How custom system development works
- How much a custom system costs and how it's paid for
- Risks and how to guard against them
- The contract: license, source code and support
- Connecting to ERP, CRM and the online store
- How to choose a vendor
- Making the decision step by step
- Frequently asked questions (FAQ)
What is a custom information system
A custom information system is software designed and developed for the processes of one specific company. In general terms, an information system includes the people, data and technology a company uses to process information. In everyday language, though, it mainly means software: tracking jobs, production, service, bookings, approvals or product data.
The opposite is an off-the-shelf system, often called boxed software or SaaS. Thousands of companies use the same product and each one just configures it. An off-the-shelf system is fast and cheap to start with, but the company has to adapt to it. A custom system adapts to the company, but it takes longer and costs more to develop.
Typical examples of custom systems: service call tracking with technician scheduling, a configurator for made-to-order products, a booking system with its own rules, product data management for multiple online stores and markets, or an internal portal that brings data from ERP, CRM and the online store together in one place.
Three paths: off-the-shelf, customized or custom-built
The choice isn't just between two extremes. In practice, a company has three or four options:
| Path | Advantages | Disadvantages | When to choose it |
|---|---|---|---|
| Off-the-shelf without changes | Fast launch, low starting price, updates included | The company adapts to the system, you pay per user | Standard processes (accounting, payroll, typical CRM) |
| Off-the-shelf with customizations | Ready-made core, specific parts adapted | Customizations complicate updates, dependence on the partner | Process is 80% standard, the rest specific |
| Your own system on a platform | Built exactly around your processes, admin and API ready-made, faster than building from scratch | Requires developers, you run it yourself | A specific process that has to be forced into off-the-shelf systems |
| Building from scratch | Complete freedom | Most expensive and slowest, most risks | A unique product or extreme requirements |
The most common mistake is the second path taken to the extreme: an off-the-shelf system with so many customizations that it can no longer be updated and costs more than a custom system.
When a custom system pays off and when it doesn't
A custom system pays off when off-the-shelf solutions don't fit and the mismatch costs you more than your own development would. Typical signs:
- the process is a competitive advantage and you don't want it to be the same as your competitors',
- off-the-shelf systems cover only half the process and the rest is done in Excel,
- you pay licenses for features you don't use and for users who only need one screen,
- you need to connect data from several systems that don't talk to each other,
- working with the system is slow because it was designed for a different type of company.
A custom system, on the other hand, doesn't pay off:
- for standard, legally regulated operations (accounting, payroll, VAT), where off-the-shelf systems track legislative changes for you,
- when the process isn't settled yet and you change it every month,
- when you lack the capacity for specification, testing and acceptance,
- when an off-the-shelf system covers your needs and the only reason is "we want our own".
Decision criteria in a table
Go through the criteria and answer each one honestly. If most answers point to the right, a custom system makes sense.
| Criterion | Leans off-the-shelf | Leans custom |
|---|---|---|
| Process | Standard, same as at other companies | Specific, a competitive advantage |
| Off-the-shelf coverage | 80% or more without changes | Under 60%, the rest in Excel |
| Legislation | Heavily regulated area | Internal process without legal changes |
| Number of users | A few people | Dozens of people, per-user licenses add up |
| Integrations | A ready-made integration exists | Multiple systems need to be connected in a specific way |
| Speed | You need to launch within a month | You can build gradually in stages |
| Process stability | The process is still taking shape | The process is settled and documented |
| Internal capacity | No one has time for specification and testing | There's a person who will lead the project on the company side |
The third way: your own system on a ready-made platform
Today, a custom system doesn't have to mean programming everything from scratch. A large part of every internal system consists of the same things: login, permissions, tables, filters, forms, change history and an API for connecting other systems. Ready-made platforms handle all of this, so development can focus only on what is specific to the company.
One such platform is Directus. It connects to a database and automatically creates an admin interface plus a REST and GraphQL API on top of it, with role-based permissions. Internal tools for tracking clients, jobs, orders, bookings or approval workflows are built on it and connected to the online store, ERP or CRM. The result is a custom system, but developed faster and more cheaply than from scratch, with an admin people can use without lengthy training. Find out more on our Directus page. How Directus works as a headless CMS and data platform is explained in our article What Is a Headless CMS.
Another option is low-code tools, where even someone without programming skills can assemble simple applications. They suit smaller internal records. For systems the company's operations depend on, however, they quickly hit limits in performance, permissions and integrations.
How custom system development works
Good custom development doesn't happen as one big delivery after a year, but in stages where the company continuously sees and tests the result. Typical phases:
- Analysis: a description of processes, roles, data and integrations. The output is a specification both sides agree on.
- Design and prototype: screens and the flow through the system in a clickable mockup, still without programming. The cheapest phase for changes.
- First usable version (MVP): the smallest scope that already replaces the current state for one part of the company.
- Gradual expansion in short stages based on priorities and user feedback.
- Testing on real data with real users.
- Data migration and launch, ideally running in parallel with the old solution for a transition period.
- Operation and development: fixes, updates, new features.
The biggest savings are in the first two phases. A specification error you catch in the prototype costs an hour. The same error caught after launch costs weeks of rework.
How much a custom system costs and how it's paid for
The price of a custom system depends on the scope, the number of integrations and whether it's built on a platform or from scratch. Only an analysis gives a reliable estimate, but always compare the total costs over several years, not just the development price.
Example comparison: an off-the-shelf system at CZK 1,000 (around EUR 40) per user per month for 25 users costs CZK 300,000 a year, or CZK 1.5 million over five years, and that's without customizations and integrations. If a custom system comes out at a comparable amount including operation and covers your processes better, it's the better deal. If it's more expensive with the same benefit, it isn't.
Three common payment models:
| Model | How it works | When it fits |
|---|---|---|
| Fixed price | A price for a precisely defined scope | Small, clearly specified projects |
| Time and materials | You pay for the hours actually worked, based on priorities | Gradual development where the scope is refined along the way |
| Prepaid hours | A block of hours drawn down as needed | Ongoing development and maintenance after launch |
A fixed price feels safe, but with an unclear specification the vendor adds a buffer, or the scope starts getting cut. For ongoing development and maintenance, we offer prepaid development hours. Always include operation in the budget too: hosting, backups, security updates and minor changes.
Risks and how to guard against them
The biggest risks of a custom system aren't technical; they lie in the specification and the relationship with the vendor. The most common:
- Scope creep. Every meeting adds a feature. Defense: an MVP with firm boundaries and a "next stage" list.
- Vendor lock-in. Only one vendor or one developer understands the system. Defense: source code, documentation and mainstream technologies for which you can find other developers.
- No owner on the company side. No one has time to specify and test. Defense: appoint a specific person with dedicated time.
- Poor-quality data. Errors from the old system are carried into the new one. Defense: clean up data before migration.
- Security and backups. No one updates your own system. Defense: an operations contract with updates and backups.
- Low user adoption. A system designed without the people who will work with it. Defense: involve users in the prototype and testing.
The contract: license, source code and support
For a custom system, the contract is as important as the development itself. Under Czech copyright law, a computer program is protected as a copyrighted work, and the copyright itself cannot be transferred. The client obtains a license, meaning the right to use the work. If the contract doesn't define the scope of the license, the law assumes for a commissioned work only use for the purpose arising from the contract. That may not include modifications by another vendor. In the contract, therefore, clarify:
- License scope: exclusive, unlimited in time and territory, with the right to modify and extend the system and to have it modified by a third party.
- Source code: handover of the current source code, ideally to your own repository on an ongoing basis, not as a one-off at the end.
- Documentation: both technical and user documentation, detailed enough that someone else can continue working on the system.
- Third-party components: which libraries and platforms the system uses and under what license terms.
- Support and SLA: response times for bugs by severity, the price of maintenance.
- Personal data processing: if the vendor runs the system and it contains personal data, the contract should include a data processing agreement under the GDPR.
- Termination: handover of the system, data and access to a new vendor.
Have the contract for a larger project reviewed by a lawyer with IT experience. The wording of the license decides whether you really own the system.
Connecting to ERP, CRM and the online store
A custom system rarely stands alone. It usually complements off-the-shelf systems, and its value lies precisely in connecting them. Typical links:
- ERP supplies customers, prices and invoices, and the custom system returns jobs and work performed. What an ERP does and which ones are used in the Czech Republic is described in our article What Is an ERP System.
- CRM holds sales relationships, and the custom system handles job delivery. See our article What Is a CRM System.
- Warehouse and WMS supply availability and shipping status. See our article What Is a WMS.
- A Shopify store receives orders, and the custom system processes them or supplies product data.
The rule for integrations: every piece of data should have one master system from which it spreads to the others. When the same data is edited in two places, the systems will sooner or later drift apart.
How to choose a vendor
You choose a custom system vendor for years ahead, so look more at how they work than at the lowest price. Questions to ask:
- What similar systems have you built, and can we talk to their users?
- How does the analysis work, and will we see a prototype before development?
- Which technologies do you build with, and can we find other developers for them?
- How often will we see the system in progress, and how are specification changes handled?
- When and how do you hand over the source code and documentation?
- What do operation, updates and support look like after launch, and what do they cost?
- What happens if we end the cooperation?
How working with us generally goes is described in our article How Does Cooperation with Us Work.
Making the decision step by step
- Describe the process you want to solve and what it costs you today (time, errors, licenses).
- Check off-the-shelf systems: what percentage of the process they cover without changes.
- Go through the decision criteria in the table above.
- Calculate the total costs of both options over 3–5 years.
- If a custom system comes out ahead, start with analysis and a prototype, not straight with development.
- Build in stages, starting from the smallest usable version.
- Watch the contract: license, source code, documentation, support.
Frequently asked questions (FAQ)
What is a custom information system?
A custom information system is software developed precisely around one company's processes. Unlike an off-the-shelf system used by thousands of companies, it adapts to the company, not the other way round. Typically it's job, service, production, booking or product data tracking connected to ERP, CRM and the online store.
When does a custom system pay off instead of an off-the-shelf one?
When the process is specific or a competitive advantage, off-the-shelf systems cover it only partly and the rest is handled in Excel, or when licenses for dozens of users exceed the cost of your own system over the long term. For standard operations such as accounting and payroll, an off-the-shelf solution is better.
How much does a custom information system cost?
It depends on the scope, the number of integrations and whether it's built on a platform or from scratch. Only an analysis gives a reliable estimate. Always compare the total costs over 3–5 years, including operation, with the license costs of an off-the-shelf system for the same period and the same number of users.
Who owns a custom-developed system?
Under Czech law, the copyright to the program remains with the author, and the client obtains a license to use it. The scope of the license is set by the contract. If the contract doesn't define it, the law assumes for a commissioned work only use for the contract's purpose. That's why you should secure an exclusive license with the right to modify and the handover of the source code in the contract.
How long does custom system development take?
The first usable version of a smaller system built on a platform can be ready within weeks; large systems are developed over months. Speed depends heavily on the quality of the specification and the availability of people on the company side. Developing in stages delivers the first benefits sooner than one big delivery.
Which is better, customizing an off-the-shelf system or building your own?
If the off-the-shelf system covers most of the process and the changes are minor, customize it. When customizations pile up and the system can no longer be updated because of them, your own system built on a platform often comes out cheaper and more reliable. The deciding factor is the total cost over several years.
Deciding whether to build a custom system?
We'll go through your processes with you, compare off-the-shelf solutions with your own system and, if it pays off, build it on the Directus platform with integrations to your online store, ERP and CRM. Take a look at our app development services or book a free consultation.
Sources
Author: Miroslav Volovec, CEO of 3NODE Software s.r.o. – specialists in e-shop and app development on the Shopify platform.
