For Doma's machine intelligence platform, should we emphasize developing new risk assessment algorithms or enhancing integration capabilities with third-party mortgage software?

Introduction

For Doma's machine intelligence platform, we're facing a critical trade-off between developing new risk assessment algorithms and enhancing integration capabilities with third-party mortgage software. This decision will significantly impact our product's value proposition and market positioning. I'll analyze this trade-off by examining our product strategy, user needs, technical considerations, and business implications.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking our platform's current performance might be influencing this decision. Could you share how our existing risk assessment algorithms and integrations are performing relative to industry benchmarks?

Why it matters: Helps determine if we're addressing a performance gap or seeking a competitive advantage Expected answer: Performance is good but not industry-leading Impact on approach: Would focus on innovation rather than catch-up

• Business Context: Based on our revenue model, I assume we charge per transaction or have a tiered pricing structure. Is this correct, and how does it factor into our strategic priorities for the year?

Why it matters: Aligns solution with revenue generation and growth targets Expected answer: Tiered pricing with focus on enterprise clients Impact on approach: Would prioritize features attractive to larger clients

• User Impact: I'm curious about our user segments. Are we primarily serving large financial institutions, or do we have a significant base of smaller lenders as well?

Why it matters: Ensures solution addresses needs of key user segments Expected answer: Mix of large and small lenders, with growth focus on larger institutions Impact on approach: Would balance solution to serve both segments while emphasizing enterprise features

• Technical: Regarding our current architecture, how modular is our system? Does it allow for easy integration of new algorithms or third-party software?

Why it matters: Determines technical feasibility and resource requirements Expected answer: Moderately modular, but some legacy systems present challenges Impact on approach: Would consider technical debt and potential refactoring needs

• Resource: Considering our team structure, do we have more expertise in algorithm development or in integration engineering?

Why it matters: Helps assess internal capabilities and potential skill gaps Expected answer: Stronger in algorithm development, integration team is smaller Impact on approach: Might lean towards algorithmic innovation unless integration is a critical bottleneck