Most established organisations have invested considerably in technology. ERP platforms, financial systems, CRM applications and specialised software support daily operations, often through processes that have been refined over many years. As organisations expand, introduce new services or change their operating models, the requirements placed on these systems evolve. New applications are introduced, processes are adapted and employees find practical ways to keep information moving between different parts of the business.
Existing technology may continue to perform its intended functions reliably, even when the organisation’s way of working has changed considerably. Periodically reviewing how business processes, software and automation work together can reveal opportunities to improve operations and make better use of technology investments. It also helps organisations assess whether their current systems can support future ambitions.
Why do manual workflows persist in modern organisations?
Manual workflows are common even in organisations with sophisticated technology environments. Financial teams export information for reconciliation, operational reports combine data from several applications and employees coordinate activities through spreadsheets or email. These processes often develop for practical reasons. A system implemented several years ago may need to support additional activities or exchange information with applications introduced later. Rather than redesigning the entire process, employees establish a workable solution.
Over time, these arrangements can become established parts of daily operations. A reconciliation that initially takes a few minutes may eventually involve several departments, while a reporting process created for one management team may become essential across the business. Not every manual activity needs to be automated. Approvals, exceptions and activities requiring professional judgement may benefit from human involvement. The opportunity lies in identifying which activities require that involvement and which exist because systems or processes have developed independently.
When should businesses reassess their existing systems?
Technology reviews are frequently associated with replacing ageing applications or preparing for major transformation programmes. However, organisations can benefit from reviewing their technology environment even when existing systems remain reliable. Changes in transaction volumes, business structure, regulatory requirements or customer expectations can affect how effectively established processes operate. Advances in software integration, automation and artificial intelligence may also create opportunities to perform familiar activities differently.
A review should examine how the organisation operates today, how its systems support those activities and what capabilities will be needed in the coming years. For example, a business expanding internationally may discover that regional operations use different processes for managing customers, orders or financial information. Each system may work well independently, but more consistent information exchange and consolidated reporting could benefit the organisation.
The appropriate response depends on the business requirements and existing technology. Some improvements involve relatively small changes to workflows or integrations. Others may justify reconsidering the architecture of a larger part of the operation.
How can system architecture improve business processes?
Business processes rarely operate within a single application. A financial transaction may involve customer records, payment processing, accounting software and reporting systems. Each application performs a particular function, while the organisation depends on information moving reliably between them. Consider a business that receives payments through several channels. Transaction information must be matched against customer accounts, reconciled with accounting records and made available for reporting. If these activities depend on separate exports and manual checks, processing times and the risk of inconsistencies may increase as transaction volumes grow.
Integrating the relevant systems can allow information to move through a more consistent process, with automated validation and clearly defined exceptions for employees to review. Designing this properly requires decisions about which systems maintain particular information, how changes are communicated and how errors are handled. Security, reliability and monitoring are equally important, particularly when processes involve financial or commercially sensitive information.
At | 91, these considerations are reflected in the development of platforms such as Blackcurrant Finance, which brings together banking capabilities, payments, accounting integrations and financial workflows. Similar architectural principles apply to e-commerce, logistics, SaaS platforms and other environments where multiple applications contribute to a single business process.
Should you integrate, automate or develop new software?
When reviewing an organisation’s technology, the first decision should not necessarily be which new system to implement. Existing applications may already provide much of the required functionality, particularly when they have been configured around established business processes. Improving the way these applications exchange information may be sufficient. In other cases, introducing automation can reduce repetitive activities and allow employees to concentrate on work requiring their expertise.
Custom software development becomes relevant when the organisation needs capabilities that existing products cannot adequately provide, or when a particular process represents an important competitive advantage. Developing a new platform can also be the right long-term investment. A business introducing a fundamentally different operating model, for example, may find that adapting its existing architecture would create more complexity than designing a new solution.
These decisions involve balancing business requirements, development costs, operational continuity, maintainability and future flexibility. At | 91, our approach is to build what differentiates a business and integrate what already works. Depending on the requirements, that may involve extending an existing application, developing a new component or engineering an entirely new platform.
How can automation become more intelligent?
Improving connections between systems creates opportunities to make better use of operational information. Automated processes generate data about transactions, processing times, exceptions and results. When this information is accessible, organisations can examine how workflows perform and identify where improvements may be worthwhile.
A financial reconciliation process, for example, may reveal recurring discrepancies associated with particular transaction types. Analysing those patterns can help improve validation rules or address underlying causes. In fulfilment operations, information about processing times, delivery performance and costs can support decisions about shipping methods or operational planning. Artificial intelligence can extend these capabilities when processes involve larger datasets or complex relationships that are difficult to evaluate using predefined rules alone. Potential applications include demand forecasting, anomaly detection and decision support.
In many cases, however, reliable integrations, clear business rules and good reporting already deliver considerable value. The appropriate level of automation depends on the process, the available information and the outcomes the organisation wants to achieve.
How do you align technology with future business ambitions?
A review of existing systems becomes particularly valuable when connected to the organisation’s longer-term plans. A company preparing to enter new markets may need to support additional currencies, regulatory requirements or regional operations. A business introducing digital services may require new customer-facing capabilities and more flexible integrations. An organisation expecting substantial growth may need to reconsider how its systems handle transaction volumes and operational monitoring.
Evaluating these requirements against the existing technology environment helps establish which capabilities are already available and where investment is necessary. It also allows improvements to be prioritised according to their expected operational value and contribution to future objectives. Rather than undertaking a large replacement programme without a clear business case, organisations can develop their technology in stages while maintaining continuity.
Making better use of your technology investments
Manual workflows can reveal where systems and business processes have developed independently. Reviewing these dependencies can identify opportunities to simplify information exchange, improve automation or reconsider how activities are performed. A broader assessment can also uncover opportunities to make better use of existing applications, improve operational reporting and introduce new software capabilities. The outcome may involve redesigning a workflow, integrating existing systems, extending a platform or developing entirely new software. By considering these options alongside business processes and future plans, organisations can make more informed technology investments and ensure their systems continue to support their ambitions.
Written by Daan Mallens, Founder | 91
Daan Mallens founded | 91 in 2010. The company specialises in software engineering and system architecture, operating across the Netherlands, India and Australia. With over 15 years of experience in technology and entrepreneurship, his work spans SaaS, FinTech an
