For Origami Risk's policy administration module, should we invest in expanding integration capabilities with third-party systems or enhance built-in underwriting automation tools?

Introduction

For Origami Risk's policy administration module, we're facing a critical decision: should we invest in expanding integration capabilities with third-party systems or enhance built-in underwriting automation tools? This trade-off involves balancing external connectivity with internal efficiency improvements. I'll analyze this decision through the lens of product strategy, user impact, technical considerations, and business alignment.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about the current market position of Origami Risk. Could you share how our policy administration module is performing compared to competitors? Why it matters: This helps us understand if we're playing catch-up or innovating ahead of the market. Expected answer: We're competitive but not leading. Impact: If we're behind, we might prioritize quick wins; if ahead, we could focus on differentiation.

• Business Context: Based on our revenue model, I assume integrations might open up new partnership opportunities. How significant is partner revenue in our current business strategy? Why it matters: This influences whether we prioritize ecosystem growth or internal efficiency. Expected answer: Partner revenue is growing but not dominant. Impact: A high partner revenue focus would lean towards integration investment.

• User Impact: Considering our user segments, I'm curious about the split between large enterprises and smaller insurers. What's the current distribution? Why it matters: Enterprise clients often require more integrations, while smaller clients might benefit more from built-in tools. Expected answer: 60% enterprise, 40% smaller insurers. Impact: A higher enterprise ratio would favor integration development.

• Technical Feasibility: Regarding our current architecture, how modular is our system for adding new integrations versus enhancing internal tools? Why it matters: This affects the complexity and timeline of each option. Expected answer: Moderately modular, with some legacy constraints. Impact: High modularity would make integrations easier to justify.

• Resource Allocation: Thinking about our team structure, do we have more expertise in integration development or underwriting automation? Why it matters: This impacts our ability to execute each option effectively. Expected answer: Balanced team with slight edge in automation. Impact: Strong integration expertise might tilt decision towards that option.