How can Onit balance the need for customization in its Contract Lifecycle Management solution with the desire for faster implementation times?

Introduction

Balancing customization and implementation speed for Onit's Contract Lifecycle Management (CLM) solution presents a critical trade-off. This scenario involves weighing the benefits of tailored solutions against the efficiency of rapid deployment. I'll analyze this trade-off through the lens of product strategy, user impact, and business objectives.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming Onit is facing pressure to reduce implementation times while maintaining its reputation for highly customizable CLM solutions. Could you confirm if this is the case, and if there are any specific market or competitive factors driving this pressure?

Why it matters: Helps understand the urgency and external factors influencing the decision. Expected answer: Confirmation of market pressure and possibly mention of specific competitors. Impact on approach: Would influence the balance between customization and speed in our solution.

• Business Context: Based on typical CLM business models, I'm thinking Onit's revenue might be split between software licensing and implementation services. What's the current revenue breakdown, and how might shifting towards faster implementations affect this?

Why it matters: Helps assess the financial implications of changing the implementation approach. Expected answer: Breakdown of revenue sources and potential impact on service revenue. Impact on approach: Would influence how aggressively we pursue faster implementations.

• User Impact: I'm assuming Onit serves a range of clients from mid-size to enterprise. How do customization needs vary across these segments, and which segment is growing fastest?

Why it matters: Helps tailor the solution to the most critical user segments. Expected answer: Breakdown of customization needs by segment and growth rates. Impact on approach: Would help prioritize which customizations to maintain or streamline.

• Technical: Considering the complexity of CLM systems, I'm thinking there might be core modules that are common across implementations. What percentage of a typical implementation involves custom work versus configuring standard modules?

Why it matters: Helps identify opportunities for standardization without sacrificing key customizations. Expected answer: Breakdown of standard vs. custom work in typical implementations. Impact on approach: Would guide efforts to modularize and standardize parts of the solution.

• Resource and Timeline: I'm assuming implementation teams are a bottleneck. What's the current average implementation time, and what's the target we're aiming for?

Why it matters: Helps set concrete goals for improvement and assess resource allocation. Expected answer: Current and target implementation timelines. Impact on approach: Would set benchmarks for our solution and help prioritize speed improvements.