We searched 1M+ documented complaints for the words people use when they describe doing work by hand. 20,000+ of them matched. Here is where the manual work actually lives.
The question comes up in almost the same words every time an experienced founder starts looking for their next thing. One version, posted tor/microsaas, reads: “what niche are you seeing that’s still running on spreadsheets?” Another, fromr/ycombinator, is blunter: “Should I just start knocking on local business doors or cold-emailing until someone complains about a spreadsheet?”
It is a good instinct and a bad search strategy. The instinct is right because a spreadsheet is the clearest possible evidence that a workflow exists, matters enough to track, and has no software that fits it. The search strategy is wrong because knocking on doors samples a dozen businesses when the answer is already written down several thousand times.
So we searched for it. We took the phrases people actually use when they describe doing work by hand, and ran them across every complaint corpus we index: Reddit, Capterra reviews, Capterra feature gaps, Capterra opportunity records, G2 insights, App Store reviews and Upwork job posts. As of September 2026, 20,000+ documented complaints contain the literal language of manual work. This is what they say and where they come from.
The phrase is used loosely, and the looseness hides the opportunity. There are three distinct situations people describe with the same words, and only two of them are worth building for.
The first is no software at all. A whole workflow lives in one shared file. This is rarer than founders assume and is concentrated in small operators, trades and volunteer-run organisations, the population profiled in small business ideas for 2026 and boring business ideas.
The second is software plus a spreadsheet bridge. The team bought a tool, the tool does most of the job, and someone exports to Excel every week to do the part it cannot. This is by far the most common pattern in our data, and it is the most attractive, because the budget question is already settled.
The third is a spreadsheet used correctly. Ad hoc analysis, one-off modelling, a process that changes monthly. Replacing this makes things worse. We cover it in when a spreadsheet is the right answer, and the broader failure mode in common validation pitfalls.
We searched every indexed complaint field for a fixed pattern of manual-work language: spreadsheet, excel, google sheet, by hand, manually, copy and paste, and pen and paper. The pattern is deliberately narrow. We excluded the bare word manual, because it matches product documentation, and we excluded whiteboard, because it matches design tooling discussion far more often than it matches a workflow complaint.
Every number below comes from a live query run against the production database on September 10, 2026. All counts are rounded down and marked with a plus, which is our standing convention for corpus figures, so “5,900+” means the exact figure was above 5,900 on that date and will be higher now.
| Source | Evidence type | Matched complaints | Limitation |
|---|---|---|---|
| Capterra feature gaps | Structured gap records derived from B2B reviews | 9,400+ | Derived from reviews, so it inherits Capterra’s alphabetical coverage decay |
| Capterra pain points | Scored complaints with severity and opportunity ratings | 5,900+ | Category coverage stops mid-alphabet, see coverage honesty below |
| App Store reviews | Consumer app reviews, filtered to 3 stars and below | 3,100+ | Consumer skew; a 1-star review over-represents anger relative to cost |
| Capterra opportunity records | Analyst-style opportunity write-ups with supporting quotes | 750+ | Second-order: generated from pain points, not independent evidence |
| G2 processed insights | Sentiment-tagged B2B software insights | 690+ | Summarised rather than verbatim, so phrasing is smoothed |
| Upwork job pain points | Paid job postings, i.e. committed budget | 310+ | Budget and hourly-rate columns are unpopulated, so no dollar figures |
| Reddit pain points | Unfiltered practitioner complaints with subreddit attribution | 140+ | Smallest stream; subreddit self-selection is strong |
| Swiper validation cards | Human swipe validation layer | 7,300+ | Derived from the sources above, so excluded from the 20,000+ headline to avoid double counting |
Adding the seven primary streams gives more than 20,000 matched complaints. The eighth row in the table above, the swipe validation layer, is deliberately excluded from that headline because those cards are generated from the same underlying records. Counting them would inflate the figure by roughly a third for no additional evidence. We flag this because most published market-size claims do exactly that and do not say so.
For context on the size of the underlying corpus these matches were drawn from, see our comparison of customer complaint databases and the 2026 state of SaaS pain points.
Ranking by average opportunity score rather than raw volume corrects for the fact that big categories generate more of everything. Opportunity score is our internal 1 to 5 rating combining pain intensity, market demand and competitive gap.
| Category | Matched complaints | Avg severity | Avg opportunity |
|---|---|---|---|
| Construction Accounting | 29 | 3.94 | 4.27 |
| Applicant Tracking | 56 | 3.89 | 4.10 |
| HR Analytics | 31 | 3.85 | 4.05 |
| Certification Tracking | 40 | 3.98 | 4.03 |
| Asset Tracking | 64 | 4.00 | 4.02 |
| Course Authoring | 37 | 3.89 | 4.02 |
| B2B eCommerce Platform | 32 | 4.06 | 4.02 |
| App Building | 29 | 4.08 | 3.99 |
| Appointment Reminder | 36 | 3.86 | 3.98 |
| 360 Degree Feedback | 55 | 3.81 | 3.96 |
| Assessment | 41 | 3.87 | 3.96 |
| Donation Management | 33 | 3.93 | 3.96 |
| Auto Dialer | 28 | 4.01 | 3.96 |
| Courier | 40 | 3.83 | 3.95 |
| Admissions | 32 | 3.98 | 3.95 |
| Construction Estimating | 42 | 3.94 | 3.94 |
| Association Management | 40 | 3.92 | 3.94 |
| Agile Project Management | 46 | 3.86 | 3.93 |
| Audit | 61 | 3.96 | 3.90 |
The spread is narrow, between 3.90 and 4.27, and that is itself the finding. Manual-work complaints score consistently high wherever they appear. The differentiator between these categories is not whether the pain is real, it is whether you can reach the buyer, which we come back to in the distribution problem. For the adjacent question of which niches are worth entering at all, see how to find a profitable niche and the most profitable SaaS niches.
Most idea signals are speculative. A trend report tells you a market is growing. A keyword tool tells you people search a phrase. Neither tells you that a specific person is currently doing a specific task badly.
A spreadsheet complaint does. It names the workflow, confirms the person performs it regularly enough to resent it, and proves no existing product covers it, because if one did they would be using it. That is three validation steps in one sentence. It is why we treat this pattern as a first-class signal alongside the ones described in multi-signal startup idea validation and customer pain point analysis.
The commenter onr/microsaaswho wrote “when your competition is a spreadsheet, your sales pitch is basically ‘stop doing this by hand.’ easiest sell in the world” is describing the same property. The pitch requires no market education.
Asset tracking carries 64 matched complaints, the highest count of any category clearing our threshold, at an average severity of 4.00. The recurring shape is an organisation that bought asset software, discovered it does not handle their particular asset type or audit cadence, and maintains a parallel spreadsheet.
One Capterra reviewer, an accounting manager at a wholesale business, put the general version plainly: “Most reports are hard to read and edit post-export to Excel.” Another, an associate accountant in electrical manufacturing, wrote that “the system’s reports require extensive workarounds to get usable data.”
Asset tracking also overlaps heavily with B2B business ideas. If you are looking at this category, cross-reference it against niche SaaS opportunities by industry and internal tool ideas worth building.
Audit shows 61 matched complaints at 3.96 severity. Compliance work is the archetypal spreadsheet domain, because requirements change by jurisdiction and by year, and software that hard-codes last year’s rules is immediately wrong.
A G2 insight in the sustainability-tracking space captures the trap exactly: current tools “excel in sustainability tracking but lack detailed reporting, customization options, and industry-specific features that prevent full compliance with evolving environmental regulations.” The spreadsheet survives because it is the only thing that can be reshaped as fast as the rules.
That also makes it a hard category for a first-time solo build. See legacy system wrapper business ideas for the adjacent, more tractable version of this opportunity.
Construction Accounting posts the highest average opportunity score in the entire matched set at 4.27, with Construction Estimating close behind at 3.94 across 42 complaints. The Upwork data is the tell here, because it shows the work being paid for by hand right now.
One posting describes it directly: “Performing material takeoffs manually from drawings is a tedious and time-consuming process that can lead to errors. This inefficiency can impact project timelines and costs.” Another: “The process of creating estimates using Xactimate is often done manually, which can be time-consuming and prone to errors. This includes comparing estimates, analyzing data, and ensuring accuracy in documentation.”
A third names the CAD version of the same problem: “The process of creating and modifying CAD drawings manually can be labor-intensive and prone to errors. Automating these tasks can save significant time and reduce the risk of mistakes.”
Construction shows up repeatedly in niche SaaS ideas and vertical AI SaaS ideas for the same reason. It is also one of the categories where the operator population is large and the software population is small, which is the supply-side view covered in SaaS market saturation in 2026.
Applicant Tracking scores 4.10 on opportunity across 56 complaints, which is unusual for a category with well-funded incumbents. The complaints are not about the absence of software but about the seam between it and everything else.
A Reddit thread from r/managers asks the question in its purest form: “Staff leave planner. Which leave management platform are you using for employees, or are you still managing it in Excel?” The framing assumes Excel is a live option, which for many teams it is.
One Capterra reviewer in education management described the downstream cost: “The system was slow and difficult to use, leading to double registrations that my team had to sort out manually.” Another, a registration co-coordinator, said “in order to add a registration on the admin side, it would take me like 15 minutes due to being slow.”
Certification Tracking sits at 4.03 opportunity across 40 complaints, with the highest severity of the top five at 3.98. This is a classic spreadsheet-with-a-deadline problem: credentials expire, someone has to notice, and the noticing is manual.
Certification tracking is a good first build for a solo operator, in the sense described in simple SaaS ideas for solo developers and what to build as a solo developer. It pairs naturally with the pattern described in single-feature micro SaaS ideas, because the entire product can be one table and one reminder engine.
Association Management shows 40 complaints at 3.94 opportunity. Member organisations run on volunteer labour and inherited files, and the handover between one volunteer treasurer and the next is usually a spreadsheet attached to an email.
One Capterra reviewer, a president in recreational services, described the accounting seam: “The only con I would have to say is the programs inability to transfer over reg pay hours separate from overtime pay hours into Quickbooks Online.” The workaround for that is always a spreadsheet.
Donation Management posts 33 complaints at 3.96 opportunity. Nonprofits are the most spreadsheet-dependent organisation type in the corpus, which matches what the supply side shows: nonprofit fundraising is one of the least software-dense categories on Stripe’s public directory.
Cross-read this with service business ideas and B2B SaaS ideas for 2026.
Courier scores 3.95 across 40 complaints. Routing, proof of delivery and driver settlement are three separate workflows that small operators typically run in one file.
The r/dropshipping version of this complaint generalises well: “I’m curious, how do you all stay on top of these updates? Do you manually check supplier websites, rely on email notifications, or use any automation tools?”
Admissions carries 32 complaints at 3.95 opportunity and 3.98 severity. The pattern is seasonal load: a process that runs hard for eight weeks a year is exactly the kind of thing nobody buys dedicated software for, and exactly the kind of thing that breaks when done by hand.
A registration assistant in education management described the failure mode: “When we tried to save changes, the system often wouldn’t take our input, leading to significant delays and frustration for our attendees.”
Appointment Reminder shows 36 complaints at 3.98 opportunity. This category illustrates the double-booking cost that recurs throughout hospitality and services.
Two Capterra reviewers in property management name it precisely. One: “If a guest books online, we can’t rely on it showing up unless we do it manually.” Another: “I have had significant issues with double bookings due to lag in updates to channel managers.” A third quantifies the lag: “Guest Point can take up to 10-20 mins to send updates to your channel manager. It risks double bookings.”
A double booking has a direct, obvious dollar cost, which is why complaints of this shape convert into willingness to pay faster than most. Compare with real estate SaaS ideas.
Auto Dialer carries 28 complaints at the second-highest severity in the set, 4.01. Sales operations teams stitch dialers to CRMs with exports, and the export is where the data goes stale.
See also sales software limitations in 2026 and the best CRM for SaaS startups.
Agile Project Management shows 46 complaints at 3.93. The irony is heavy: teams buy project software and then track the project in a spreadsheet because the software models a process they do not follow.
An r/devops thread describes the environment-booking version: “When devs, testers, or even sales people share the same environments, collisions happen. We’ve tried to book an environment in a Spreadsheet / Wiki for a certain timeframe, but still some problems happen.”
Related reading: visual AI project management for indie hackers.
360 Degree Feedback shows 55 complaints and HR Analytics 31, at 3.96 and 4.05 opportunity respectively. HR is a spreadsheet stronghold because the data is sensitive, the process is annual, and the outputs are bespoke.
One G2 insight names the general integration failure: “The primary pain points revolve around high cost for small businesses, missing desired features like integration with Google Sheets, and user interface usability issues.”
Course Authoring posts 37 complaints at 4.02. The complaints cluster on export and formatting, which is the tell for a tool that produces artifacts someone else has to finish.
A proposals and data analyst on Capterra: “Images don’t embed properly and I often have to fix formatting manually after an export, it’s so time-consuming.” A proposal writer, more bluntly: “I dread the formatting stage after exporting, it feels like wasted time redoing work.”
B2B eCommerce Platform shows 32 complaints at the highest severity in the top ten, 4.06. Wholesale ordering still runs on emailed spreadsheets in a large share of the market, and the complaints are about the reconciliation that follows.
The 3,100+ matched App Store reviews are the least commercial and the most honest. Consumers say what B2B reviewers will not.
One review, on a meal-planning app: “Not paying for a meal planner that has no beneficial features. Can create better, customized menus using a simple web search and a spreadsheet.” That is a customer explicitly comparing a paid product to a free spreadsheet and choosing the spreadsheet.
Another, on an onboarding flow: “This was the most tedious 5 minutes of my life and it made me realise pen and paper will work best.” A third, on a hardware companion app: “I have to manually input the info and the app freezes when I press done every time.” And the sharpest: “The diabolical greed of the developers to monetize a glorified spreadsheet UI.”
That last one is the warning attached to this whole article. A thin wrapper over a grid is not a product. See how to find SaaS ideas from negative reviews and how to analyse App Store reviews.
A review is an opinion. A job post is a budget. The 310+ matched Upwork postings are the only stream in this analysis where someone has already decided to spend money on the manual version of the task.
“Many businesses struggle with the time-consuming and error-prone process of manually compiling data from multiple sources into reports. This often leads to inaccuracies and delays in decision-making.” “Creating dynamic and interactive dashboards manually is labor-intensive and often results in outdated or inaccurate visualizations.” “Businesses often need to gather data from various websites or platforms, which can be time-consuming and prone to human error when done manually.”
One important caveat: the budget and hourly-rate columns in our Upwork data are unpopulated, so we never quote dollar figures from this source. Frequency of the pain point is the usable signal, not price. More on using this source properly in validating SaaS demand with Upwork jobs and the state of freelance demand.
G2’s 690+ matched insights skew toward a single shape: the product does its job but does not talk to the next thing.
“Key pain points include the lack of integration with Google Sheets and other Google products, making collaboration difficult.” “The primary pain point identified is the inconsistency of email synchronization, leading to disruptions in users’ workflow due to having to manually restart the application.” “Users find ProofStuff’s dashboard vague and feature-limited, especially for handling complex spreadsheets.”
And a subtle one worth sitting with: “Users have identified critical usability issues such as a steep learning curve, complexity in usage, and missing core features traditionally found in spreadsheets.” That is a product losing to Excel on Excel’s own terms.
If you read enough of these, one phrase recurs more than any other: export to Excel. It is the single most reliable indicator of an unfinished workflow, because it marks the exact point where the software gave up and handed the job back to a person.
When you find it, the opportunity is almost never “build a better version of the product they already have.” It is “build the thing they do in Excel after they export.” That is a much smaller product and a much easier sale.
One reason to trust the pattern is that it does not respect industry boundaries. Pull the matched complaints without filtering by category and the same sentence appears in law, finance, analytics, healthcare and logistics, written by people who have nothing in common except the workaround.
From r/lawfirm: “In LEAP, we have to post all ID check fees and search-pack fees manually, one matter at a time. No way to bulk-import or automate cost postings? Anyone have workarounds?”
From r/consumerfinance: “Need a smarter way to handle all my loans without manually juggling spreadsheets and calculators.”
From r/trading: “One thing that’s always frustrated me is how much time it takes to clean raw TOS strategy report CSVs into usable OHLCV format. Excel PowerQuery, even PowerShell. None of it feels efficient.”
From r/PowerBI, a complaint from inside a business-intelligence tool, which is the most telling place to find one: “I want the full data table produced from the semantic model to be linked into Excel with scheduled refresh but only get pivot table option. Does anyone do this process?”
The B2B review corpus repeats it in academic and research tooling. One research associate professor on Capterra: “Manually correcting in-text citations got old quickly, especially during dissertation writing.” A PhD student: “References update would fail when logged into multiple accounts, which made bibliography maintenance frustrating.” A research associate, more forgiving: “Sometimes the citation is imported incorrectly, but given the multitude of formats that papers come in these days I find that a forgivable fault.”
On G2, the file-conversion version: “Key issues include high costs for premium features, inefficiency in converting certain file types (like Excel), limited OCR accuracy, user interface usability concerns, and overall reliability during usage.”
On the App Store, the sync version: “Most of the time it does not sync with my watch or health data. Very frustrating to not be able to see my calories burned or heart rate during my workouts and to have to go back and manually add my workouts through the apple health app.” And the terse version: “unable to create a trip manually. AI function takes forever.”
On Upwork, the recurring-labour version: “Many businesses struggle with the time-consuming process of manually scheduling and posting content across multiple social media platforms.” And: “Ensuring high-quality recordings with no background noise and proper emotion is a time-consuming and error-prone process when done manually.”
Nine sources, nine industries, one sentence. That cross-vertical consistency is why we treat manual-work language as a structural signal rather than a quirk of one category. It is also why the method transfers: see how to use AI for market research and the SaaS market research guide.
Sorting the corpus by what the complaint is actually about produces four repeating shapes. Knowing which one you are looking at determines what you build.
Double entry. The same data typed into two systems. Fix: a connector.
Export and repair. Data leaves clean and arrives broken. Fix: a formatter or a report builder.
Watch and remind. A human is the alerting system. Fix: a rules engine.
Reconcile. Two sources disagree and someone diffs them by hand. Fix: a matching tool.
All four are small enough for one person to ship. That is the argument made at length in micro SaaS with no API dependency and launching a micro SaaS in a weekend.
Severity measures how much the complaint hurts. Opportunity combines pain intensity, market demand and competitive gap. They diverge in useful ways.
App Building scores 4.08 severity but only 3.99 opportunity, because the competitive gap is small: plenty of companies already compete there. Construction Accounting scores lower severity at 3.94 but the highest opportunity at 4.27, because almost nobody is serving it. When the two disagree, follow opportunity. See how the opportunity score is calculated.
Founders treat a free incumbent as a pricing problem. It is the opposite. A spreadsheet has no vendor, no contract, no champion and no switching cost to defend. Nobody in the organisation will fight to keep it.
What it does have is zero marginal cost, which means your pricing has to be justified in time rather than in features. The correct anchor is the hours the manual process consumes, not what comparable software charges. Practical guidance in how to price a micro SaaS and SaaS pricing strategies for 2026.
Every category in the table above shares a weakness: the buyers are hard to reach online. Association treasurers, courier dispatchers and certification administrators do not read startup newsletters.
This is the real reason these categories stay open, and it is a better filter than pain score. Before committing, answer the question oner/startupscommenter posed: “If i asked you to find just 1 potential customer for the product online, how long would it take?” If the answer is more than an hour, the distribution problem outranks the product problem. See how to get your first customer and where to launch your startup.
Not every spreadsheet is a market. Leave these alone: processes that change monthly, one-off analysis, anything where the flexibility of a blank grid is the actual feature, and any team small enough that coordination costs nothing.
The r/EntrepreneurRideAlong question “At what point did your startup outgrow the basic bank account and spreadsheet setup?” contains the right test. There is a threshold, and below it the spreadsheet wins on merit.
The European Spreadsheet Risks Interest Group maintains a catalogue of publicly reported spreadsheet errors running to dozens of documented incidents. Several are instructive about where the money is.
Norway’s sovereign wealth fund, managing roughly $1.5 trillion, reported losing about $92 million on a benchmark calculation because an incorrect date was entered. The UKPrudential Regulation Authorityfined Standard Chartered Bank £46,550,000 over regulatory reporting failures, and fined Metro Bank £5,376,000 for failings in reporting governance and controls. The Police Service of Northern Ireland suffered a breach exposing personal data of 10,799 staff.
The most widely cited case is documented by the BBC: Public Health England lost nearly 16,000 COVID-19 test results because developers used the obsolete XLS format, which caps a sheet at roughly 65,000 rows rather than the1,048,576 rows modern Excel supports. In practice each template held about 1,400 cases, and everything past that was silently dropped.
These are the kinds of failure that make a category buy software after years of resisting it, which is worth watching for in business pain points. The teaching point is not that spreadsheets are bad. It is that silent failure is the characteristic spreadsheet risk. Software that makes an error visible is selling something a spreadsheet structurally cannot offer.
Most of these categories already contain a vendor who attempted the full platform. The complaints in our corpus are the residue of those attempts. Reading them tells you which part of the job the platform could not absorb, and that part is usually the one that varies most between customers.
This is why the winning wedge is rarely a competing platform. Related: competitive landscape analysis and the most underserved software markets.
A feature request describes something missing inside the product. A workflow gap describes work happening outside the product. Only the second reliably supports a standalone tool, because the first will eventually be built by the incumbent.
The linguistic test is simple. Feature requests say “it should let me.” Workflow gaps say “so I have to.” Search for the second phrasing. More on this in market gap analysis and the most requested software features.
There is no credible dollar figure for “the spreadsheet replacement market,” and any article quoting one is generating it rather than measuring it. What is measurable is relative: how many complaints, at what severity, in which category, from how many distinct sources.
Use that as a ranking signal and do your sizing bottom-up from a real customer count, then sanity-check it against revenue benchmarks by category and TrustMRR revenue benchmarks. See how to calculate market size for a startup.
Across every category above, the tractable entry point is the same. Find the single artifact the spreadsheet produces, the weekly report, the reconciliation, the expiry list, and produce that artifact automatically. Nothing else.
This keeps the build inside one person’s capacity and makes the value obvious on day one. Compare with single-feature micro SaaS ideas and getting to the first $1K MRR.
Start with the import. Every one of these buyers has an existing file, and the product that reads their file on the first screen wins the demo. The product that asks them to re-enter six months of data loses, regardless of how good the rest is.
Guidance on the build itself: how to build a SaaS in 2026, building with Next.js, Supabase and Stripe, and the micro SaaS build guide.
The buyers in these categories congregate in trade associations, licensing bodies and regional Facebook groups, not on Product Hunt. Budget more time for finding them than for building. Practical routes are covered in how to get customers for a startup, getting your first 100 SaaS users, and finding your first SaaS customers.
Complaint volume is the demand side. The other half of the question is how much software already exists in the category, which we measure separately against 30,000+ companies listed onStripe’s public customer directory. A category with heavy manual-work complaints and low software density is the strongest configuration.
That analysis lives in SaaS market saturation in 2026, the Stripe Index database, and companies using Stripe. Read this article for demand and that one for supply.
This is the most important caveat in the article and we put it in its own section because burying it would make the ranking misleading.
Our Capterra scrape stopped part-way through the alphabet. Matched manual-work complaints by the first letter of the category name run: C 1,522, A 1,339, B 618, D 492, E 382, F 270, I 202, M 204, H 190, L 181, G 142, K 53, O 49, N 48, P 45, J 43, S 43, V 21, R 15, T 14, W 6. The letters Q, U, X, Y and Z return nothing at all.
That is a coverage artifact, not a fact about the world. There is no reason Warehouse Management or Time Tracking should have a twentieth the manual-work complaints of Asset Tracking. If a category you care about starts with a late letter, treat a thin result as “unknown,” not “no problem here,” and verify it directly.
| Letter | Categories | Companies | Matched complaints |
|---|---|---|---|
| C | 114 | 1,287 | 1,522 |
| A | 65 | 1,138 | 1,339 |
| B | 37 | 527 | 618 |
| D | 61 | 426 | 492 |
| E | 52 | 330 | 382 |
| M | 50 | 170 | 204 |
| L | 37 | 155 | 181 |
| S | 15 | 36 | 43 |
| R | 6 | 13 | 15 |
| T | 6 | 14 | 14 |
| W | 2 | 6 | 6 |
| Q, U, X, Y, Z | 0 | 0 | 0 |
Keyword matching is not semantic. A complaint that describes manual work without using our seven phrases is invisible to this analysis. The true figure is higher than 20,000, not lower.
False positives exist. “Excel” is also an English verb, and some G2 insights matched on phrases like “current solutions excel at.” We estimate this at a small single-digit percentage of the G2 stream and have left it in rather than hand-filter, so the number stays reproducible.
Sources are not equally weighted. A Capterra feature gap and a Reddit comment are not equivalent evidence, but both count as one in the total.
Swipe cards are excluded. As noted, the 7,300+ matched validation cards are derived from the primary sources and are not in the headline figure.
Consumer and B2B are mixed. App Store reviews describe consumer frustration; Capterra and G2 describe purchased business software. They answer different questions.
You do not need our database to use the method. Search any complaint corpus you can reach for the seven phrases, group the hits by category, and read a hundred of them. The pattern will be obvious within an hour.
If you want the version that spans all seven sources at once, that is what BigIdeasDB is for. Start with the pain points explorer, then use discover to filter by category and severity. The complaint analysis platform guide and how to find problems worth solving walk through the workflow. If you work inside an AI assistant, our MCP server exposes the same corpus directly.
Filter by category, severity and opportunity score across Reddit, Capterra, G2, the App Store and Upwork in one query. No guessing which industry still uses spreadsheets.
Start searching →Asset tracking, audit, construction estimating and accounting, applicant tracking, certification tracking, association management, donation management, courier and last-mile logistics, admissions, and 360-degree feedback carry the highest density of documented spreadsheet and manual-work complaints in our corpus, as of September 2026.
Search complaint corpora for the literal words people use: spreadsheet, Excel, Google Sheets, by hand, manually, copy and paste, pen and paper. Those phrases appear in 20,000+ documented complaints across Capterra, G2, the App Store, Upwork and Reddit, and each one names a workflow someone already resents.
It is one of the strongest starting points, because the buyer already performs the workflow and needs no education. The risk is not demand. It is that a spreadsheet is free, infinitely flexible and already integrated into how the team works, so you have to beat free on time saved rather than on features.
Because it costs nothing extra, requires no procurement, adapts instantly to a process that changes, and is already understood by everyone. Purpose-built software wins only when the workflow is stable enough to encode and painful enough that the manual version has a visible cost.
Re-entering data that already exists somewhere else. The dominant shape is not the spreadsheet itself but the manual bridge between two systems, described as exporting to Excel, fixing the formatting, and pasting it back.
There is no single credible figure, and any specific number should be treated with suspicion. What is measurable is the volume and severity of documented complaints per category. Use complaint density as a relative signal, not a market size estimate.
No. Most come from people who already bought software and still export to Excel. That is a better signal than an empty category, because budget is proven and the complaint identifies exactly which part of the workflow the incumbent left unfinished.
A feature request asks for something inside the product. A spreadsheet complaint describes work happening outside it. The second is a workflow gap and far more likely to support a standalone tool.
Ones where the spreadsheet is genuinely right: ad hoc analysis, one-off modelling, processes that change every month, and anything where the flexibility of a blank grid is the point.
Look for a complaint naming a time cost, a headcount, or an error with a consequence. Double entry, double bookings, and redoing work after an export all carry a cost the buyer already feels.
Documented cases include Norway’s sovereign wealth fund losing roughly $92 million to a single incorrect date, and Public Health England losing nearly 16,000 COVID-19 test results to an obsolete file format capped at about 65,000 rows. Both are catalogued by the European Spreadsheet Risks Interest Group.
You can, but only by substituting documented evidence for lived experience. Reading several hundred complaints is a reasonable proxy for the first month of customer discovery, not a replacement for talking to operators. See validating an idea in an industry you do not know.
Capterra and G2 show where existing software stops. App Store reviews show consumer-grade frustration. Upwork job posts show work someone is paying a human to do right now. Reddit shows the unfiltered version.
Because a job post is money already committed. When someone hires a freelancer to compile a report by hand every month, that recurring spend is the budget a tool would replace.
Counts were re-run against the live database on September 10, 2026. The corpus grows continuously, so totals rise over time while relative ranking between categories moves slowly.
Capterra category coverage decays alphabetically. Categories starting with A and C carry more than a thousand matched complaints each; R, T and W carry fewer than twenty, and Q, U, X, Y and Z are absent. A thin late-alphabet result means thin coverage, not an absent problem.
BigIdeasDB indexes the corpus across Reddit, Capterra, G2, the App Store and Upwork, and lets you filter by category, severity and opportunity score. Start at the pain points explorer or discover. For further reading, see business ideas that solve real problems, problem-solving app ideas, micro SaaS ideas for 2026, low competition SaaS ideas, uncovering real-world problems, turning problems into products, finding problems to solve, daily frustrations that need an app, mining Capterra reviews for SaaS ideas, turning G2 reviews into SaaS ideas, small business software pain points, customer review analysis, how to find startup ideas, tools to find customer pain points, how to find SaaS ideas, and the SaaS idea validation tool.
BigIdeasDB Research. (2026). Industries Still Running on Spreadsheets (2026 Data). BigIdeasDB. Retrieved from https://bigideasdb.com/industries-still-running-on-spreadsheets