B2B sales
Sales: Gmail lead follow-up automation from Sheets CRM
Zero missed follow-ups. 8 hrs/week saved on manual email.
Reps tracked leads in Sheets but sent follow-ups manually from Gmail. Missed touches cost pipeline. We automated sequenced emails with stop rules when replies arrived.
Context
A 12-person sales team using Sheets as a lightweight CRM. No budget for Salesforce seats for every rep.
Challenge
- Follow-up dates lived in Sheets; emails were sent one-by-one from Gmail.
- Reps forgot touches after busy weeks — no audit trail of what was sent.
- Mail merge add-ons broke when volume exceeded a few dozen rows per day.
Approach
- Mapped pipeline stages to email templates with personalization tokens from sheet columns.
- Time-driven trigger every morning reads rows where Next Touch = today and Status = Open.
- Gmail thread search stops sequence when a reply is detected.
- Sent log written to a History tab for manager visibility.
Solution
Container-bound Apps Script with GmailApp.sendEmail(), template Docs for HTML bodies, and Script Properties for rate limiting. Runs entirely in the client's Workspace.
Outcome
- Follow-up compliance improved — managers see daily sent counts in one sheet.
- Reps reclaimed ~8 hours/week previously spent on manual Gmail copy-paste.
- No per-seat CRM tax; script cost was a one-time build.
Technical approach
Morning time-driven trigger → filter sheet by date/status → merge template → GmailApp.sendEmail → append History row → optional Slack digest to manager.
Lessons learned
Always log sends to a sheet. Build stop-on-reply early — sequences without it annoy prospects. Keep templates in Docs, not hard-coded strings.
At a glance
- Time saved
- ~8 hrs/week team-wide
- Follow-up compliance
- Near 100% on scheduled touches
- Stack
- Sheets + Gmail + Apps Script
Related on this site
More case studies
- Shopify → Sheets ops hub, E‑commerce & retail
- VBA migration & approvals, Manufacturing & B2B sales
- Field web app + Sheets backend, Logistics & field services
Discuss a similar build
Share your stack and constraints, we'll be honest about quotas, security, and timeline.