Apps, Platforms & Bolt-On Bedlam: Untangling the Tech Tangle | Podcast
Never miss a thing.
Sign up to receive our insights newsletter.
As organizations modernize their technology environments, the line between applications and platforms has become increasingly blurred, and costly misunderstandings often follow. In this episode of Weaver: Beyond the Numbers, Morgan Page examines how today’s tech ecosystems are built and where they commonly go off track. The conversation focuses on how organizations can more clearly distinguish between applications and platforms, evaluate what functionality is truly included and avoid unintentionally creating a fragmented, bolt-on technology environment.
Key Points:
- Applications solve narrow problems, while platforms introduce architectural decisions that shape how your organization operates, scales and integrates long term.
- “Platform sprawl” often emerges when organizations assume core capabilities are native, only to discover they require add-ons, custom development or ongoing technical debt.
- Discovery is the most effective control point for preventing over-customization and misaligned technology investments.
In this episode, we break down the technology terrain, beginning with applications — tools designed for specific functionalities with limited adaptability. As businesses evolve, the preference often shifts toward platforms like Salesforce and ServiceNow, which offer broader capabilities that can grow with your enterprise. However, this shift brings its own set of challenges, including understanding what functionalities are inherently provided and which require additional investment.
Morgan compares this dynamic to purchasing a vehicle based on assumptions rather than specifications. A base model may appear capable at first glance, but critical features often require upgrades that significantly change the total investment. He emphasizes the importance of being intentional early and clearly defining whether a solution is a platform or an application, then determining what functionality is included and what will require additional procurement.
The episode emphasizes discovery as the most effective mechanism for controlling complexity before it becomes embedded. By doing so, you can pinpoint essential functionalities and discern whether custom development is necessary. Morgan advises, “One of the great things I like to encourage people to do is leverage discovery exercises. Oftentimes, a $50,000 or $100,000 functional criteria discovery exercise with a short list of your vendors can really help identify what you’re in for from a design perspective and what those applications can do natively.” This proactive approach helps mitigate long-term costs associated with custom solutions, ensuring sustainable integration and support.
Subscribe and listen to future episodes of Weaver: Beyond the Numbers on Apple Podcasts or Spotify.
©2026