For Globality's services procurement solution, how do we balance automating more of the sourcing process versus maintaining human oversight and relationship management?

Introduction

The trade-off we're examining today is how to balance automating more of the sourcing process versus maintaining human oversight and relationship management in Globality's services procurement solution. This scenario touches on the core tension between efficiency and personalization in B2B SaaS products. I'll approach this analysis by examining the product context, identifying key metrics, designing experiments, and providing a structured decision framework.

Step 1

Clarifying Questions (3 minutes)

• Based on the current market trends, I'm thinking automation is becoming increasingly important in procurement. Could you share more about the competitive landscape and how our automation capabilities compare to other players?

Why it matters: Helps position our solution in the market and informs prioritization. Expected answer: We're mid-range in automation, with room for improvement. Impact on approach: Would influence the urgency and extent of automation efforts.

• Considering our user base, I'm assuming we have a mix of enterprise and mid-market clients. Can you provide more details on our customer segments and their preferences regarding automation vs. human touch?

Why it matters: Different segments may have varying needs, affecting our trade-off decision. Expected answer: Enterprise clients value relationship management more, while mid-market prefers efficiency. Impact on approach: Would lead to a potentially segmented strategy.

• From a technical perspective, I'm curious about our current automation capabilities. What areas of the sourcing process are already automated, and where do we see the most potential for further automation?

Why it matters: Identifies low-hanging fruit and technical constraints. Expected answer: Basic vendor matching is automated, but scope definition and negotiation still require human input. Impact on approach: Would help prioritize which areas to focus automation efforts on.

• Regarding our team structure, I'm wondering about the current balance between our technology and customer success teams. How are we currently resourced to handle automation development versus relationship management?

Why it matters: Helps understand internal constraints and potential resource reallocation needs. Expected answer: Tech team is larger, but customer success is growing to meet demand. Impact on approach: Would influence how quickly we could implement changes in either direction.

• Thinking about our product roadmap, I'm curious about the timeline for this decision. Is this a near-term priority or part of a longer-term strategic shift?

Why it matters: Affects the scope and depth of changes we can consider. Expected answer: Mid-term priority, looking to implement changes within 6-12 months. Impact on approach: Would determine the scale of experiments and implementation plans.