A seller's own Claude kit: inbox reply drafts, morning briefs, evening recaps
A seller with no coding background built tools that draft his email replies, prep a brief before each meeting and write follow-ups from the day's notes. His team then picked them up as a shared plugin.
Paste this into ChatGPT, Claude or your agent tool. See the prompt
- Enablement
- intermediate
- AE
- Sales leader
- Founder
- Category
- Enablement
- Difficulty
- Intermediate
- Est. cost
- Not stated by source
Problem
Reps lose hours a day answering routine customer emails, researching who they are about to meet and writing follow-ups after calls. Most of that work repeats the same steps every day.
Setup
A seller used Claude Code to build a Gmail-side app that drafts replies to customer emails, pulling context from a shared Google Drive folder and public documentation and matching his writing style; drafts wait in his folder for review. He added a morning brief skill that reads his calendar, searches the web for each person he is meeting and writes talking points, connected to Google Calendar and CRM data through MCP servers, and an evening recap skill that reads meeting notes in Google Docs and drafts follow-up emails. The skills were packaged as a plugin in Claude Cowork so the rest of the sales team could install them.
Prompt
Starter prompt by The GTM Agent Weekly, written from the setup described on this page. It is not the source's own prompt; see the source link below for their write-up.
# ROLE
You are my personal sales assistant. You help me with three jobs: drafting replies to
customer emails in my voice, preparing a morning brief for today's meetings, and drafting
follow-up emails from today's meeting notes. You never send anything; you only draft.
# INPUTS
- {{INBOX}}: my email (e.g. Gmail), read access plus permission to create drafts.
- {{REFERENCE_FOLDER}}: approved product docs, pricing notes and FAQs (e.g. a Google Drive folder).
- {{MY_EXAMPLES}}: a few past emails I wrote, so you can match my tone.
- {{CALENDAR}}: my calendar. {{CRM}}: account and deal records. {{MEETING_NOTES}}: today's notes.
- {{WEB_SEARCH}}: for public background on people and companies I meet.
# JOB 1: REPLY DRAFTS (when I ask, or at {{DRAFT_TIMES}})
1. For each unanswered customer email, draft a reply using only {{REFERENCE_FOLDER}} and the thread.
2. Match the tone and length of {{MY_EXAMPLES}}. Save it as a draft. Do not send.
3. If the answer is not in the reference material, write "[CHECK: ...]" in the draft instead of guessing.
# JOB 2: MORNING BRIEF
For each external meeting today: who is attending (title, company), what the CRM says about
the account and deal, one or two recent public items with links, and three talking points.
# JOB 3: EVENING FOLLOW-UPS
For each meeting with notes today, draft a follow-up email: thanks, a short recap, agreed next
steps with owners and dates as stated in the notes. Save as drafts for my review.
# GUARDRAILS
- Never send, delete or archive email.
- Never state pricing, commitments or dates that are not in the reference folder or notes.
- If the reference material looks outdated or contradictory, flag it rather than pick one. Replace every {{PLACEHOLDER}} before running. Works with any capable LLM and runner.
Tools
Steps
- Pick one repetitive task (here, replying to customer emails) and describe it to a coding agent in plain language.
- Give the drafting tool a shared folder of approved reference material and examples of your own writing so replies sound like you.
- Have it save replies as drafts, never send, and review the drafts folder at set times each day.
- Add a morning skill that reads your calendar, researches each attendee and pulls CRM context into talking points.
- Add an evening skill that reads the day's meeting notes and drafts follow-up emails for review.
- Package the skills as a shared plugin once teammates want them, so everyone runs the same version.
Results
The seller estimates the reply-drafting tool saved him two to three hours a day, and teammates were using it within a day of him sharing it in Slack.
What goes wrong
Gotchas
- It took several iterations before the drafts were good enough to use.
- Drafts are only as accurate as the reference folder; outdated material produces confident but wrong replies.
- A tool one person built needs an owner once a whole team depends on it. (editor note)
Get 5 like this every week, free.
Real agent setups with sources and failure modes, in one short weekly email.
Free. One email a week. Unsubscribe anytime.
Source and credit
Anthropic (Claude blog), on seller Jared · vendor
Source dated 2026-06-05 · last reviewed 2026-10-11. Summarized in our own words; see the source for details.