Why business apps get bloated, and how to keep yours lean

Most internal apps start with one clear job: take orders, schedule crews, track jobs. Then the requests arrive. A report for finance, a field for one customer, a second approval step, a mobile version, a module for the warehouse. Each one is reasonable on its own. A few years later the app does everything, nobody enjoys using it, the one developer who understood it has left, and the company starts talking about replacing it.

Most features are rarely used

Pendo, which measures how people use software, analyzed usage data from 615 of its customers and found that about 80 percent of features are rarely or never used. In a follow-up, it found that 80 percent of clicks came from as little as 12 percent of features. Those figures come from commercial software built by product teams whose whole job is deciding what to build. Internal apps, built on request with nobody measuring usage, rarely do better.

Every feature costs money forever

Building a feature is a one-time cost. Keeping it is not: it has to be updated, tested, secured, documented and explained to every new hire. Maintenance is generally estimated at 65 to 85 percent of what an application costs over its life. An unused feature is not free; it is a cost with no return, and it makes every future change slower and riskier.

How the build-forever trap happens

• Nobody owns saying no. Requests come from the loudest voice or the most senior person, and the app absorbs them all.
• Adding is easier than removing. Nobody gets credit for deleting a feature, so nothing is ever deleted.
• Progress is measured in features shipped, not in whether the work got faster or fewer mistakes were made.
• There is no usage data, so nobody can see that half the screens are never opened.
• The project never ends. Research by McKinsey and the University of Oxford on more than 5,400 IT projects found that large projects ran 45 percent over budget and delivered 56 percent less value than predicted, and every additional year added about 15 percent to cost overruns.

Bloat kills adoption

Here is what that feels like from the inside: one person, one simple task, in an app that grew for months.

An overloaded app is hard to learn, so people learn the minimum and work around the rest. The spreadsheets come back, data gets entered twice, and the reports stop matching reality. The company is now paying to maintain an app and the workarounds around it. The usual ending is a rewrite or a replacement, and if nothing about how it was built changes, the cycle starts again.

How to keep an app lean

• Start with one workflow. Launch the one thing that saves the most time, done well, and add the next only when the first is in daily use.
• Measure usage from day one. Know which screens and features people actually use, so decisions are based on data, not opinions.
• Give every feature a reason. Before building, write down who asked, what problem it solves and how you will know it worked.
• Keep a "not now" list. Most requests are good ideas for later. Writing them down gets them out of the way without a fight.
• Remove what is not used. Review usage a few times a year and retire features nobody opens. Fewer features means less to maintain and less to learn.
• Design for the newest user. If a new hire cannot complete the main task on their first day without training, the app is too complicated.
• Budget for maintenance up front. Plan for the years after launch, not just the build.

Questions to ask about your current app

• Which features did anyone use last month?
• How long does it take a new hire to learn it?
• Which spreadsheets have grown up around it?
• What would break if the one person who understands it left?
• If you were building it again today, what would you leave out?

If the honest answers are uncomfortable, the fix is rarely another feature. Often it is a smaller app that does the important work well, connected to the systems you already use. Tell us about yours and we will tell you what we would keep, cut and connect. Not sure whether to build at all? Start with custom software vs off-the-shelf.

More guides: How much does a custom app cost? · How much does a B2B ordering portal cost? · NetSuite SuiteCommerce or a custom B2B portal? · ServiceTitan or custom dispatch software? · How much does an AI customer support assistant cost? · Custom software or off-the-shelf? How to decide · What to prepare before you hire an app developer · Adding AI to business software, safely · How to stop taking orders by email · A customer portal on top of NetSuite or QuickBooks · Shopify app or custom build? How to tell · How to forecast inventory for retail stores · Your team can build apps with AI. Here’s what it really costs.