For founders & operators who live in email

The inbox triaged,drafted, and done.

Four Claude Skills read your inbox through the Gmail MCP, triage every thread, draft the replies that actually need you, and hand you one ordered plan. From backlog to finished in about 30 minutes — and it drafts, you send.

Get the Engine — $129one-time · instant download · yours to keep
Six deliverables · MCP-driven
Inbox Triage Engine
python
Four Claude Skills
skills
Triage Scorer workbook
xlsx
Daily-brief template
template
Daily Workflow playbook
docx
Gmail MCP Setup playbook
docx
Works alongside
Meeting Intelligence · Brand Voice · Chat & SMS Concierge
01.The Problem

The inbox is where your day goes — and where your real work stalls.

Everything looks urgent

A cold pitch sits next to a key client and they shout equally loud. Triaging by hand burns your sharpest hours.

You're the bottleneck

Half the threads don't actually need you — but they pile into your reply queue and wait, because nothing routes them away.

Loops go quiet

You sent the proposal. No reply. It vanishes under new mail, and a live deal dies in the inbox.

02.See It Work

Every thread routed to the right pile — and the one to start with.

This is the triage core, live. Tune the four levers and watch where a thread routes — then see how the morning's inbox ranks, whether it's clearable today, and what to handle first. The delegate gate is the honest part: a thread that doesn't need you leaves your reply pile, whatever its score.

Inbox Triage Engine · live
inbox 2026-06-19
Score this thread
Tune the four levers and watch where it routes
55
/ 100
Sender value · w35
key client → 5, stranger → 1
3
Urgency · w30
today → 5, no clock → 1
3
Needs you · w20
only you → 5, anyone → 0
1
Clarity to act · w15
act now → 5, blocked → 1
4
DELEGATE

Delegate gate — it matters, but it doesn't need you. Routed off your reply pile to protect your focus.

Raise “Needs you” to 2 or more and it returns to your pile — the same gate the engine and workbook enforce.

This morning's inbox
Clearable · 2 reply-now / budget 5
Key client: contract renewal needs your sign-off today
REPLY NOW100
Prospect from Tuesday's demo: pricing question
REPLY NOW80
Vendor invoice #4471 — approve payment
DELEGATE55
Conference: speaker invitation for Q4 keynote
SCHEDULE62
Partnership intro — worth exploring next week
SCHEDULE56
Cold pitch: we do SEO for SaaS
ARCHIVE25
Newsletter: 10 AI tools you should try this month
ARCHIVE16
Start here
Key client: contract renewal needs your sign-off today100/100 — handle this before anything else.

Demo resets on reload. Bring your own Gmail MCP for the live inbox. It drafts; you send. No inbox-zero promised.

03.What's Inside

One pipeline, four Skills, from backlog to done.

01.Triage the inbox

The scout reads your threads via the Gmail MCP and sorts each into REPLY NOW / DELEGATE / SCHEDULE / ARCHIVE, then names the one to handle first.

02.Draft what needs you

The drafter writes the REPLY NOW replies in your voice, grounded in each thread, with any open decision flagged [decision needed]. It never sends.

03.Build the brief

One ordered plan: do first, delegate (with a suggested owner and forward line), schedule, archive — plus what you're waiting on.

04.Finish, and close loops

You send, delegate, and block time. The waiting-on tracker surfaces overdue follow-ups so a stalled deal doesn't die in the inbox.

Plus a runnable Python triage engine with a worked sample, a spreadsheet that reproduces the same math, the daily-brief template, and two playbooks — the 30-minute daily loop and the Gmail MCP setup & safe-automation guide.

04.The Standard

Three rules the engine holds to.

Reads real mail, never invents

Triage runs on your actual inbox through the Gmail MCP. Summaries are faithful; the drafter never fabricates a fact, price, or commitment.

You stay the sender

It reads and drafts only — it never sends, archives, or deletes on its own. Every reply and hand-off is an action you take after review.

The delegate gate

A thread that matters but doesn't need you is routed off your reply pile, whatever its score. Giving you time back means handing off what others can do.

05.What This Is — And Isn't

An orchestration layer on top of your inbox — honest about its limits.

What it is
  • A repeatable daily loop that triages your inbox and drafts the replies that need you.
  • The orchestration layer — Skills, scoring, a template, and playbooks — on top of Gmail + Claude.
  • Built to protect your attention: it routes away what someone else can handle.
What it isn't
  • Not a Gmail subscription or a source of mail — you bring your own Google account and MCP connection.
  • Not an auto-pilot: it reads and drafts only, and never sends, archives, or deletes on its own.
  • Not a promise of inbox-zero or a fixed time saved; and not legal advice.
06.Who It's For

Built for people whose inbox is the job — but shouldn't be.

A fit if you're…
  • A founder, operator, or consultant who handles your own inbox.
  • Drowning in mail where most threads don't actually need you.
  • Willing to connect the Gmail MCP and keep yourself as the sender.
Not a fit if you…
  • Want a bot that empties your inbox and sends on its own.
  • Won't connect Gmail or won't review drafts before sending.
  • Expect inbox-zero magic rather than a repeatable triage system.
08.Common Questions

The honest answers, before you buy.

No — and that's deliberate. The engine reads your inbox and drafts replies; it never sends, archives, labels, or deletes on its own. Every reply, delegation, and follow-up is an action you take after reviewing it. When you connect the Gmail MCP, you can grant it the narrowest scopes that let it work — read access for triage and draft access for the drafter — and skip send/delete permissions entirely if you want.

Stop triaging by hand.
Start your day already sorted.

One purchase, lifetime access, 12 months of updates. $129, once. Bring your own Gmail MCP.

Sold by RedHub AI LLC · Secured by Stripe · redhub.ai