How a 50-Call-a-Day Florist Uses Grain + Claude for Coaching, Context, and Follow-Ups
Four AI workflows built for a sales team where every customer is new, bookings happen a year out, and there's no time to watch calls. With exact prompts and verbatim quotes from the discovery session.
TL;DR
- Poppy Flowers records approximately 50 virtual sales meetings per day across 9 salespeople, all connected to Grain.
- Their sales director was spending 1 to 1.5 hours manually reviewing calls to coach reps, before discovering instant Claude coaching analysis.
- Claude can pull scorecards from any rep's last 7 days and generate a pattern summary in seconds, no manual review needed.
- When clients book a year in advance, reps can search by name or email to recover full context from calls that happened 12 months ago, on demand.
- Connecting Claude to Gmail and running a scheduled end-of-day task drafts every follow-up email automatically, leaving the rep to review and send.
- Grain trackers plus a scheduled Claude task can auto-collect customer testimonials and update a highlight reel every week or month, without manual curation.
Why AI advice for sales teams usually misses the mark
Most content about AI in sales assumes you're in SaaS. Long deal cycles, multiple touchpoints, lots of context to carry from call to call. Your AI tools are supposed to help you remember what you talked about last quarter, prep for the expansion call, and surface patterns across twelve months of a customer relationship.
Poppy Flowers doesn't work that way.
They're a nationwide wedding florist. Nine salespeople. About 50 virtual calls a day, all recorded in Grain. One conversation per customer, usually. Book your wedding flowers a year in advance, and by the time the wedding arrives, the team needs a clear picture of what the client’s expectations were.
One rep from our team noted it directly: "You're probably the first non-SaaS call I've had."
That's actually the most interesting part of this conversation. The workflows that work for Poppy Flowers work precisely because even though they have long relationships with clients from making the sale through the wedding day, that sale is most likely done in one design meeting. Every recording has to stand on its own. They have to get value from each individual call, immediately, or that value is gone.
The four workflows below come from a live discovery call. None of them require technical setup beyond connecting Claude to Grain via MCP.
What is Grain Claude sales coaching?
Grain Claude sales coaching is the practice of using Claude's access to your Grain workspace (via MCP) to query coaching scorecards, surface call patterns, and generate rep feedback on demand, without manually watching recordings. Claude reads the scoring data Grain already generates, then synthesizes it into summaries, pattern reports, and improvement recommendations.
Workflow 1: Instant coaching analysis
What it is: Replacing manual call review with Claude-generated scorecards and pattern summaries pulled directly from Grain's coaching data.
Inspired by: Poppy Flowers sales coaching workflow. Build time: A few minutes once Grain's coaching feature is enabled. Replaced: 1-1.5 hours of manual call review per coaching session.
The old way
Michelle was spending an hour to 90 minutes reviewing two or three calls to coach reps.
Before Claude was around, I would have to watch their calls. I would watch like two or three of them. That's like an hour of my time, an hour and a half. And then see what they need to improve. But how can we do that faster.
The team is on Grain's business plan, which automatically scores external sales calls. The scores exist. The patterns exist. But surfacing them required watching.
The prompt
Pull coaching scorecards for [rep name] from the past 7 days.
Show me calls where the score was below 4.
Give me the key issues per call and a pattern summary across all of them.
How it runs
- Claude queries Grain for the rep's recent calls with low coaching scores.
- It returns a list of flagged calls with key issues.
- It generates a cross-call pattern summary: what's happening consistently, what's an outlier.
- The manager reviews the summary in minutes. No watching required.
Reps can also run this on their own calls. Self-coaching becomes possible without waiting for a manager.
What it produces
A list of flagged calls. Key issues per call. A cross-call pattern summary. All in seconds.
It'll give me the key issues and things that I should work on and then give me like a kind of TLDR key pattern summary. And this happens like pretty much instantaneously. You don't have to watch any.
Why this is worth copying
If you have Grain's coaching scorecards running, you already have the data. You're just not surfacing it efficiently. Claude turns three hours of async review into a three-minute read, and it works whether the manager pulls it or the rep pulls it themselves.
Workflow 2: Year-old client context on demand
What it is: Searching Grain by client name or email to recover full call context from recordings made up to a year ago, without opening the recording or skimming manually.
Inspired by: Poppy Flowers' year-ahead booking cycle. Build time: Zero — it's a prompt. Replaced: Manual recording search or starting a follow-up call without context.
The problem
Weddings are booked 12 months out. The rep takes the initial sales call. Then a year later, our team designs the wedding. All florists book in advance, and here at Poppy, we are using these tools to make sure there's total continuity across the lifecycle of a client.
I might have had their sales call with this client a year ago. And just now do we need to do the design work to make the wedding happen. Having the recordings in place and being able to ask Claude for the details is a priceless efficiency hack.
Michelle's instinct was exactly right: "I'm imagining they could open Claude and just say, tell me what I talked about with Amanda Smith about her bridal bouquet."
The prompt
Search my Grain meetings for conversations with [client name].
Give me a summary of what we discussed — what they wanted, any specific requests, what was agreed.
[Optional: I think the call was around May 2025.]
Or, to search without using Claude tokens at all, Grain's native search handles this by email address directly.
How it runs
- Rep types the client's name or email into Claude.
- Claude searches Grain transcripts. Providing a date range helps narrow the search if the default 50-call window doesn't reach that far back.
- Claude returns a summary of what was discussed, including specific requests, concerns, and any commitments made.
What it produces
The key details from the original call: what was requested, what concerns were raised, what was agreed. Without opening the recording or reading the full transcript.
Why this is worth copying
Any business with long-cycle transactions (real estate, legal, accounting, events) faces this problem. You took a great call. The context decayed. Claude and Grain is a way to get it back. For Poppy Flowers, it means a rep can walk into a year-old sale with full context in 30 seconds.
ƒWorkflow 3: End-of-day follow-up drafts
What it is: A scheduled Claude task that drafts follow-up emails for every call in the last 24-48 hours, connected to Gmail, ready for the rep to review and send.
Inspired by: Our rep's own daily CSM workflow. Build time: 10-15 minutes to connect Gmail and write the task prompt. Replaced: 20-30 minutes per rep per day of follow-up writing.
The workflow
Connect Claude to Gmail. Set a scheduled task that runs at the end of the workday. Claude looks at today's Grain recordings, drafts a follow-up email for each one, and queues them for review.
At the very end of my day after I've had all of my demo calls or meetings like that, I'll have it draft some follow-up emails for me. And then at least I have a chance to review it and then before sending it out. It saves me so much time from actually doing the follow-up emails myself after every call.
The scheduled task
At end of day:
- Pull all Grain recordings from today
- For each recording, draft a follow-up email to the client
- Reference 2-3 specific things from the call
- Include any next steps or action items
- Tone: warm, direct, under 150 words
- Queue drafts in Gmail for my review
What it produces
A draft email per call. The rep reviews, edits if needed, and sends. The raw follow-up writing time drops to near zero.
CRM note
This doesn't require the Claude + ActiveCampaign connector (which needs API-level setup). For simpler automations like pushing meeting notes to a CRM, Zapier handles that independently. Claude is best for the drafting and interpretation work; Zapier is best for the simple data transfer.
Why this is worth copying
Follow-up is the highest-value, lowest-completion task in most sales teams. Automated drafts remove the blank-page friction. Reps still review and own the send. The relationship stays human. The busywork doesn't.
Workflow 4: Auto-updating testimonial reel
What it is: A Grain tracker plus a scheduled Claude task that automatically collects customer testimonial moments from calls and updates a shared story every week or month, without any manual curation.
Inspired by: Poppy Flowers' need to build social proof from happy wedding clients. Build time: 20-30 minutes to set up tracker and scheduled task. Replaced: Manual clip curation, which mostly wasn't happening at all.
The workflow
Set up a Grain tracker with keywords or phrases your happiest customers use. "This is exactly what I wanted." "You've made this so easy." "I'm so glad we went with you." When calls trigger the tracker, a scheduled Claude task finds those clips, creates highlights, and adds them to a Grain story automatically.
You can set up a tracker for customer feedback. Set up a keyword or key phrase where customers are indicating that they have like very positive feedback. Then you can have Claude set up a scheduled task where it'll search for whenever these trackers were triggered and then create a clip of it, update it in the story for you. Like every week or month or something like that.
How it runs
- Create a Grain tracker with your testimonial keywords.
- Set a scheduled Claude task: "Search for calls where my customer feedback tracker was triggered this week. Create clips from those moments. Add them to my Testimonials story."
- Claude runs the task on its schedule, adding new clips automatically.
- The Grain story (a collection of clips) grows with every triggered call.
What it produces
A self-curating testimonial library that grows every time a happy customer says something worth keeping. Can be shared externally, embedded on a website, or used for new-hire sales training to show what great looks like.
"Oh, that's cute," Michelle said when our rep showed the demo. "You can put together like a highlight reel or a presentation of just the clips and customer feedback."
Why this is worth copying
Customer testimonials are usually gathered manually, if at all. Most teams capture great moments in calls and let them disappear. This turns every recorded call into a potential source of social proof, with no additional work after the one-time setup.
Comparing the four workflows
The pattern across all four
They work on single recordings, not sequences. None of these require prior context or multi-call history. Each workflow extracts full value from one recorded call. That's what makes them work for any sales team, not just long-cycle SaaS.
They reduce the time after the call. The hard part isn't having the call. It's the coaching review, the follow-up email, the context recovery a year later. All four workflows compress or automate the gap between the call ending and the next useful action.
They work without technical setup. Connecting Claude to Grain via MCP and Gmail takes minutes. The tracker setup is the most involved piece, but our walked through it live without notes. If your team has someone who handles ops or tools, they can configure it once for everyone.
They're as useful to reps as to managers. Reps can pull their own coaching analysis. Reps can search their own old calls. The manager gets a reporting view. Reps get a coaching tool. Both get time back.
What to try this week
- New to Grain + Claude? Start with the coaching analysis workflow. Ask Claude to pull your team's last 7 days of scorecard data and give you a pattern summary. See what it flags in five minutes.
- Sales leader trying to cut coaching time? Pull scorecards for your two lowest-performing reps. Have Claude write up the key patterns. Compare against what you'd have found watching their calls.
- Rep with long-cycle clients? Try the context retrieval workflow before your next follow-up call. Ask Claude to find what you discussed with a specific client 6-12 months ago.
- Not technical? Start with follow-up drafts. Connect Gmail to Claude and ask it to draft a follow-up from your last call. Review it, edit it, send it. That's the whole workflow.
Frequently asked questions
What is Grain Claude sales coaching and how does it work?
Grain Claude sales coaching uses the Grain MCP connector to give Claude access to your Grain workspace. Claude can read coaching scorecards that Grain automatically generates for your calls, then surface patterns, flag issues, and write rep feedback on demand, without anyone watching the recordings. It runs from the Claude interface once the connector is set up.
Does Claude search all my Grain recordings or just recent ones?
By default, Claude searches about 50 calls. You can ask Claude to search beyond that limit, and it will, though it uses more tokens. For most coaching and follow-up workflows, 50 calls is enough. For older recordings, providing a date range (or a rough timeframe like "around May 2025") helps Claude narrow the search without scanning everything.
Can reps use Claude coaching analysis on their own, without a manager pulling the data?
Yes. Reps can connect their own Claude account to Grain and pull their own scorecard data and pattern summaries. Teams on a Claude team plan can also build a shared skill that all reps run, so no one has to set up their own workflow from scratch.
Does Claude replace Grain's built-in coaching tab?
No. Grain's coaching tab still runs and auto-scores calls. Claude is a faster way to surface insights from that data. The scores and sessions are all still in Grain. You're not duplicating the coaching feature, you're querying it more efficiently.
What CRM integrations work with Grain + Claude?
Grain doesn't have a direct integration with all CRMs, but Zapier bridges most of the gap. For simple automations like pushing meeting notes or action items to a CRM, Zapier is the recommended path. Claude handles the drafting and interpretation work. The two tools serve different roles and work well together.
Can Claude pull client context from calls that happened a year ago?
Yes. Providing a date range or rough timeframe helps Claude narrow the search. You can also search Grain by client email address directly, without going through Claude, which avoids any token usage. That works well for simple lookups where you just need to find the right recording.
How do Grain trackers work with the testimonial workflow?
Grain trackers monitor calls for specific keywords or phrases you define. When a call triggers the tracker, Claude can be scheduled to find those clips, create highlights from the triggered moments, and add them to a named Grain story automatically. You define the tracker keywords and the Claude task once. After that, it runs on its own.
Is this accessible for non-technical sales reps?
The coaching analysis, context retrieval, and follow-up draft workflows require no technical setup. You connect Claude to Grain and write a prompt. The testimonial tracker involves setting up a Grain tracker (five to ten minutes) and a scheduled Claude task, which a manager or ops person can configure once for the whole team.
What Grain plan do I need for coaching scorecards?
Coaching scorecards are available on Grain's Business plan. On that plan, external calls are automatically scored, and Claude can query that scoring data without any additional setup.
Can I build a shared Claude skill for my whole team?
Yes. If you have a Claude team plan, you can create a shared skill that all reps run. Individual setups also work and let each rep customize their own outputs. Michelle was asking exactly this question about how to roll out workflows to her nine-person team without making each rep build their own.
Resources
- Set up the Grain MCP connector: developers.grain.com/mcp
- Book a demo with Grain: grain.com/live-demo
If your team has built something that isn't on this list, we'd want to hear about it.
