Scaling professional services in multi-product SaaS

When SaaS companies go from one product to several, the services challenge compounds fast. What worked for a single offering rarely scales to many.

Justin Collins, Vice President of Professional Services at Proofpoint, has lived through that transition. At Propel25, Justin’s session focused on their journey of scaling professional services in a multi-product company as well as the organizational questions that came with it.

Here are the key takeaways from the session.

6 lessons from scaling services in a multi-product enterprise

When Proofpoint acquired a company with a completely different tech stack, they made a familiar mistake: they kept everything separate, delivery models, services teams, and customer experiences.

Operationally, it looked clean. In reality, it created friction for customers and constant negotiation across internal teams.

1. Fragmented orgs = fragmented experiences

Customers buying across product lines had to go through two separate onboarding paths. Internally, services leaders argued over headcount, timelines, and responsibilities.

Fragmentation helped no one. A unified services organization, regardless of how products are sold or acquired, is essential to create a seamless customer experience.

2. Structure beats good intentions

Collaboration doesn't scale just because people want it to. Real efficiency only kicks in when you align teams structurally, not socially.

Two rules emerged:

• One owner per outcome. Shared ownership kills accountability. Every engagement needs a single, named leader. Not a pair.
  
  
• Org design must follow metrics. If your team isn’t built around measurable outcomes, you’ll miss them by default.
  

3. Standardize selectively

Improving margins meant looking beyond internal delivery. Proofpoint began moving lower-touch segments to:

• Outsourced partners
• Low-cost delivery centers
• Automated, standardized deployment frameworks
  

But not every product, or customer, is ready for this model. Mature, well-defined products and low-complexity accounts are good candidates. Others still need hands-on support.

4. One point of ownership per customer

One of the costliest mistakes in multi-product onboarding is assigning different consultants to different products in the same account. 

Every customer needs a single-threaded owner, even if that means building a specialized PMO. 

5. Success must be defined, and measured, the right way

In bundled deals, customers rarely want everything. Forcing full adoption is a waste. You need clear, pre-aligned expectations. For instance, you need to be able to answer questions like:

• What percentage of adoption equals success?
• Is a 7/10 product rollout a win?

Also, traditional measures like “utilization” are outdated. They show busyness, not value. The org shifted to success-aligned metrics:

• Customer satisfaction: Did they get value?
• Time to value: How fast did it happen?
• Implementation friction: Was it painful or smooth?
• Referenceability: Would they recommend the experience?

6. Redefine what “done” means in multi-product delivery

Multi-product projects rarely move in lockstep. One product may go live in a week. Another could take a year. Using a binary definition of “done” forces premature closures or bloated timelines.

Here’s what worked for Proofpoint:

• Holding projects open for the contract term (1–3 years): This gives customers room to implement on their timeline without starting over.
• Supporting staged delivery in tooling: This helps track each product’s status individually, don’t force a false “open vs. closed” model.
• Staying aligned with finance: Revenue recognition must account for staged rollouts and deferred go-lives. If the customer delays, the project stays open by design. If they opt out, close it, and recognize revenue.

The three pillars of Proofpoint’s multi-product approach 

1. Manager alignment with Sales

They aligned services managers directly to the sales regions they supported. This gave every region:

• A single point of contact, regardless of which product was purchased
• A clear owner of delivery success, accountable for outcomes in that region.
  
  

2. A shared technical resource pool

Instead of each manager owning and staffing their technical teams, Proofpoint created a shared pool of consultants. Key moves included:

• Matrixed management: Line managers handled career development, but didn’t “own” their consultants’ availability
• Skills matrix: Every consultant’s capabilities were documented, making assignments based on skill, not proximity
• Central coordination team: A neutral resource management function matched talent to projects, preventing resource hoarding.
  
  

3. Virtual practices for product specialization

To maintain product depth, Proofpoint created virtual practices consisting of groups of experts aligned to specific product sets. These teams were tasked with:

• Interfacing directly with product and engineering
• Serving as a structured feedback loop for customer pain points
• Ensuring implementation challenges inform product decisions

Getting matrix organizations right: When to use them and how to make them work

Leaders often hear about matrix organizations as a solution for scaling complexity, but the reality is, most implementations fail because they’re adopted too early or managed poorly. 

A matrix model is unnecessary, and often counterproductive, until certain thresholds are met:

• Three or more active products: Complexity increases when multiple teams must work across more than one product line.
  
  
• Headcount around 20–25 or higher: Once teams grow beyond this size, resource conflicts and prioritization issues surface across functions.

Why matrix models fail (and how to avoid this)

Many matrix efforts fall apart because of cultural resistance, not structural design. The most common failure mode: leaders who come from siloed, region-based management backgrounds struggle to adapt to shared accountability. In their previous roles, they owned performance end-to-end. 

To succeed in a matrix environment, you need to:

• Rewire managerial expectations: Managers must understand that while they are accountable for outcomes in their region, they share resource ownership with their peers. Success depends on collaboration across regions, not just execution within a silo.
  
  
• Centralize coordination: One of the most effective decisions is to remove resource assignment from individual managers and hand it to a neutral central coordination team. This improves prioritization based on company goals, not local preferences, and increases transparency and fairness in resource allocation.

Check out the rest of our Propel25 recaps here for more insights from the industry’s best.