---
title: Why building your own planning tool might be a realistic option
description: Building your own planning tool used to be too costly. AI changes that. Discover the advantages, the risks and when an APS is still the better choice.
image: https://articles.involvation.com/hubfs/Building%20your%20own%20planning%20tool.png
---

- [English](https://articles.involvation.com/build-vs-buy-supply-chain-planning-tool)
- [Nederlands](https://articles.involvation.com/nl/planningstool-zelf-bouwen-of-aps-kopen)

[![logo involvation](https://articles.involvation.com/hs-fs/hubfs/logo_Involvation_payoff_en.png?width=234&height=48&name=logo_Involvation_payoff_en.png "logo involvation")](https://www.involvation.com/)

- [Consultancy & Implementation](https://www.involvation.com/consultancy-implementation/)

    - [Supply Chain Network Design](https://www.involvation.com/nl/advies-realisatie/sc-network-design/)
    - [S&OP/IBP](https://info.involvation.com/sales-and-operations-planning)
    - [Supply Chain Resilience](https://info.involvation.com/supply-chain-resilience)
    - [Resilience Quickscan](https://info.involvation.com/resilience-quickscan-how-resilient-is-your-supply-chain)
    - [Forecasting & Inventory Management](https://www.involvation.com/consultancy-implementation/forecasting-inventory-management/)
    - [Production & Process management](https://www.involvation.com/consultancy-implementation/production-control/)
- [Learning & Development](https://www.involvation.com/learning-development-2/)

    - [The Value Chain Academy](https://www.involvation.com/learning-development-2/the-value-chain-academy/)
    - [Serious gaming](https://www.involvation.com/learning-development-2/serious-gaming/)
    - [Our training approach](https://www.involvation.com/learning-development-2/approach/)
    - [Our areas of training](https://www.involvation.com/learning-development-2/our-areas-training/)
- [Interim Management](https://www.involvation.com/interim-management/)

    - [For Interim Managers](https://www.involvation.com/interim-management/voor-interim-managers/)
    - [For Clients](https://www.involvation.com/interim-management/voor-opdrachtgevers/)
- [Our assignments](https://www.involvation.com/our-assignments/)

    - Per area

          - [Supply Chain Strategy & Design](https://www.involvation.com/our-assignments/sc-strategy-redesign/)
          - [S&OP/IBP](https://www.involvation.com/our-assignments/sop/)
          - [Forecasting & Inventory Management](https://www.involvation.com/our-assignments/stock-control/)
          - [Production & Process management](https://www.involvation.com/our-assignments/production-control/)
          - [Learning & Development](https://www.involvation.com/our-assignments/learning-development/)
          - [Interim Management](https://www.involvation.com/our-assignments/interim-management/)
          - [Demand Driven SCM](https://www.involvation.com/our-assignments/demand-driven-scm/)
    - Per industry

          - [Mechanical engineering](https://www.involvation.com/our-assignments/mechanical-engineering/)
          - [Construction](https://www.involvation.com/our-assignments/construction/)
          - [High tech & automotive](https://www.involvation.com/our-assignments/high-tech-automotive/)
          - [Energy & Utilities](https://www.involvation.com/energy-utilities/)
          - [Chemicals](https://www.involvation.com/chemicals/)
          - [Pharma & life sciences](https://www.involvation.com/pharma-life-sciences/)
          - [Agri business](https://www.involvation.com/agri-business/)
          - [Consumer products & retail](https://www.involvation.com/consumer-products-retail/)
    - [Customer stories](https://articles.involvation.com/tag/customer-stories)
- [About us](https://www.involvation.com/about-us/)

    - [Who we are](https://www.involvation.com/about-us/who-we-are/)
    - [How we work](https://www.involvation.com/about-us/how-we-work/)
    - [Partner team](https://www.involvation.com/about-us/partnerteam/)
    - [Job Vacancies](https://www.involvation.com/about-us/job-vacancies/)
    - [Contact](https://www.involvation.com/about-us/contact)
- [Publications](https://articles.involvation.com)

    - [Articles](https://articles.involvation.com)
    - [Downloads](https://info.involvation.com/download-overview)
- [Events](https://info.involvation.com/event-overview)

# Why building your own planning tool might be a realistic option

![](https://articles.involvation.com/hubfs/Building%20your%20own%20planning%20tool.png)

Developing your own supply chain planning tooling has, for most companies, not been a realistic option. The developer time needed to create software that actually works made it too costly. Because of this, software companies emerged that build one piece of software that can be used by a lot of companies. These economies of scale have created a lot of strong planning applications, the so-called APS systems, that have drastically improved the supply chain planning function within companies.

Developments in AI technology, more specifically large language models (LLMs), are now changing this equilibrium. Because LLMs in essence speak ‘language’, the step from a written specification to working code has become much faster and cheaper. The software industry itself shows how quickly this is moving: in April 2026 [Google reported](https://www.semafor.com/article/04/24/2026/google-ceo-says-75-of-companys-new-code-is-ai-generated) that 75% of its new code is generated by AI and approved by engineers, up from about a quarter in late 2024. Writing code is no longer the bottleneck it used to be. Building reliable planning software takes more than code, and I will come back to that. But the costs have shifted enough that building your own tool deserves a place next to buying an APS.

## Advantages of developing yourself

The key advantage of developing a tool yourself is the ability to tune the planning application exactly to your physical process. If you have complex process dynamics, configuring that process into a ‘generic’ APS tool can be a hassle. Consider a food producer that has to sequence production runs around allergen cleaning and minimum batch sizes. An APS can often handle such logic, but it either does not capture the full essence of the process or it requires customizations that introduce costs and update risks. When you build the tool yourself, the physical process is the starting point instead of something you fit into an existing application.

Apart from the process fit, developing your own tool can reduce costs significantly. The main reason is speed. A realistic prototype is possible within a few days, and within a month (or sooner) the key functions can work as they should. This means you do not have to implement a full planning suite at once. You can start with one specific problem, for instance a view that flags expected inventory shortages based on the forecast, current stock and confirmed supplier deliveries. Once your planners have validated it, you extend the functionality as your needs grow. You avoid long-term licensing costs, and you only build what you actually need. The costs do not disappear, though: there is an upfront investment, and hosting, maintenance and support costs are still there depending on how you organize it. 

An additional argument is that you are not locked into a fixed contract that makes you inflexible to improve your processes. With APS systems you often depend on the vendor’s development roadmap. Organizations often have more ambitions than the tool can deliver directly. If you own the code and the process, you can act quicker. Especially with the uncertainties we face today, being able to change and adapt your planning process can be a game changer. Consider for instance an acquisition, where new products or factories enter the network with a slightly different planning need.

Most APS tools allow custom adaptations, but those come with disadvantages. One is the time it takes to build them. Another is that it is not certain future updates will match your custom stack, and at some point a full migration might be required to benefit from new functionality. Many SAP APO users are in this position right now: [mainstream maintenance ends at the end of 2027](https://sapinsider.org/blogs/sap-support-deadlines-2027-2030-2033/), with paid extended maintenance until the end of 2030, and the successors, SAP IBP and the planning functions embedded in S/4HANA, are different products. Moving to them is a new implementation rather than an upgrade. The timing of that migration is set by the vendor, not by the business.

To be fair, owning the code does not make you free of dependencies. You depend on the people who understand the code and on whoever hosts and maintains it. The difference is that this is a dependency you can design and contract for yourself.

## Potential risks need to be addressed

Moving from a tool that has been built with prompts to production-ready software that performs your key planning calculations requires careful consideration. The first two concerns are about the code itself.

Security risks are real. We see it in the number of companies being hit by cyber incidents, and the rise of AI increases the risk further: code that is written quickly by AI is not automatically secure code. A planning tool holds sensitive data and usually connects to your ERP, so this needs attention from the start.

The second concern is maintainability. AI makes it easy to add code quickly, and without clear architectural rules a code base grows into something that is hard to understand and hard to change. A planning tool is never finished: your process changes, the underlying software components need updates, and at some point someone other than the original builder has to make a change. If the code is not structured for that, every change becomes slower and riskier, and you lose the flexibility that was the reason to build yourself.

Support is the third concern. For a vendor whose software is used by many companies, setting up support is economically easy: what support engineers learn pays off across all customers. For a tool used by one company, that scale advantage is missing.

Finally, there is the functional risk. A planning tool that miscalculates inventory or ignores a production constraint produces a plan that looks fine but is wrong, and the consequences show up in operations. Rigorous testing is therefore essential before you can trust the outcomes. Established APS systems have an advantage here, because their calculations have already been proven at many customers.

These concerns are real, but here AI also has a real impact. We are learning how to use the power of AI systems effectively. This means setting up agents that work on and review each other’s work against the security and architectural rules we define up front, which addresses both the security and the maintainability of the code. Because every code base follows the same rules, hosting, maintenance and support can be standardized on a larger scale, which brings back part of the scale advantage vendors have. And the same agents can write and run automated tests on the planning calculations. This does not make mistakes impossible: independent testing with your planners and clear ownership remain necessary.

Within Involvation we are creating a platform in which these key elements are standardized, so that every application adheres to the latest standards. The architectural, maintenance and support principles we apply were already in use before AI. What is new is that AI lets us apply them across many different code bases.

## Having clear requirements is still essential

What does not change compared to implementing an established APS tool is the need for a clear understanding of the operating model: the key decisions you need to make, the granularity of those decisions, the data model that supports them, and the calculation logic that solves the problems at hand. To me, these requirements are part of the solution architecture that needs to be done up front anyway. Building a planning tool yourself might even push you to consider them more specifically. That is an advantage, but also a risk: there is no standard functionality to catch what you did not think of.

This is why having the right people, internal or insourced, is essential. Their main job is no longer writing code. It is translating your supply chain operating model into the right decisions and logic, and making sure the application is properly tested and maintained.

## When an APS is still the better choice

Going for an off-the-shelf APS is still very reasonable in many situations. APS providers have a lot of intelligent people who have already solved many different supply chain problems. Their solutions are often the result of iterations in which multiple options have been weighed and tried. Think of forecasting methods or multi-echelon inventory optimization. If many of your planning problems are of that kind, that accumulated knowledge is worth a lot and rebuilding it yourself might be overkill.

[In a previous blog post](https://articles.involvation.com/buy-or-build-the-supply-chain-managers-guide-in-the-age-of-ai-coded-apps)we already shared where an AI coded app might be an interesting option versus established APS systems. The point of this post is not to say that everything should be build from scratch but that the AI technology boost has changed the economics and in many cases should therefore be entered in the conversation.

![](https://articles.involvation.com/hs-fs/hubfs/Allard%20Bontes%20vierkant.jpg?width=100&height=100&name=Allard%20Bontes%20vierkant.jpg) [By Allard Bontes ![](https://articles.involvation.com/hubfs/raw_assets/public/Involvation_March2021/images/Capture.png)](mailto:a.bontes@involvation.com)

## Related items

- [Supply chain resilience and the cost of doing nothing](https://articles.involvation.com/supply-chain-resilience-cost-of-doing-nothing)
- [What are the benefits of a resilient supply chain?](https://articles.involvation.com/counting-benefits-resilient-supply-chain)
- [If you want a resilient supply chain, you need to think in terms of scenarios](https://articles.involvation.com/if-you-want-a-resilient-supply-chain-you-need-to-think-in-terms-of-scenarios)

 Everything should be made as simple as possible, but not simpler

![einstein](https://articles.involvation.com/hubfs/einstein.jpg)

**Albert Einstein**

### Contact

---

Emmalaan 5   
 3732 GM De Bilt   
 T +31 30 - 2217766   
 E [info@involvation.com](mailto:info@involvation.com)

### Website

---

- [Home](https://www.involvation.com/)
- [Consultancy & Implementation](https://www.involvation.com/consultancy-implementation/)
- [Learning & Development](https://www.involvation.com/learning-development-2/)
- [Our assignments](https://www.involvation.com/our-assignments/)

- [About us](https://www.involvation.com/about-us/)
- [Publications](https://articles.involvation.com)
- [Login](https://simcurve.involvation.nl/)

### Online games

---

[Inventory Game](https://inventorygame.involvation.com/en)  
[Beer game](https://www.involvation.com/learning-development-2/serious-gaming/beer-game/)

© 2026 Involvation 

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Allard Bontes",
    "url" : "https://articles.involvation.com/author/allard-bontes"
  },
  "dateModified" : "2026-11-18T11:40:11.267Z",
  "datePublished" : "2026-11-18T11:39:36.000Z",
  "headline" : "Why building your own planning tool might be a realistic option",
  "image" : [ "https://articles.involvation.com/hubfs/Building%20your%20own%20planning%20tool.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://articles.involvation.com/build-vs-buy-supply-chain-planning-tool",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://articles.involvation.com/hubfs/logo_Involvation_payoff_nl.png"
    },
    "name" : "Involvation"
  }
}
```