بابيل

Every innovation program has one. It’s usually called something like Applications_FINAL_v3_USE_THIS_ONE.xlsx. It has 14 tabs, three color codes nobody remembers agreeing on, and a column called “Notes (Maria).” Maria left two cohorts ago. Nobody has the heart to delete her column.

We have a soft spot for the hero spreadsheet. It got your program off the ground when there was no budget and no time. But somewhere along the way it stopped being a tool and started being a single point of failure. This post is about spotting that moment, and about retiring the spreadsheet gracefully, without buying a stack of new software you don’t need.

It works right up until it doesn’t

The hero spreadsheet rarely fails in a dramatic way. It fails quietly, in moments that feel small at the time.

Reviewer number four scores everything from 1 to 10 while everyone else used 1 to 5. Nobody notices until the shortlist meeting, when a mediocre application is suddenly sitting in the top three. Someone spends an evening normalizing scores by hand and hoping they got the formula right.

A funder asks a simple question: how many of last year’s founders went on to raise money? The answer exists, technically. It’s in a few follow-up emails, a mentor’s notes and one program manager’s memory. It takes a week to reconstruct, and the number still comes with an asterisk.

Then a second program launches. Someone duplicates the file to save time, and the spreadsheet has a baby. Now there are two versions of the truth, slowly drifting apart, and every new hire has to learn which tab in which file is the real one.

Why “buy more software” is not the answer

The obvious reaction is to go shopping. But look at what most program teams already run: a form builder for applications, a CRM for partners, a shared drive for documents, a survey tool for feedback and at least three WhatsApp groups where the actual decisions get made.

The problem was never a lack of tools. It’s that the truth about your program lives in too many places at once. Every new tool you add without retiring an old one creates another place to check, another export to reconcile and another login for your mentors to forget.

The fix is fewer places where the truth lives, not more software.

Ideally, that means one place where applications, scoring, mentoring, progress and reporting connect. When a founder applies, gets reviewed, gets matched with a mentor and reports back six months later, all of that should sit on the same record. Then the funder question takes minutes instead of a week.

Is your spreadsheet holding your program hostage? 7 warning signs

Not every spreadsheet needs retiring. A simple tracker for a small, one-off event is fine. But if several of these sound familiar, your spreadsheet has quietly become infrastructure, and fragile infrastructure at that.

  1. Only one person really understands it. If that person goes on vacation during selection week, the process stalls.
  2. You have a “do not sort this column” warning. Formulas, merged cells and hidden tabs are holding the whole thing together.
  3. Reviewers are scoring in different scales or different files. Every round ends with someone merging and cleaning scores by hand.
  4. Past applicants are effectively invisible. You can’t easily see that someone applied twice before, or that a rejected team from last year is now a strong fit.
  5. Reporting means archaeology. Every funder report starts with digging through inboxes, chat threads and old exports.
  6. There are multiple “final” versions. People email copies around, and nobody is sure which one has the latest decisions.
  7. You’re nervous about who can see what. Applicant data, reviewer comments and contact details all sit in one file with a sharing link you’d rather not think about.

If you counted three or more, the spreadsheet isn’t serving the program anymore. The program is serving the spreadsheet.

How to retire it without drama

The good news is that you don’t need a big migration project, a steering committee or a six-month rollout. You need a clear starting point and a few rules everyone agrees on. Here’s the approach we recommend.

  1. Start with the next open call, not the current cohort. Don’t move a program mid-flight. Pick the next application round and run it end to end in the new setup. The old spreadsheet retires naturally as the current cohort finishes.
  2. Agree on one scoring scale before anyone reviews anything. Define your criteria, their weights and the scale, then lock it in. Reviewer number four can still have opinions, just on the same 1 to 5 scale as everyone else.
  3. Import your past applicants. Your historical applications are a real asset. Bring them into a searchable database so you can spot repeat applicants, revisit near-misses and see how your pipeline has changed over time.
  4. Decide one source of truth for each question. Write down the questions people ask most often, such as “Who’s in the current cohort?”, “What did the jury decide?” and “How are our alumni doing?”, and name the one place where each answer lives. Then stop answering those questions anywhere else.
  5. Give Maria’s column a proper burial. Read through the notes, move anything useful onto the relevant applicant or startup record, and archive the rest. Institutional knowledge deserves a better home than column AF.

Most teams find that the second and fourth steps do most of the work. Consistent scoring removes the late-night cleanup, and a clear source of truth removes the “which file?” conversations.

Where Babele fits

We’ve been building Babele since 2014 for exactly this situation: programs that have outgrown their hero spreadsheet but don’t want five more tools. Applications, scoring, mentoring, program delivery and reporting all sit on the same record for each applicant and venture.

The part where most hero spreadsheets live, applications and deal flow, is free forever. That includes open calls, weighted scoring with multiple reviewers and rounds, pipelines, shortlisting and a searchable applicant database. When you’re ready, you can add paid modules for mentoring, program delivery and impact tracking and reporting, so the funder question finally has a quick answer.

We’re ISO/IEC 27001 and 27701 certified and GDPR compliant, which helps with that seventh warning sign about who can see what.

The takeaway

Your hero spreadsheet did its job. It deserves thanks, not blame. But a program that runs on one fragile file, one person’s memory and a handful of chat groups is a program that can’t answer simple questions about itself.

You don’t need more tools. You need fewer places where the truth lives. Start with your next open call, keep your scoring consistent, bring your history with you and name one home for every answer.

Ready to give your spreadsheet a well-earned retirement? Start free with Babele and run your next open call in one place.