5 Automations That Run My Clients' Businesses While They Sleep

The Goal Isn’t Fancy. The Goal Is Invisible.

Nobody wants to think about automation. They want to think about their clients, their growth, their weekends. The best automations are the ones that quietly do their job at 3am, never ask for a day off, and only make themselves known when something genuinely exceptional needs a human eye.

Here are five that run right now, unattended, for real clients.

1. The Overnight Email Sorter

What it does: Scans Gmail every 15 minutes overnight. Identifies emails by sender, subject pattern, and attachment type. Sorts them into labelled categories. Saves attachments to dated folders in Google Drive. Flags anything that needs urgent attention. Logs everything to a master spreadsheet.

Why it matters: The client is a consultancy that receives 100-200 emails per day from suppliers, clients, and regulatory bodies. Before automation, the first 45 minutes of every morning was spent triaging the inbox. Now, when they open their laptop at 8am, their inbox is sorted, attachments are filed, and a summary email tells them exactly what needs their attention.

The invisible detail: The script handles shared drive permissions, filename conflicts (appending timestamps when duplicates exist), and character encoding in filenames from international senders. It also detects when Gmail’s API is temporarily unavailable and retries silently instead of failing.

Time saved: ~45 minutes per day × 260 working days = 195 hours per year

2. The Automatic Client Report

What it does: Every Monday at 6am, the script pulls data from 4 Google Sheets (time tracking, task completion, project milestones, and budget), calculates key metrics, generates a formatted HTML email with conditional colour-coding (green/amber/red status indicators), and sends it to each client; personalised with their project data only.

Why it matters: The client runs 12-15 active projects simultaneously. Writing individual progress reports was eating an entire day every week. Now the reports write themselves. They’re consistent, they’re never late, and they don’t contain the kinds of calculation errors that creep in when you’re copying data between sheets at 4:30pm on a Friday.

The invisible detail: The script calculates whether each metric is trending better or worse than last week and includes a directional indicator. It also detects when a project has had no updates for 7+ days and flags this to the project manager (but not the client); catching stalled projects before the client notices.

Time saved: ~8 hours per week × 52 weeks = 416 hours per year

3. The Lead Capture Pipeline

What it does: When someone fills out the website contact form (Google Forms), the script instantly: checks for duplicate submissions, adds them to the CRM spreadsheet with a timestamp, creates a Google Drive folder for the lead, sends a personalised auto-response email within 60 seconds, adds a follow-up task to the sales Calendar for 48 hours later, and notifies the sales team via email with the lead’s details.

Why it matters: Speed-to-response is the single biggest factor in converting leads. Research consistently shows that responding within 5 minutes is dramatically more effective than responding within an hour. This script ensures every lead gets a personalised response in under a minute, 24/7; even at midnight on a Sunday.

The invisible detail: The duplicate check isn’t just matching email addresses. It uses fuzzy matching on company name and phone number to catch variations (e.g., “ABC Ltd” vs “ABC Limited” vs “A.B.C. Ltd”). It also tracks which marketing channel the lead came from (using UTM parameters embedded in the form URL) and includes this in the CRM entry for campaign tracking.

Time saved: ~20 minutes per lead × 30 leads per month = 10 hours per month = 120 hours per year

4. The Document Generator

What it does: When a row is marked as “Approved” in the project spreadsheet, the script: pulls the relevant data, opens a Google Docs template, replaces all placeholder tags with real data, generates a formatted PDF, saves the PDF to the client’s Drive folder, emails the PDF to the client with a personalised cover message, and updates the spreadsheet with the sent date and document link.

Why it matters: The client sends 200+ customised documents per month; proposals, confirmations, certificates, and reports. Each one used to take 15-20 minutes of manual copy-paste-format-export-email work. Now it takes a checkbox tick and 30 seconds of waiting.

The invisible detail: The template system handles conditional sections; paragraphs that only appear if certain conditions are met (e.g., a warranty clause only appears for hardware projects, not software). It also handles tables with variable numbers of rows, adjusting the document layout dynamically. And it creates an audit trail; every generated document is logged with a version number, so if a template is updated, the system knows which version each client received.

Time saved: ~15 minutes per document × 200 documents per month = 50 hours per month = 600 hours per year

5. The Self-Healing Trigger Monitor

What it does: Runs every morning at 5am. Checks that all other automations ran successfully in the last 24 hours. Verifies that triggers are still active (Google Apps Script triggers can silently deactivate). Tests that API connections are responding. Sends a daily “all clear” or “attention needed” email.

Why it matters: The worst thing about automation breaking is not knowing it’s broken. A failed script doesn’t send you a notification by default; it just stops running. This monitor ensures that if anything stops, someone knows within 24 hours.

The invisible detail: If the monitor detects a dead trigger, it doesn’t just report it; it recreates the trigger automatically and logs the event. Most trigger failures are transient (caused by temporary permission issues or Google maintenance). The self-healing logic means 90% of issues resolve without any human intervention. The email only escalates to a human when the self-heal fails.

Time saved: Hard to quantify directly, but prevents the cascading damage of undetected automation failures; which can cost days of manual recovery work.

The Common Thread

All five of these automations share three characteristics:

They run inside Google Workspace. Sheets, Gmail, Drive, Calendar, Docs. No external tools, no paid middleware, no per-task costs.
They handle edge cases. Duplicates, encoding issues, permission problems, API outages. The scripts don’t just handle the happy path; they handle Monday morning.
They monitor themselves. Every script logs what it did, and the monitor script watches all of them. If something breaks, someone knows before anyone is affected.

That’s what separates a script from a system. The code is the easy part. The reliability engineering is the job.

What’s Running Your Business While You Sleep?

If the answer is “nothing”, or “Zapier, I think, but I’m not sure it’s still working”; we should talk.

Book a free 15-minute automation audit →

Tell us your most repetitive task. We’ll tell you what it would look like automated, and what it would look like at 3am, running without you.

Nicola Berry is the founder of Empower Automation, based in Falkirk, Scotland. Building automations that work while you don’t.