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.
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
| Pain | Impact |
|---|---|
| 120–200 emails/day | 90 min morning block |
| No triage system | Important threads buried |
| Repetitive replies | "Thanks, looking into it" × 20 |
| Context switching | Deep 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
| Metric | Before | After 4 weeks |
|---|---|---|
| Morning email time | 90 min | 25 min |
| Emails needing manual open | ~120 | ~18 |
| Missed urgent threads / month | 2–3 | 0 |
| Drafts accepted without major edit | — | 58% |
The founder's quote: "I didn't get an AI assistant. I got a morning back."
What he'd do differently
- Label 80 emails before writing code — his first classifier used too many buckets and confused "reply" with "urgent."
- Build the digest first — even without drafts, the 8am urgent summary was valuable on day three.
- 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
Related on AIKnowHub
Workflow
Build an AI Email Assistant
An assistant that drafts replies in your voice, classifies incoming mail, and surfaces only what needs you.
Concept
LLM Cost Optimization
The operational playbook for cutting LLM spend without cutting quality. Model routing, caching, batching, and the metrics that actually matter.
Concept
Structured Outputs Explained
Structured outputs make models return valid JSON every time — no more parsing failures, no more 'almost JSON.' Here's how they work and when to use them.
Workflow
Meeting Notes to Action Items
Turn raw notes or a transcript into decisions, owned action items, open questions, and risks — then push to Linear, Jira, or Slack.
Case Study
Case Study: Ops Team Turns Meeting Recordings into Action Items
How a remote ops team automated meeting notes to structured action items in Linear — with owner, due date, and human approval before ticket creation.
Tool Guide
Make Guide
The definitive guide to Make (Integromat) for AI automations — routers, iterators, Claude modules, pricing, and when to pick it over Zapier or n8n.