Free Website Audit: Discover what's holding your digital presence back
What does this choice actually decide?
The choice decides who carries the product risk. With an off-the-shelf tool, the vendor decides the roadmap, the price and the end of life. You get a working system on day one and you live inside its rules. With custom software, you decide all of it, and you also own every bug, update and security patch.
The choice is not “flexible versus rigid”. Many ready tools are very flexible. It is “rented capability versus owned capability”. Ask which of the two your business actually needs for this process.
Start with the process, not the software. Write the steps, the people, the data, the exceptions and the handovers. Most of a process is standard and a small part of it is specific. A ready tool covers the standard part. The question is whether the specific part is worth a build.
How do the two compare?
| Decision criterion | Off-the-shelf tool | Custom software |
|---|---|---|
| Cost | Low to start. A recurring licence per user that grows with the team. | High to start. Then hosting, maintenance and change requests. |
| Time to launch | Days to weeks. Configuration, data import and training. | Weeks to months. Discovery, design, build, test and rollout. |
| Who can change it | Your admin, inside the settings the vendor allows. | Your development partner or your internal team, anywhere in the code. |
| Scale limits | Vendor plan tiers, user seats, API rate limits and record caps. | Your architecture and your budget. No vendor ceiling. |
| Lock-in | High. Data model, workflows and exports follow the vendor. | Low on the vendor side. Higher on the team that maintains the code. |
| When it is the wrong choice | The process is your advantage, or no tool fits without harming it. | The process is standard. You rebuild what a ready tool already does well. |
Do not read the bottom row as an insult to either option. Most companies should run nearly all of their operations on ready tools and build only the part that makes them different.
Choose off-the-shelf when
- The process is standard: accounting, payroll, email, helpdesk, CRM, storage.
- You need it working this month, and configuration is enough.
- Your team is small and cannot carry a maintenance budget.
- Compliance or security certification matters and the vendor already holds it.
- The vendor has an open API, so you can integrate rather than replace.
- You are still learning the process and the requirements change every week.
Choose custom when
- The process is how you win. Copying a competitor’s tool would remove your advantage.
- No tool fits, and the near misses each force a change that costs you money.
- Licence cost per user has passed, or will soon pass, the cost of building.
- Your data lives in three systems and people move it by hand every day.
- You need an integration the vendor will not build and the API cannot reach.
- You need to own the system for the long term: the code, the data and the roadmap.
What should you check before you decide?
Count the real cost of the ready tool. Take the per-user price, multiply by the users you expect in five years, add the paid add-ons, the integration middleware, the implementation help and the admin time. Then compare that number with a build plus five years of maintenance. Many buy-or-build arguments end at this step.
Count the cost of the workaround. Ask how many hours a week your team spends copying data, fixing records or explaining an exception the tool cannot hold. Multiply by the salary cost. That number is the real price of a tool that nearly fits.
Check the exit. For a ready tool, confirm you can export your data in a usable format, and confirm how. For a custom build, confirm you hold the repository, the infrastructure and the documentation. Both choices need an exit that does not depend on goodwill.
A middle path often wins. Keep the ready tool as the system of record, and build only the thin layer your business needs on top of its API. Konzept builds this kind of work under software development, and larger multi-system programmes under enterprise solutions. If the gap is repetitive manual work rather than missing features, AI automation may be the smaller fix.
Two worked examples show the middle path in practice. A client portal for a law firm usually reads from the practice management system rather than replacing it. A patient booking and telehealth flow usually writes into the clinic’s existing scheduling system. In both, the ready tool stays the system of record.
What does it cost?
Scope drives the cost. The number of user roles, the integrations, the data migration, the reporting, the security requirements and the rollout plan move it far more than the choice of language or framework.
Konzept publishes starting project prices on the pricing page. Growth starts from EUR 14,500, Scale from EUR 29,500 and Enterprise from EUR 44,000. Enterprise is the tier that covers full-stack software, API architecture and integrations. Monthly plans start at EUR 1,200 for Support, EUR 2,350 for Core and EUR 3,450 for Accelerate. These are published starting prices, not a quote.
We do not publish third-party licence prices. Vendor pricing changes and depends on your plan, so check the vendor’s own pricing page before you compare.
What should you do next?
Write the process down in one page: the steps, the people, the systems, the exceptions and the number of records per month. Add what breaks today and what it costs you. That page is enough to decide buy or build in most cases.
For help framing the discovery, use the website discovery and strategy checklist. If you are also weighing an internal hire against a partner, read agency vs in-house. To see the kind of systems we have delivered, read the work portfolio.
When the page is written, get a quote. Send the process and the tools you use today. We will say plainly whether a build is worth it, or whether a ready tool and a small integration would serve you better.
