Time management4 min read
230 Hours a Year — What Reordering Tasks Actually Saves a Freelancer
A freelance web designer billing €70 an hour batches her tasks instead of switching constantly. The math shows 230 hours a year freed up — and where that turns into real money and where it doesn't.
- #Zeitmanagement
- #Aufgabenmanagement
- #Produktivität
- #Rechenbeispiel
- #Selbstständige
AI-assisted · editorially reviewed Details
Only 18 percent of employees report having a reliable system for handling their tasks, according to a recent ad-hoc-news analysis. Everyone else works through whatever lands in front of them: an email, a call, an invoice, another email. What that actually costs can be worked out for a single working day.
The setup: a freelance web designer at €70 an hour
Assume a self-employed web designer bills €70 per hour. She manages ongoing client work, writes proposals, issues invoices, and answers calls. On an average day she switches between these task types around 15 times — not because the work demands it, but because the inbox and the phone set the rhythm. Each switch costs time before her focus returns to where it was. For this example, that refocusing cost is set at 6 minutes per switch: an assumption, not a measured figure, but a reasonable one for the jump between creative work and admin.
Fifteen switches at 6 minutes each add up to 90 minutes a day spent just getting back into the task.
What changes with a different order
The core idea behind sequential task ordering isn't working faster, it's arranging tasks differently. Ad-hoc-news puts it this way: "Produktivität weniger durch ein höheres Arbeitstempo entsteht als durch die methodische Anordnung einzelner Tätigkeiten." Applied to the web designer, that means one fixed morning slot for calls, invoices batched into a Friday afternoon block, client emails checked twice a day instead of continuously.
With that batching, the number of switches drops from 15 to 5 a day. That is the central assumption in this calculation, and it won't transfer to every business.
The calculation, step by step
- Switches before: 15 a day. Switches after: 5 a day. Difference: 10 switches
- 10 switches × 6 minutes of refocusing time = 60 minutes saved per day
- 60 minutes equals 1 hour
- At 46 working weeks of 5 days each (a common assumption after subtracting vacation, public holidays, and sick days), that's 230 working days a year
- 230 days × 1 hour = 230 hours a year
At €70 an hour, that comes to 230 × 70 = €16,100. The precise wording matters here: it's 230 hours that no longer disappear into refocusing time. Whether that turns into €16,100 of actual revenue depends on whether there is enough work in the pipeline to fill those hours. The standard formula for labor productivity, output divided by input as Studyflix defines it, doesn't improve just because time was freed up. The denominator shrinks; the numerator stays flat unless someone sells the freed hours.
The sanity check: half as much, twice as much
Not every business can batch its way from 15 switches down to 5. Someone who only gets from 15 to 10 saves five fewer switches, not ten: 5 × 6 = 30 minutes a day, or 115 hours a year. At €70 an hour, that's €8,050 in freed-up time, less than half the original figure, because the math scales linearly with the number of switches avoided.
Run it the other way: assume the cost per switch is 12 minutes rather than 6, because recovering focus after a technical problem simply takes longer. With the same 10 switches avoided, that produces 460 hours and €32,200. The spread between €8,050 and €32,200 makes one thing clear: the refocusing cost per switch is the lever the whole calculation hangs on, and in this example it's estimated, not measured.
Where the math breaks down
For work that genuinely demands an immediate response (a client whose site goes down the day before a trade show, say), batching doesn't work. Someone who processes every inquiry in an afternoon block risks losing that client. The method suits routine tasks, not emergencies.
For teams rather than solo operators, the math changes again. Coordination overhead between several people adds a cost that this formula doesn't capture. How that overhead shows up in small businesses is covered in more depth in Was ein Kleinbetrieb gegen die Arbeit über die Arbeit tun kann.
One more caution belongs here. A freshly built time-block system feels productive immediately, even when the actual work stays untouched. Die Tagespost describes the effect like this: "Ein neu eingerichteter Kalender liefert dagegen sofort ein sichtbares Resultat." Colorful calendar blocks are no proof that fewer switches are happening. The only real evidence is fewer open items left at the end of the day than at the start.
Anyone who wants to pin down their own time sinks before reordering anything will find a closer look at which methods actually hold up in Was sich beim Zeitmanagement für Kleinbetriebe 2026 wirklich verändert hat.
For many small businesses, some of those 15 daily interruptions don't come from their own working habits at all — they come from the website. A contact form that sends no confirmation. A load time slow enough that customers pick up the phone instead of filling in the form. Small causes. Enough to generate extra calls, though. The free website check from Log-System Development reviews speed and SEO in a few minutes and shows whether that's where some of the avoidable back-and-forth originates. For businesses that want the site, an AI integration, or an app rebuilt after that, Log-System Development works directly with developers, with no agency layer in between.