In developing Notarize's business services, should we emphasize customization options for enterprise clients or standardize offerings to streamline operations and reduce costs?

Introduction

The trade-off we're examining today is whether Notarize's business services should emphasize customization options for enterprise clients or standardize offerings to streamline operations and reduce costs. This decision is crucial for Notarize's growth strategy and operational efficiency. I'll analyze this trade-off by considering user needs, business impact, technical feasibility, and long-term strategic implications.

Step 1

Clarifying Questions (3 minutes)

• Based on our current enterprise client base, I'm thinking we might have a mix of industries with varying regulatory requirements. Could you give me an overview of our top enterprise client segments and their primary use cases for Notarize?

Why it matters: Helps understand the diversity of client needs and potential impact of standardization Expected answer: Mix of financial services, real estate, and healthcare with different compliance needs Impact on approach: High diversity would lean towards customization, while similarity might favor standardization

• Considering our revenue model, I assume we have a tiered pricing structure for enterprise clients. How much of our current revenue comes from customization fees versus standard package pricing?

Why it matters: Indicates the financial impact of moving towards standardization Expected answer: 30% from customization, 70% from standard packages Impact on approach: Higher customization revenue would require careful transition planning

• From a user perspective, I'm curious about the adoption rates of custom features versus standard offerings. Do we have data on feature usage across our enterprise clients?

Why it matters: Reveals actual value of customization to clients Expected answer: Mixed usage, with some custom features highly utilized and others rarely used Impact on approach: Would help identify which features to standardize and which to keep customizable

• Technically, I'm wondering about the current architecture of our platform. How modular is our system, and what would be involved in creating a more standardized offering?

Why it matters: Determines feasibility and effort required for standardization Expected answer: Moderately modular, would require significant refactoring for full standardization Impact on approach: High technical debt might favor gradual standardization approach

• Regarding our team capacity, how are our product and engineering resources currently split between maintaining custom solutions and developing new features?

Why it matters: Indicates potential efficiency gains from standardization Expected answer: 40% on custom maintenance, 60% on new development Impact on approach: High maintenance overhead would strengthen case for standardization