Build a mutual success plan canvas after the first customer call
Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Lusha, Zoom, and Slack Canvas connector output, but were not pulled from a live session. Run the prompt with your own call data and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.
CS teams usually start a new customer relationship with a “thanks for the call” email and a blank onboarding doc. This Claude prompt does it differently — Zoom pulls the kickoff call transcript, Lusha validates the full contact map, and a structured Mutual Success Plan lands in Slack as a Canvas within minutes of the call ending. The customer’s words, not the CS manager’s summary. Every commitment dated and owned. CS starts informed.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
A deal just closed and I've completed the first customer kickoff call on Zoom. Before I send a generic welcome email, I want to build a mutual success plan — a structured document in the customer's Slack channel that captures what success looks like for them, the milestones we agreed on, who owns what, and the first 90 days plan. CS should start the relationship with a document, not a blank page.
My kickoff call:
- Customer company: [COMPANY NAME]
- Zoom recording or transcript: [ZOOM MEETING ID OR "FIND MOST RECENT ZOOM CALL WITH [COMPANY]"]
- CS owner: [CS MANAGER NAME]
- AE who closed: [AE NAME]
- Slack channel: [CHANNEL NAME — e.g. #customer-[company] or #cs-handoffs]
- Contract start date: [DATE]
- ACV: [DOLLAR AMOUNT]
</context>
<task>
1. Pull the transcript from the most recent Zoom call with this customer:
- What did the customer say success looks like in 90 days — in their exact words
- What specific outcomes or metrics did they mention
- What milestones or timelines were discussed
- What concerns or risks did the customer raise about the implementation
- What did the CS owner commit to delivering and by when
- What did the customer commit to doing on their side
2. Use Lusha to validate and map all contacts at the account:
- Primary contact: confirmed title, email, direct phone
- Any other contacts who were on the kickoff call
- Any new stakeholder who appeared on the call but wasn't the main buying contact
3. Build a Mutual Success Plan and post it as a Slack Canvas:
## Mutual Success Plan — [Company Name]
CS Owner · AE · Contract start · ACV
## What Success Looks Like
In the customer's own words — pulled from the Zoom transcript
## 90-Day Milestones
Milestone · Owner (customer or CS) · Target date · Status (Not started)
## Our Commitments to [Company]
Everything CS committed to on the kickoff call — specific, dated
## [Company]'s Commitments
Everything the customer committed to doing — specific, dated
## Key Contacts
All verified contacts from Lusha — name, title, email, role in the relationship
## Open Questions
Anything raised on the call that wasn't resolved
## Risks to Watch
Any concern or risk the customer mentioned — monitor these early
## Next Check-in
Date and agenda for the next scheduled call
4. Tag the CS owner and AE in the Canvas post.
5. Draft a one-paragraph email to the customer summarising the mutual success plan and linking to the Canvas.
</task>
<constraints>
- What Success Looks Like must use the customer's exact words from the transcript — not a paraphrase.
- Every commitment must have a specific owner and date — not "soon" or "shortly."
- If the Zoom transcript isn't available yet: flag it and build the Canvas structure without the content — ready to fill in once the transcript processes.
- The Canvas is a living document — structure every section for easy weekly updates.
</constraints>What you'll get back
The situation: A CS manager has just completed the first kickoff call with Ashford Platforms — a $95K customer. The Zoom transcript is available. Running the prompt immediately after the call.
Slack Canvas — posted to #customer-ashford · @marcus.cs @sarah.ae
Mutual Success Plan — Ashford Platforms
CS Owner: Marcus · AE: Sarah · Contract start: June 1, 2026 · ACV: $95K
What Success Looks Like
In D.R.’s words from the kickoff call:
“By the end of Q3 I want our new SDRs ramping in 3 weeks instead of 8. Right now they’re spending the first month just building lists manually — that’s the thing I need fixed most. If the data layer is there when they start, the ramp problem goes away.”
90-Day Milestones
| Milestone | Owner | Target date | Status |
|---|---|---|---|
| HubSpot connector live and tested | CS | June 14 | Not started |
| First SDR cohort onboarded with data pre-loaded | Customer (D.R.) | June 21 | Not started |
| 30-day ramp review — compare to baseline | CS + Customer | July 1 | Not started |
| Full team rollout — all AEs and SDRs | Customer (M.L.) | July 15 | Not started |
| 90-day ramp metric review vs 8-week baseline | CS + Customer | August 31 | Not started |
Our Commitments to Ashford Platforms
- HubSpot connector setup documentation sent by June 7 · Owner: Marcus
- Technical setup call with M.L. and IT scheduled for week of June 9 · Owner: Marcus
- SDR onboarding template pre-populated with Ashford’s ICP criteria · Owner: Marcus · Due: June 14
- 30-day check-in call scheduled in Calendar by June 3 · Owner: Marcus
Ashford Platforms’ Commitments
- D.R. to confirm IT contact for HubSpot connector call by June 5 · Owner: D.R.
- M.L. to share the current SDR onboarding checklist so CS can map the data layer · Owner: M.L. · Due: June 7
- D.R. to provide baseline ramp data (current 8-week average) for 30-day comparison · Owner: D.R. · Due: June 10
Key Contacts
| Contact | Title | Role | Contact |
|---|---|---|---|
| D.R. | Head of Sales Strategy & Ops | Primary contact, success sponsor | d.r@[ashford].com ✓ |
| M.L. | Head of Sales Operations | Technical implementation lead | m.l@[ashford].com ✓ |
| ⚠ IT contact | TBD | HubSpot connector setup | D.R. to provide by June 5 |
Open Questions
- Which HubSpot instance is the primary — Ashford has two workspaces mentioned on the call. D.R. to clarify.
- Will procurement need to countersign the DPA? D.R. said “probably not” but couldn’t confirm.
Risks to Watch
- SDR onboarding cohort starts June 17 — connector must be live by June 14 or the milestone slips.
- D.R. mentioned the IT team at Ashford “can be slow to respond.” Flag if HubSpot connector call doesn’t get scheduled by June 9.
Next Check-in
30-day review — July 1, 10am · D.R. and M.L. · Agenda: ramp data comparison vs baseline
Draft email to customer
To: d.r@[ashford].com · m.l@[ashford].com Subject: Ashford Platforms — Mutual Success Plan
Hi David and Michael,
Following today’s kickoff call, I’ve put together our Mutual Success Plan in our shared Slack channel — it captures what success looks like by Q3, the 90-day milestones we agreed on, and every commitment on both sides with dates. [Link to Canvas]
First action from my side: HubSpot connector documentation by June 7. From your side: the IT contact for the setup call by June 5.
Looking forward to the 30-day review on July 1.
Marcus
88 words.
Illustrative example — fictional company names used. Run with your own Zoom transcript and customer data to see live results.
Why use Lusha in Claude
The “What Success Looks Like” section is the most important part of this Canvas — and the hardest to get right without a transcript. D.R.’s exact words — “our new SDRs ramping in 3 weeks instead of 8” — are the success metric the CS manager now owns. Paraphrasing loses the specificity. A generic “improve SDR ramp time” is unmeasurable. D.R.’s language is the benchmark CS is accountable to at the 90-day review. Zoom holds the exact words. The Canvas holds the commitment. The 30-day review date is already in the Calendar. None of this requires a separate doc, a follow-up email asking for notes, or a verbal debrief from the AE.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
What if the Zoom transcript isn't ready yet?
Zoom typically processes transcripts within 10–15 minutes. If the transcript isn’t available, the prompt flags it and builds the Canvas structure with empty sections — headers, milestone table, commitment rows — ready to fill in once the transcript processes. The structure is still useful: the CS manager can open the Canvas and start filling in manually while the transcript loads.
Should I share the Canvas with the customer?
The Canvas is internal — posted to the CS team’s Slack channel. The draft email at the end summarises the plan and links to the Canvas for internal reference. If a customer-facing version is needed, copy the relevant sections into a Google Doc and share that. The Canvas is the internal source of truth; the email summary is what goes to the customer.
What if the customer didn't articulate success clearly on the kickoff call?
The transcript section returns what was actually said. If success wasn’t defined clearly on the call, the Canvas flags “success definition not captured on this call — schedule a follow-up conversation with D.R. to establish metrics before the 30-day review.” That’s a better outcome than inventing a success definition the customer never agreed to.
How is this different from the closed-won CS brief?
The closed-won CS brief posts a Slack message immediately when a deal closes — it’s a handoff document based on the sales thread. This play runs after the first kickoff call and builds a forward-looking Mutual Success Plan based on what the customer said on the call. Different timing, different source, different purpose. Run the closed-won brief at close; run this play after the kickoff.
Can I use this for renewal or expansion conversations?
Yes — the same structure works for a renewal kickoff or an expansion planning call. Change the context field to “renewal planning call” or “expansion scoping call” and the sections adjust: success definition becomes “what does the expanded use case need to deliver,” milestones reflect the new scope, and commitments capture the renewal or expansion terms discussed.
Ready to build this?
Get started with Lusha and set up this play in minutes.
