Is it better for Intercom to develop a more robust API for developers or improve our no-code solutions for non-technical users?

Introduction

The trade-off between developing a more robust API for developers or improving no-code solutions for non-technical users is a critical decision for Intercom's product strategy. This scenario involves balancing technical depth with user accessibility, potentially impacting our market reach and product adoption. I'll analyze this trade-off by examining our product ecosystem, user segments, and business objectives to provide a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about Intercom's current market position. Could you share our market share in the customer communication space and how it's trending?

Why it matters: Helps determine if we need to focus on expanding our user base or deepening engagement with existing users. Expected answer: Moderate market share with steady growth. Impact on approach: A growing market share might favor improving no-code solutions to attract more non-technical users.

• Business Context: Based on our revenue model, I assume API usage contributes significantly to our income. What percentage of our revenue comes from API-based integrations versus standard product usage?

Why it matters: Helps prioritize development efforts based on revenue impact. Expected answer: 30-40% from API integrations. Impact on approach: A high percentage would lean towards prioritizing API development.

• User Impact: I'm curious about our user segmentation. What's the split between technical and non-technical users in our current customer base?

Why it matters: Identifies which user group might benefit more from our focus. Expected answer: 60% non-technical, 40% technical. Impact on approach: A higher percentage of non-technical users might justify prioritizing no-code solutions.

• Technical: Considering our current API, what are the most requested features or improvements from our developer community?

Why it matters: Helps assess the urgency and potential impact of API improvements. Expected answer: Better documentation, more endpoints, improved rate limits. Impact on approach: Specific, high-demand improvements might make the API development more attractive.

• Resource: What's our current team composition in terms of API developers versus UX/UI designers for no-code solutions?

Why it matters: Helps understand our capacity to execute on either option. Expected answer: Balanced team with slight lean towards UX/UI. Impact on approach: Team composition might influence which option is more feasible in the short term.