Business Approximate reading time: 20 minUpdated

Off-the-Shelf vs Custom Software: When to Choose Which

If the process fits an off-the-shelf tool, take it. Custom software is justified when the process is part of your competitive edge or ready-made products demand too many compromises.

Illustration: a browser window with a shopping cart facing a pair of braces — the choice between an off-the-shelf product and commissioned code.

You buy a CRM because the sales manager can no longer keep up with the notes, and after three months an Excel file with three price lists stands beside the system, together with a folder of invoices that someone copies into the accounts. The product is no worse than promised, because it knows the customer, the deal and the next call, but it does not know your process, because that process was not what the vendor built for hundreds of companies, and this gap, rather than a hole in a feature list that one customisation can fill, is the whole subject of this article: whether you are buying a tool for your process or a process for your tool. If what is missing is a connection between systems that already do their job, that is not an argument for custom software development: we connect what is already there first.

The choice between an off-the-shelf product and custom software is not a question about which button looks more modern, and it is not a question of whether you are “big enough to build it yourselves”. Our answer is the same sentence we have written on the service page: if your process fits an off-the-shelf tool, take the off-the-shelf tool, it will be cheaper, and a custom system is justified when the process is part of your competitive edge or off-the-shelf products demand too many compromises, and that sentence is not a sales trick so that we can sell custom software development afterwards anyway, but a test with which we lose the deals where we would have to write yet another CRM, and keep those where this test is passed.

This article is not a comparison of shop platforms, because we have already written that elsewhere, and it is not a price list for custom software, because we have no such article and will not have one, since we do not make up prices out of our heads, and it is also not a promise that your own system always wins. We sell both the implementation of an off-the-shelf product and custom software development from scratch, and an honest text starts from the fact that sometimes the most expensive service we can sell you is the one you do not need, so what follows is the boundary at which this choice can be made before someone sells you a sprint.

Off-the-shelf vs custom software: when to choose which

Take the off-the-shelf product if the process fits it, and commission software if the process is part of your competitive edge or the off-the-shelf products demand too many compromises: that is the whole answer, and the rest of this article is how to test that sentence against a concrete piece of work, not against a slide deck. A comparison that starts with a feature table ends before it has begun, because the table shows what the vendor has named, not who will decide on your next changes a year from now.

The consequences of the two wrong choices differ, because an off-the-shelf tool into which you have forced your process becomes a subscription plus Excel plus a person who holds the two together, and after a year that person is more expensive than any licence, whereas a commissioned system for a process that already runs in the accounts, the mail application and a standard CRM is the result of development that you will maintain yourselves even though someone else already maintains an equivalent product on the market. In the first case you have bought a product and then written a second system beside it; in the second you have written a system where a licence would have been enough; and both mistakes keep costing longer than they look in a proposal.

We name this boundary because we have seen both ends in a single week: a company that wanted “its own HubSpot” when what it needed was HubSpot, and a company that spent three years adapting a ready ERP to its price table and finally came for that same table as a new project, not because “the ERP cannot do it”, but because the compromises had already outgrown configuration. Neither of those cases is the result of ill will, because both start from the sentence “we need a system”, which is not yet a test, and the test begins only when you write the process on one page without a tool’s name and then look for which tool already provides the process described on that page.

Before a purchase, write down what the system has to do on the first day, what it must not forget in the second year, and who is allowed to change it without another vendor’s release. If the answers fit a product that can be configured, take the product. If the question is about a catalogue, prices, an order and delivery in an online shop, that is the shop test, and we do not rewrite it here; if the answers are a process a competitor cannot buy as an off-the-shelf tool, only then is it worth talking about a sprint. From here on this article is about that order, not a specific tool.

What an off-the-shelf product is, and what custom software is

An off-the-shelf product is software someone has already written for many buyers, which you purchase or subscribe to so that you can use it without a substantial rebuild, and in the Technology Code of Practice guidance on defining your purchasing strategy, updated in September 2026 for UK government buying, that same split is a written decision to build, buy or combine. COTS — commercial off-the-shelf software — we take here as a product you use as it was intended and configure rather than rewrite, and SaaS as software as a service, an application you subscribe to over the internet. Those are planning words for public money, not a duty on a private firm, and we take them here as names already written down, not as a law that imposes a public-sector spend control on you.

Custom software is a system written for your process, and specialised software, in our usage, is software written individually for a particular organisation or sector. We also call it a custom system, on the service page a non-standard system, and in the title custom software, and those are not three products but one piece of work: code that starts from your process, not from the vendor’s assumption about what a customer, an order or an invoice is, so the difference is not “better” against “worse”, but who is afterwards allowed to change that assumption.

An off-the-shelf product is not failed custom software, and custom software is not a better CRM, because WooCommerce is a ready e-commerce product, Moodle is a ready learning platform, WordPress is a ready content platform, and we sell all three as implementations, not as hidden development under another name. Laravel is not a product in this sense: it is a framework on which we have written custom systems since version 4.0 in 2013, and it does not give you a catalogue, a cart or a CRM until someone has written them, so to confuse a framework with a product is to imagine that “on Laravel” is already an answer, when it is only a way of writing the answer.

Here people also confuse subscription and ownership: SaaS means you pay for use and the supplier stores the data, a perpetual licence means you have paid for the right to use a version and updates are often a separate cost item, and commissioned code that we hand over means the source code, the documentation and the infrastructure configuration are yours. None of these options is automatically better. What matters is knowing clearly what you are buying, because otherwise a year later you are arguing about whether “the system is ours” when what you actually have is a subscription you can cancel.

The test we use to make this choice

The test is not “whether we like this screen”, but whether the process you must not hand to a competitor fits a tool the competitor can buy in the same shop: if it fits, the tool is the right answer, because it will be cheaper and it will be maintained by someone whose only job is that tool, but if it does not fit, because the price table, the order approval or the delivery terms are what you compete on, then the off-the-shelf product becomes a compromise, and a compromise here means the process gets done in Excel spreadsheets beside the system.

The other side of this test is too often forgotten: needs are more often common than unique, and you do not build a mail application, you do not build the accounts that already do what the law requires, and you do not build a standard sales funnel in which a deal is a deal. Public bodies have expressed the same principle differently. The UK Technology Code of Practice guidance on defining your purchasing strategy says to check whether suitable products are available and consider building software when commercial products cannot meet core needs or when ownership is needed. That is not a duty on a private company, and we do not turn it into one, but it is the same principle by which we refuse to develop what can be bought.

The third mistake is rebuilding a product until it is no longer a product, because configuration stays within supported limits — the fields, roles and flows the vendor has provided — whereas a customisation that rewrites the core so that the process “finally fits” wastes exactly the advantages for which the product was bought: the updates, the documentation, the fact that someone else finds the bug. We have seen this in Moodle implementations, where we first check whether a plugin already exists and only then write our own, and on WordPress sites, where we do not put on an off-the-shelf theme because it brings in dozens of features you do not need and which become a security risk, so a product with someone else’s core is not a custom system but a product from which you have taken the vendor’s core away.

We run this test in a discovery workshop, not on a proposal slide, because on a slide custom software development that looks like it cares about you always wins, whereas in the workshop the process that can be named wins. If after two days it turns out that the process fits an off-the-shelf tool, we say so, even when that means this week’s deal is not our non-standard system, because an article that always ends with “we will build you your own” is not a test, but a proposal hiding behind a question.

When the off-the-shelf product is the right answer

The off-the-shelf product is the right answer where the process has already been named in the industry and you are not the ones who invented that name, because email, accounts that issue an invoice the way the law requires, a standard sales CRM, a learning platform that records a course and its completion, and a small shop with one price and one warehouse are places where custom software development gives you nothing worth paying the difference between a licence and a sprint. We do not sell these products as “a temporary solution until you are ready for the real system”, because they are the real systems for these processes.

We also sell these products, and that is not a hidden promise that custom software development will be needed a year later: WordPress remains a content platform with a theme we write, not with an off-the-shelf theme from a marketplace; for a small shop with standard processes we ourselves recommend WooCommerce; Moodle remains a learning platform that we configure, migrate and theme, not invent from scratch. Implementation prices for these products are listed on the service pages and in one place lower in this article, where we need to show that the custom starting figure is not automatically the most expensive line on the price list, and here it is enough to say that the product remains a product.

The consequence, if in this place you still commission custom software development, is not “better control”, but maintenance you no longer share with thousands of others, because someone ships a security patch for a mail application to everyone, whereas the patch for your own mail application you ship yourselves, and that sounds like freedom until the second night on which you have to fix what the vendor has already fixed in their product. We sell that freedom where the process earns it, not where a licence is enough, because otherwise we are selling you work that a year later you will hate as an expensive duplicate.

So the most honest thing we can say before any estimate of a non-standard system’s price is a list of products we would recommend instead: if the process is learning, start with Moodle; if the process is content, start with WordPress; if the process is a small shop, start with WooCommerce; and if the process is invoices and the accounts the law already requires, start with the accounts you already have, and only then ask whether any of that has to become your own system. This list is not a partner agreement; it is a test we apply to ourselves.

When custom software is justified

Custom software is justified when the process is part of your competitive edge or off-the-shelf products demand too many compromises, and the process can remain subordinate to your core business and still pass this test, because the test is the number of compromises, not whether you sell software. If the off-the-shelf product starts to require that you become the average customer, and the role of the average customer does not help you compete, custom software development is justified by the test result, not by a wish for your own screen.

Integration is not an argument on its own here, because products have interfaces too, and we connect them, and the argument begins only when the interface is not enough and the process requires that current data on stock, price or status be kept in one place you control. The Sadales tīkls map portal, which we have built on Laravel and Leaflet, shows outages, free capacity and the connection fee, and that is not “a map plus a plugin”, because the fee and the capacity are the operator’s process, not a field on a maps product; on the Elektrum portal an SSO session attaches to every request before the Vue configurator is rendered, and that is not “an energy theme on WordPress”, because the session is part of the service, not decoration.

Colour, a logo and the order of a menu are not this test, because those can be done in a product, and we do them in a product: a Moodle theme with your palette, a WordPress theme without the surplus, a WooCommerce shop that looks like you. If the only thing that cannot be done in the off-the-shelf tool is “so that it looks like us”, you have not reached custom software, but a theme, and to confuse those two things is to pay for custom software development where design would have been enough, and then to wonder why maintenance is expensive for a system whose only difference is colour.

We also do not say that every industry automatically requires its own platform, because the name of the industry is not a test, and the test is whether this industry’s process in your company is the same thing the vendor has already put in the package, or whether it is your way of working in that industry, and that way cannot be bought as an off-the-shelf product. If it can be bought, buy it; if it cannot, then the conversation is about a custom business system, and only then is it worth talking about a discovery workshop, not about a theme.

The third route: a product with our code on top

Between the off-the-shelf product and development from scratch there is a third route, which we also sell and which comparisons most often leave out: the product remains a product, and on top we write what the product does not do, and that is not “a little custom software”, but a decision to leave the core where the vendor maintains it and to write only the layer that is yours. The Sadales tīkls service portal runs on October CMS, and the calculators, calendars and the fault report are work on the product, not a new content engine; in a Moodle implementation we first check whether a grading or reporting plugin already exists, and only then write our own, because otherwise we are selling you a duplicate.

If the question is about a catalogue, prices, an order and delivery, that is the shop test, and it has already been written in the article on the WooCommerce or Laravel choice, so we do not rewrite it here and we do not make a non-standard system the default answer. If the question is a CRM, an ERP, an internal panel or an industry process, stay here, because a shop is one case of the same test, not the whole content of the choice.

On the WordPress side the third route looks like a refusal, because we do not put on off-the-shelf themes, they bring in features that become a security risk, and we build a clean theme with only what is needed, and that is still a product: the editor writes in WordPress, not in an editor we invented, and updates come from WordPress, not from a release of ours alone. The difference between this and a custom system is that the content process fits the product, but the theme process does not fit a ThemeForest theme, and to confuse them is either to put on someone else’s theme and then wonder about the plugins, or to build your own CMS for content for which a CMS already exists.

This boundary is also the place where we say no to a “small rebuild” that by the third month already touches the core, because if the customisations become more than the configuration, if our code must be adapted before every update, if the vendor’s field no longer holds current data, you are no longer on the third route. That is already a development project hiding behind a product’s name, and then it is more honest to call it development and calculate its costs accordingly, because otherwise you are paying for a product you can no longer update, and for a system you cannot yet take over.

Money and time: principles, not a price list

A custom system with us starts at €8,000, and a full cycle usually takes from 12 to 32 weeks, and that is a starting figure, not an invoice, and 12 weeks are not the same as the first three months in which we promise a usable MVP: the shortest term is meant for a small development project, the MVP is the step after which the system is already in use, and 32 weeks is the upper bound of a larger piece of work, which also fits within the six to eight months stated in the general FAQ for a large custom system. The Laravel page starts at the same €8,000 and 6–24 weeks, and that is not cheaper custom software: it is a page for someone who already knows the work is Laravel, and it is not a test of whether development is needed at all.

These figures must not become the sentence “custom software is the most expensive choice”, because a Moodle implementation starts at €15,000, the Pro version of a shop is €9,500, and both sit above the custom starting figure, because one is the implementation of a large product and the other is a shop with a warehouse and B2B prices. To compare the €8,000 start with the Moodle start as the prices of development and of a product is the wrong arithmetic, because you can only compare two routes for the same process, and even then both sides are starting figures, not totals; for larger non-standard work we bill for time and materials with a weekly cap, because a fixed price there usually means a mark-up for risk or a fight about scope, and the hourly rate is €50 excluding VAT, but for orders exceeding 200 hours in a six-month period we set it individually.

Comparing a subscription and development is also not a formula in which after N years one side automatically wins. In private contracts, we see that the fee can rise as user numbers grow or because of indexation, integrations remain your cost and the data is kept with the supplier. It is advisable to have an exit plan in case the service stops or becomes too expensive. For UK government contracts, the Digital, Data and Technology Playbook calls for clear exit and transition arrangements. We do not quote a percentage of development costs here, because such figures rest on vendor publications, and we do not write numbers of that kind, but the principle stays: a subscription brings costs every year, and development has initial and maintenance costs. There are costs in both cases.

The Data Act, which applies in the Union from 12 September 2025, helps you retrieve exportable data from a cloud service and forbids the supplier from putting obstacles in the way of switching, but the functional equivalence it requires is of an infrastructure service, not of a CRM you simply “move”, and Regulation 2023/2854 does not promise that the process will travel with the file. Article 20 of the General Data Protection Regulation (Regulation (EU) 2016/679) allows the data subject to port the personal data they have provided, not the application, not your configuration, not the business rules, so if you want a system you can move to another developer, that is the source code we hand over, not an export from someone else’s panel.

What we do not say when we talk about custom software

We do not say that your own system is always the smarter choice, that the off-the-shelf product is for those who “have not grown up yet”, or that after three years custom software development has certainly paid for itself, because a curve of that kind without your process is an invention. An article that after an honest start still arrives at the claim that you should commission custom software development has gone too far, and we have seen that often enough to stop here, because our aim is a short and honest test.

We also do not say that Laravel is the answer to the off-the-shelf product question, because Laravel is how we write when the test has already shown that development is needed, and to sell a framework to a person who needs Moodle is to sell a hammer to a person who needs a shelf. Our Laravel page starts at €8,000 and talks about APIs, queues and tests, but this article talks about whether you need that page at all, and to confuse these two things is to choose the instrument before you have chosen the work.

We also do not say that a discovery workshop is a hidden way of luring you into a development project, because the result of the workshop is a plan that stays useful even if you decide not to use us, and sometimes the plan says: take the product you have already named, and we will implement it, or someone else will. If that sentence sounds to you like a lost deal, that is because it is a lost deal, and we would rather lose a development order in which we would have to write yet another CRM than gain a client who a year later asks why they are maintaining a system they could have subscribed to.

For public procurement, this test for private firms has to be adapted, because public-sector planning often asks first whether there is already a ready solution on the market, and that is a procurement question we do not go into here, while in the private sector the decision rests on your process and our price list. Both sides can reach the same answer, although different requirements apply to them.

How this decision is made with us

The work starts with a two- to three-day discovery workshop in which, together with your team, we go through the processes, the user roles, the risks and the MVP scope, and that is not a morning of slides, but work after which we can say whether the process fits an off-the-shelf tool, whether it needs the third route, or whether it needs development from scratch. If the answer is a product, the workshop has paid for itself with that sentence; if the answer is development, the next step is not code.

Before production code we prepare a clickable prototype in two to three weeks, because changing your mind there is cheaper than in a finished system, and the prototype is not “so that there is something to show the board”, but the place where you see that the price table you named yesterday is in fact another table, and where that discovery costs days, not months. Only then does development begin: in the first three months we build an MVP that can actually be used, and from there we expand iteratively, in two-week sprints with a demonstration after each one.

At the end you receive the source code, the documentation and the infrastructure configuration and can move them to another developer, and that is not a promise that the move will be pleasant, but a promise that you are not locked in to us. On larger projects we stay on time and materials with a weekly cap, and we still fix the MVP boundary, because otherwise “agile” becomes a word behind which the scope disappears, and if after the workshop you take another path, the plan stays yours, as we have written on the service page, and this article does not change that.

Before you write to us, write the process on one page without a tool’s name and mark which parts of the process must not depend on another vendor’s releases: if the page is empty or contains only “so that we have our own system”, you need a product, and we will say so, but if the page holds a process a competitor cannot buy as an off-the-shelf tool, then it is worth talking about custom software development. Write to us if you want us to read that page with you and tell you which solution suits you, even when the answer is to take the product you have already named.

FAQ

Frequently asked questions.

How do I decide on off-the-shelf vs custom software?

If your process fits an off-the-shelf tool, take the off-the-shelf tool — it will be cheaper. Custom software is justified when the process is part of your competitive edge or off-the-shelf products demand too many compromises. Write the process on one page without a tool’s name and mark which parts of the process must not depend on another vendor’s releases. If what remains is only “so that we have our own system”, you need a product, not custom software development.

Is a ready CRM or ERP worse than a system of my own?

No. An off-the-shelf product is not failed custom software, and custom software is not a better CRM. WooCommerce, Moodle and WordPress we ourselves sell as product implementations, not as hidden development. A system of your own is justified when the process is part of your competitive edge or the off-the-shelf products demand too many compromises, not when you want another colour on the same process.

Does the custom starting figure mean custom software development is more expensive than a product?

No. A non-standard system starts at €8,000, and that is a starting price, not an invoice. A Moodle implementation starts at €15,000, the Pro version of a shop is €9,500, and both sit above this starting figure, so the custom starting figure is not the most expensive line on the price list. For larger non-standard work we work on time and materials with a weekly cap, and the hourly rate is €50 excluding VAT, but for orders exceeding 200 hours in a six-month period we set it individually.

Who owns the code after custom software has been developed?

You do. The source code, the documentation and the infrastructure configuration are handed over, and you can move all of them to another developer. In the Union, the Data Act helps retrieve exportable data from a cloud service, but it does not rebuild the process in another CRM. Article 20 of the General Data Protection Regulation (Regulation (EU) 2016/679) allows the data subject to port the personal data they have provided, not the application.

Can I start with an off-the-shelf product and later move to a system of my own?

Yes, and often that is the right start if the process has not yet been clearly defined. The third route is a product with our code on top, while the core stays in the vendor’s hands. If the customisations become more than the configuration, it is more honest to call it development and calculate its costs accordingly, not to hide it behind a product’s name.

RELATED SERVICE
Custom software development

Custom software development for businesses and institutions: internal systems, web platforms, registers and integrations. We start with process research and a prototype, then build the first usable version.

Learn more