You are an enterprise B2B sales strategist writing for complex, multi-stakeholder deals. Task: Create a contrarian cold email for a target buyer. Inputs: - Company: [COMPANY] - Industry: [INDUSTRY] - Persona / title: [TITLE] - Trigger or context: [TRIGGER OR SITUATION] - Likely pain: [PAIN] - Business impact: [RISK, COST, DELAY, REVENUE IMPACT, COMPLIANCE IMPACT] - Solution / offer: [SOLUTION] - Desired next step: [CTA] Requirements: - Make the message specific, credible, and useful - Tie the opening to a trigger, pattern, or business issue - Connect pain to a measurable business consequence - Use plain language, no hype, no buzzwords, no generic personalization - Keep the core message concise and written for a busy executive or functional leader - If relevant, include 2 subject line options or 2 message variants Output: 1. Final version 2. Why this angle should work 3. One lighter CTA option and one stronger CTA option

Analyze these sales call notes using MEDDIC framework: [Paste your call notes here] Score each category 0-10 and tell me what's missing: 1. **Metrics:** Did we quantify the problem in dollars or hours? 2. **Economic Buyer:** Do we know who signs the contract and have we talked to them? 3. **Decision Criteria:** What are they evaluating us on? (price, features, security, etc.) 4. **Decision Process:** Who needs to approve? What's the timeline? 5. **Identify Pain:** Is this a real urgent problem or just nice-to-have? 6. **Champion:** Do we have an internal ally selling for us when we're not in the room? For each low score (below 7), tell me what question to ask in the next meeting. Example Metrics (4/10): They said "takes too long" but no specific hours or cost. → Next call, ask: "If we cut this down by 50%, how many hours per week does that free up? What's your team's hourly cost?" Economic Buyer (2/10): Only spoke with manager. VP of Operations signs contracts over $25K. → Red flag! Ask your contact: "Who needs to approve this purchase? Can you introduce me?" Tips ● A score below 7 in any area means you have homework before the next call ● Re-score after every meeting to track deal progression ● If Champion and Economic Buyer are both below 5, seriously consider whether to invest more time

You are a senior enterprise sales coach. I have a deal that is stuck and I need your honest assessment. Deal details: ● Company: [INSERT] ● Deal size: [INSERT] ● Stage: [INSERT] ● Days in stage: [INSERT] ● Close date: [INSERT] ● Champion: [INSERT / none] ● Economic buyer engaged: [Yes/No] ● Last meaningful activity: [INSERT] ● What I think the blocker is: [INSERT] Please: 19. Tell me the most likely real reason this deal is stuck 20. Identify what I am probably missing (champion, business case, urgency, etc.) 21. Give me 3 specific actions to take in the next 7 days 22. Tell me honestly — should I keep investing or qualify this out?

I am a [YOUR ROLE] and I just closed a deal with [customer name]. I need to create a thorough internal handoff document for [CS manager name], the assigned Customer Success Manager, so they can onboard this customer with full context and set the account up for long-term success. Contract details: ● AE: [AE name] ● ACV: [contract details — ACV, term, start date, billing structure] Customer contacts: ● Primary Day-to-Day Contact: [primary contact and role] ● Executive Sponsor: [executive sponsor and role] ● Full Stakeholder Map: [full stakeholder map — names, titles, roles in the deal, and disposition] (e.g., "Sarah Chen, VP Ops — Champion, highly engaged; Tom Liu, IT Director — Supportive but cautious on timeline; James Park, CFO — Signed off but skeptical, needs ROI proof at 90 days; Nina Patel, End User Lead — Was not involved in evaluation, will need onboarding attention") Business context: ● Original Business Problem: [original business problem and quantified pain] ● Agreed Success Metrics: [success metrics agreed during the sale] ● What They Bought (and didn't buy): [product capabilities purchased and any features explicitly excluded] ● Competitive Alternatives Evaluated: [competitive alternatives they evaluated and why they chose us] Technical context: ● Implementation Requirements: [implementation requirements and technical environment] (e.g., "Integrate with Salesforce (Enterprise edition), SSO via Okta, data migration from legacy system, API connection to their data warehouse") Deal dynamics (critical for CS): ● Known Risks, Sensitivities, or Political Dynamics: [known risks, sensitivities, or political dynamics] (e.g., "CFO was the last to approve and set a hard 90-day ROI checkpoint; IT team is stretched thin with another migration; the VP of Sales who championed this reports to a new CRO who wasn't involved in the evaluation") ● Promises Made During the Sales Process: [promises made during the sales process — explicit and implied] (e.g., "Committed to a dedicated onboarding specialist for the first 30 days; implied we could customize the dashboard layout; told them implementation would be 'about 6 weeks'") ● Expansion Opportunities: [expansion opportunities identified but not sold] Key dates: ● [key dates — go-live target, first QBR, renewal date] Generate a comprehensive Post-Sale Handoff Document with the following sections: 85. **Account Overview & Deal Summary:** A concise summary of who the customer is, what they bought, the contract structure, and why they bought. This should give the CSM a complete picture in 60 seconds. 86. **Stakeholder Intelligence Brief:** For each stakeholder, provide: - Their role in the organization and in this deal (Champion, Economic Buyer, Technical Evaluator, End User, Blocker, etc.) - Their communication style and preferences (if known) - Their personal win — what they individually care about getting from this solution - Their current disposition (Enthusiastic, Supportive, Neutral, Skeptical) - Recommended CS engagement approach for each person 87. **Success Criteria & Measurement Plan:** A clear definition of what "success" looks like for this customer, including: - The specific metrics they expect to improve (with baseline numbers from discovery) - The timeline for when they expect to see results - How success will be measured and reported - Who on the customer side is accountable for each metric - A recommended QBR cadence and agenda framework 88. **Promises & Commitments Register:** A detailed log of every commitment made during the sales process — both explicit contractual commitments and informal verbal commitments. For each, note: - What was promised - Who it was promised to - When it was promised - Current status (fulfilled, pending, or at-risk) - Owner on our side responsible for delivery This section is critical. Broken promises are the #1 cause of early churn. 89. **Risk Register & Early Warning Signals:** A list of known risks to the account's success, including: - Political risks (org changes, skeptical stakeholders, champion dependency) - Technical risks (complex integrations, resource constraints, data quality) - Adoption risks (change management gaps, end-user resistance, competing priorities) - Timeline risks (aggressive go-live date, dependency on customer-side resources) For each risk, provide a severity level, a trigger signal to watch for, and a recommended mitigation action. 90. **Implementation & Onboarding Roadmap:** A recommended phased onboarding plan including: - Phase 1 (Week 1-2): Technical setup, integrations, data migration - Phase 2 (Week 3-4): Admin training, workflow configuration, pilot user group - Phase 3 (Week 5-6): Full user rollout, end-user training, go-live - Phase 4 (Week 7-12): Adoption monitoring, optimization, first QBR Include specific milestones, owners, and dependencies for each phase. 91. **Expansion & Growth Roadmap:** A forward-looking view of where this account can grow, including: - Products or modules they didn't buy but showed interest in - Additional teams, departments, or business units that could benefit - Trigger events or success milestones that would open the expansion conversation - Recommended timing for the first expansion discussion 92. **Warm Introduction Plan:** A script for the AE to use when introducing the CSM to the customer's primary contact and executive sponsor, designed to: - Transfer credibility and trust from the AE to the CSM - Reinforce the customer's decision to buy - Set expectations for the CS relationship - Position the first onboarding call Example Input: ● Customer Name: Apex Logistics ● CS Manager: Jordan Rivera ● AE: Lauren Mitchell ● Contract: $220K ACV, 3-year term, annual billing, starts April 1, 2026 ● Primary Contact: Derek Huang, Director of Fleet Operations ● Executive Sponsor: Patricia Morales, COO ● Stakeholder Map: Derek Huang, Director of Fleet Ops — Champion, highly engaged, drove the ● evaluation; Patricia Morales, COO — Executive Sponsor, supportive, wants quarterly updates on ROI; ● Kevin Tran, VP of IT — Technical Evaluator, supportive but firm on security requirements; Aisha ● Johnson, Fleet Manager (Southeast Region) — End User Lead, was part of the pilot, enthusiastic; Bill ● Crawford, CFO — Signed off reluctantly, set a hard 6-month ROI review; Maria Santos, VP of HR — Not ● involved in evaluation, but her team will be impacted by workflow changes ● Original Business Problem: Manual route planning costing $1.8M/year in excess fuel, overtime, and ● missed deliveries across 400 vehicles in 3 regions ● Success Metrics: Reduce fuel costs by 15%, cut route planning time from 4 hours to 30 minutes per day, ● improve on-time delivery rate from 91% to 97% What They Bought: Route optimization platform (all 3 regions), real-time GPS tracking, driver mobile app, analytics dashboard. Did NOT buy: predictive maintenance module, customer delivery notifications Competitive Alternatives: RouteMaster ($160K/year, weaker optimization algorithm) and manual expansion of existing spreadsheet process Implementation Requirements: Integrate with SAP TM (transportation management), GPS hardware already installed on 380 of 400 vehicles (20 need retrofitting), SSO via Azure AD, historical route data migration (2 years) Known Risks: CFO set a hard 6-month ROI checkpoint; IT team is simultaneously migrating to a new ERP; 20 vehicles need GPS hardware installed before full go-live; Southeast region (Aisha's team) is enthusiastic but Northeast region has not been involved yet; Patricia reports to a new CEO who started in January and wasn't involved in the deal Promises Made: Dedicated implementation manager for first 60 days; told Derek route planning time would drop to "under 30 minutes" by Week 6; committed to a custom analytics dashboard view for Patricia's monthly board report; implied we could integrate with their future ERP (SAP S/4HANA migration planned for Q4) Expansion Opportunities: Predictive maintenance module ($45K/year) — Derek expressed strong interest for Year 2; customer delivery notifications ($30K/year) — Patricia mentioned this as a future priority; 2 additional distribution centers opening in Q1 2027 Key Dates: Go-live target May 15, 2026; first QBR August 1, 2026; 6-month ROI review October 1, 2026; renewal date April 1, 2029 Output: Post-Sale Handoff Document — Apex Logistics Prepared by: Lauren Mitchell (AE) → For: Jordan Rivera (CSM) Date: March 28, 2026 1. Account Overview & Deal Summary Customer: Apex Logistics — mid-market logistics company operating 400 vehicles across 3 U.S. regions (Southeast, Northeast, Central). What They Bought: Route optimization platform with real-time GPS tracking, driver mobile app, and analytics dashboard for all 3 regions. 3-year term, $220K ACV, annual billing, starting April 1, Why They Bought: Manual route planning was costing them $1.8M/year in excess fuel, driver overtime, and missed deliveries. Their Director of Fleet Operations, Derek Huang, championed the evaluation after calculating that their route planners were spending 4 hours per day building routes in spreadsheets. The COO, Patricia Morales, sponsored the deal because on-time delivery had dropped to 91% and was becoming a customer retention issue. Why They Chose Us Over Alternatives: RouteMaster was $60K/year cheaper but their optimization algorithm couldn't handle Apex's multi-stop, multi-constraint routing (temperature-controlled + timewindow deliveries). The internal spreadsheet expansion was rejected by Derek as unsustainable at scale. What They Did NOT Buy: Predictive maintenance module and customer delivery notifications. Both are expansion opportunities (see Section 7). 2. Stakeholder Intelligence Brief Derek Huang — Director of Fleet Operations ● **Deal Role:** Champion. Drove the entire evaluation, built the internal business case, and personally ● presented to the CFO. ● **Communication Style:** Data-driven, detail-oriented, prefers email with supporting documentation. ● Responds quickly. Likes to be consulted before decisions are made, not informed after. ● **Personal Win:** He wants to be seen as the person who modernized Apex's fleet operations. A successful rollout strengthens his case for a VP promotion. **Disposition:** Enthusiastic — deeply invested in the success of this project. **CS Approach:** Treat Derek as your primary partner. Give him early visibility into metrics so he can report wins up the chain. He will be your best internal advocate if he feels informed and respected. Patricia Morales — COO (Executive Sponsor) ● **Deal Role:** Executive Sponsor. Approved the budget and set the strategic direction. Wants ROI data ● for her monthly board report. ● **Communication Style:** High-level, outcome-focused. Does not want to be in the weeds. Prefers a ● monthly 15-minute update or a polished dashboard she can pull from herself. ● **Personal Win:** She needs to show the board that operational efficiency is improving under her leadership. On-time delivery rate is her marquee metric. **Disposition:** Supportive — trusts Derek's judgment, but will disengage if she doesn't see results surfaced proactively. **CS Approach:** Build the custom board report dashboard early (this was a promise — see Section 4). Send a monthly executive summary email. Keep it to 5 lines and 3 numbers. Don't schedule meetings with Patricia unless Derek recommends it. Kevin Tran — VP of IT ● **Deal Role:** Technical Evaluator. Approved the security assessment and integration architecture. ● **Communication Style:** Thorough, process-oriented. Wants technical documentation ahead of any ● call. Will hold us to SLAs. ● **Personal Win:** A clean implementation that doesn't disrupt his ERP migration timeline or create ● security incidents. **Disposition:** Supportive but cautious. He's stretched thin with the SAP S/4HANA migration in Q4. **CS Approach:** Proactively share technical status updates weekly during implementation. Never surprise Kevin with a change. Loop in our Solutions Engineering team for any integration questions — Kevin will escalate fast if he feels under-supported. Aisha Johnson — Fleet Manager, Southeast Region ● **Deal Role:** End User Lead for the pilot region. Participated in the evaluation and tested the product. ● **Communication Style:** Hands-on, practical, quick to give feedback. Prefers Slack or phone over ● email. ● **Personal Win:** She wants her drivers to stop complaining about inefficient routes and late-night rework. **Disposition:** Enthusiastic — she's already seen the product in action and is a vocal advocate. ● **CS Approach:** Leverage Aisha as a power user and internal trainer for the other regions. She can be the bridge to the Northeast region, which hasn't been involved yet. Ask her to co-lead end-user training sessions. Bill Crawford — CFO ● **Deal Role:** Economic Buyer. Approved the $220K spend reluctantly and set a hard 6-month ROI ● review on October 1. **Communication Style:** Numbers only. Does not care about features or functionality — cares about ● dollars in vs. dollars out. ● **Personal Win:** He needs to justify this spend to the new CEO. If the ROI is clear, he looks smart. If ● it's not, he'll be the first to push for cancellation. **Disposition:** Skeptical. He approved the deal but is not emotionally invested. He will be a churn risk if we don't deliver measurable ROI by October. **CS Approach:** Do not engage Bill directly unless invited. Feed all financial data through Derek and Patricia. Build toward the October 1 ROI review from Day 1 — this is the single most important milestone for retention. Have the ROI case airtight by September. Maria Santos — VP of HR ● **Deal Role:** Not involved in evaluation. Her team will be impacted by workflow changes (driver ● scheduling, route assignments). ● **Communication Style:** Unknown — Lauren did not interact with Maria during the sales process. ● **Personal Win:** Unknown — but likely cares about driver satisfaction and change management. ● **Disposition:** Neutral — unaware of the project details. **CS Approach:** Flag Maria as a stakeholder to engage during Phase 2 (admin training / workflow configuration). Derek should make the introduction. If driver workflows change significantly, Maria's team may need to update scheduling policies. Ignoring HR is a common adoption risk in fleet tech rollouts. 3. Success Criteria & Measurement Plan Success Metric | Baseline (Current) | Target | Timeline | Owner (Customer) Fuel cost reduction | $1.2M/year in fuel | 15% reduction ($180K savings) | Measurable by Month 4 | Derek Huang Route planning time | 4 hours/day per planner | Under 30 minutes/day | By Week 6 (go-live) | Derek Huang On-time delivery rate | 91% | 97% | By Month 6 (Oct 1 ROI review) | Patricia Morales How Success Will Be Measured: ● Fuel cost data: Pulled from SAP TM integration — compare monthly fuel invoices pre- and postimplementation. ● Route planning time: Self-reported by planners in Weeks 1-2 (baseline), then tracked via platform time-toplan analytics. ● On-time delivery rate: Tracked via real-time GPS data against delivery windows — dashboard metric available from Day 1 of go-live. QBR Cadence: Quarterly, starting August 1, Recommended QBR Agenda: 93. Success metrics scorecard (5 min) — green/yellow/red on each metric 94. Usage and adoption data (5 min) — active users, feature utilization by region 95. Customer feedback and open issues (10 min) — what's working, what's not 96. Roadmap preview and expansion discussion (5 min) — new features, additional modules 97. Action items and next steps (5 min) ⚠️ Critical Milestone — October 1 ROI Review: Bill Crawford set a hard 6-month checkpoint. Jordan, this is the renewal decision in disguise. Start building the ROI narrative from Week 1. By September 1, you should have a draft ROI report ready for Derek to review before it reaches Bill. Do not wait until September to start pulling numbers. 4. Promises & Commitments Register ⬜ # | Promise | Made To | When | Status | Owner (Our Side) 1 | Dedicated implementation manager for first 60 days | Derek Huang | During negotiation (Feb 2026) | Pending — must assign before April 1 kickoff | CS / Implementation Team 2 | Route planning time under 30 minutes by Week 6 | Derek Huang | Discovery call (Jan 2026) | Pending — this is a hard expectation | Implementation Manager 3 | Custom analytics dashboard view for Patricia's monthly board report | Patricia Morales | Proposal meeting (Feb 2026) | Pending — needs scoping during Phase 2 | CSM + Product 4 | Future ERP integration support (SAP S/4HANA) | Kevin Tran | Technical review (Feb 2026) | Implied, not contractual — Lauren said "we can work with you on that" but no formal commitment. Kevin may expect this is included. | CSM — clarify scope early 5 | GPS hardware retrofit for 20 remaining vehicles | Derek Huang | Implementation planning (March 2026) | Pending — customer responsibility, but Lauren offered to coordinate with our hardware partner | AE + Implementation ⬜ ⬜ ⚠️ ⬜ ⚠️implementation. Highest Risk Promise: #4 — the implied ERP integration. Kevin may bring this up during Jordan, get ahead of this. In Week 1, confirm with Kevin what his expectations are for S/4HANA integration support. If it's out of scope, set that expectation now — not in Q4 when his migration starts. If it requires a professional services engagement, surface that early so it becomes an expansion conversation, not a broken promise. 5. Risk Register & Early Warning Signals 🔴 # | Risk | Severity | Trigger Signal | Mitigation 1 | **CFO 6-month ROI checkpoint** — Bill may push to cancel or renegotiate if ROI is unclear by October 1 | High | Bill asks for an unscheduled financial review before October; Derek reports "Bill is asking questions about the spend" | Build ROI tracking from Day 1. Deliver a preliminary ROI snapshot at the first QBR (August). Give Derek and Patricia the data to presell Bill before October. 2 | **IT bandwidth — ERP migration conflict** — Kevin's team is simultaneously migrating to SAP S/4HANA in Q4, creating resource contention for our integration work | Medium | Kevin delays integration milestones or stops responding to technical requests in Q3 | Front-load all integration work into Phase 1 (April). Get SAP TM connected before Kevin's team pivots to S/4HANA. Confirm Kevin's resource availability in Week 1. 3 | **Northeast region adoption gap** — This region was not involved in the evaluation. Drivers and planners there may resist the change. | Medium | Low login rates from Northeast users in Weeks 5-6; complaints or workaround reports from Northeast fleet managers | Use Aisha (Southeast) as an internal advocate. Schedule a dedicated Northeast onboarding session. Identify a Northeast fleet manager early to serve as a regional champion. 4 | **20 vehicles without GPS hardware** — Full go-live requires all 400 vehicles instrumented. 20 still need retrofitting. | Medium | Hardware vendor delays; vehicles not retrofitted by go-live date | Confirm hardware order status in Week 1. If there's a delay risk, plan for a phased go-live (380 vehicles first, 20 added post-retrofit) rather than holding up the entire rollout. 5 | **New CEO — unknown relationship** — Patricia's new CEO (started January) wasn't part of the deal. If the CEO questions the spend, Patricia may not have full air cover. | Medium | Patricia mentions the CEO is "reviewing all major vendor contracts" or asks for additional justification materials | Prepare an executive briefing one-pager for Patricia to share with the CEO proactively. Include the business case, competitive rationale, and early wins. It's better for Patricia to introduce us on her terms than for the CEO to discover us during a cost review. 6 | **Maria Santos (HR) — unmanaged stakeholder** — Workflow changes will affect driver scheduling, and HR hasn't been briefed. | Low | Maria raises concerns about driver workflow changes after rollout; HR pushes back on new scheduling processes | Derek should introduce Jordan to Maria during Phase 2. A 30-minute briefing on what's changing and how it benefits drivers will prevent an avoidable blocker. 🟡 🟡 🟡 🟡 🟢 6. Implementation & Onboarding Roadmap Phase 1 — Technical Foundation (Weeks 1-2: April 1-14) ● [ ] Assign dedicated implementation manager (fulfill Promise #1) ● [ ] Kickoff call: Jordan + Implementation Manager + Derek + Kevin ● [ ] SAP TM integration: begin API configuration and data mapping ● [ ] Azure AD SSO setup and testing ● [ ] Historical route data migration (2 years of data from legacy system) ● [ ] Confirm GPS hardware retrofit timeline for 20 remaining vehicles ● [ ] Clarify S/4HANA integration expectations with Kevin (address Promise #4) ● **Owners:** Implementation Manager (our side), Kevin Tran (IT) ● **Dependency:** Kevin's availability — confirm in kickoff call Phase 2 — Configuration & Pilot (Weeks 3-4: April 15-28) ● [ ] Configure platform for Apex's 3-region structure (Southeast, Northeast, Central) ● [ ] Build custom analytics dashboard view for Patricia's board report (fulfill Promise #3) ● [ ] Admin training for Derek and 2 regional fleet managers ● [ ] Pilot launch with Southeast region (Aisha's team — 140 vehicles) ● [ ] Introduce Jordan to Maria Santos (HR) — brief on workflow changes ● [ ] Collect baseline route planning time data from planners (for ROI tracking) ● **Owners:** CSM + Implementation Manager (our side), Derek + Aisha (customer side) ● **Dependency:** SAP TM integration must be complete before pilot data flows correctly Phase 3 — Full Rollout & Go-Live (Weeks 5-6: April 29 - May 15) ● [ ] Expand to Northeast and Central regions ● [ ] End-user training: drivers (mobile app) and planners (desktop platform) ● [ ] Dedicated Northeast onboarding session — identify and enable a regional champion ● [ ] Validate route planning time is trending toward <30-minute target (Promise #2) ● [ ] Go-live: May 15, 2026 — all 3 regions, all vehicles (or phased if 20 retrofits aren't complete) ● [ ] Go-live celebration email from Derek to his team (CSM to draft, Derek to send) ● **Owners:** CSM (our side), Derek + regional fleet managers (customer side) ● **Dependency:** GPS retrofits on remaining 20 vehicles Phase 4 — Adoption & Optimization (Weeks 7-12: May 16 - July 15) ● [ ] Weekly adoption check-ins with Derek (first 4 weeks post-go-live) ● [ ] Monitor usage dashboards: daily active users, feature adoption by region, route optimization acceptance ● rate ● [ ] Address any driver app adoption issues (common: drivers reverting to old habits in Week 2-3) ● [ ] Optimize routing algorithms based on real-world Apex data (first 30 days of data) ● [ ] Prepare preliminary ROI snapshot for first QBR (August 1) ● [ ] First QBR: August 1, 2026 **Owners:** CSM (our side), Derek (customer side) ● **Success Gate:** By July 15, all three regions should show >80% daily active user rate and route planning time should be under 45 minutes (trending toward 30) 7. Expansion & Growth Roadmap Opportunity | Est. Value | Interest Level | Trigger Event | Recommended Timing **Predictive Maintenance Module** | $45K/year | High — Derek explicitly asked about this for Year 2 | Successful go-live + Derek seeing maintenance cost data in the analytics dashboard | Month 6-8 (after October ROI review proves base platform value) **Customer Delivery Notifications** | $30K/year | Medium — Patricia mentioned as a future priority for customer experience | On-time delivery rate hits 95%+ and Patricia is ready to invest in customer-facing improvements | Month 9-12 **2 New Distribution Centers (Q1 2027)** | ~$75K/year (incremental licensing) | High — confirmed by Derek, facilities under construction | Derek confirms operational launch dates for new centers | Month 10-12 (begin scoping before centers open) **SAP S/4HANA Integration (Post-Migration)** | Professional services engagement (TBD) | Medium — Kevin expects some level of support (see Promise #4) | Kevin's ERP migration reaches UAT phase in Q4 2026 | Q1 2027 (after their migration stabilizes) Total Year 2 Expansion Potential: $150K+ ACV uplift Expansion Principles: ● Never pitch expansion before the base platform is delivering measurable value. Derek and Patricia must ● both be able to say "this is working" before we ask for more. ● Use the first QBR to plant seeds. Share a roadmap slide that includes the modules they didn't buy. Let Derek react — don't sell. The October ROI review is the expansion gate. If Bill Crawford sees clear ROI, he becomes an ally rather than a blocker for Year 2 investment. 8. Warm Introduction Plan Email from Lauren (AE) to Derek and Patricia, cc: Jordan (CSM) Subject: Introducing Jordan Rivera — Your Dedicated Customer Success Manager "Derek, Patricia — I'm thrilled that we're officially kicking off together. Working with you both over the past few months has been a highlight — the rigor you brought to evaluating this decision gives me full confidence that we're going to deliver real results for Apex. I want to introduce you to Jordan Rivera, who will be your dedicated Customer Success Manager from here forward. Jordan is one of our best — they've led onboarding for several of our logistics customers and they know the fleet operations world inside and out. Jordan has the full context of our conversations — the goals we set around fuel cost reduction, route planning efficiency, and on-time delivery — and they'll be your primary point of contact for everything from implementation through your first QBR and beyond. Jordan will be reaching out this week to schedule your kickoff call and walk through the onboarding timeline. I'll join that first call to make sure the transition is seamless, and I'll stay involved for any commercial or strategic conversations. Thank you again for your partnership. I'm looking forward to celebrating some big wins together. Best, Lauren" Talking points for Lauren on the first joint call (5 minutes): 98. "Derek, Patricia — I want to personally hand this off and make sure you never have to repeat anything you've already told me. Jordan has the full picture." 99. "Jordan, why don't you share a bit about your background and how you'll be working with the Apex team?" (Let Jordan build their own credibility.) 1. "I'll stay connected for anything strategic or commercial, but Jordan is your go-to from here. You're in great hands." 2. Transition to Jordan leading the kickoff agenda. Tips ● The handoff is the most fragile moment in the customer lifecycle. If the customer feels like they're starting over with a stranger, trust erodes immediately. The AE must personally transfer credibility to the CSM. ● Document every promise — especially the informal ones. "We can probably do that" during a sales call ● becomes "you committed to that" in the customer's mind. Surface these early so the CS team can manage ● expectations before they become complaints. ● The stakeholder map is not a list of names — it's a political intelligence brief. The CSM needs to know who is enthusiastic, who is skeptical, who has power, and who is watching from the sidelines. This is what separates a good handoff from a great one. Start building toward the first major milestone (in this case, the October ROI review) from Day 1. If you wait until Month 4 to think about Month 6, you're already behind. A Presidents Club AE doesn't disappear after the close. They stay involved through the first QBR, attend the executive sponsor check-in, and show up when expansion conversations begin. Your commission is earned at close; your reputation is earned in renewal.

I am a [YOUR ROLE] preparing a pricing justification package for [prospect company name]. The deal is in late-stage evaluation and I need to arm my Champion and defend our pricing through the full buying committee. Deal details: ● Primary Contact: [primary contact and role] ● Economic Buyer: [economic buyer name and role] ● Our Solution: [our solution and annual cost] ● Contract Term: [contract term and structure] (e.g., "3-year contract, annual billing, $150K/year") Value case: ● Prospect's Quantified Pain (Cost of Inaction): [prospect's quantified pain — current cost of the problem] ● Key Value Metrics Our Solution Improves: [key value metrics our solution improves] (e.g., "time-toclose, rep productivity, forecast accuracy") Competitive landscape: ● Alternatives Being Evaluated: [competitive alternatives and their approximate pricing] (e.g., "CompetitorX at $90K/year, internal build estimated at $300K one-time + $80K/year maintenance") Buying process: ● Budget Cycle / Fiscal Year: [prospect's budget cycle and fiscal year] ● Procurement Requirements: [known procurement or purchasing requirements] (e.g., "3-bid requirement, procurement board review, security assessment") Risk of inaction: ● [risk of doing nothing — what happens if they don't act] (e.g., "they lose 2 more senior engineers per quarter, pipeline coverage continues to decline") Generate a comprehensive Pricing Justification Framework with the following sections: 1. **Executive Value Summary (1 page):** A CFO-ready summary that presents the investment, the return, and the payback period in plain business language. This should be something my Champion can forward directly to the Economic Buyer. Include: - The investment amount and term - The quantified annual return (in dollars and as ROI %) - The payback period - A single-paragraph "why now" argument tied to their business cycle or risk of inaction - A one-line value statement (e.g., "For every $1 invested, you receive $X back in Year 1") 2. **Total Cost of Ownership (TCO) Comparison:** A side-by-side comparison of our solution vs. each competitive alternative (including the status quo and any internal build option), factoring in: - Licensing / subscription cost - Implementation and onboarding costs - Ongoing maintenance, support, and internal IT overhead - Hidden costs (training, customization, integration work, opportunity cost of delay) - A 3-year total cost view Format this as a Markdown table. 3. **Value Waterfall:** A breakdown of every line item of value our solution delivers, quantified wherever possible. Structure it as: - Hard savings (cost reduction, headcount avoidance, contract consolidation) - Productivity gains (time saved, throughput improvement, cycle time reduction) - Revenue impact (faster sales cycles, higher win rates, reduced churn, expansion revenue) - Risk mitigation (compliance, security, business continuity) - A total annual value estimate and the resulting ROI multiple 4. **Price Anchoring & Negotiation Strategy:** Guidance for how I should position and defend the price, including: - The anchoring narrative — how to frame the price relative to the cost of inaction and the total value delivered (not relative to competitors) - 3-4 prepared responses to common procurement negotiation tactics (e.g., "We need 20% off," "CompetitorX is cheaper," "We only have budget for $X," "Can you do a pilot first?") - Concession strategy — what I can offer that protects price integrity (e.g., extended payment terms, phased rollout, added services) vs. what I should never concede - Walk-away signals — indicators that the deal economics don't work and I should hold firm 5. **Champion Enablement Package:** Materials I can give my Champion so they can sell the deal internally when I'm not in the room: - A 3-bullet "elevator pitch" for why this investment makes sense - Pre-built answers to the top 3 questions the CFO / procurement will ask - A one-page comparison table they can use to show why we are the best option - A "cost of delay" calculation showing what the prospect loses for every month they don't decide 6. **Procurement Navigation Playbook:** A tactical plan for getting through the prospect's procurement process, including: - A checklist of documents and materials to have ready (security questionnaire, SOC 2 report, W-9, insurance certificates, references, etc.) - How to handle a 3-bid requirement when I know I'm the front-runner - Timing strategy — how to align my proposal with their budget cycle to avoid "wait until next fiscal year" - Escalation path — when and how to go above procurement to the Economic Buyer if the process stalls Example Input: ● Prospect Company: Velocity Financial Group ● Primary Contact: Marcus Webb, SVP of Sales ● Economic Buyer: Diana Rojas, CFO ● Our Solution: Revenue intelligence platform — $180K/year ● Contract Term: 3-year contract, annual billing ● Quantified Pain: $2.1M/year in lost revenue from inaccurate forecasting and missed pipeline signals ● (derived from discovery: 15% forecast miss rate costing ~$1.4M in misallocated resources + $700K in ● deals lost to slow follow-up) ● Value Metrics: Forecast accuracy, rep productivity, pipeline-to-close conversion rate ● Competitive Alternatives: CompetitorX at $110K/year (weaker analytics, no real-time signals); internal BI ● dashboards at $250K one-time build + $60K/year maintenance Budget Cycle: Fiscal year starts July 1; budget planning begins in April Procurement Requirements: VP-level sign-off for deals under $200K; 2-vendor comparison required Risk of Inaction: Q3 pipeline is already showing 12% lower coverage than last year; two senior AEs left in Q4 citing tool frustration Output: Pricing Justification Framework — Velocity Financial Group 1. Executive Value Summary To: Diana Rojas, CFO From: Marcus Webb, SVP of Sales Re: Revenue Intelligence Platform Investment — $180K/year (3-year term) The Investment: ● Annual cost: $180,000 ● 3-year total: $540,000 The Return: ● Quantified annual value: $2.1M (conservative estimate based on discovery findings) ● Net annual gain: $1,920,000 ● **ROI: 1,067%** ● **Payback period: 32 days** Why Now: Velocity's Q3 pipeline is showing 12% lower coverage year-over-year, and the sales team lost two senior AEs in Q4 who cited tool frustration as a contributing factor. Every quarter without accurate pipeline signals and real-time coaching capability compounds the forecasting gap and increases attrition risk. With budget planning opening in April and FY starting July 1, securing this investment now means the platform is live and delivering value before Q1 of the new fiscal year — rather than starting the cycle over. Value Statement: For every $1 Velocity invests in this platform, you can expect $11.67 back in recovered revenue and productivity gains in Year 1. 2. Total Cost of Ownership (TCO) — 3-Year Comparison Cost Category | Our Solution | CompetitorX | Internal BI Build Year 1 License / Subscription | $180,000 | $110,000 | $0 Year 2 License / Subscription | $180,000 | $110,000 | $0 Year 3 License / Subscription | $180,000 | $110,000 | $0 Implementation & Onboarding | $0 (included) | $25,000 | $250,000 (build cost) Ongoing Maintenance & Support | $0 (included) | $15,000/yr | $60,000/yr Internal IT / Admin Overhead | ~$10,000/yr (0.1 FTE) | ~$30,000/yr (0.3 FTE) | ~$120,000/yr (1.2 FTE) Training & Change Management | $5,000 (one-time) | $15,000 (one-time) | $40,000 (one-time) Integration / Customization | $0 (native CRM integration) | $20,000 (custom work) | $80,000 (estimated) Opportunity Cost of Delay | $0 (live in 6 weeks) | $0 (live in 10 weeks) | $525,000 (9-month build = $175K/quarter in continued losses) **3-Year Total** | **$575,000** | **$500,000** | **$1,115,000** Key Insight for Diana: CompetitorX appears $75K cheaper over 3 years — but that gap disappears when you factor in the 0.3 FTE admin overhead, weaker analytics that won't solve the forecast accuracy problem, and the absence of real-time pipeline signals that are driving the $2.1M annual loss. The internal build is over 2x the cost and won't deliver value for 9+ months. 3. Value Waterfall Value Category | Line Item | Annual Value **Hard Savings** | Eliminate 2 redundant reporting tools ($35K + $22K) | $57,000 Reduce reliance on external forecast consultants | $40,000 **Productivity Gains** | Reps save 5 hrs/week on manual CRM data entry (50 reps × 5 hrs × $75/hr × 50 weeks) | $937,500 Sales managers save 3 hrs/week building manual pipeline reports (8 managers) | $90,000 **Revenue Impact** | Improve forecast accuracy from 85% → 95% — reducing resource misallocation | $1,400,000 (from discovery) Faster follow-up on stalled deals — recover 10% of currently lost pipeline | $700,000 (from discovery) **Risk Mitigation** | Reduce AE attrition by addressing tool frustration (cost to replace 1 AE = ~$150K) | $300,000 (avoid losing 2 AEs/year) **Total Annual Value** | **$3,524,500** **Conservative Estimate (used in ROI)** | **$2,100,000** ROI Multiple: $2,100,000 ÷ $180,000 = 11.7x return (using conservative estimate only) 4. Price Anchoring & Negotiation Strategy Anchoring Narrative: Never let the price conversation become "$180K vs. $110K." The frame is "$180K vs. $2.1M in annual losses." Position the price as: "This isn't a $180K expense — it's a $180K decision that returns $1.9M. The question isn't whether you can afford to invest; it's whether you can afford another year of 15% forecast misses and losing senior AEs." Prepared Responses to Procurement Tactics: Tactic | Response "We need 20% off to get this done." | "I understand the pressure to optimize the investment. Before we talk about price adjustments, let's make sure we agree on the value — because if this platform delivers even half of the $2.1M return we've projected, a 20% discount saves you $36K but the real conversation is about the $1.9M you're gaining. That said, I can look at options around payment terms or phased rollout if that helps your budget structure." "CompetitorX is $70K cheaper." | "They are — and I'd expect that, because their platform doesn't include real-time pipeline signals or native forecasting intelligence. The $70K difference buys you the capabilities that directly solve the forecast accuracy problem Marcus identified. If CompetitorX could solve that, you'd already be using them. Let me put together a side-by-side capability comparison so Diana can see exactly where that $70K goes." "We only have $150K in budget." | "Let's work with that. I can structure a phased rollout — we start with your top 30 reps in Q3 for $150K, prove the value with a 90-day success milestone, and expand to the full team in Q4 with a separate budget line. That way you're within budget today and the expansion is funded by the results from Phase 1." "Can we do a 90-day pilot first?" | "I'm open to a structured pilot, but I want to make sure it's set up to succeed. A 90-day pilot with 10 reps won't generate statistically meaningful forecast accuracy data — it takes a full pipeline cycle. What I'd propose instead is a 6-month initial commitment with a success milestone at 90 days. If we don't hit the agreed metrics, we'll have an honest conversation. That gives you real data, not a sandbox experiment." Concession Strategy: ✅ Safe to Offer (Protects Price) | ❌ Never Concede Extended payment terms (net-60, quarterly billing) | Per-unit price reduction without scope change Phased rollout to match budget availability | Free months or "trial" periods that devalue the platform Additional onboarding / training sessions | Removing core features to hit a lower price point 30-day early termination clause in Year 1 | Multi-year discount without a multi-year commitment Executive business review at 90 days | Custom SLA terms that create operational risk Walk-Away Signals: ● Procurement insists on >25% discount with no willingness to discuss value ● The Economic Buyer has not engaged and procurement is acting as a gatekeeper with no path to Diana ● The prospect wants to strip the real-time signals module (the core differentiator) to match CompetitorX ● pricing Timeline pushes past two budget cycles with no committed decision date 5. Champion Enablement Package For Marcus to use when selling internally to Diana and the buying committee: Elevator Pitch (3 bullets): 7. "We're losing $2.1M a year to bad forecasts and slow pipeline follow-up. This platform fixes both for $180K — that's an 11.7x return." 8. "CompetitorX is cheaper but doesn't solve the forecast accuracy problem. The internal build costs 2x more and takes 9 months. This is the only option that solves the problem at the right price and speed." 9. "If we start now, we're live before FY begins in July. If we wait, that's another $525K in losses before we even kick off." Pre-Built CFO / Procurement Q&A: Question Diana Will Ask | Marcus's Answer "Why can't we use CompetitorX and save $70K?" | "CompetitorX doesn't have the real-time pipeline signals or forecasting engine — it's a CRM overlay, not a revenue intelligence platform. We'd save $70K and still have the same $2.1M problem." "What's the payback period?" | "32 days. We recoup the full annual investment in the first month based on the productivity gains alone — before we even count the forecast accuracy improvement." "What if it doesn't work?" | "We're proposing a 90-day success milestone with defined metrics. If we don't hit them, we have an early termination clause. But our comparable customers see results in 45-60 days." One-Page Comparison Table for the Buying Committee: ✅ ✅ ❌ ⚠️ Criteria | Our Solution | CompetitorX | Internal Build Solves forecast accuracy gap | Yes — AI-driven | No — manual only | Partial — depends on build Real-time pipeline signals | Native | Not available | Not planned Time to value | 6 weeks | 10 weeks | 9+ months 3-year TCO | $575K | $500K | $1,115K Internal IT burden | 0.1 FTE | 0.3 FTE | 1.2 FTE Rep adoption risk | Low (native CRM) | Medium (separate UI) | High (custom tool) ❌ ❌ Cost of Delay Calculation: ● Quantified annual loss: $2,100,000 ● Monthly cost of inaction: **$175,000** ● Every month the decision slips = $175K in continued losses ● "Diana, the difference between deciding in March and deciding in June is $525,000. That's 3x the annual cost of the platform." 6. Procurement Navigation Playbook Document Readiness Checklist: ● [ ] SOC 2 Type II report (current year) ● [ ] Security questionnaire (pre-filled with standard answers) ● [ ] W-9 / tax documentation ● [ ] Certificate of insurance (general liability + cyber) ● [ ] 3 customer references (matched to Velocity's industry and size) ● [ ] Master services agreement (MSA) — redline-ready ● [ ] Data processing agreement (DPA) if applicable ● [ ] Implementation timeline and onboarding plan ● [ ] Case study from a comparable financial services customer Handling the 2-Vendor Comparison Requirement: ● Velocity requires a 2-vendor comparison. Since CompetitorX is already in the mix, this requirement is met. Use this to your advantage: proactively provide the comparison table (Section 5) so that your Champion controls the narrative rather than procurement running a blind evaluation. Say to Marcus: "I know you'll need a comparison for Diana's review. Here's a side-by-side I've built from our conversations — feel free to adjust it, but this will save you time and make sure the right criteria are being evaluated." Budget Cycle Timing Strategy: ● FY starts July 1. Budget planning begins April. ● **Target:** Get verbal commitment and contract language agreed by end of March, so Marcus can ● include the line item in his April budget submission. ● **Risk:** If the decision slips past April, it becomes a "next fiscal year" conversation — which means 6+ months of delay and $1.05M in additional losses. **Action:** Frame every timeline conversation around this: "Marcus, the April budget deadline is the forcing function. If we can align on terms by March 28, you can include this in your FY budget submission and be live before Q1. If we miss that window, we're looking at January at the earliest." Escalation Path if Procurement Stalls: 10. **Week 1-2 of stall:** Ask Marcus to check in with procurement and identify the specific blocker. 11. **Week 3:** Request a joint call with Marcus and the procurement lead to address open items directly. 12. **Week 4:** If procurement is unresponsive, ask Marcus to escalate to Diana: "Diana, the procurement review has been pending for 3 weeks. Given the April budget deadline, can you help us prioritize this so we don't miss the window?" This is a Champion-led escalation — never go around your Champion. Tips ● Price is never the real objection. The real objection is either unclear value, unresolved risk, or a lack of ● urgency. A Presidents Club AE diagnoses which one it is before responding. Never negotiate against yourself. When procurement asks for a discount, ask "What's driving that request?" before offering anything. Sometimes the answer is just "it's my job to ask." ● Build the value case before the price conversation ever happens. If you're justifying price in Stage 4, you ● should have quantified value in Stage 2. Retrofitting ROI feels defensive; presenting it early feels ● consultative. ● Arm your Champion, don't depend on them. Give them the exact words, tables, and numbers to use — because when they're in the room without you, they'll use whatever you gave them verbatim. The cost of delay is your most powerful closing tool. It converts an abstract value conversation into a concrete, time-bound financial argument that creates genuine urgency. Know your walk-away point. The best AEs protect their price because they know discounting trains the buyer to ask for more next time. Hold firm, offer creative structure, and let the value case do the work.

You are my AI sales strategist, sales researcher, territory planner, and prospecting analyst. Analyze everything accessible across my internal company environment and create the strongest possible 30-day prospecting strategy to find real opportunities, generate qualified pipeline, and book meetings. Research scope: CRM/account records, email threads, call notes, opportunity history, enablement materials and playbooks, product materials, partner information, marketing assets, sales decks, prior proposals, and any other internal sources. Output required: (1) Where to focus. (2) Who to target and why. (3) What message to use. (4) What sequence or motion to run. (5) Which existing deals/opportunities to revive, expand, or accelerate. (6) Which prospects to contact first with specific messages. For each identified prospect, provide: account/company name, target contact name, title, work email if available, LinkedIn profile if available, why this person/account is a strong target, best outreach angle, and custom message(s). Output format (7 phases): Phase 1 — Internal Research & Intel Gathering. Phase 2 — Territory & Account Prioritization. Phase 3 — Prospect Identification & Contact Intelligence. Phase 4 — Messaging Strategy. Phase 5 — Outreach Sequences. Phase 6 — Deal Revival & Expansion. Phase 7 — 30-Day Execution Roadmap. Do not invent anything. If data is unavailable, say so clearly.

Create follow-up email templates for these scenarios. Context: ● My product: [WHAT YOU SELL] ● My value prop: [KEY BENEFIT] Generate templates for: After no response to first email (Day 3) After meeting request ignored (Day 5) After they opened but didn't reply (Day 7) After they clicked a link (same day) After voicemail left (next day) After LinkedIn connection (Day 2) After referral introduction (Day 1) After trade show/event (Day 1) After their competitor news (same day) Final breakup email (Day 14) Each template should: ● Be under 75 words ● Have a clear subject line ● Reference the previous touch ● Add new value (not just "following up") ● Have a specific CTA

We're [sponsoring / attending / speaking at] [CONFERENCE] on [DATES] in [CITY]. Our sponsorship level is [Gold/Silver/etc.] and we have [booth / speaking slot / both]. Build me a complete conference strategy: 1. Pre-event: Target attendee outreach plan, LinkedIn content arc (4 posts), internal coordination checklist 2. Booth strategy: Messaging, conversation starters, qualifying questions for badge scans, swag recommendations that tie to our brand story 3. Speaking prep (if applicable): Key messages for [X]-minute slot, audience-specific framing 4. On-site: Day-by-day execution plan with time blocks 5. Post-event: Follow-up cadence, lead scoring criteria, handoff to Salesforce What's our unique angle at this event that no other vendor can claim? Lead with that.

You are helping an enterprise seller prepare for a live customer meeting. Task: Create a multi-threading plan. Inputs: - Account: [COMPANY] - Persona(s): [TITLE / STAKEHOLDERS] - Opportunity stage: [STAGE] - Known pain or initiative: [PAIN / INITIATIVE] - Goal of the meeting: [MEETING GOAL] - Risks / unknowns: [RISKS] Requirements: - Prioritize what will improve the quality of the conversation - Keep the seller focused on business outcomes, not product dumping - Anticipate objections, stakeholder dynamics, and next-step traps - Make the output usable immediately before the meeting Output: 1. Recommended structure 2. Talking points 3. Key questions 4. Risks to watch 5. Desired next step

Write a cold email to [prospect name], [job title] at [company name]. Use this structure: 1. **Hook (1 sentence):** Reference a specific trigger event (they just got funding, launched a product, posted a job, hit the news) 2. **Problem (1 sentence):** Connect that trigger to a common pain point for their role 3. **Proof (1 sentence):** Share one result a similar company got with our solution 4. **Ask (1 sentence):** Request a specific, short call to share one relevant insight Rules: ● Maximum 100 words total ● No buzzwords like "synergy," "game-changer," "solutions" ● Don't mention features—focus on THEIR problem ● Subject line: [Company name] + [specific trigger], no hype words Example Input: ● Prospect: Sarah Chen, VP Engineering at DataCorp ● Trigger: They just posted 10 engineering jobs ● Problem: Onboarding new engineers usually slows teams down Output: Subject: DataCorp's 10 new engineering roles Hi Sarah, Saw you're hiring 10 engineers—congrats on the growth. Most teams we talk to see productivity dip 30% during big hiring waves while ramping new people. When FinTech startup [Name] doubled their eng team last year, our onboarding playbook cut ramp time from 8 weeks to 3 weeks. Worth 15 minutes to share what worked? I have their week-by-week checklist. [Your name] Tips ● Send Tuesday-Thursday, 10am-2pm their timezone ● If no response in 4 days, try a different angle (not the same email twice)

You are a B2B SaaS lead prioritization analyst. Your task is to evaluate multiple leads simultaneously and categorize them into priority tiers (HIGH / MEDIUM / LOW) to help sales teams allocate their time effectively. ## Input Format: Provide 3-5 leads with the following information for each: **Lead [#]:** - Company: [Name & Industry] - Size: [Employees, Revenue if known] - Contact: [Name, Title/Role] - Engagement: [Brief summary of activities and timeline] - Context: [Any additional signals: tech stack, urgency, pain points, competitors mentioned] ## Analysis Framework: For each lead, evaluate across these dimensions: ### 1. Intent Signals (Are they actively buying?) - **High Intent:** Pricing views, demo requests, trials, technical questions, timeline mentioned, multiple stakeholders - **Medium Intent:** Product-focused content, case studies, repeated visits, engaged in conversations - **Low Intent:** Generic content only, passive browsing, single touch, educational content only ### 2. Fit Quality (Are they the right customer?) - **Strong Fit:** ICP match on size/industry/role, decision-maker engaged, budget likely available - **Moderate Fit:** Some ICP misalignment, influential role but not decision-maker, unclear budget - **Weak Fit:** Outside ICP, wrong role, structural barriers ### 3. Timing & Urgency (Will they buy soon?) - **Immediate:** Expressed timeline, contract expiring, pain event, compressed evaluation - **Near-term:** Active evaluation, no explicit timeline, normal buying pace - **Long-term:** Early research, no urgency signals, slow engagement ### 4. Conversion Probability (Based on industry/behavioral patterns) - **High:** Industry converts well + behaviors match successful deal patterns - **Medium:** Mixed signals, industry has moderate conversion rates - **Low:** Industry/behaviors suggest research-only or low conversion likelihood ## Output Format: ### PRIORITY SUMMARY TABLE | Lead # | Company | Priority | Score | Key Reason | Est. Timeline | |--------|---------|----------|-------|------------|---------------| | 1 | [Name] | HIGH | 85/100 | [One-line reason] | [Days/weeks] | ### DETAILED LEAD ANALYSIS #### LEAD [N]: [Company Name] **PRIORITY: [HIGH / MEDIUM / LOW]** **SCORE: [X/100]** **Quick Assessment:** [2-3 sentences summarizing why this lead is prioritized at this level] **Scoring Breakdown:** - Intent Signals: [X/35] - [Brief rationale] - Fit Quality: [X/30] - [Brief rationale] - Timing/Urgency: [X/20] - [Brief rationale] - Conversion Probability: [X/15] - [Brief rationale] **Strengths:** - [Key positive factor] **Concerns:** - [Key risk or limitation, if any] **Recommended Action:** [Specific next step] **Expected Outcome:** [Conversion likelihood and timeline estimate] ### RELATIVE RANKING & RATIONALE **Why Lead [#] is Higher Priority than Lead [#]:** [Compare leads directly, explaining the differentiating factors] ### SALES TEAM ACTION PLAN **FOCUS THIS WEEK (High Priority Leads):** - Lead [#]: [Specific action] by [date] **SCHEDULE FOR NEXT 2 WEEKS (Medium Priority Leads):** - Lead [#]: [Specific action] by [date] **NURTURE QUEUE (Low Priority Leads):** - Lead [#]: [Long-term approach] ### RESOURCE ALLOCATION GUIDANCE **High-Touch Sales Effort:** Leads [#, #] - Assign to senior AEs, daily follow-up **Standard Sales Process:** Leads [#, #] - Standard cadence, qualification calls **Marketing Nurture:** Leads [#, #] - Automated sequences, educational content ### PATTERN INSIGHTS (Across All Leads) **Common Themes:** [Patterns across the lead batch] **Portfolio Health:** [Assessment of overall lead quality] **Red Flags to Watch:** [Systemic issues: wrong ICP targeting, lack of decision-makers] ### QUICK DECISION TREE **If you only have time for ONE lead:** Lead [#] because [compelling reason] **If you have time for TWO leads:** Leads [#] and [#] because [rationale] **Leads to deprioritize/disqualify:** Lead [#] because [clear reason] ## EVALUATION STANDARDS: **HIGH PRIORITY (80-100 points)** = Active buyer, strong fit, near-term opportunity — engage within 24-48 hours **MEDIUM PRIORITY (50-79 points)** = Qualified prospect, moderate intent — engage within 5-7 days **LOW PRIORITY (0-49 points)** = Poor fit or low intent — marketing nurture or disqualify Now analyze these leads and provide prioritization guidance: [Paste 3-5 leads in the Input Format above]

You are a senior B2B sales strategist, pipeline generation expert, and prospecting analyst. Your job is to create a practical prospecting plan for [COMPANY] that helps a sales rep generate qualified pipeline. Do not write in vague generalities. Do not make up facts. If something cannot be verified, say “Insufficient evidence.” Focus on actions a rep or team can actually take in the next 30 to 90 days to create meetings and opportunities. Context Company: [COMPANY] Industry / category: [INDUSTRY] What we sell: [PRODUCT / SERVICE SUMMARY] Target customers: [TARGET MARKET] Core buyer roles: [BUYER TITLES / TEAMS] Average deal type: [SMB / MID-MARKET / ENTERPRISE / SERVICES / SOFTWARE / OTHER] Current prospecting motion: [Any known outbound, inbound, partner, event, content, SDR, AE-sourced, or referral activity today] Known challenges: [Low reply rates, low connect rates, unclear ICP, weak targeting, poor personalization, long sales cycles, weak value prop, etc.] Your objectives 1. Clarify who to target Identify the highest-potential buyer roles, teams, segments, and account types. 2. Clarify why they would care Identify likely pains, triggers, priorities, and reasons someone would take a meeting now. 3. Recommend where and how to prospect Prioritize channels, targeting angles, outreach themes, and sequencing strategy. 4. Give a practical prospecting plan Provide specific actions a rep or manager can use to create more qualified pipeline. Research rules - Use credible public evidence where possible - Separate facts from inference - Do not invent buying triggers or company priorities - If evidence is limited, note that clearly Output requirements Write the response as a clean plain-text report with these exact sections: Prospecting summary Provide a concise summary of the best prospecting opportunities and where reps should focus. Best-fit target segments List the account types, industries, company sizes, or situations most worth targeting first. Best buyer personas For each buyer persona: - title / role - what they likely care about - why they may engage - what message may resonate most Likely trigger events List the most useful trigger events or signals that suggest a prospect may be open to a conversation. Best outreach themes List the 5 to 10 strongest messaging angles reps can use and explain why each one works. Channel recommendations Explain the best mix of channels, such as email, phone, LinkedIn, partner-led, events, referrals, content follow-up, or others. Prospecting plan Provide a practical 30-day prospecting plan including: - targeting priorities - weekly focus - sequencing recommendations - personalization guidance - follow-up suggestions Common prospecting mistakes to avoid List the biggest mistakes reps are likely to make and how to avoid them. Success metrics Recommend what should be measured to evaluate whether the prospecting plan is working. Sources Provide a numbered list of the most important sources used. Style rules - Be direct - Be practical - Use plain English - Make the output useful for a real rep trying to book meetings

You are an elite B2B sales strategist. Task: Execute a POV Strategy Context: - Industry: [insert] - ICP: [insert] - Persona: [insert] - Deal Stage: [insert] - Current Situation: [insert] Instructions (optimized for Perplexity): - Provide structured output - Use concise, high-signal language - Include real examples (emails, questions, talk tracks) - Tie to business impact (risk, revenue, compliance) - Anticipate objections - Prioritize practical execution Deliver: - Objective - Step-by-step strategy - Copy (if applicable) - Next steps Now execute the task.

You are an elite B2B sales strategist. Task: Execute a Executive Outreach Context: - Industry: [insert] - ICP: [insert] - Persona: [insert] - Deal Stage: [insert] - Current Situation: [insert] Instructions (optimized for ChatGPT): - Provide structured output - Use concise, high-signal language - Include real examples (emails, questions, talk tracks) - Tie to business impact (risk, revenue, compliance) - Anticipate objections - Prioritize practical execution Deliver: - Objective - Step-by-step strategy - Copy (if applicable) - Next steps Now execute the task.

You are an elite B2B sales strategist. Task: Execute a MEDDIC Context: - Industry: [insert] - ICP: [insert] - Persona: [insert] - Deal Stage: [insert] - Current Situation: [insert] Instructions (optimized for ChatGPT): - Provide structured output - Use concise, high-signal language - Include real examples (emails, questions, talk tracks) - Tie to business impact (risk, revenue, compliance) - Anticipate objections - Prioritize practical execution Deliver: - Objective - Step-by-step strategy - Copy (if applicable) - Next steps Now execute the task.

You are an elite B2B sales strategist. Task: Execute a Discovery Prep Context: - Industry: [insert] - ICP: [insert] - Persona: [insert] - Deal Stage: [insert] - Current Situation: [insert] Instructions (optimized for ChatGPT): - Provide structured output - Use concise, high-signal language - Include real examples (emails, questions, talk tracks) - Tie to business impact (risk, revenue, compliance) - Anticipate objections - Prioritize practical execution Deliver: - Objective - Step-by-step strategy - Copy (if applicable) - Next steps Now execute the task.

You are an elite B2B sales strategist. Task: Execute a Partner Co-Selling Context: - Industry: [insert] - ICP: [insert] - Persona: [insert] - Deal Stage: [insert] - Current Situation: [insert] Instructions (optimized for Perplexity): - Provide structured output - Use concise, high-signal language - Include real examples (emails, questions, talk tracks) - Tie to business impact (risk, revenue, compliance) - Anticipate objections - Prioritize practical execution Deliver: - Objective - Step-by-step strategy - Copy (if applicable) - Next steps Now execute the task.

You are an elite B2B sales strategist. Task: Execute a Prospect Research Context: - Industry: [insert] - ICP: [insert] - Persona: [insert] - Deal Stage: [insert] - Current Situation: [insert] Instructions (optimized for ChatGPT): - Provide structured output - Use concise, high-signal language - Include real examples (emails, questions, talk tracks) - Tie to business impact (risk, revenue, compliance) - Anticipate objections - Prioritize practical execution Deliver: - Objective - Step-by-step strategy - Copy (if applicable) - Next steps Now execute the task.

You are an expert B2B copywriter specializing in high-converting cold email scripts for enterprise outbound campaigns. Using the research data provided, generate systematic, persona-targeted cold email variations that follow the rules below. Research Foundation [PASTE_STEPS 3-5_OUTPUTS_HERE] Source priority (in order): Primary: Direct client feedback & onboarding data Secondary: Call transcripts & stated objectives Supporting: Market research & competitive analysis Scriptwriting Fundamentals (Non-Negotiables) Offer is everything Anchor each angle in a concrete, valuable front-end offer or lead magnet (audit, playbook, calculator, teardown, benchmark, quick win, etc.). Tone Short, conversational, professional, not slangy or too casual. Zero fluff Every sentence must earn its place and advance relevance or value. Hyper-relevance Messaging, pains, and outcomes must be tailored to the exact persona and industry context. Soft/value CTA only Question-based CTAs that invite low-friction next steps, for example, “Worth a quick look?” Front-end value first Ideally propose a lead magnet/front-end offer before selling core services to open the door. Social proof If used, it must be hyper-relevant to the persona/vertical, same role, similar company size, adjacent tech stack, or near-neighbor use case. Pain points Only mention pains that are persona-true and likely active, avoid generic boilerplate. Value props & offers Make them hyper-specific, metrics, timelines, constraints, integration realities. Brevity vs clarity Do not sacrifice clarity for shortness. If under 30 words, it should be primarily a single sharp question with one line of context. If over 30 words, apply the fundamentals above and keep flow natural, no choppy “telegram” style. Prompt Execution Logic Read research foundation and identify persona(s), PQS, and viable front-end offers/lead magnets. Generate subject lines first (plaintext, 1–3 words, 3 variants). For each persona, produce the required length x complexity matrix. Enforce fundamentals, structural elements, and guardrails per script. Append personalization ideas (with examples only). Conclude with the Reasoning Summary. Soft CTA Examples (use/iterate as needed) “Worth a 2-minute look if I send it?” “Should I send the teardown for [system_or_process]?” “Open to a quick benchmark to compare against peers?” “Would a 5-minute audit help pressure-test this?” “Want the 1-pager, no pitch, just the framework?” Front-End Offer Starters (choose one if relevant) [Audit] 5-point deliverability audit for [company_name] (24 hrs)* [Playbook] 2-page [persona_role] outreach sequence (ready to paste)* [Calculator] ROI model using your [primary_kpi] inputs* [Teardown] Loom review of [process/tool] with prioritized fixes* [Benchmark] Peer comparison using [industry] data (3 charts)*Output Rules Subject Line Rules Always 1–3 words. Provide exactly 3 variations in spintext format: [OPTION1|OPTION2|OPTION3]. Variations must include one 1-word, one 2-word, one 3-word line. No punctuation. Curiosity- or benefit-driven. Reasoning Summary (2–4 sentences) Explain: Why you chose the angles, complexity tiers, and lengths How each aligns with the persona’s likely pains or goals from the research Script Length & Complexity Variations If 1 persona provided, produce 6 variations for that persona: Lengths: ~30 words, ~45 words, ~60 words For each length, write 3 complexity tiers: Simple: Clear, plain-English, universally understandable Niche-aware: Uses light industry knowledge/lexicon Hyper-specific: Deeply tailored to the persona’s unique challenges, KPIs, constraints If 2–3 personas provided, produce 3 variations per persona (mix lengths/complexities). If 5+ personas provided, 1 variation per persona that still includes the 3 lengths & complexities inside it. Output Format for Each Script Script Metadata Persona: [SPECIFIC_ROLE] Industry: [SPECIFIC_SECTOR] Pain Point: [PRIMARY_CHALLENGE] Complexity: [Simple / Niche-Aware / Hyper-Specific] Length: [Approx. word count] Subject Line (spintext): [ONE WORD|TWO WORDS|THREE WORD LINE] Email Body (use [variables] as needed): Keep under 70 words. Include at least 3 structural elements (above). Use soft, question-based CTA. If ~30 words, prefer a single sharp question + 1 line context. Word Count: [number] Clay Variables Needed (list): [first_name], [company_name], [persona_role], [industry], [recent_news], [tech_stack], [primary_kpi], [core_system], [peer_company], [pqs_trigger] (include only those actually used) Structural Elements (include at least 3 per script) Choose whichever fit the angle best: Personalized Hook (8–12 words) Social Proof Bridge (15–20 words) Value Proposition (10–15 words) Front-End Offer (8–12 words) Soft CTA (5–8 words, question-based, never a hard call ask) Script Priorities Focus each variation on either: A pain-qualified segment (PQS from context), or A strong, differentiated value proposition the persona cares about. CTAs remain soft, e.g. “Would it make sense to…”, “Open to exploring…”, “Worth a peek?” Personalization Ideas Section (after all scripts) Provide a bullet list of personalization ideas with an example for every idea. If you can’t give an example, don’t include the idea. Format examples: Use [recent_news]: Reference their new funding round. Example: “Saw [company_name] just closed a $40M Series B, congrats on the momentum.” Use [tech_stack]: Show additive fit with their tools. Example: “Looks like you’re running HubSpot, our workflow plugs in without new training.” Use [hiring_signal]: Tie to open roles. Example: “Hiring 3 SDRs suggests pipeline goals, want the 2-page ramp blueprint we give new teams?” Use [competitor_touch]: Neighbor proof without namedropping. Example: “Teams like [peer_company] cut reply time 27% with the same playbook.” Quality Standards & Guardrails 25–69 words per script (strict). All [variables] must be valid, consistently named, and Clay-merge-safe. Use plain language, avoid jargon unless in Hyper-specific tier where it improves trust. Each variation must feel meaningfully different, not light rewrites. No emojis. No punctuation in subject lines. Proof rigor: Social proof must be adjacent (same role/region/size/stack). Pains must be current and role-true. Offer clarity: Front-end offers must be specific (format + outcome + time requirement). Brevity/clarity rule: If a short line feels stilted or vague, do not ship it, choose the 45- or 60-word band for natural flow.

You are an elite B2B sales strategist. Task: Execute a Objection Handling – Scenario 1 task. Context: - Industry: [insert] - ICP: [insert] - Persona: [insert] - Deal Stage: [insert] - Current Situation: [insert] Instructions (optimized for ChatGPT): - Provide structured output - Use concise, high-signal language - Include real examples (emails, questions, talk tracks) - Tie to business impact (risk, revenue, compliance) - Anticipate objections - Prioritize practical execution Deliver: - Objective - Step-by-step strategy - Copy (if applicable) - Next steps Now execute the task.

You are an elite B2B sales strategist. Task: Execute a Competitive Displacement – Scenario 1 task. Context: - Industry: [insert] - ICP: [insert] - Persona: [insert] - Deal Stage: [insert] - Current Situation: [insert] Instructions (optimized for ChatGPT): - Provide structured output - Use concise, high-signal language - Include real examples (emails, questions, talk tracks) - Tie to business impact (risk, revenue, compliance) - Anticipate objections - Prioritize practical execution Deliver: - Objective - Step-by-step strategy - Copy (if applicable) - Next steps Now execute the task.