When the office closed: software's continuity test
The pandemic exposed the distance between putting work online and keeping a business operating. Access, capacity and support became decisive tests of enterprise software.
On 11 March 2020, the World Health Organization assessed that COVID-19 could be characterised as a pandemic. The public health emergency brought immediate questions for employers: how to protect staff, maintain essential services and conduct work that had depended on a shared location. For enterprise software, this became a demanding test of access, capacity and operational control.
The commercial consequences were uneven. Collaboration and cloud services faced increased use, while businesses serving interrupted industries confronted falling activity and uncertain budgets. The investment question was which products could keep an important business process working when its usual conditions disappeared.
A surge in use did not mean a uniform recovery
Microsoft's results, published on 29 April 2020, reflected this uneven demand. For the quarter ending 31 March, the company reported increased use of Microsoft 365, Teams, Azure, Windows Virtual Desktop and security services as customers worked and learned from home. Its commercial cloud revenue reached $13.3 billion, up 39% against the corresponding quarter a year earlier.
The same release reported slower transactional licensing in the final weeks of the quarter, particularly among small and medium businesses, and lower advertising spending on LinkedIn. Microsoft said COVID-19 had a minimal net effect on total company revenue for that quarter and warned that its effects might emerge more fully later. Even within a single company, demand was moving in different directions.
The bottleneck could sit outside the application
A hosted application could remain available while an employee lacked a suitable device, permission to access a file or a reliable connection to an internal system. CISA's enterprise VPN advisory, first issued on 13 March and revised in April, specifically warned that organisations could exhaust their available VPN connections. Critical operations and the security team's own work could then suffer.
Scroll to view all columns
| Comparison | System observation | Operational question |
|---|---|---|
| Access | The service is online | Can authorised staff reach the systems and records they need? |
| Capacity | More users are connected | Can priority work finish when demand peaks? |
| Recovery | An incident is detected | Can the responsible team restore the affected process? |
Access and capacity risks identified in CISA's enterprise VPN advisory.
For a software supplier, this changed the meaning of a successful deployment. Installation was only one part of the work. Customers also needed account provisioning, clear access rules, usable support and a way to recover when a dependency failed. A product that reduced those administrative burdens had a different practical value from one that merely added another place to communicate.
Security travelled with the work
CISA advised organisations to update VPNs and devices, prepare for phishing attempts, strengthen authentication and ensure security staff could review logs, detect attacks and respond to incidents. It also recommended testing VPN limits before mass use. The shift changed operating conditions and exposure to familiar security risks.
Those requirements matter when assessing a young security or infrastructure company. A useful product must fit the customer's identity systems and working practices. Its deployment should not depend on every employee understanding a new security architecture. The evidence worth examining includes the time required to configure access, the support needed when an employee changes role and the ability to investigate an incident using records the customer can actually retrieve.
From emergency use to a durable customer relationship
Urgency could shorten a buying decision while leaving the eventual contract uncertain. An organisation might adopt a tool for a temporary team, use a free allowance or increase consumption because other channels were unavailable. Investors therefore needed to separate the initial demand signal from evidence about willingness to pay, ongoing use and the costs of serving that use.
For an enterprise software business, the relevant review would follow a customer group through subsequent months: which activities remained in the product, whether paid accounts expanded or contracted, and how much staff assistance each deployment required. Infrastructure bills also deserved attention. More traffic could improve revenue while increasing delivery and support costs. A busy system and a sustainable business were distinct things to demonstrate.
Continuity as an investment test
The disruption put ordinary dependencies under unusual strain. Access, identity, connectivity, approvals and support became visible together. The resulting demand did not guarantee any individual startup's success, and subsequent cloud purchases had other drivers too. It did establish a demanding test for software: could a customer continue an essential task when people, location and demand changed at the same time?
For investors in enterprise software and communications, evidence against that standard is more informative than a demonstration under ideal conditions. It connects technical performance to a customer's operating priorities and makes the work required after the sale visible before it becomes a constraint on growth.
Investment implications
- Measure whether customers complete essential work, alongside the number of people logging in.
- Access controls, support capacity and recovery procedures belong in the same assessment as software availability.
- Emergency adoption provides evidence of need; renewal and sustained use establish a different commercial claim.
Sources
- Archived WHO timeline of COVID-19 (opens in a new tab)
World Health Organization
- Enterprise VPN Security, advisory AA20-073A (opens in a new tab)
Cybersecurity and Infrastructure Security Agency
- Microsoft FY2020 third quarter results (opens in a new tab)
Microsoft
Published
