- Jared, a go-to-market architect at Anthropic, describes how Claude let him move from a startup account executive role into a technical builder role he never thought he had the chops for.
- As an AE managing 600-700 accounts and working until 8-9pm answering emails, he built "Class" (Claude Draft), a system that drafts customer emails using the Claude API, a system prompt, context retrieval, and pattern matching.
- Class saves him 2-3 hours a day and has sent thousands of emails; with the technical barrier dissolving, he now designs products and has senior engineers help implement them, changing his career path entirely.
How Anthropic uses Claude in GTM Engineering
- Jared was a startup account executive managing roughly 600-700 accounts toward the end, often working until 8-9pm answering emails and scouring Slack, knowledge bases, Google Docs, and Google Drive.
- He asked himself how to bring Claude into the loop and built "Class" — short for Claude Draft — to manage his inbox.
- Class uses the Claude API behind the scenes, with a system prompt (role: account executive; what you help customers with), context retrieval via a Google Docs integration that can also fetch web URLs (including a Claude Doc website), and pattern matching.
- The workflow: set up a system prompt, add a doc for context retrieval, open an email, and click "generate draft"; Claude retrieves information from the website, documentation, and internal context to draft a reply.
- The system lets him speak more technically with customers without manually digging through Slack or Google Docs, since Claude loads the relevant context and starts generating.
- Class saves him at least 2-3 hours a day, and thousands of emails have been sent through it.
- With the technical barrier dissolving, he can design more products and have senior engineers help implement them to the final stretch.
- He moved into the go-to-market architect role and feels his career has changed completely, now able to build solutions he never could before.
Go-to-market architect — A role that designs and builds technical solutions to support go-to-market (sales/marketing) work.
Account executive (AE) — A sales role responsible for managing and growing a set of customer accounts.
Class (Claude Draft) — Jared's email-management system that drafts customer emails using the Claude API, context, system prompts, and pattern matching.
System prompt — Instructions given to the model (here defining the user's name, role, and what they help customers with) that shape how it responds.
Context retrieval — Pulling in relevant information (via Google Docs integration or web URLs) so the model can ground its draft.
Pattern matching — Using past patterns of correct responses to guide how new email drafts are generated.
Claude API — Anthropic's API used behind the scenes by Class to generate email drafts.
If you told me I was going to be a go-to-market architect at Anthropic a year ago, I would be pretty surprised. I don't think I've ever had the technical chops to be in these conversations, but with Claude, I'm able to design and build things that allow me to see things differently.
As a startup account executive, you typically have a couple hundred. I think towards the end, I had about 600-700 accounts that I had to manage. I was probably working until 8:00-9:00 at night just answering emails back and forth, scouring through Slack, knowledge bases, Google Docs, Google Drives. That's when I asked myself the question, "How could I bring Claude in the loop?" I started developing Class to help me build solutions around generating emails to customers. Class is short for Claude Draft, that allows you to manage your inbox via hooking up to context knowledge, system prompt, and pattern matching.
Let me show you how to use Class. This is typically the workflow that an AE would go through. First, you need a system prompt. This is using the Claude API behind the scenes. I'm going to type my name, Jared. My role — there's a drop-down as you can see. Click on account executive. And what do I help customers with? And then I'll just generate a prompt. And then for the context retrieval, we're going to use our integration with Google Docs. This can also fetch web URLs. Being able to go to a Claude Doc website and generate context off of that. So for today, what we're going to do is just add a doc. And now, we're going to click onto an email. We'll click generate draft. And now, Claude is going to retrieve information from our website, our documentation, and also use the context that we have internally.
I can speak more technically with my customers using this system, which is great. I don't have to go over Slack. I don't have to go over Google Docs to figure out how I need to respond. Claude is able to load that at the top and essentially just start generating for me.
I would say Class is saving me probably at least 2-3 hours a day for answering emails, and probably thousands of emails have been sent by the Class system. I feel like with the technical barrier dissolving, I'm almost able to design more products and have senior engineers help me implement this to the final stretch. I was able to move into this role, go-to-market architect, and now my career, I feel like it's almost changed completely. I'm able to build solutions that I don't think I ever would have been able to.
TL;DR
- Jared, a go-to-market architect at Anthropic, describes how Claude let him move from a startup account executive role into a technical builder role he never thought he had the chops for.
- As an AE managing 600-700 accounts and working until 8-9pm answering emails, he built "Class" (Claude Draft), a system that drafts customer emails using the Claude API, a system prompt, context retrieval, and pattern matching.
- Class saves him 2-3 hours a day and has sent thousands of emails; with the technical barrier dissolving, he now designs products and has senior engineers help implement them, changing his career path entirely.
Takeaways
- Jared was a startup account executive managing roughly 600-700 accounts toward the end, often working until 8-9pm answering emails and scouring Slack, knowledge bases, Google Docs, and Google Drive.
- He asked himself how to bring Claude into the loop and built "Class" — short for Claude Draft — to manage his inbox.
- Class uses the Claude API behind the scenes, with a system prompt (role: account executive; what you help customers with), context retrieval via a Google Docs integration that can also fetch web URLs (including a Claude Doc website), and pattern matching.
- The workflow: set up a system prompt, add a doc for context retrieval, open an email, and click "generate draft"; Claude retrieves information from the website, documentation, and internal context to draft a reply.
- The system lets him speak more technically with customers without manually digging through Slack or Google Docs, since Claude loads the relevant context and starts generating.
- Class saves him at least 2-3 hours a day, and thousands of emails have been sent through it.
- With the technical barrier dissolving, he can design more products and have senior engineers help implement them to the final stretch.
- He moved into the go-to-market architect role and feels his career has changed completely, now able to build solutions he never could before.
Vocabulary
Go-to-market architect — A role that designs and builds technical solutions to support go-to-market (sales/marketing) work.
Account executive (AE) — A sales role responsible for managing and growing a set of customer accounts.
Class (Claude Draft) — Jared's email-management system that drafts customer emails using the Claude API, context, system prompts, and pattern matching.
System prompt — Instructions given to the model (here defining the user's name, role, and what they help customers with) that shape how it responds.
Context retrieval — Pulling in relevant information (via Google Docs integration or web URLs) so the model can ground its draft.
Pattern matching — Using past patterns of correct responses to guide how new email drafts are generated.
Claude API — Anthropic's API used behind the scenes by Class to generate email drafts.
Transcript
If you told me I was going to be a go-to-market architect at Anthropic a year ago, I would be pretty surprised. I don't think I've ever had the technical chops to be in these conversations, but with Claude, I'm able to design and build things that allow me to see things differently.
As a startup account executive, you typically have a couple hundred. I think towards the end, I had about 600-700 accounts that I had to manage. I was probably working until 8:00-9:00 at night just answering emails back and forth, scouring through Slack, knowledge bases, Google Docs, Google Drives. That's when I asked myself the question, "How could I bring Claude in the loop?" I started developing Class to help me build solutions around generating emails to customers. Class is short for Claude Draft, that allows you to manage your inbox via hooking up to context knowledge, system prompt, and pattern matching.
Let me show you how to use Class. This is typically the workflow that an AE would go through. First, you need a system prompt. This is using the Claude API behind the scenes. I'm going to type my name, Jared. My role — there's a drop-down as you can see. Click on account executive. And what do I help customers with? And then I'll just generate a prompt. And then for the context retrieval, we're going to use our integration with Google Docs. This can also fetch web URLs. Being able to go to a Claude Doc website and generate context off of that. So for today, what we're going to do is just add a doc. And now, we're going to click onto an email. We'll click generate draft. And now, Claude is going to retrieve information from our website, our documentation, and also use the context that we have internally.
I can speak more technically with my customers using this system, which is great. I don't have to go over Slack. I don't have to go over Google Docs to figure out how I need to respond. Claude is able to load that at the top and essentially just start generating for me.
I would say Class is saving me probably at least 2-3 hours a day for answering emails, and probably thousands of emails have been sent by the Class system. I feel like with the technical barrier dissolving, I'm almost able to design more products and have senior engineers help me implement this to the final stretch. I was able to move into this role, go-to-market architect, and now my career, I feel like it's almost changed completely. I'm able to build solutions that I don't think I ever would have been able to.