Skip to content

Case Study · Productivity

Case Study: Solo Founder Cuts Email Time 70% with an AI Assistant

How a bootstrapped SaaS founder used a local email triage + draft pipeline to get mornings back — without auto-sending a single message.

B2B SaaSShipKit (fictional)Stack: Claude Sonnet, Gmail API, Node.js, LiteLLM
EmailAutomationSolo founderGmailProductivity
Edited by The AIKnowHub team · Editorial team

Results

Daily email processing time

25 min

Draft acceptance rate

58%

Emails triaged automatically

~45/day

Monthly API cost

$12

Background

The founder of ShipKit — a 2-person bootstrapped analytics tool — spent the first 90 minutes of every day in Gmail. Investor updates, customer bugs, partnership intros, newsletters disguised as urgents. Real work started at 10:30.

He'd tried Superhuman, SaneBox, and inbox-zero systems. The bottleneck wasn't reading speed — it was deciding what needed a reply and writing the first sentence.

The problem

PainImpact
120–200 emails/day90 min morning block
No triage systemImportant threads buried
Repetitive replies"Thanks, looking into it" × 20
Context switchingDeep work delayed until late morning

Hiring wasn't an option at $8k MRR. He needed automation that made him faster, not a bot talking to customers.

Architecture

Built from the AI Email Assistant workflow:

Cron (every 5 min, VPS)
  → Pull new unread from Gmail
  → Classify: urgent | reply | fyi | archive
  → FYI/archive → label + skip
  → Urgent → flag in daily digest
  → Reply → draft in founder's voice (Gmail draft API)
  → 8am digest email: urgents + stats

Hard rule: no gmail.send scope. Every outbound message required a human click.

Implementation

Week 1 — Classification only

Structured JSON output via Claude Haiku:

{
  "bucket": "urgent | reply | fyi | archive",
  "reason": "one line",
  "confidence": 0.0–1.0
}

He labeled 80 historical emails manually. Holdout accuracy: 91%. FYI/archive auto-labeling alone reclaimed ~20 minutes/day.

Week 2 — Voice-matched drafts

He fed 15 sent emails into a style guide prompt: short sentences, no exclamation marks, signs off with first name only. Draft acceptance started at 34% and climbed to 58% over three weeks of edits.

Rejected drafts still helped — they surfaced the right thread context even when the wording was wrong.

Week 3 — Cost routing

Classification moved to Haiku ($0.002/email). Drafting stayed on Sonnet ($0.03/draft). LiteLLM proxy handled both with one config file. Monthly cost: ~$12.

Results

MetricBeforeAfter 4 weeks
Morning email time90 min25 min
Emails needing manual open~120~18
Missed urgent threads / month2–30
Drafts accepted without major edit58%

The founder's quote: "I didn't get an AI assistant. I got a morning back."

What he'd do differently

  1. Label 80 emails before writing code — his first classifier used too many buckets and confused "reply" with "urgent."
  2. Build the digest first — even without drafts, the 8am urgent summary was valuable on day three.
  3. Keep send manual forever — one bad auto-reply isn't worth any time saved.

Takeaway

Email automation for individuals isn't about AI sending mail — it's about AI doing the sorting and first draft so you can batch the human part into 25 minutes. The workflow guide is the blueprint; voice examples are the secret ingredient.

Lessons learned

  • 01

    Voice matching required 15 sent-email examples — generic 'professional' drafts were useless and got rejected immediately.

  • 02

    Classifying into urgent/reply/fyi/archive beat a single 'needs response' boolean — FYI auto-archive alone saved 20 minutes.

  • 03

    Never auto-send. The founder tried it for one week; one wrong acknowledgment to an investor nearly cost a follow-up meeting.

  • 04

    Running on a 5-minute cron on a $5 VPS was more reliable than a laptop daemon that slept when the lid closed.

  • 05

    LiteLLM let him A/B Sonnet vs Haiku for classification — Haiku won at 1/6 the cost with identical accuracy on his inbox.

Frequently asked questions

No — and it wasn't trying to. It removed triage and first-draft work so the founder could spend 25 focused minutes instead of 90 scattered ones.