The SaaS Sales Method: POD Structure

SaaS Sales Model

In the dynamic world of SaaS, a well-structured sales organization is essential for driving growth and ensuring customer success. One highly effective model is the POD structure. This model optimizes the sales process by dividing responsibilities among specialized roles, ensuring that every aspect of lead, sales, and customer management is handled efficiently. Let’s delve into the details of how the POD structure works, focusing on lead management, sales management, and customer management.

Lead Management

Lead management in a SaaS environment involves generating and nurturing leads to move them through the sales funnel. The POD structure allocates specific roles to handle this process seamlessly:

  • Marketing Development Representative (MDR): The MDR is responsible for the initial stages of lead management. Their primary task is to convert Marketing Qualified Leads (MQLs) into Sales Qualified Leads (SQLs). In a typical POD structure, one MDR converts 360 MQLs into 36 SQLs per month. This role is critical for maintaining a steady flow of high-quality leads for the sales team.

Sales Management

Sales management in a POD structure ensures that the sales team efficiently handles SQLs, converts them into opportunities, and closes deals. This involves a collaborative effort among various roles:

  • Sales Development Representative (SDR): The SDR takes over from the MDR, focusing on developing SQLs into potential sales opportunities. In our example POD structure, one SDR develops 24 SQLs per month, preparing them for the Account Executives (AEs).
  • Account Executives (AEs): The AEs are the primary drivers of revenue generation. In a POD structure, three AEs work together to secure 20 wins per month out of 60 SQLs. Their responsibilities include conducting demos, negotiating contracts, and closing deals. This team effort ensures a high conversion rate and consistent revenue growth.

Customer Management

Customer management is crucial for maintaining long-term relationships and ensuring customer satisfaction. The POD structure includes dedicated roles to manage customer onboarding and support:

  • Customer Success Manager (CSM): The CSM plays a pivotal role in onboarding new customers and ensuring they receive maximum value from the product. In a typical POD, one CSM is responsible for onboarding 20 new deals per month. They work closely with customers to provide training, support, and ongoing engagement, fostering customer loyalty and reducing churn.

The POD Structure in Action

A well-implemented POD structure can generate significant revenue and ensure operational efficiency. Here’s a breakdown of a typical POD setup and its impact:

  • Lead Management: 500 MQLs per month
  • Sales Management: $20,000 in Monthly Recurring Revenue (MRR)
  • Customer Management: 1 MDR, 1 SDR, 3 AEs, 1 CSM

This setup generates $1.56 million per year in Annual Recurring Revenue (ARR). The roles within the POD work in harmony to achieve these results, each focusing on their specialized tasks to drive overall success.

Example: Monthly Flow in a POD Structure

  1. MDR: Converts 360 MQLs into 36 SQLs.
  2. SDR: Develops 24 SQLs into qualified sales opportunities.
  3. AEs: Secure 20 wins per month from the 60 SQLs handled.
  4. CSM: Onboards 20 new deals per month, ensuring smooth transitions and customer satisfaction.

Conclusion

The SaaS Sales Method POD Structure is a powerful model that optimizes lead management, sales management, and customer management. By dividing responsibilities among specialized roles, the POD structure ensures that each aspect of the sales process is handled with expertise and efficiency. This model not only drives revenue growth but also fosters strong customer relationships, making it an invaluable approach for any SaaS business aiming for sustainable success.

Blog post was inspired by the book:
Blueprints for a SaaS Sales Organisation by Jacco van der Kooij and Fernando Pizzaro

Subscribe for new articles!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.