Features vs workflows: why most business software goes unused
Business software is sold as a list of features. A business runs as a chain of steps handed from one person to the next. Most unused software sits in the gap between the two.
Most business software demos follow the same script: a tour of what the product can do. Very few start by asking how work moves through the business today, who touches it, and where it waits.
In brief
- A feature is something software can do. A workflow is the chain of steps and handoffs that turns a request into an outcome, such as an enquiry into a paid invoice.
- Unused features are the norm. Pendo’s 2019 usage analysis found that 80% of features in the average software product are rarely or never used.
- Small businesses lose the most time between features, in handoffs that happen over WhatsApp, phone calls and paper.
- Software built around a workflow is judged by the outcome it moves, such as days to get paid, not by the length of its feature list.
That sounds like a difference of emphasis. We think it decides whether the software gets used at all. At SETITUP LABS it is the first question we ask of any problem, and this note explains why.
What is the difference between a feature and a workflow?
A feature is a capability of a tool: create a quotation, export a report, set a reminder. It is described from the software’s point of view.
A workflow is the sequence of steps, people and decisions that turns a trigger into an outcome. An enquiry becomes a quotation, the quotation is approved, the order is confirmed, the goods are dispatched, an invoice is raised and the payment is collected. Finance teams call that chain order to cash. It is described from the business’s point of view, and it crosses several people and usually several tools.
An operational solution is software that makes a workflow’s outcome faster or more reliable. Its test is whether that outcome improved: fewer days to get paid, fewer wrong dispatches, less time to answer a price enquiry. A product can have every feature on the list and still fail that test.
How much business software actually goes unused?
More than most buyers would guess. Three data points, from different decades and different kinds of software, point the same way.
- 80% of features rarely or never used. Pendo’s 2019 Feature Adoption Report, built from anonymised usage data across 615 of its customers’ subscriptions, found that 80% of features in the average software product are rarely or never used. Pendo estimated that publicly traded cloud software companies had spent up to $29.5 billion building them (Pendo).
- 45% never used. At the XP 2002 conference, Jim Johnson of the Standish Group cited a study that found 45% of features were never used and only 20% were used often or always (Martin Fowler’s conference notes). The figure is quoted widely, but it came from a study of four internal applications, so it is better read as a direction than a law (Mike Cohn).
- 36% of paid licences unused. Zylo’s 2026 SaaS Management Index, based on more than 40 million licences and $75 billion in software spend, found that organisations leave an average of 36% of their SaaS licences unused (Zylo).
None of these studies looks at small Indian businesses, and the exact numbers should not be carried across. The pattern is the useful part: software is bought for everything it can do and then used for a small part of it.
Why feature-led software fails small businesses
The work happens between the features. A quotation is created in the software, but the discount is approved on a WhatsApp call, the order is confirmed in a chat, and the dispatch is noted in a register. Every handoff is a place where the software loses track of the work, and its reports stop describing what actually happened.
Moving between tools costs time as well. In a study published in Harvard Business Review in 2022, researchers followed 137 people in 20 teams at three Fortune 500 companies. They switched between applications about 1,200 times a day and lost just under four hours a week, roughly 9% of their working time, reorienting after each switch (Harvard Business Review). Those were large companies with integrated systems. A small business stitching together a billing app, a spreadsheet and WhatsApp has more seams, not fewer.
Features assume roles the business does not have. An approval feature assumes an approver. A purchasing module assumes a purchase manager. In a business of twelve people, those are all the owner, who has the least time to use the software.
Flexible features hand the design work to the customer. Custom fields, configurable stages and workflow builders sound like a way to fit any business. In practice they give the business the job of designing its own system, which is the job it bought software to avoid.
Buying rewards the feature list. Comparison pages and demos compare what products can do, because that is easy to show. How well a product fits one business’s handoffs is hard to show in thirty minutes, so it rarely decides the sale.
What building around a workflow looks like
This is the method SETITUP LABS works by. A problem only moves to the next stage when the one before it holds.
- Observe. Watch the work itself, not the request for software. Where does a job wait? Who asks whom for what?
- Research. Map the steps, the handoffs and the exceptions, and find the one outcome that matters most, such as days from invoice to payment.
- Validate. Check that the problem recurs across businesses, and that fixing it would be worth paying for, before writing code.
- Build. Build the smallest thing that removes a handoff or a wait, then measure the outcome again.
- Scale. Turn what moved the outcome into a product that other businesses can rely on.
An illustration, not a client case: a distributor’s order-to-cash chain might have eleven steps and seven handoffs, with most of the delay sitting in two of them, waiting for a price approval and waiting for someone to notice an unpaid invoice. A workflow-first product starts with those two waits. A feature-first product starts with a module list.
| Aspect | Feature-led | Workflow-led |
|---|---|---|
| Starting point | A list of capabilities | How work moves through the business today |
| Unit of design | Screens and modules | Steps, handoffs and waits |
| Data entry | In the software, often a second time | Once, where the work already happens |
| Exceptions | Edge cases, handled later | Part of the design from the start |
| Who configures it | The customer | The product, shaped by what was observed |
| Success measure | Features shipped, users onboarded | An outcome, such as days to get paid |
| Typical failure | Bought, partly used, abandoned | Too narrow, if the workflow was mapped badly |
How to choose software that fits the way you work
For a business owner comparing tools, these five checks tell you more than a feature comparison.
- Write your workflow down as steps before you look at any product, and mark every point where work passes from one person to another.
- Ask the vendor to run one of your real exceptions in the demo: a partial delivery, a return, a discount agreed over the phone.
- Count how many times the same information has to be entered. More than once is a warning sign.
- Trial the product with the person who does the work every day, not only with the person who signs off the purchase.
- Pick one outcome you can measure, such as days to collect payment, and measure it before and after.
SETITUP, the lab’s parent company, builds custom business systems on this principle: it connects the spreadsheets, chats and apps a business already runs on, instead of adding one more tool to the pile. SETITUP LABS takes the problems that keep recurring in that work and studies whether they deserve a product of their own.
Frequently asked questions
Why do most software features go unused?
Because features are designed around what software can do, while businesses work in sequences of steps and handoffs. Features that do not fit a real step in someone’s work get ignored. Pendo’s 2019 usage data found that 80% of features in the average software product are rarely or never used.
What is workflow-first software?
Software designed from how work actually moves through a business: the steps, the people who hand work to each other, the waits and the exceptions. It is judged by whether an outcome improves, such as the time to send a quotation or the days to get paid, rather than by how many features it offers.
What is feature bloat?
Feature bloat, also called software bloat or feature creep, is the steady addition of features that most users do not need. It makes software harder to learn and slower to use, and it pulls attention away from the few workflows that matter most.
How can a small business tell whether software will fit its workflow?
Write the workflow down as steps first, then test the software against it. Ask for a demo using one of your real exceptions, count how often data must be entered twice, trial it with the people who do the work, and measure one outcome before and after.
Sources
- Pendo, “Pendo Data Suggests $29.5 Billion in Global Cloud R&D Investment Squandered When Software Features Go Unused”, on the 2019 Feature Adoption Report, 5 February 2019.
- Martin Fowler, “The XP 2002 Conference”.
- Mike Cohn, “Are 64% of Features Really Rarely or Never Used?”, Mountain Goat Software.
- Zylo, “Zylo’s 2026 SaaS Management Index Finds AI-Native App Adoption Is Surging, with ChatGPT Now the Most Expensed App”, 29 January 2026.
- Rohan Narayana Murty, Sandeep Dadlani and Rajath B. Das, “How Much Time and Energy Do We Waste Toggling Between Applications?”, Harvard Business Review, August 2022.
- SETITUP, setitup.in, the lab’s parent company.