Email That Works For You, Not The Other Way Around

Every marketing team has the same email problem. It just wears different masks.

Maybe it's the Monday morning inbox with 200 unread messages, half of which need action and half of which are noise. Maybe it's the invoice buried in a thread from three weeks ago that finance has been asking about. Maybe it's the outbound sequence you set up in one tool, tracked in another, and reported on in a third.

The typical response is to throw SaaS at it. An inbox management tool here, an automation platform there, a sequence builder on top of that, and a Zapier glue layer holding the whole thing together. Before you know it, you're paying for five subscriptions and spending more time managing the tools than doing the work they were supposed to replace.

We know this because we lived it. At Admirate Agency, our email stack used to look like a Rube Goldberg machine -- functional, technically, but fragile and expensive.

The shift we made

The turning point wasn't a single tool. It was a realization: email is fundamentally a language problem. Sorting, summarizing, drafting, extracting data from attachments -- these are all tasks where AI excels, but only if you give it the right context and structure.

That's what Skills and Plugins in Claude Code gave us. Not another SaaS dashboard with someone else's idea of what our workflow should look like. Instead, composable building blocks we could assemble into workflows that matched how our team actually works.

A Skill, in this context, is a reusable prompt with structure -- it knows what to look for, how to reason about it, and what to produce. A Plugin connects Claude Code to external systems -- your inbox, your file storage, your CRM. Together, they turn email from a chore into a system.

How we actually use this

Inbox triage that thinks, not just sorts. Every morning, a Skill scans new mail and categorizes it -- not just by sender or subject line, but by what it actually requires. Client feedback that needs a response today. An invoice that should go to finance. A newsletter that can wait. A thread where someone asked a question three messages deep.

The difference from rule-based filters is that this understands context. A message from a client about billing isn't the same as a marketing email about billing software. The Skill knows the difference because it reads the content, not just the metadata.

Drafting responses that sound like us. When the triage identifies messages that need replies, a second Skill drafts them. Not generic AI-sounding responses -- drafts that match our tone, reference the right context, and anticipate follow-up questions. We review and send. The time from "this needs a reply" to "reply sent" dropped from hours to minutes.

The important part: these are drafts for review, not auto-sends. The human stays in the loop, but the human is editing instead of writing from scratch.

Documents that route themselves. This one changed how we operate day to day. Invoices, contracts, creative briefs, NDAs -- they all arrive as email attachments. A Plugin pulls attachments, a Skill reads and classifies them, and they get routed to the right place. Invoices go to the accounting folder with extracted amounts and dates. Briefs go to the project management system with key details pulled out.

We used to have someone spend an hour a day on this. Now it happens in the background.

Outbound sequences with actual context. Building email sequences used to mean choosing a template, filling in merge fields, and hoping the personalization didn't feel robotic. Now a Skill builds each message with actual context about the recipient -- what they do, what they've engaged with, what's relevant to them right now.

The sequence logic lives in a Skill we wrote, not in a vendor's product. When we want to change the cadence, the tone, or the follow-up strategy, we modify the Skill. No fighting with a SaaS UI that doesn't quite do what we need.

The economics aren't bad either

We're not going to pretend the primary motivation was cost savings -- it was about having workflows that actually fit. But the math works out. Five email-related subscriptions at $50-200/month each adds up. Skills and Plugins running on Claude Code cost a fraction of that, and they do exactly what we need instead of 80% of what we need plus 200% of what we don't.

More importantly, when something needs to change, we change it. We don't submit a feature request and wait for a product team to prioritize it. We don't work around limitations with duct-tape integrations. We just update the Skill.

That's probably the part that matters most. Your email workflow should evolve as fast as your team does. When it's authored in code instead of configured in someone else's product, it can.