---
title: "When Excel Becomes a Full-Time Job"
lang: "en"
slug: "when-excel-becomes-a-full-time-job"
date: "2026-08-03"
category: "other"
featured_image: "/assets/img/excel-full-time-job.jpg"
featured_image_alt: "Close-up of endless rows of numbers in a spreadsheet — when routine work in Excel grows into an entire system"
description: "Excel is brilliant for ad hoc tasks — but once a spreadsheet has a weekly time slot, multiple users, and rituals of its own, it has become a system. And systems can be built better. Here's how to calculate what your spreadsheet really costs."
---

It's Monday evening. Somewhere, a volunteer at an NGO sits down with a CSV export from the bank and a spreadsheet with fourteen tabs. The next three hours go to matching payments against the donor list, fixing the formula another volunteer accidentally overwrote last week, and copying the totals into *the other* spreadsheet — the one the treasurer needs. She has done this every Monday for four years.

She's not alone. Multiply that scene by every association, club, small business, and department inside larger companies running fixed routines in Excel, and you have one of the biggest hidden time sinks in working life.

## Let's Start by Defending Excel

This is not an anti-Excel post. Excel is one of the finest pieces of software ever written. If you need to analyse a dataset once, make a quick estimate, test an idea, or build a budget for the next board meeting — Excel is unbeatable. Open, type, calculate, done. No developer, no waiting, no requirements document.

Excel is brilliant for **ad hoc tasks**. The trouble starts when the task stops being ad hoc — and that happens gradually, without anyone ever deciding it.

## The Tipping Point: When Has a Spreadsheet Become a System?

There is a tipping point where a spreadsheet has quietly grown from "a calculation" into "a system". Do you recognise any of these signs?

<div class="ait-feature-grid">
  <div class="ait-feature-card">
    <div class="ait-feature-card__icon blue">
      <svg viewBox="0 0 24 24"><rect x="3" y="4" width="18" height="18" rx="2" ry="2"/><line x1="16" y1="2" x2="16" y2="6"/><line x1="8" y1="2" x2="8" y2="6"/><line x1="3" y1="10" x2="21" y2="10"/></svg>
    </div>
    <h3>It has a fixed time slot</h3>
    <p>Every Monday. Every month-end. Every quarter. When a spreadsheet appears in the calendar, it is no longer a calculation — it is an operational task.</p>
  </div>
  <div class="ait-feature-card">
    <div class="ait-feature-card__icon green">
      <svg viewBox="0 0 24 24"><path d="M17 21v-2a4 4 0 0 0-4-4H5a4 4 0 0 0-4 4v2"/><circle cx="9" cy="7" r="4"/><path d="M23 21v-2a4 4 0 0 0-3-3.87"/><path d="M16 3.13a4 4 0 0 1 0 7.75"/></svg>
    </div>
    <h3>Several people use it</h3>
    <p>Versions fly around by email. The file is called <em>final_v3_REAL.xlsx</em>. Two people have edited separate copies, and now someone has to merge them.</p>
  </div>
  <div class="ait-feature-card">
    <div class="ait-feature-card__icon purple">
      <svg viewBox="0 0 24 24"><polyline points="17 1 21 5 17 9"/><path d="M3 11V9a4 4 0 0 1 4-4h14"/><polyline points="7 23 3 19 7 15"/><path d="M21 13v2a4 4 0 0 1-4 4H3"/></svg>
    </div>
    <h3>It has rituals</h3>
    <p>Copy from the bank export. Paste as values — <em>never</em> as formulas. Don't touch column F. The macro only works if you open the file on the old laptop.</p>
  </div>
  <div class="ait-feature-card">
    <div class="ait-feature-card__icon amber">
      <svg viewBox="0 0 24 24"><path d="M10.29 3.86L1.82 18a2 2 0 0 0 1.71 3h16.94a2 2 0 0 0 1.71-3L13.71 3.86a2 2 0 0 0-3.42 0z"/><line x1="12" y1="9" x2="12" y2="13"/><line x1="12" y1="17" x2="12.01" y2="17"/></svg>
    </div>
    <h3>Errors have consequences</h3>
    <p>One wrong cell means a wrong tax report, a donor who never gets their receipt, or an invoice with the wrong amount. The spreadsheet validates nothing — it simply does whatever gets typed.</p>
  </div>
</div>

Recognise two or more? Then you don't have a spreadsheet. You have a system that happens to live in Excel.

## Why Do We Stay in the Spreadsheet?

The answer isn't stupidity — it's comfort. Excel is familiar ground. Everyone has it, everyone can open it, and nobody has to ask for permission or budget to use it. New software is the opposite: unfamiliar, possibly expensive, possibly hard to learn, possibly a failure.

So we stay. And what's remarkable is *how far* we're willing to go to stay. We have seen spreadsheets whose total upkeep genuinely amounted to a full-time position — tasks a dedicated tool could handle in fifteen minutes a week. That's not an outlier; it's what happens when a system grows one column at a time for ten years without anyone ever doing the math.

## The Math

And the math is simple. Three questions:

1. **How often?** Daily, weekly, monthly?
2. **How long?** Hours per session — including troubleshooting and "who has the file?"
3. **What does an error cost?** A wrong report, an angry customer, a lost donor?

Time is money. Correctness is money too. A spreadsheet that swallows three hours every week costs more than 150 hours a year — year after year. Add the price of the error that *will* happen, because humans type, copy, and overwrite. A dedicated tool costs something to build or buy, but that's a one-off expense or a subscription — versus a bill that never ends.

## Build It — or Find It

Here's the good news: chances are the tool already exists. Time tracking, invoicing, member registries, inventory management — many routines have ready-made solutions that cost less per month than the spreadsheet costs per week. We're happy to find that tool for you before we ever talk about building anything.

And if it doesn't exist, we build it. We've done it many times before: a [MobilePay import that replaced manual payment entry](/en/posts/work-done/importing-mobilepay-payments-its-easy/), a [program for automatic reporting of tax-deductible donations](/en/posts/projects/program-for-reporting-tax-deductible-donations/), and a [telephone receptionist app that retired paper lists and whiteboards](/en/posts/work-done/user-controlled-receptionist/). What they all have in common: a recurring routine that used to require a person with a spreadsheet or a paper list — and afterwards required a click.

And here's the best part, if you dread writing a long requirements document: **your spreadsheet *is* the requirements document.** If it works today, it already describes exactly what data comes in, what calculations happen, and what needs to come out the other end. The columns are the data model, the formulas are the business logic, and the tabs are the screens. In other words, you've already done the hard part — it just needs translating into a tool that can't be typo'd to pieces.

## About Those Monday Evenings

And the volunteer from the opening? That exact scenario is what we're working on right now: a dedicated donation-management tool for NGOs — payment imports, automatic donor matching, and correct receipts, with no spreadsheets and no Monday evenings. We look forward to sharing more later this year.

## What Does Your Spreadsheet Do?

Tell us what your spreadsheet does — how often, how long, and what an error costs. Then we'll tell you what it would cost to never open it again. Sometimes the answer is an off-the-shelf tool for a modest monthly fee. Sometimes it's a small custom-built system. And once in a while, the answer honestly is: "Keep the spreadsheet — it's fine for this."

[Contact us](/en/contact-us/) — the first conversation costs nothing.