Creating Focus in Revenue Teams by applying the Stanford PARC Modeling
Stanford University Pictures from Author′s private library.

Creating Focus in Revenue Teams by applying the Stanford PARC Modeling


Operationalizing Focus

FOCUS has always been a widely discussed topic but operationalizing focus is a challenge for many sales leaders who have to make multiple strategies work while creating high-performance teams. That’s why I use the Stanford PARC method, which exemplifies the best way to create focus and keep strategic perspective as we operate the revenue machine.


The PARC Model I learned at Stanford

The Strategic Leadership class is a must and it was because of this key lesson.

The PARC model was published by Jesper B. S?rensen, a Stanford professor that states the design of an organization directly affects its ability to deliver superior capabilities and sustain them over time. Extensive research shows that there is no single correct organizational design. Every organization is unique, with different policies, practices, and cultures. Even among highly successful organizations in the same industry, there are significant differences in how companies operate. PARC is an acronym for the key elements of organizational design: People, Architecture, Routines, and Culture. These are the main elements to focus on when trying to understand how an organization works and assessing the degree of organizational and strategic alignment.

People (First!)

  • Knowledge, Skills, and Training: Hire for cultural fit and skills (but consider the cultural add when needed). A cohesive team is more productive. Hire account executives and customer success managers who deeply understand SaaS metrics. Use structured interviews and practical tests to assess cultural fit and skills.
  • Employee Motivation: Understand what motivates your employees – money, the meaning of work, or community. Offer stock options and opportunities to work on innovative projects. Offer incentives aligned with individual motivations.
  • Employee Expectations: Align employee expectations with career and life opportunities at the company. Create clear career paths within the company for software engineers. Create personalized career development plans.

Architecture and Routines

  • Organizational Structure: Structure your team with clear roles and responsibilities, organizing tasks by function, vertical, product, or customer segment. Use a pod structure for sales or CSM teams to cover different market segments. Create detailed job descriptions and set expectations from day one.
  • Organizational Hierarchy: Determine whether your hierarchy should be flat or have many layers, depending on coordination needs. A flat structure can speed up decision-making in a fast-paced SaaS environment. Regularly evaluate the effectiveness of the hierarchy. Make sure your span of control for AEs is no bigger than 1:6 (1 leader for 6 AEs), and BDRs max (1:10). This is given the level of complexity. Your Heads should be either splitted by Squad or Vertical, or Channel. If you created a Velocity Service Level, make sure that team is empowered and concise enough to move quickly.
  • Employee Compensation: Consider how employees are compensated – do they receive a share of profits directly or indirectly? What is the total On Target Earnings (OTE) ? Use performance-based bonuses tied to MRR targets. Adapt compensation plans to align with company goals but make sure to create momentum and celebrate as much as possible.
  • Decision-Making Process: Define clear decision-making processes, decision matrix, opportunity creation criteria and pricing approvals should be crystal clear. Also delegating or centralizing authority as needed is critical, so do not concentrate power into one single role, but create criteria so everyone has a degree of ownership. Implement agile methodologies and most specifically retrospectives with the revennue teams for quick decision-making and iteration.
  • Role Definition: Decide whether jobs will be specific or whether employees will cover a wide range of tasks. Are you going to split acquisition from expansion? What channels will be operating and what type of roles will be needed. Focus on the sales cycle and ICP for different Service Levels.
  • Teamwork: Promote teamwork to increase collaboration. Encourage cross-functional teams for product and GTM involvement. Squads are great for this. Eg. everyone working on the Finance Squad meet once a week (including CSMs, AEs, BDRs, Product, and Support). Structure projects that require collaborative efforts.
  • Knowledge and Information Flow: Ensure that knowledge and information flow freely within the organization. Choose the right CRM for you. Salesforce, Hubspot or others, but it might be fit for purpose (and budget). Also Slack and Confluence to enhance information sharing. Establish fit for purpose tech stack to facilitate communication and information sharing (check integrations with outreach tools like Apollo, DemandBase, 6sense too )

Culture (stronger than strategy)

  • Core Values: Identify and promote the core values of the organization. Emphasize adaptability, diversity and customer-centricity in company values. Integrate these values into daily practices.
  • Shared Beliefs and Assumptions: Understand the shared beliefs and assumptions of employees. Foster a belief in data-driven decision-making. Use these beliefs to guide decision-making.
  • Consensus and Strong Values: Assess the degree of consensus among employees about what is important and how the world works. Ensure all team members are aligned on the importance of user experience. Reinforce these values and beliefs through clear communication and leadership examples.

Critical Tasks

The final element of the PARC model is the set of critical tasks that the organization needs to accomplish to succeed. These tasks are the activities that the firm absolutely has to perform to deliver on its competitive advantage. They link your strategy to your organization: they translate the strategy into actionable steps.


Here a few personal tips on where your core focus should be:

  • Lead Generation "Don't scale until you have continued lead generation and a clear understanding of your sources and you revenue per lead (e.g. ARR/Signup)"
  • Lead Qualification "This goes in addition to your Ideal Customer Profile (ICP). To qualify a lead means to bring it closer to the opportunity definition by understanding if there is a fit, budget, or buying intent, and ensuring you are talking to the right persona."
  • Personalized Outreach "Forget the 'more leads, the merrier' mentality. Instead, focus on increasing perceived value. You'll need to balance volume to scale, but always start with quality first"
  • Sales Funnel Management "Sales specially in SAAS is a people game that is won with data. If your funnel is broken - your sales process is broken.
  • Scenario Building - "Make sure your sales team knows how to build different proposals and scenarios for your customer, and teach them the art of possible, many sales teams stick to transactional sales and have difficulties selling value. Scenario Building address some of this gap"
  • Simplified Onboarding - "Ensure you have the best possible onboarding - your team must know how to demonstrate and use your product well "

Final thoughts

Operationalizing focus using the PARC method can transform the way you structure your team and conduct your sales. Ensure your weekly, monthly and quarterly plan address the impact to the PARC model from each item of the activity list. These clear and effective strategies will help increase your MRR and consistently optimize your revenue growth.

If you are interested in discussing recurring revenue models, DM me let′s grab some coffee.??

Thomaz Coelho

Head of Customer Success @ Pipefy | Customer Success | CX | SaaS | Process Automation | RevOps | GTM | BPM | AI Workflows |

7 个月

Loved the article Nano! I had the chance to study this framework as well, very helpful on organizing an approach to complex environments, you nailed it on applying it to revenue team. Thanks for sharing your insights

Anne Johansson

Senior Enterprise Account Executive driving Enterprise Growth with Customer Success Expertise

7 个月

Nano, such an easy read for what is usually so dense to digest. Certainly a “save” for me. Thanks so much for sharing. It was the first time I read about PARC. Please keep up with posts like this one, always so comfortable to see things in your perspective.

Bill McCrossen

Exec. Coach Empowering Brazilians- Global Leadership & Communication

7 个月

Congrats, Fernando Henderson ?????! Very informative article! I’ve never heard of the PARC model. Thank you for sharing your insights! ??

Bernardo R.

Sales Development Manager at @Arena | Boosting Ad Revenue & Driving Engagement Solutions for Publishers

7 个月

Great Nano! i'd also like to add, specially on the Architecture-Teamwork part, that if possible, have your C-level present within the sales reps's day-to-day, listening, reading and even joining their live customer interactions. It's a win-win for both sides. For the C-level, those customer insights can help identify improvement points on product-valueprop and if needed, review strategy. For the reps, it's a great opportunity for recognition and to also help speed-up deals throughout the sales funnel.

Miguel Alcantara

Biotech Engineer | Onboarding Success Manager @ Oyster | Remote worker and Explorer

7 个月

Great article Nano, very PARCtical ?? But since we are talking about focus, felt like it needs a stronger attention into defining the ICP. For me that's the juice of focus and without it, not even the first step of the C (lead generation) is possible.

要查看或添加评论,请登录

Fernando Henderson ??????的更多文章

  • Esta é a Minha História de Orgulho

    Esta é a Minha História de Orgulho

    Quantos anos você tinha quando se assumiu como heterossexual? Parece uma pergunta estranha, né? O ponto aqui é que…

    48 条评论

社区洞察

其他会员也浏览了