9horsemenStart building
Essays

The Death of the Enterprise Monolith: Why Micro-Apps Are the Future of Work

Published on 11 Sept 2026 by Shri Krishnan

An essay from 9horsemen's founder. For practical help running a business, see the blog. More thinking like this on our podcast, Why Your Software Sucks.

A corporate worker manually edits a dense spreadsheet on their main monitor while a sleek, expensive enterprise dashboard sits ignored in the background, illustrating the failure of monolithic software to handle specific tasks.

TL;DR:

  • The Core Problem: Multi-million-dollar enterprise software platforms focus on executive dashboards but fail to handle the granular, specific logic required by operators like compensation architects and finance teams.
  • The Structural Reality: Enterprise SaaS vendors rely on massive contract values, forcing them to build generalised bloatware rather than solving the localised, daily workflow bottlenecks of individual departments.
  • The Solution: The future of enterprise scale is a swarm of targeted micro-apps. Each one does a specific job that the monolith handles badly.

Micro-apps are small, single-purpose apps that each do one job well, like a sales incentive calculator built for one team. Here’s why big all-in-one platforms let specialist teams down, and why companies are turning to micro-apps instead.

Why do companies buy all-in-one platforms?

Because they promise one system for every department, and that pitch is very persuasive in a boardroom.

The corporate world is completely brainwashed by the cult of the “All-in-One” platform. If you read any top-tier consultancy report published in the last five years, it insists that to survive the modern market, your enterprise requires a “unified digital transformation.”

The pitch is intoxicating to an executive board. The Chief Information Officer drops $8 million on a massive, monolithic Human Resources Information System (HRIS) or Enterprise Resource Planning (ERP) suite. The vendor promises a beautiful, interconnected utopia where every department, from global payroll to localised logistics, flows through a single pane of glass. The boardroom applauds. The contract is signed.

Three years later, the implementation is a bloated disaster, the system architecture is rigidly impossible to update, and the actual operators on the ground floor are miserable. The fundamental trap is assuming that enterprise scale requires monolithic software. It doesn’t. Big software excels at generating macro-alignment for the board, but it creates agonising micro-friction for the workers actually running the company.

Where do all-in-one platforms fail?

At the specialist jobs: a platform built for standard processes can’t handle one team’s custom rules, so people export to spreadsheets and do it by hand.

To see the exact point where the monolith fails, you have to walk away from the executive dashboards and look at the desk of a senior compensation architect.

It is 4:00 PM on a Thursday. The architect is tasked with benchmarking and designing a localised Short-Term Incentive (STI) and Sales Incentive Plan for regional commercial managers. The company just deployed that multi-million-dollar HR platform, which is supposed to handle global compensation.

But there is a fatal flaw. The massive software is built for broad standardisation, not deep specificity. It cannot handle the custom tiering logic required to map incentive target percentages across specific job levels. It has no capacity to incorporate margin preservation metrics or calculate net return thresholds unique to this specific sales division.

So, what does the highly paid compensation architect do?

They abandon the $8 million platform. They hit “Export to CSV.” They pull the raw data out of the monolithic system and dump it into a messy, disconnected Excel file—or they quietly spin up a custom, single-page web app just to visualise the compensation structure accurately.

The enterprise software didn’t solve the problem; it just became an overly expensive database that the architect has to bypass to do their actual job.

Why don’t enterprise software vendors fix this?

Because their revenue comes from big contracts with the whole company, not from solving one department’s specific problem.

Why do legacy software companies refuse to fix these granular, department-level problems? Because their financial survival depends on ignoring them.

Venture-backed enterprise SaaS companies are engineered to close CIOs. Their underlying economic model dictates massive Annual Contract Values (ACVs) to justify staggering customer acquisition costs. You cannot pitch a seven-figure enterprise licence by telling the board you built a hyper-specific calculator for custom sales incentive tiering.

To justify the price tag, big tech is forced to build generalised bloatware. They must continuously bolt on generic modules to maintain the illusion of absolute comprehensiveness. They attempt to be everything to everyone. Consequently, they fail at the exact, highly specific friction points that actually dictate how a department functions. They build software for the buyer’s ego, completely abandoning the operator’s reality.

What are micro-apps?

Small apps that each solve one specific problem for one team, without a big platform or a per-user licence around them. A tool that works out one team’s sales incentives is a good example.

Modern, resilient organisations do not need another multi-year “digital transformation” initiative; they need a clean digital decoupling.

The most agile operators and high-margin enterprises are no longer waiting on eighteen-month enterprise IT backlogs or buying six-figure SaaS suites to solve localised friction. Instead of forcing high-output teams to wrestle with clunky, all-in-one software suites, they are systematically deploying fleets of hyperspecialised, single-purpose micro-apps that resolve exact operational bottlenecks without recurring licensing tolls.

You do not commission an entire factory just to drive a single nail. You forge a hammer.

That’s the idea behind 9horsemen: small tools built for the people who use them, not one platform built for everyone.

Our first product, Gallop, is one of those tools, for local service businesses. Describe your business and it builds your website, online booking and business app, with customers, services and staff in one place. If Gallop is missing something your business needs, tell us at hello@9horsemen.com. We’d rather build it into Gallop for everyone than quote you for custom work.

If you’re building software of your own, I write more about it in the other essays and talk about it on the podcast Why Your Software Sucks.