Evolve or Rebuild? How to Decide What Your Business Software Really Needs
When a system starts to fall short
A business system can continue to operate while gradually becoming a constraint on an organization’s growth. New processes, integrations, larger volumes of data, or changing business needs can make a solution that once worked well less efficient over time.
At that point, an important question arises: should the system be replaced and rebuilt from scratch, or can it still evolve? The answer should not depend solely on how old the technology is. In a Microsoft Research session on Full Stack Greenfield projects, the discussion highlights that starting completely from scratch can make sense in certain scenarios, but the decision should be evaluated in light of the organization’s context, goals, and the value already embedded in its existing solution.
Before rebuilding, it is important to understand what would be left behind and which problem the organization is actually trying to solve.
An existing system can still hold value
When an organization evaluates an older system, the focus often falls on its limitations: inflexible interfaces, manual processes, integration challenges, or an architecture that is difficult to maintain. Yet that same system may also contain years of accumulated knowledge. Business rules, validations, processes, integrations, and features can remain valuable even when the underlying technology needs to evolve.
That is why the question should not simply be, “How old is our system?” but rather, “Which parts still create value, and which ones are holding the business back?” This assessment helps avoid unnecessary rebuilds and directs effort toward the areas where change can have the greatest impact.
Evolving does not mean leaving everything as it is
Evolving a solution may involve modernizing modules, automating manual processes, improving the user experience, adding new integrations, or replacing components that are limiting scalability. This approach allows organizations to move forward progressively, prioritize the most important needs, and reduce the disruption of a full transformation. The key is to preserve what works and change what is genuinely constraining operations or growth.
When does rebuilding make sense?
Rebuilding a solution may be justified when current limitations prevent the organization from adding essential capabilities, when maintaining the system requires a disproportionate amount of effort, or when the architecture makes it increasingly difficult to respond to future business needs.
It may also become necessary when years of modifications have created too many dependencies and every new change adds more risk or complexity.
In these situations, starting with a different architecture can provide greater flexibility. However, rebuilding should not automatically be viewed as the better option simply because it uses newer technologies. It should address a specific business need.
Greenfield: starting from scratch is not always the best answer
Greenfield projects provide the freedom to rethink a solution from the ground up, choose new technologies, and design an architecture with fewer inherited constraints.
The Microsoft Research session emphasizes, however, that this approach should be evaluated carefully based on each organization’s needs and circumstances. Before committing to a complete rebuild, it is important to identify which existing knowledge, processes, and capabilities are worth preserving. New technology can create opportunities, but the decision should begin with the needs of the business.
The decision starts with understanding the problem
Before choosing between evolving and rebuilding, a company should assess which processes the system supports, which capabilities remain critical, where the main limitations appear, and what new capabilities the business will need in the future.
A few questions can help guide this assessment:
- Which current capabilities still provide value?
- Where are the main problems or constraints?
- Can the system support the business’s future needs?
- What would be the impact of a gradual modernization compared with a full rebuild?
- Which business rules and knowledge should be preserved?
These questions shift the conversation away from “Which technology should we use?” and toward “What does the organization actually need to solve?”
How Sphere helps organizations make better decisions about software evolution
At Sphere IT Consulting, we help organizations evaluate their technology solutions and identify the path that best supports both their current and future needs.
We assess the value of existing systems, their main limitations, and opportunities for evolution, helping determine whether the right approach is to modernize components, integrate new capabilities, or build a new solution.
Our approach is designed to ensure that every technology decision aligns with business goals and supports solutions that can grow alongside the organization.
Reference source:
Microsoft Research. Full Stack Greenfield Projects: Are they still relevant? Published June 24, 2026.
https://www.microsoft.com/en-us/research/video/full-stack-greenfield-projects-are-they-still-relevant/