For most of the history of business software, an application was a commitment. You scoped it, funded it, built it over months and then ran it for a decade, whether you still loved it or not.
That assumption is about to break, and disposable software is what replaces it.
In its strategic predictions for 2027 and beyond, published this month, Gartner forecasts that by 2029, 80% of new applications will be intentionally disposable, used for less than a year (Gartner). Short-lived tools, often built by employees rather than IT, for a specific job, then thrown away.
If that sounds far-fetched, look at what is already happening. AI app builders and coding assistants mean someone in operations can describe a tool in plain English and have something working by the afternoon. A tracker for a product recall. A dashboard for a three-month campaign. A form to coordinate a one-off site move. Why spend months building something that will only be needed for weeks?
The upside is real
Disposable software solves a problem that has frustrated organisations for years: the long queue of small requests that IT never gets to. Most of those requests were never worth a full project. They were worth an afternoon.
Letting people build what they need, when they need it, puts problem-solving closer to the problem. It reduces the number of spreadsheets doing jobs they were never designed for. And because the tools are meant to be thrown away, nobody spends years maintaining something that should have been retired long ago.
The risk is just as real
Here is the catch. A disposable app is still an app. It still reads data, often sensitive data. It still makes decisions, sends messages and shapes how work gets done. Multiply it by hundreds or thousands across an organisation and you have a governance problem that makes old-fashioned shadow IT look tidy.
Who knows which tools exist? What data are they touching? Are any of them quietly becoming critical? The classic failure mode is the "temporary" tool that ends up running a core process for five years, with no owner, no backups and no documentation.
Make throwaway safe
The organisations that benefit from disposable software will be the ones that make it safe to build and safe to throw away. That is a platform job. A few principles make a big difference:
- Governed data access. Disposable apps should read and write data through approved, permissioned interfaces, never direct database connections or exported copies.
- Expiry by default. Every new app gets an owner and an end date. When it arrives, the app is reviewed and either retired or promoted.
- A clear promotion path. When a throwaway tool proves essential, there must be a route to rebuild it properly, with testing, support and security.
None of this needs to slow people down. Done well, it is what lets you say yes to far more ideas, because you know the guardrails will hold.
The core gets more important, not less
There is an irony in all this. As more software becomes disposable, the systems underneath it, the data platforms, integration layers, identity and core transaction systems, become more important. Disposable apps are only as good as the data and services they can safely reach.
That means investment in core systems and clean, well-documented APIs pays off twice: once in the systems themselves, and again in everything people build on top of them. Organisations with messy core data will find their disposable apps are messy too, only faster.
Our view
Disposable software is not a fad and it is not a threat. It is a shift in where software gets made and how long it lives. The right response is neither to ban it nor to ignore it, but to build the platform that makes it safe, and to keep the long-lived systems in excellent shape.
That is exactly where consulting and engineering need to sit together. If you want help designing the guardrails, data access and core platform that let your organisation build quickly without losing control, talk to us. Our article on what AI coding tools are doing to delivery covers the quality side of the same shift.
Frequently asked questions
What is disposable software?
Disposable software is an application deliberately built for a short-lived purpose, often by the people who need it, and retired once that purpose is served, typically within a year.
Will most new applications be disposable?
Gartner predicts that by 2029, 80% of new applications will be intentionally disposable, used for less than a year.
How should organisations govern disposable apps?
Provide governed data access through approved interfaces, give every app an owner and expiry date, and create a clear path to rebuild apps properly when they become essential.