Featured article / Research report

Stale by Thursday

The hidden cost of manual spreadsheet work, and how to get your week back.

The report at a glance

Download, clean, merge, rebuild. For many teams, the weekly report is a familiar routine—and by the time it is ready, the data has already moved on.

This report brings together survey findings, spreadsheet research, and practical examples to explore the time, errors, and stale information behind manual reporting. It then lays out a practical way to start: measure one recurring task, automate it, and compare the results before moving to the next.

Download the full report

Free PDF · 30 pages · 3.1 MB

Cover of Stale by Thursday, a Nexusflow research report on the hidden cost of manual spreadsheet work.
The complete research, examples, and practical guide in one document.

Inside the report

Where the week goes.
What getting it back could look like.

Two charts from the full report offer a starting point. Explore the bars and payback curves to see the values and assumptions behind them.

How much time is it, really?

Published estimates vary because they measure different tasks and different groups of workers. The figures below should not be added together.

Hours per week · published estimates

Hover over a bar or tap it for source details. Use Tab or ↑ ↓ to explore with a keyboard; Escape dismisses the tooltip.

From page 5. Sources: Parseur/QuestionPro (2025), IDC for Alteryx, and ProcessMaker. Populations and definitions differ; figures are not additive.

When could automation pay back?

Hours saved each week change the payback period. The report explores this relationship using an illustrative value of $50 per hour.

Illustrative line chart showing weeks to pay back falling as weekly hours saved increase, for build costs of $1,500, $3,000, and $6,000, assuming time is valued at $50 per hour.
View larger chart
From page 23. Nexusflow illustration: build cost ÷ (hours saved per week × $50 per hour). Build costs are placeholders, not quotes or promised results.

From research to a practical first step

Start with one recurring chore.

The report recommends timing a task for two weeks, choosing the simplest automation that works, and running the new output alongside the old for several cycles.

The full document includes examples across finance, operations, sales, HR, and facilities, plus an automation ladder, a scoring framework, payback examples, and a 30–60–90 day plan.

About the evidence: The report draws on studies with different populations and definitions, including vendor-commissioned surveys, some older research, and anecdotal online discussions. Illustrations use simplified assumptions. Full sources and limitations appear in the PDF.

More articles

Explore our growing collection of research and process playbooks. Read a summary, preview the charts, and download the complete PDF.