Where work still runs on spreadsheets, November 2026
Published · By Daily Product Idea · Our methodology
The short answer
Of 487 usable problem signals collected from public communities between 30 August and 5 November 2026, 108 (22%) described a spreadsheet as the workaround. They were most common among people who track many similar records, such as bookkeepers (17 of 25 signals) and recruiters (20 of 38). People with a spreadsheet workaround asked for a tool more than twice as often as others (33% against 14%) but were no more likely to show they were ready to buy (11% against 10%). 22 of the 44 public researched ideas trace back to at least one of these problems.
Key findings
- About one usable problem in five is handled in a spreadsheet. Of 487 usable problem signals collected between 30 August and 5 November 2026, 108 (22%) described a spreadsheet as the workaround.
- Spreadsheet problems sit in specific jobs. Two thirds of the usable problems from r/Bookkeeping (17 of 25) and half of those from r/recruiting (20 of 38) involved a spreadsheet. None of the 31 from Hacker News did.
- People with a spreadsheet workaround ask for a tool more often. 33% of spreadsheet signals included an explicit request for a tool, against 14% of the rest. They were no more likely to show someone ready to buy (11% against 10%).
- They tend to be problems other people share. 97% of spreadsheet signals joined a cluster of repeated problems, against 78% of the rest.
- Half of the published ideas trace back to one. 22 of the 44 public researched ideas were built from a problem cluster that includes at least one spreadsheet signal.
What this report is
This is the second report in the Product Opportunity Index, an editorial series built from the research pipeline behind Daily Product Idea. It counts one thing, the problems people say they handle in a spreadsheet, and compares them with every other usable problem the pipeline found. It describes what one pipeline read. It is not a survey of how businesses work. The method and limits section says exactly what was counted.
A spreadsheet workaround is worth counting because it is evidence of a particular kind. Someone has felt the problem often enough to build something for it, and the columns they chose describe the job. It is also a warning: a spreadsheet is free, flexible and already open, so a product has to beat it, not just exist.
Where spreadsheet workarounds come from
Communities with at least 10 usable signals, ranked by the share involving a spreadsheet. The table counts usable problem signals, not posts read.
| Community | Usable signals | Spreadsheet | Share |
|---|---|---|---|
| r/Bookkeeping | 25 | 17 | 68% |
| r/recruiting | 38 | 20 | 53% |
| r/EtsySellers | 31 | 13 | 42% |
| r/restaurantowners | 14 | 5 | 36% |
| r/projectmanagement | 18 | 5 | 28% |
| dev.to | 79 | 19 | 24% |
| r/QuickBooks | 15 | 3 | 20% |
| r/PropertyManagement | 15 | 3 | 20% |
| r/Accounting | 11 | 2 | 18% |
| r/smallbusiness | 86 | 13 | 15% |
| r/realtors | 15 | 2 | 13% |
| r/hvacadvice | 10 | 1 | 10% |
| r/Teachers | 15 | 1 | 7% |
| r/Insurance | 14 | 0 | 0% |
| r/Dentistry | 11 | 0 | 0% |
| Hacker News | 31 | 0 | 0% |
The pattern follows the work. Bookkeepers, recruiters and marketplace sellers keep records of many similar things (clients, candidates, orders) that their main software does not join up, so a spreadsheet fills the gap. Communities that discuss a profession more generally, or technology in the abstract, rarely mention one. Reddit supplied 89 of the 108 spreadsheet signals and dev.to the other 19.
How spreadsheet problems differ
Each usable signal is tagged with what it shows, and a signal can carry several tags. The table compares the 108 spreadsheet signals with the other 379.
| The post shows | Spreadsheet (108) | Other (379) |
|---|---|---|
| A manual workaround | 68% | 55% |
| An explicit request for a tool | 33% | 14% |
| Information scattered across systems | 27% | 21% |
| A gap in a tool they already use | 27% | 27% |
| A repeated admin task | 25% | 27% |
| Something that could be automated | 20% | 17% |
| Time lost | 16% | 31% |
| Paying a person or service to do it | 12% | 16% |
| Someone looking to buy | 11% | 10% |
| Joined a cluster of repeated problems | 97% | 78% |
Observation
Hypothesis, not a finding
The ideas built from them
Problem signals are grouped into clusters of the same problem, and ideas are drafted from clusters. 37 of the 84 clusters that hold usable signals include at least one spreadsheet signal. The ideas whose clusters lean most heavily on spreadsheet signals:
| Idea | Signals | Spreadsheet |
|---|---|---|
| LedgerLine | 15 | 11 |
| Statement Stack | 15 | 11 |
| Forward & File | 20 | 11 |
| Slab Ledger | 20 | 11 |
| Desk Ledger | 10 | 9 |
| UOM Bridge | 11 | 8 |
They are mostly about getting information into a spreadsheet or out of one. LedgerLine and Forward & File would type supplier invoices and forwarded messages into a sheet the business already keeps. Statement Stack would turn PDF bank statements into importable files. Slab Ledger, Desk Ledger and UOM Bridge would replace a tracking sheet with a purpose-built record. Several keep the spreadsheet rather than replace it, which suits a buyer who trusts the sheet they already have. Each idea page lists the competitors its research found, and for most of these there are several.
What this means for builders
- Look where records are kept, not where problems are discussed. Spreadsheet problems clustered in the communities of people who track many similar things for a living. The guide How to find product ideas on Reddit explains how to read them.
- Treat a request for a tool as a reason to test, not as demand. Spreadsheet owners asked for tools often, but were no more likely to show an intent to buy. The guide How to test whether people will pay covers that step.
- Compete with the spreadsheet as well as with other products. It is free and already open. The guide How to assess the competition counts it as a competitor.
Method and limits
- Period. Problem signals created from 30 August to 5 November 2026. Counts taken on 6 November 2026.
- Usable signals. Signals that passed triage (status accepted or clustered): 487, from 484 distinct posts. Signals rejected at triage or still awaiting it are excluded.
- Spreadsheet signals. Signals carrying the
spreadsheet_workaroundtag. A language model assigns tags when it extracts the signal from the post, from a fixed list, and a signal can carry several. Tags were not re-checked by hand for this report, so treat small differences between rows as noise. - Sources. Public posts from Reddit communities, Hacker News, dev.to, GitHub and a few individual sites, read through their public interfaces. The communities were chosen by the pipeline’s editor, not sampled at random, and the mix changed during the period, so community shares are indicative rather than like-for-like.
- Ideas. An idea counts as tracing back to a spreadsheet signal when the problem cluster its candidate was drafted from holds at least one. Public researched ideas only: illustrative samples are excluded.
- No personal data. Only aggregate counts are reported. No post is quoted, and no poster is identified.
The first report in the series, the Problem Signals Report, autumn 2026, covers the whole research funnel. Every idea, with its sources, scores and tests, is in the ideas archive. Please cite this report as: Daily Product Idea, “Where work still runs on spreadsheets”, Product Opportunity Index, November 2026, dailyproductidea.com.
Related guides
- Problem Signals Report, autumn 2026
Six weeks of community posts, counted: where real problems surface, how people work around them, and why most product ideas are easy to build but hard to differentiate.
- How to find product ideas worth building
Find product ideas by starting from problems people describe in their own work, not from brainstorms. A practical method with real examples, from the research behind Daily Product Idea.
- How to find problems worth solving
A problem is worth solving when specific people repeatedly have it, it costs them something, they already work around it and you can reach them. How to check each, with examples.
- How to evaluate a product idea before you build it
Evaluate a product idea by scoring the evidence rather than your enthusiasm: six dimensions, a written reason for each score, the assumptions it rests on and the cheapest test to run first.
