Begin with the operational requirement.

Technology discussions often begin with products: ERP, CRM, dashboards, automation or custom software. A better starting point is the management and user requirement.

What outcome must improve? Which workflow must be supported? What information must be captured? Who may view, edit or approve it? Which exceptions require escalation? What evidence does leadership need?

Three legitimate technology choices

Configure an existing tool

Use this when the workflow is common, platform capability is mature and the organisation can adapt without losing an important operating advantage.

Integrate current systems

Use this when existing tools work in their own domains but duplicate entry and disconnected data damage the end-to-end process.

Build a focused custom module

Use this when a specialised workflow, physical context or control requirement cannot be supported effectively through configuration.

Evaluate total operating complexity.

Licence price is only one component. Include configuration, migration, integrations, training, internal ownership, support, security, change effort and the cost of workarounds.

Custom software creates its own responsibilities: product ownership, testing, backup, documentation, access control and continuing maintenance. Existing platforms create constraints and dependency on vendor roadmaps. The decision should make those trade-offs explicit.

Use a decision gate before procurement or build.

  • Is the future workflow approved?
  • Has it been tested with users?
  • Are data ownership and definitions clear?
  • Can an existing tool meet the critical requirements without harmful workarounds?
  • Who will govern the system after launch?
  • What failure or adoption signal will trigger redesign?

OECD research shows both the value of SME digitalisation and the persistence of adoption gaps. The technology choice must therefore include the organisation’s capability to use and govern it.

Research base

This insight combines Ragaventhra Systems’ operating-architecture methodology with the following external sources. Findings are used within their original scope and are not presented as promised client outcomes.