Something has been working. Over the last two years the tools have taken real weight off small businesses: the first draft that used to stall a Tuesday, the research pass, the pile of receipts, the summary of a meeting nobody had time to write up. If you have felt that, you were feeling something measurable.
You may also have quietly wondered whether you were getting the small version of it, because the story around you was much larger. In March 2026 the US Census Bureau put a number on the ordinary version.
The Census Bureau's Household Trends and Outlook Pulse Survey found 56% of US workers had used AI on the job for at least one of eleven measured tasks. Among those who used it in the previous week, a quarter saved less than an hour and 31% saved one to two hours. Counting the 10% who said it saved them no time, about two-thirds of that week's users recovered two hours or less.
What workers used AI for
| Task | Share of US workers |
|---|---|
| Searching for information or technical help | 37% |
| Writing communications or documentation | 32% |
| Generating ideas | 32% |
| Interpreting or summarizing | 31% |
| Administrative work | 27% |
Four of the five sit on the shallow side of the work. On generating ideas, a tool can draft the options and you still choose among them, which is where your taste comes in.
Why one to two hours reads as a disappointment
The number lands badly because of what it's being compared to.
Is the story you are measuring against a measurement, or a projection? Is it describing a firm of your size, with your data, doing your work? Is the person telling it selling something whose value depends on the number being large?
If you got an hour or two back, you're in the same band as nearly a third of the people the Census asked who had used AI that week.
In our reading, an hour or two is about what one handed-over task gives back, and the gain adds up once you hand over a second.
What seventy hours looks like
At an hour and a half a week, you're looking at roughly seventy hours a year per person, the better part of two working weeks.
Seventy hours is a real return and a modest one; it's too small for a hire. You could put it toward the concept work you keep pushing to the evening, or the follow-up calls that decide next quarter, if you decide in advance where the hours go. Without that decision, returned time tends to evaporate, which is the subject of the productivity paradox briefing.
You get the compounding from repetition. Hand over one recurring task this quarter, watch it for a month, then hand over the next one. Four quarters of that is four tasks off the desk, and each one was small enough that nobody had to be convinced.
From time spent on due diligence for new clients or turning over your notes from initial engagements into a full team brief, our firm has saved 4-8 hours of time per week for creative businesses to streamline their workflows and focus on the more important work that contributes to the bottom line.
Related questions
How much time does AI save at work?
The US Census Bureau's March 2026 survey found 56% of US workers had used AI on the job. Among those who used it in the previous week, 25% saved less than an hour and 31% saved one to two hours; with the 10% who saved no time, about two-thirds saved two hours or less.
What do workers use AI for at work?
Mostly shallow tasks. The Census Bureau measured searching for information or technical help at 37%, writing communications or documentation at 32%, generating ideas at 32%, interpreting or summarizing at 31%, and administrative work at 27%.
Is one to two hours a week worth pursuing?
An hour and a half a week is about seventy hours a year for one person. It compounds by repetition, one recurring task at a time, and it stops compounding when somebody quits after the first.
Why is this survey different from vendor research?
It's federal statistical work using a national household sample, so nobody selling AI chose the questions or the framing.
How we read this
If you've been grading your result against the transformation story, you've been grading it against an expectation well above what the Census measured, and the ordinary result, an hour here and ninety minutes there, starts to look like evidence that you did something wrong.
We've argued for small compounding wins from the start. The Census figure puts a size on the ordinary result: an hour or two a week, for 31% of the people who used it that week. We'd read that as a first gain, and a business can stack several. In our reading, the tasks on the Census list sit around the part a client pays for, which is your taste and the perspective you're hired for.
What you can do this week
Count your own, for one week, and count it honestly.
Keep a list open and log the minutes at the moment you finish a task, with the task named. Searching, drafting, summarizing, admin, whatever it was. By the end of the week you'll have your own version of the Census table, drawn from your own business.
The failure in week two is that the small entries never get logged. Twenty minutes here and ten there feel too minor to write down, and they're the entries most likely to go missing from the total. Log each one when you finish it; a list written up at the end of the day comes out low, and you'll draw the wrong conclusion from your own data.
Then pick the single task that appeared most often, and make that one repeatable before you touch anything else.
Working together
Flow State Found works with a limited number of businesses to make their best work their baseline. You tried it, got an hour or two back, and quietly assumed you were doing it wrong. We find the shallow work worth handing over next, so the second handoff happens and the hour compounds.
We take on limited engagements, so it starts with a conversation.
Start a conversationFor Deeper Context
- US Census Bureau, America Counts, AI use at work, drawn from the Household Trends and Outlook Pulse Survey, March 2026 collection, published 11 August 2026
- BCG, AI at Work 2026, fourth annual study, nearly 12,000 workers across 14 markets, cited in the productivity paradox briefing
- National Bureau of Economic Research, Working Paper 34836, February 2026