Should Tradeshift invest in developing a mobile app to increase user engagement or allocate resources to enhance our API capabilities for better system integrations?

Introduction

The trade-off we're considering is whether Tradeshift should invest in developing a mobile app to increase user engagement or allocate resources to enhance our API capabilities for better system integrations. This decision involves balancing user-facing improvements against backend infrastructure enhancements. I'll analyze this trade-off by examining our product ecosystem, potential impacts, key metrics, and experimental approaches to inform a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Based on our current user base, I'm thinking mobile usage might be significant. Could you share what percentage of our users currently access Tradeshift via mobile devices?

Why it matters: Helps gauge potential impact and adoption of a mobile app Expected answer: 30-40% mobile usage Impact on approach: Higher mobile usage would strengthen the case for app development

• Considering our revenue model, I assume API integrations play a crucial role. What percentage of our revenue is tied to customers using our API integrations?

Why it matters: Indicates the strategic importance of API capabilities Expected answer: 50-60% of revenue from API-integrated customers Impact on approach: Higher API-related revenue would prioritize API enhancements

• Looking at user behavior, I'm curious about engagement patterns. What's our current average user session frequency and duration?

Why it matters: Helps identify engagement gaps that a mobile app could address Expected answer: 3-4 sessions per week, 15-20 minutes per session Impact on approach: Lower engagement might justify mobile app investment

• Regarding our technical infrastructure, how scalable is our current API architecture?

Why it matters: Determines urgency of API enhancements Expected answer: Moderate scalability, approaching limits with current growth Impact on approach: Lower scalability would prioritize API improvements

• Considering resource allocation, what's our current team composition between mobile and API developers?

Why it matters: Influences feasibility and timeline for each option Expected answer: 70% API developers, 30% mobile developers Impact on approach: Imbalance might affect development speed for chosen option