How a Non-Profit Got the Output of 11 People From a Team of 10

Ten people on a mentoring non-profit were doing the work of ten, but producing the output of eleven. The difference was a Google Sheets email automation that replaced hours of daily copy-paste work with a system that fires the right email, from the right person, the moment an applicant’s status changes. Here’s how that project came together.

Applications came in through a form and landed in a Google Sheet, which served as the team’s CRM. From there, everything was manual. They had a system that worked, but there was no automation in place, no templates firing on their own.

For every applicant, at every stage, someone on the team had to: check the qualification status, find the right email template, copy in the applicant’s name and email, and send it from their own business address. Multiply that across dozens of applicants per week, across multiple stages, and you’ve got a team spending a significant chunk of their day on repetitive email work.

The process held up during normal intake periods. But when new cohorts opened and application volume surged, the team had to work hard to keep up, which sometimes meant applicants waited longer than ideal to hear back. It was a capacity problem, not a process problem. The workflow was sound; it just didn’t scale.

The manual email workflow that was bleeding time

I mapped the workflow and found a pattern that’s common in small teams: a simple process that grew organically until it became a time sink nobody planned for.

Every application moved through stages: received, under review, qualified, not qualified, matched with mentor, onboarding. Each stage triggered an email. The templates were mostly the same, but the sender changed based on who was assigned to that applicant, and the content varied by stage.

The team had the templates saved in a shared doc. The process was: check the sheet, find what changed, look up the template, copy it, personalize it, send it from the right account. For every applicant, at every stage transition.

Three things made this painful:

• Volume. Dozens of applicants moving through stages every week. Each one needed multiple emails across the pipeline.
• Sender routing. The email had to come from the assigned handler, not a generic address. That meant each team member was logging in and sending individually from their own account.
• Error risk. Wrong template, wrong name, wrong stage. All easy mistakes when you’re copying and pasting 30 times a day. With applicants, even a small mix-up is embarrassing and creates extra work to correct.

The team had workarounds in place: color-coding in the sheet to track what was sent, shared checklists for high-volume periods. These helped manage the load, but the underlying manual work remained. No amount of organization could change the fact that every email still required a human to assemble and send it.

How we built the automated email system

The solution had four components, each handling one piece of the pipeline:

Google Apps Script webhook

A small script attached to the sheet that fires whenever the stage column changes. No polling, no scheduled checks. It triggers in real time when someone updates a row. The alternative was polling on a schedule, but that would introduce delays between status changes and emails going out, and it would consume Make.com credits on every check regardless of whether anything had changed. Event-driven was the right call for both speed and cost.

Make.com scenario

The webhook hits a Make.com scenario that reads the row data: applicant name, email, current stage, and assigned handler. Based on the stage, it selects the right email template and populates it with the applicant’s details. The email templates themselves are stored directly in the sheet, so the team can update copy, subject lines, or add new stage templates without ever opening Make.com. No code, no deployments. Just edit a cell.

After each email sends, Make.com fires a callback that writes back to the sheet, updating a “processed” flag column and appending to a history column that logs every email sent to that applicant with timestamps. This isn’t just a nice audit trail. It’s how the team maintains full visibility without leaving the tool they already work in. At a glance, anyone can see which applicants have been contacted, what was sent, and when. The sheet triggers the automation, and the automation reports back to the sheet.

SendGrid for delivery

Emails are sent through SendGrid with full domain authentication (DMARC, DKIM, and SPF all configured). This means emails land in inboxes, not spam folders. Each email sends from the assigned handler’s address, so it looks and feels personal to the applicant. SendGrid also gives the team a delivery log so they can see exactly what was sent, when, and whether it was opened.

The sheet stays the CRM

This was a deliberate choice. Every piece of information the automation needed (assigned handler, applicant name, email, stage) was already in the sheet the team used daily. Nobody had to learn a new tool. Nobody had to change how they worked. The automation was completely invisible to them. They update a stage column the same way they always did, and the right email goes out automatically, replacing what used to be 5 minutes of manual work per applicant, per stage transition. This is exactly the kind of low-disruption setup we identify in an operations audit.

Total build time: about a week, including testing across all stage transitions and training the team.

The result: 10% productivity gain without hiring

The team got back roughly 10% of their daily productivity. For a 10-person team, that’s the equivalent output of an extra employee, without hiring anyone.

But the numbers only tell part of the story. Three things changed:

Speed. Applicants now get stage-appropriate emails within seconds of a status change, not hours or the next morning. Response time went from “whenever someone gets to it” to instant.

Consistency. Every applicant gets the right email, with the right content, from the right person. No more wrong templates. No more “sorry, that email was meant for someone else.” The color-coding system in the sheet became unnecessary overnight.

Focus. The team stopped spending mental energy on a repetitive task and redirected it toward the work that actually matters: mentoring. That’s the part that’s hard to measure but easy to feel.

Where else Google Sheets email automation works

The pattern here (spreadsheet trigger, webhook, automation platform, transactional email) isn’t specific to non-profits or mentoring programs. It applies anywhere a team is manually sending templated emails based on status changes in a sheet or simple database.

A few real-world scenarios where the same architecture fits:

• Hiring pipelines. Candidate moves from “phone screen” to “technical interview” in your tracker, and the scheduling email and prep materials go out automatically from the hiring manager’s address.
• Client onboarding. New client row gets added to the sheet, and the welcome email, intake form link, and team introduction fire in sequence without anyone lifting a finger. This is a textbook case of knowing whether to hire or automate.
• Grant applications. Application status changes from “under review” to “approved” or “declined,” and the appropriate notification goes out instantly with next steps included.
• Event registrations. Attendee registers and their row appears in the sheet. Confirmation, logistics details, and pre-event reminders are handled automatically based on the event date.
• Vendor management. Purchase order status updates trigger the right email to the right supplier: acknowledgment, shipping request, or payment confirmation.

In every case, the ingredients are the same: data already lives in a sheet, status changes are the trigger, and the emails follow predictable templates. If that describes a process in your business, it’s a strong candidate for automation.

What it costs

This was a one-time build investment. The ongoing cost is under $50/month: Make.com credits and SendGrid sends at this team’s volume. No recurring labor cost, no additional headcount.

The ROI compounds. Every new cohort that opens, every new applicant the program processes, the system pays for itself again. The 10-person team that built this hasn’t grown, but their capacity has, and it keeps growing with every intake cycle. If you want to see how the math works for your own team, the automation ROI calculator takes 30 seconds.

The takeaway

This wasn’t a complex engineering project. The tools involved (Google Sheets, Apps Script, Make.com, SendGrid) are all accessible and affordable. The hard part isn’t the technology. It’s recognizing that a process your team has been doing manually for years doesn’t have to stay that way. That recognition gap is also why most automation projects fail when they start with tools instead of process mapping.

If your team is manually sending emails based on data that already lives in a spreadsheet, that’s automation waiting to happen. Book an operations audit to see exactly what’s possible, or tell us about your workflow and we’ll map it out together.