How might Divvy (Draper) enhance its mobile app to provide more real-time insights into company spending patterns?

Introduction

To enhance Divvy's mobile app with real-time insights into company spending patterns, we need to consider the evolving needs of finance teams and company decision-makers. I'll outline a strategic approach to improve this critical feature, focusing on user needs, technical feasibility, and business impact.

Step 1

Clarifying Questions

• Looking at Divvy's position in the expense management market, I'm curious about the current user base and their engagement levels. Could you share some information about our active user count and how frequently they're accessing real-time spending data?

Why it matters: This helps us understand the scale of impact and prioritize features based on usage patterns. Expected answer: Around 100,000 active users, with 60% accessing real-time data at least weekly. Impact on approach: High engagement would prioritize advanced features, while low engagement might focus on improving accessibility and notifications.

• Considering the competitive landscape, I'm wondering about our unique value proposition. How does our current real-time insight feature compare to competitors like Expensify or Concur?

Why it matters: Identifies gaps and opportunities for differentiation in our solution. Expected answer: We offer faster updates but less granular categorization than some competitors. Impact on approach: Would focus on enhancing categorization while maintaining our speed advantage.

• Given the importance of data accuracy in financial reporting, I'm interested in our current data refresh rate and any limitations. What's our current latency for updating spending data, and are there any technical constraints we should be aware of?

Why it matters: Determines the feasibility of truly "real-time" updates and potential infrastructure needs. Expected answer: Current latency is 15 minutes, limited by API calls to banking partners. Impact on approach: Might explore predictive analytics or push notifications to mitigate latency issues.

• Thinking about the broader company strategy, I'm curious about how this feature aligns with Divvy's long-term goals. Are there any specific business objectives or KPIs that this enhancement should support?

Why it matters: Ensures our solution aligns with company-wide initiatives and metrics. Expected answer: Aiming to increase user retention by 20% and expand into enterprise market. Impact on approach: Would prioritize features that demonstrate clear ROI and scalability for larger organizations.