For Pipedrive's mobile app, should development efforts focus on feature parity with the desktop version or on creating unique mobile-first experiences?

Introduction

For Pipedrive's mobile app, we're facing a critical decision: should we focus on achieving feature parity with the desktop version or prioritize creating unique mobile-first experiences? This trade-off involves balancing user expectations, resource allocation, and strategic product positioning in the competitive CRM market.

In my analysis, I'll examine the context, evaluate potential impacts, design experiments, and provide a data-driven recommendation. Let's start by clarifying some key aspects of this situation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about Pipedrive's current market position. Could you share how our mobile app usage compares to desktop, and what percentage of our users are primarily mobile?

Why it matters: Helps determine the potential impact and urgency of mobile improvements. Expected answer: 30-40% mobile usage, growing steadily. Impact on approach: Higher mobile usage would prioritize mobile-first experiences.

• Business Context: Based on our revenue model, I assume mobile improvements could impact user retention and upsells. How does mobile app engagement correlate with our key business metrics?

Why it matters: Aligns product decisions with business objectives. Expected answer: Strong correlation between mobile engagement and customer lifetime value. Impact on approach: Would justify more investment in unique mobile experiences.

• User Impact: Considering our user segments, I'm curious about the differences in mobile usage between small businesses and enterprise clients. Can you provide insights on this?

Why it matters: Helps tailor our approach to key user segments. Expected answer: Small businesses rely more heavily on mobile. Impact on approach: Might lead to segment-specific mobile features.

• Technical: Regarding our current tech stack, how challenging would it be to maintain feature parity across platforms versus developing unique mobile features?

Why it matters: Assesses feasibility and long-term maintenance costs. Expected answer: Feature parity is more straightforward but limits mobile innovation. Impact on approach: Easier parity might influence short-term decisions, but could limit long-term mobile growth.

• Resource: Thinking about our team structure, do we have dedicated mobile developers, or would this require reallocating resources from other projects?

Why it matters: Determines our capacity for mobile-focused development. Expected answer: Limited dedicated mobile resources. Impact on approach: Might necessitate a phased approach or additional hiring.