DirectoryWorkflowsCase studiesPodcastsWho's Noah Take the stack assessment
← All case studies
Web-design agency

$43k a year of founder time back from one inbox

Inbox → sort, reply or draft, schedule follow-ups → Outlook + Google Sheets

Industry Web-design agency (Australia)
Stack n8n · Outlook (Graph API) · Google Sheets
Timeline Prototype in 1 day, live in 5
Value ~$43,000 / year
$43k/yr founder time back
720 hrs returned per year
3.5h → 0.5h on email per day

Michael ran his whole agency out of one Outlook inbox. No automation, no CRM. Email took about 3.5 hours of his day. We built a workflow that sorts every message, replies instantly to the safe ones, drafts the tricky ones for approval, and schedules follow-ups for leads and invoices. Inbox time dropped to about 30 minutes. That is three hours a day back, from the one person in the business who cannot be replaced.

What it's worth

$43,000 a year of founder time back, costed deliberately low

Founder time back

Hours a day on email, before
3.5 hrs
Hours a day on email, after
0.5 hrs
Hours back per day
3.0 hrs
Working days per year
240
Hours back per year
720 hrs
Founder time
$60 / hr
per year
$43,000
How this was calculated — every assumption
  • The 3.5 hours and 30 minutes are the founder's own figures, before and after.
  • Founder time is costed at $60/hour. An hour of owner attention in a working agency is worth more than that, which is the point: the figure is set low so it holds up if you argue with it.
  • 240 working days a year, allowing for holiday.
  • Faster invoice chasing almost certainly helped cash flow too. There is no measured figure, so it is left out.

Results at a glance

The problem

Michael ran the entire business through one Outlook inbox with no automation and no CRM. He needed messages sorted properly into leads, invoices, support, and spam. He needed instant replies where that was safe and drafts to approve where it was not. He needed lead and invoice follow-ups scheduled automatically, Australian Spam Act compliance, and all of it inside Outlook. The real cost was not the email. It was that the person doing it was the same person who should have been selling.

What was built

01

Sorting

Every message lands in one of six buckets: lead, quote, invoice, support, spam, or out-of-office.

02

Replies

Instant replies for the safe cases. A one-click draft for anything tricky. The system only acts alone where getting it wrong is cheap.

03

Lead follow-ups

An immediate first reply, then nudges at 2 and 5 business days. Stops the moment someone replies or books.

04

Invoice follow-ups

Reminders before due, on the due date, then at 3 and 7 business days. Pauses after two unanswered attempts.

05

Personal touches

Pulls in business names, suburbs, requested services, and earlier thread context, in local tone and spelling.

06

Operations

Sends only in business hours, with duplicate protection, retries, and failure alerts.

What keeps it from breaking

Never answers twice

A message that gets reprocessed does not get a second reply. In inbox automation, duplicate sends are the mistake everyone notices.

Business hours only

Nothing sends outside working hours. A 3am instant reply announces itself as a robot and undoes the personalization.

Follow-ups know when to stop

Lead nudges halt on any reply or booking. Invoice reminders pause after two silent attempts. Chasing without a stop condition turns a helpful system into a complaint.

How the approach worked

Take a channel someone is drowning in. Sort what is in it. Handle the safe cases automatically and queue the rest for a one-click approval. Compliance and business hours are part of the build, not an afterthought. The maths is simple, and it is the whole argument: three hours a day, times the value of the one person you cannot replace.

The results

Manual inbox management became scheduled automation. Three hours a day came back, roughly 720 hours a year, about $43,000 at a deliberately low founder rate. In his words: replies go out fast, follow-ups never slip, and he only reviews the tricky ones. Spam Act compliance was built in, including sender identification, opt-out, and DKIM, SPF, and DMARC through Microsoft 365.

Replies go out fast, follow-ups never slip, and I only review the tricky ones.

Tools & technologies

n8nOutlook (Graph API)Google Sheets

Have a process like this slowing your business down? Tell me your stack and goals and I'll send back a build plan.

Take the stack assessment →