Why implement a framework?

As a Solutions Engineer, I've consistently observed that the most effective prospect engagements begin with a deep, structured understanding of the prospect's goals, pain points, and current processes. With this goal in mind, our solution engineering team developed the Discovery Summary Framework—a structured approach designed to consistently capture the essentials of each discovery call, ensuring every insight is substantiated and no critical information is overlooked.

This framework provides both sales and solution engineering teams with a clear path for each prospect, connecting Rocketium’s features directly to what matters most to the prospect. For our prospects, it also means that their unique challenges are understood from the outset, allowing us to shape our demos and solutions to address their actual needs. In essence, this framework enhances alignment across all sides, focusing on high-priority areas to drive more strategic, solution-focused conversations.

The Discovery Summary Framework: Overview

Our goal is straightforward: to generate a discovery call summary grounded in verified, accurate data. Each point in the summary is validated against direct quotes or documented information from the initial and discovery calls. Supplementary research is included only when appropriate and explicitly marked for transparency.

Building Blocks of the Framework

1. Company Overview: We begin by creating a comprehensive snapshot of the company's organizational structure and operational processes. The focus is on the specific use cases and goals discussed during the call, ensuring every insight is validated against the transcript.
   When necessary, we supplement this section with external research and contextual information from previous sales interactions, always maintaining a clear distinction between primary and secondary sources.

2. Team and Business Goals

   • Primary Objectives: We document the principal business initiatives and strategic goals the prospect aims to achieve.

   • Specific Goals: We quantify the precise outcomes the prospect seeks, illustrating how Rocketium can support their key results.

   • Potential Impact: We capture the anticipated operational or strategic transformations resulting from achieving these goals.

3. Current Workflow Overview: This section provides a detailed breakdown of the prospect’s workflow, covering:

   • Specific stakeholders

   • Existing tools

   • Performance metrics

   Every component is supported by conversational evidence, eliminating assumptions and providing a structured foundation for subsequent discussions.

4. Identified Pain Points

   • Bullet-Pointed Pain Points: Each pain point is summarized with direct quotes for validation.

   • Metric Validation: For any mentioned pain point, we follow up to capture relevant metrics (e.g., turnaround time). This ensures all data is based on shared insights, with no assumptions about timeframes or volumes.

5. Key Decision Makers

   We list the key decision-makers identified during the call, detailing their roles and responsibilities. This helps the team understand who influences the buying process and the role of each stakeholder.

6. Competition or Capabilities

   Any capabilities or competitors referenced by the prospect are noted in this section.

7. Action Items and Demo Requirements

   We outline the next steps and specific demo requirements exactly as described by the prospect. This ensures follow-ups are straightforward and aligned with their expectations.

8. Derived Business Goals for Rocketium

   Finally, we summarize any business goals Rocketium can address based on the prospect’s stated needs and challenges. This section connects their pain points with our solution’s impact areas.

Genesis of the Framework

The framework has evolved with every call and each piece of feedback we’ve gathered over several months. The process draws from three key areas of primary research:

1. Discovery Insights: Calls with prospects across sectors such as media, retail, banking, and automotive helped shape an industry-agnostic approach to summarizing calls and extracting actionable insights.

2. Sales Team Collaboration: Feedback from our sales team revealed confirmation biases in earlier processes, where inference-based summaries led to misalignments. This insight reinforced the need for rigorous validation of insights.

3. Market Research on Discovery Best Practices: We studied industry best practices to refine our approach, emphasizing consultative, outcome-focused discovery processes validated by stakeholder feedback.

MEDDPICC Framework Integration

The MEDDPICC methodology significantly influenced our framework's design, emphasizing:

• Precise metric definition

• Clear pain point identification

• Comprehensive decision process mapping

• Stakeholder influence analysis

This methodology shaped our emphasis on rigorous validation and data-backed insights, ensuring every summary is actionable, reliable, and directly relevant to Rocketium and the prospect.

By implementing this framework, we’ve not only improved alignment and focus during pre-sales discussions but also enhanced our ability to deliver tailored solutions that resonate with our prospects’ unique needs.

This is where your strategic ally—Customer Success—steps into the spotlight. Trust us: a strong Customer Success function is not just beneficial—it’s essential for sustainable business growth.

Key Drivers for Building Rocketium’s Customer Success Team

a) Growing the business: Rocketium offers license-based access to customers upon onboarding as a creative operations management platform. In this model, recurring revenue hinges on year-over-year (YOY) renewals and upsells. As our sales team grew, we ramped up trials and pilots on a weekly and monthly basis. The shift to introduce a CS team allowed sales to focus on converting prospects into customers. At the same time, Customer Success took ownership of seamless onboarding and delivering a top-notch product experience.

b) Preventing Churn: While growth is appealing, preventing revenue leakage is equally crucial if you want a healthy business. The customer Success team could actively identify at-risk accounts and take corrective actions. Regular check-ins, QBRs (Quarterly Business Reviews), and health checks helped CS identify and address pain points before they escalated.

c) Customer advocacy: Our first enterprise customers included global leaders like Amazon, Infosys, and Walmart. Establishing trust was pivotal to securing their long-term advocacy. A dedicated Customer Success team delivered tailored guidance for setup, usage, and achieving impactful outcomes. Satisfied customers became brand advocates, driving referrals and reducing CAC.

d) Driving innovation: The CS team leverages their account knowledge to identify customers who would benefit from or value a new feature. By engaging in regular customer interactions and gathering feedback, they can pinpoint the ideal candidates to test new functionality, fostering early adoption of the features.

The Framework of Rocketium’s Customer Success Team

We are a lean, high-performing team dedicated to exceeding expectations. Over time, we’ve experimented with different structures, always aligning with our evolving business needs and product goals.

As of today, our team operates within 7 specialized pods:

1. Enterprise Pods (2): Focused on expanding and retaining enterprise customers, comprising Senior Customer Success Managers (Sr. CSMs), Customer Success Managers (CSMs), and Customer Success Associates (CSAs).

2. Small Accounts Pod: Dedicated to managing smaller customer accounts.

3. Support Pod: Handles customer tickets and ensures timely issue resolution.

4. Onboarding Pod: Oversees seamless onboarding for new customers.

5. Go-to-Market (GTM) Pod: Focused on executing go-to-market strategies and initiatives.

6. Solutioning Pod: Customizes platform setups to meet unique customer requirements and provides technical consultations, at the pre-sales stage.

How Customer Success Outpaces Support

One of the key distinctions between customer success and customer support is their approach to driving business impact. Customer success is proactive, while customer support primarily addresses reactive challenges. In building a B2B SaaS business, growth is significantly influenced by customer relationships and product experience. The proactive nature of the customer success team ensures they engage with customers before issues arise, rather than waiting for problems to surface. Their goal is to anticipate potential challenges, prevent disruptions, and help customers extract maximum value from their investments.

Real-world wins with Customer Success

• Case Study 1: Workflow Transformation for a Latin American Marketplace (on-demand delivery)

  Challenge: An early enterprise customer in the Latin American market sought to scale their video creative production significantly. However, inefficiencies in their workflow caused delays, leading to customer dissatisfaction.
  
  Solution: Our customer success team stepped in to investigate the root cause. By analyzing the customer’s end-to-end workflow on Rocketium, they discovered that .MOV files were being used as base templates. These large files were difficult to adapt within Rocketium’s platform, resulting in slower conversions.

  
  Outcome: Collaborating closely with the customer, our team recommended switching to .MP4 files. This seemingly minor change dramatically improved efficiency, enabling faster adaptation and seamless product adoption.

• Case Study 2: Streamlining Processes for Asia's Leading Fashion Marketplace
  Challenge: The customer aimed to produce creatives at scale but faced significant challenges. Setting up banner templates on Rocketium was proving difficult, and despite their extensive efforts, the desired reach remained elusive.

  
  Solution: Our customer success team intervened to boost product adoption by identifying blockers through in-depth discussions. They discovered that the customer's banner designs were overly complex, making them unsuitable for scaling. Partnering with design consultants from our managed services team, the customer success managers guided the users on adopting a minimalist design approach.

  Outcome: By simplifying their templates and reducing visual components, the customer not only eased the setup process but also improved the likelihood of audience engagement and visibility.