5 Signs Your Hiring Spreadsheet Has Stopped Working

The spreadsheet was perfect for your first three hires. One tab, eight columns, color-coded statuses. You could see the whole pipeline at a glance and you knew where every candidate stood.

Then the spreadsheet got to 40 rows. Then 80. Then somebody DM'd you about an applicant and you spent six minutes hunting for their email. That is the moment you have outgrown it.

Most founders and creators run their first few hiring rounds out of Google Sheets, Notion, or Airtable. It is free, it is familiar, and it works — until it does not. The break is rarely dramatic. There is no single error message. Instead, the spreadsheet quietly stops being the thing that helps you hire and starts being the thing you avoid opening on Monday morning.

Here are the five signs your spreadsheet has stopped working, in the order they usually show up.

1. You are typing the same email three times a week

Stage transitions need emails. "Thanks for applying." "We'd like to set up a call." "Unfortunately we're moving forward with other candidates." For three candidates a month, you write the email each time. By candidate 30, you are pasting from a Notes file, then editing names, and then forgetting to edit one of them and sending the wrong person's name to the wrong person.

The spreadsheet has no concept of "when a row moves from column B to column C, send this email." It is a grid of cells. Every time you move a candidate forward, you are doing two pieces of work: updating the sheet, and writing the email. The sheet does not know about the email, the email does not know about the sheet, and nothing connects them.

A real pipeline ties stages to email templates. You write the rejection email once. Every applicant who lands in the "Not a fit" column gets it automatically, with their name and the role they applied for. The four hours a week you spent on copy-pasted email goes back into actually evaluating candidates.

2. You cannot tell who has already been reviewed

In a spreadsheet, "reviewed" is a checkbox or a status column. Which is fine — until two people on your team are reviewing in parallel, or you come back after a week and cannot remember whether the "Maybe" tag means you flagged them or your co-founder did.

The collaboration model that spreadsheets give you is co-editing the same grid. There is no notion of a comment thread on a single candidate, no internal note attached to that specific person, no record of who moved them where and when. If you and your co-founder disagree on a candidate, you cannot have that conversation in the spreadsheet — it has to happen in Slack, in a thread, on a different surface, and now context is split in two places.

Pipelines built for hiring have per-candidate comment threads, internal notes that the candidate never sees, and a stage history. You open the candidate, you see the last 10 things that happened, including who said what. The conversation lives where the work lives.

3. You are losing files

Resumes. Portfolio links. Cover letters as Google Docs. Video answers as Loom URLs that someone pasted into a cell. Maybe a few are uploaded to Drive. Maybe a few are URLs only, hosted by someone else, who could revoke access tomorrow.

The spreadsheet was not built to be a file system. Cells hold text well; they hold attachments terribly. By candidate 50, you have a folder of resumes named Resume_FINAL_v2.pdf, you have Loom links that the candidate has since taken private, and you have at least one applicant whose entire portfolio lives behind a Notion page that 404s the moment they delete it.

This matters most for portfolio-first hiring — creators evaluating video editors and thumbnail designers, founders looking at side projects from a founding engineer. The work sample is the application. Losing it means you cannot evaluate the candidate. A real pipeline stores uploads with the candidate record, not in a separate cloud folder you also have to manage.

4. You cannot remember where applicants came from

You posted the role on LinkedIn, Twitter, IndieHackers, and your newsletter. After three weeks you have 40 applicants. Where did each one come from?

Spreadsheets let you add a "source" column. Then you have to fill it in for every candidate, by hand, by remembering — and you will not remember by candidate 25. The source data is what tells you whether your next round of hiring should lean into Twitter or stop bothering with LinkedIn. Without it, you are guessing.

Real hiring tools attach a source to every applicant automatically — UTM parameters on the public hiring page, referrer headers when they arrived, an explicit "Where did you hear about this role?" question on the form. When the round closes, you can see, at a glance: 60% of applicants came from one tweet, 5% from LinkedIn. Next round, you know what to do.

5. You dread opening it

This is the soft sign and the most important one. The spreadsheet has stopped being a tool and started being a chore. You know there are six candidates who have been sitting in "Applied" for a week. You know two of them deserve a "no thanks" email. You know one might be great. But the spreadsheet feels like work, and writing the emails feels like work, and updating the columns feels like work — so you do not open it. The pipeline stalls.

Candidates who do not hear back within five business days assume they did not get the role. The good ones take other offers. The spreadsheet has stopped being a hiring tool and become a backlog. (The same failure mode shows up when creators run hiring out of DM threads — see why hiring from DMs is costing you.)

When the friction of using the system is higher than the friction of doing the work it tracks, the system has lost. Switching to something that does the chores for you — sends the emails, surfaces the unreviewed candidates, tells you what is overdue — is not a luxury. It is the only way the pipeline starts moving again.

What to switch to

If two or more of the five symptoms above sound familiar, you have outgrown the spreadsheet. The options:

• A "lite" ATS like hire.page — built for one to thirty hires a year. Public hiring page, kanban pipeline, stage-triggered emails, file upload, source tracking, custom domain. Starts free. This is the category the spreadsheet has just graduated you into.
• A mid-market ATS like Workable or Breezy — more features, more cost, more setup. Worth it if you are hiring 20+ people a year, overkill if you are not.
• An enterprise ATS like Greenhouse or Ashby — only makes sense if you have an HR team and a multi-step requisition approval process. Annual contracts in the $6K–$30K range.

For most founders and creators reading this, the right move is the first one. You are not going from sheets to Greenhouse. You are going from sheets to "the tool I should have started with."

How to migrate without losing data

Migration is the part people fear. It does not need to be hard.

1. Export the spreadsheet to CSV. Most pipeline tools accept a CSV import of candidate name, email, source, stage, and notes. The structure of your sheet maps directly.
2. Upload your file backlog. If you have resumes in Drive, drop them into the imported candidate records. This is the one piece of manual work, and it is one Sunday afternoon.
3. Mark stale candidates as closed. Anyone who has been in "Applied" for more than three weeks is, in practice, rejected. Mark them closed in the new system; do not import the rot.
4. Set up your stage emails before you take a new applicant. Write the four templates you need — Applied, Interview Requested, Offer, Rejected — and tie each one to a stage. Then the next candidate gets the right email, automatically. (For the page candidates land on before they hit your pipeline, see how to build a hiring page that attracts candidates — the spreadsheet upgrade is only half the fix.)

Day-one cost: a Sunday. Recurring cost: zero, until you exceed the free tier of whichever tool you picked. The four hours a week you get back from auto-sent emails alone pays for any paid plan inside a month.

The spreadsheet was the right tool when you had three candidates. It is not the right tool at 40, and it has actively cost you good hires by 80. The signs above are not theoretical — they are the actual moments founders describe when they switch. If you have seen any of them, the spreadsheet has already told you it is done. The only question is whether you listen this round or the next.

---

Try the lite ATS that replaces the spreadsheet. hire.page builds a branded hiring page, routes every applicant into a kanban pipeline, and sends stage emails automatically. Free plan; paid plans from $29/mo.