Published: Last updated:

Standard Software

In a modern IT strategy, the goal is no longer to build everything from scratch. The art lies in selecting the right standard software (SaaS / COTS) for generic processes and integrating it seamlessly into your own value-creating architecture.

le dot treats standard software not as a closed silo, but as an API-based component within a larger Composable ecosystem.

Anti-Patterns: The Island Solution

Many organisations buy specialised software for accounting, HR, or marketing that does its job well but doesn't communicate with other systems. This leads to manual data entry, inconsistent reports, and prevents the automation of end-to-end processes. Dependency on the vendor's update cycles and roadmap also slows down your own agility.

Integration by Design

  1. API check before purchase: New software is only procured if it offers modern, well-documented interfaces (REST/GraphQL).
  2. Middleware & iPaaS: Using integration platforms (such as n8n, Make, or Azure Logic Apps) to automate data flow between systems without writing custom code every time.
  3. Master Data Management (MDM): Defining which system has authority over which data (e.g. the CRM for customer data, the PIM for product data).
  4. Single Sign-On (SSO): Centralised management of user identities (e.g. via Keycloak or Entra ID) across all standard applications.
  5. No-Code / Low-Code Integration: Enabling business units to create simple workflows between standard tools themselves, in compliance with IT governance.

The Advantage: Best-of-Breed Without Silos

A company uses Salesforce for sales, SAP for logistics, and Microsoft 365 for collaboration. Through consistent integration, data flows automatically from the first customer enquiry through to delivery and invoicing.

FAQ

Isn't standard software always cheaper than custom development?

In terms of acquisition cost, yes. But integration costs and the costs of process adaptation (when the business has to conform to the software) must be factored in. Composable Architecture minimises these costs.

How do we prevent sprawl when dealing with hundreds of SaaS tools?

Through centralised SaaS management and clear architecture guardrails. Every new tool must meet the organisation's integration and security standards.

Reference Guide

  • Gartner: Composable Business: The research report on the future of enterprise IT. gartner.com
  • The iPaaS Market Guide: Overview of modern integration platforms. G2
  • Enterprise Integration Patterns: The standard reference for system integration. enterpriseintegrationpatterns.com

Related Topics

Open Items