How would you improve receipt submission in the Ramp mobile app for employees who spend on their Ramp card?

Introduction

Receipts are the smallest unit of pain in expense management. Every Ramp card swipe creates a transaction that needs a receipt, a memo, and the right accounting code before finance can close the books. Ramp already automates much of this: it matches emailed receipts, pulls itemized receipts from some merchants, and lets employees snap a photo in the mobile app or reply to an SMS. Yet the long tail of missing receipts is what finance teams still chase at month-end. The question is how to improve receipt submission in the Ramp mobile app so that fewer transactions ever reach "missing receipt."

I'll clarify the context, segment users, walk through the journey to find pain points, generate solutions, prioritize with RICE, and define metrics.

Step 1

Clarifying Questions (5 minutes)

• Looking at the goal, are we trying to reduce missing receipts, reduce employee time spent, or improve accuracy for finance? I'll assume the primary goal is reducing transactions that remain without a receipt after seven days, with employee time as a secondary goal.

• Considering the current state, what share of receipts already arrive automatically through email forwarding, integrations, or SMS? I'll assume roughly 60% are matched automatically and the remaining 40% depend on the employee acting in the app.

• Thinking about user mix, are we focused on employees with physical cards, virtual cards, or both? I'll focus on physical card spend at in-person merchants (meals, taxis, supplies), where receipts are paper and easily lost.

• On constraints, are there compliance rules such as IRS documentation requirements above certain amounts? I'll assume the company sets a receipt threshold (for example, all transactions over $75) and Ramp enforces it.