The situation: You need new software that fits your needs in logistics, field service, service or sales. The strategic question: Should you develop your own individual solution with your IT or would you rather buy standard software on the market? Make or buy?

MAKE OR BUY: IN-HOUSE DEVELOPMENT

Software is developed to solve problems, and to do so in a highly targeted way. If the user company develops the software itself, then the solution is fully focused on their requirements. That is fundamentally a great advantage. You set the direction yourself and ultimately receive customised software that is precisely tailored to the tasks you need to manage. Be it in route planning, transport management, scheduling, or sales.

SHORT PATHS AND HIGH TRANSPARENCY

Another advantage: the short service routes to the IT department. If software development takes place internally, developers are greatly more accessible than with an external provider. And you usually know exactly who is working on what and receive a transparent development process. In addition, you have full control over the data when you use the software later.

BUT THEY ARE THE 'GUINEA PIG'.

One major disadvantage is that the programme has to be developed first. That costs time. And since it is a completely new solution, it has not yet proven itself under the real conditions of daily business. You yourself are the 'guinea pig' and risk increases.

DO NOT UNDERESTIMATE ADDITIONAL EFFORT

This means that you will probably have to deal with a number of teething problems at the beginning of the software's use. Problems often arise that you could not have foreseen. Then your IT team has to get back to work. Such bug-fixing and software adaptation can be costly, and you don't have the capacity to test and test again.

DEVELOPMENT IS AN ONGOING PROCESS

There is no external customer service that you can quickly ask for help. The responsibility lies with your own team. This certainly has advantages at certain points, but it can create its own disadvantages for the rest of the business. In software, development alone is not enough. External factors, such as technical architecture take over, and you'll soon find a costly adjustment is necessary within a couple of years. Ask yourself: can your IT do this and is it prepared for it?
Furthermore, there is the question of how much sense it makes to develop software if a very similar solution is already offered on the market. The decision to 'make or buy' should therefore always be made after researching and analysing the existing market.

MAKE OR BUY: A SOLUTION FROM THE MARKET

What are the advantages and disadvantages in terms of 'make or buy' when you take your software requirements to the market?
One advantage is definitely that the chosen solution is already in use in many companies. It is accordingly field-tested and mature. There are demos, trial versions, and testimonials whose feedback you can draw on to evaluate the software.

WITH 'BUY' YOU HAVE THE CHOICE OF APPROPRIATE OPTIONS

In contrast to in-house development, with a buy decision you have choice, and you can compare different systems and their modules. This means you have alternatives instead of 'this software or none' as with in-house development. And since the programme does not have to be developed first, a standardised software platform is often implemented faster than custom software.

IT MAY NOT FIT 100 PER CENT

What could happen: that you do not find a solution on the market that fits your requirements 100 per cent. You may have to agree on individual adjustments to the software (custom features) with the provider of your choice. You must seek ensure you're not paying for functions that you do not need.

RAPID UPGRADES AND ONGOING DEVELOPMENT

However, the latter point can also be an advantage. If you need additional functions later, they are already available. Plus, you benefit from ongoing developments of the software by the provider. Especially if you use a cloud solution, these are worked-on in the background and are well tested. Updates and further developments for other customers are then usually also played out for your software version (and can be rolled back in a short window should problems arise).