Common Scenarios for Using the Weekly Action Plan
This guide illustrates how top-performing account executives use the Weekly Action Plan feature to address common sales scenarios. Each scenario includes the specific actions recommended by the system and real outcomes from successful AEs.
Scenario 1: Deal Approaching Close Date with Missing Decision Maker
System Identified Risk:
"Acme Corp deal is forecasted to close in 15 days, but no Economic Buyer has been identified or engaged."
Recommended Action:
Identify and engage Economic Buyer
The system recommended reaching out to the current champion to request an introduction to the economic decision maker, with a specific prompt for drafting an email that emphasized timeline urgency.
How a Top AE Used This:
Sarah J. used the AI-generated email template, customized it to include specific ROI metrics from earlier discovery calls, and sent it to her champion. Within 24 hours, she received an introduction to the VP of Operations who had final sign-off authority.
Outcome:
The deal closed on time after the VP of Operations joined the next demo call. Sarah maintained her forecast integrity and avoided what would have been a costly slip to the next quarter.
Scenario 2: Multiple Stakeholders with No Recent Contact
System Identified Risk:
"GlobalTech opportunity has 5 stakeholders with no communication in the last 21 days."
Recommended Action:
Re-engage key stakeholders
The system suggested sending a value-focused update to all stakeholders with recent customer success stories and new feature announcements relevant to their industry.
How a Top AE Used This:
Miguel R. used the AI prompt to create a concise email highlighting a recent case study from a similar company. He added specific benefits relevant to each stakeholder's role and included a recommendation for next steps with a clear call to action.
Outcome:
Three of the five stakeholders responded, revealing that the project had been temporarily paused due to a leadership change. Miguel was able to schedule a meeting with the new executive sponsor, salvaging what would have become a stalled opportunity.
Scenario 3: High-Value Deal Missing Business Impact Metrics
System Identified Risk:
"InnovateCorp deal ($650K value) is missing quantifiable metrics for business impact and ROI."
Recommended Action:
Validate business impact with metrics
The system provided a framework of specific questions to help quantify the business impact, focusing on time savings, cost reduction, and revenue opportunities.
How a Top AE Used This:
Alex T. scheduled a call with the Director of Operations using the suggested talking points. They collaboratively built a business case using the company's actual operational data, uncovering that the current process was consuming over 120 hours per month of team time.
Outcome:
The business case revealed a potential 380% ROI over three years. This became a key selling point that the champion used in their internal presentation to the executive team, leading to faster approval of the purchase.
Scenario 4: Late-Stage Deal with Potential Objections
System Identified Risk:
"TechFlow deal is in negotiation stage, but security requirements have not been thoroughly addressed."
Recommended Action:
Finalize terms and handle objections
The system recommended proactively addressing potential security compliance concerns before they became formal objections that could delay or derail the deal.
How a Top AE Used This:
Jordan L. used the AI-generated talking points to prepare for a call with the customer's security team. She invited Summit53's security engineer to join and address technical questions, and sent over SOC2 documentation and a security questionnaire response in advance.
Outcome:
The proactive approach satisfied the security team's requirements and prevented a potential 2-3 week delay in the procurement process. The deal closed on schedule with minimal redlining of the security terms.
Scenario 5: Leveraging Framework Relationship Insights for Task Creation
System Identified Risk:
"CloudSystems deal shows strong Metrics qualification (85%) but weak Budget alignment (25%). Framework relationship analysis flagged this as 'mismatch' attention level."
Recommended Action:
🔗 Create Task from Framework Insight
The framework relationship card surfaced an actionable insight: "Schedule ROI workshop to align strong metrics evidence with budget approval process." The system displayed a "Create Task" button directly on the insight card.
How a Top AE Used This:
Taylor M. was reviewing the CloudSystems opportunity and noticed the framework relationship insight. With one click on "Create Task," the system automatically:
- Created a high-priority task in her weekly action plan
- Pre-populated the action: "Schedule ROI workshop"
- Included detailed context about the Metrics/Budget gap in the notes
- Set the due date to match the opportunity's close date
- Linked back to the source framework relationship for reference
Taylor used the auto-generated task notes to prepare for her call with the CFO, focusing the conversation on how their current metrics would translate into budget justification.
Outcome:
The ROI workshop resulted in a detailed business case that bridged the gap between proven metrics and budget approval. The CFO became an internal champion, using the ROI model to secure executive sign-off. The deal closed 2 weeks ahead of schedule with a 15% upsell based on the expanded scope identified during the workshop.
Scenario 6: Custom Task Management for Account-Level Activities
Business Context:
"Enterprise account 'DataFlow Industries' has 3 active opportunities but needs strategic relationship building at the C-suite level that doesn't fit into any single deal."
Recommended Action:
✏️ Create Manual Account Task
The AE recognized that quarterly business reviews (QBRs) with the CTO would benefit all three opportunities but wasn't specific to any single deal.
How a Top AE Used This:
Rachel K. clicked "Add Task" in her weekly action plan and selected "Account" as the entity type:
- Task Description: "Prepare and schedule Q1 QBR with DataFlow Industries CTO"
- Entity: DataFlow Industries (Account)
- Priority: 85 (High value account)
- Urgency: High
- Due Date: End of quarter
- Notes: "Cover usage trends across all 3 opportunities, renewal timeline, and expansion roadmap"
The task appeared in her weekly action plan alongside AI-generated deal-specific actions, ensuring it didn't fall through the cracks despite not being tied to a single opportunity.
Outcome:
The QBR strengthened the strategic relationship with the CTO, who shared insights about upcoming projects that led to a $450K expansion opportunity. The manual task system allowed Rachel to manage account-level relationships alongside deal-specific actions in a unified view.
Key Takeaway: Manual tasks excel at capturing account and contact-level activities that span multiple opportunities or don't fit the AI-generated action patterns.