with the skill
## Research Synthesis: Clearclaim Expense Submission
**Method:** Six interview summaries | **Participants:** 6
**Timing:** Last week | **Researcher:** Not specified
### Executive Summary
Receipt-capture failures were the most common issue, reported by **4 of 6 participants**, with examples of manual re-entry and difficulty scanning damaged receipts. Slow approvals affected **2 of 6 participants**; one explicitly delayed submissions as a result. Both sales reps tracked mileage outside Clearclaim, suggesting an opportunity to simplify that workflow. SAP integration was a non-negotiable requirement for the CFO interviewed—a potentially important enterprise sales blocker, but not evidence of broad demand.
### Key Themes
#### 1. Unreliable receipt capture creates extra work
**Prevalence:** 4 of 6 participants: P1, P2, P4, P6.
**Supporting evidence:**
- “I took a photo of a taxi receipt at night, it came out dark and the app rejected it. I gave up and typed it all in by hand.” — P1
- “Thermal receipts get crumpled in my van and the scanner can't read them.” — P4
- “Half my receipt photos bounce.” — P6
- P2 reported two rejected receipt photos in the previous week.
**Implication:** Capture is failing under real-world conditions, including poor lighting and damaged receipts. Failures add work and may undermine confidence in a core workflow. P5 explicitly reported no capture issues, so the problem is not universal.
Show the rest (58 more lines)
#### 2. Approval delays can discourage timely submission
**Prevalence:** 2 of 6 participants: P4, P5.
**Supporting evidence:**
- “I wait about nine days for my manager to approve anything.” — P5
- P4 reported slow approvals and said he consequently stops submitting until month end.
**Implication:** Submission friction extends beyond the employee-facing app. Clearclaim may need to help approvers act sooner, but these notes do not establish whether delays come from missing notifications, unclear ownership, workload, or company policy.
#### 3. Mileage tracking happens outside Clearclaim
**Prevalence:** 2 of 6 participants—both sales reps: P2, P6.
**Supporting evidence:**
- “I log mileage in a notebook and add it up on Fridays. Takes 20 minutes.” — P2
- P6 tracks mileage manually in a spreadsheet.
**Implication:** Sales reps have an ongoing mileage workflow that Clearclaim is not currently serving effectively. The interviews do not establish whether mileage functionality is absent, hard to find, or unsuitable.
#### 4. Enterprise adoption may depend on accounting integration
**Prevalence:** 1 of 6 participants: P3, the CFO of a 400-person company.
**Supporting evidence:**
- “If you don't integrate with SAP, we're out. Non-negotiable.” — P3
**Implication:** SAP integration is a purchase gate for this prospective buyer. Its strategic importance could outweigh its low frequency in this sample, but broader demand and implementation requirements need validation.
### Insights → Opportunities
*Impact and effort are preliminary hypotheses, not measured estimates.*
| Insight | Opportunity | Potential impact | Effort |
|---|---|---|---|
| Receipt capture fails in everyday conditions | Diagnose rejection reasons; improve low-light/damaged-receipt handling; offer guided retries and a fallback that preserves entered data | High | Medium–High |
| Approval delays affect reimbursement and submission behavior | Investigate the approval workflow; test reminders, aging queues, and escalation | Medium–High | Medium |
| Sales reps maintain separate mileage records | Test quick mileage entry and automatic totals before investing in automated trip tracking | Medium; concentrated in sales users | Medium |
| SAP is a deal-breaker for one enterprise buyer | Validate requirements and commercial demand before committing to an integration | Potentially high for enterprise sales | High, scope-dependent |
### User Needs Identified
These are **overlapping needs, not validated market segments**:
- **Receipt-heavy mobile workers:** Reliable capture in imperfect conditions — 4 participants.
- **Employees affected by slow approvals:** Faster decisions and better status visibility — 2 participants.
- **Sales reps tracking mileage:** Less manual logging and calculation — 2 participants.
- **Enterprise finance buyers:** Compatibility with existing finance systems — 1 participant.
### Recommendations
1. **Prioritize receipt-failure diagnosis and recovery.** This is the broadest observed pain point. Track rejection reasons, retry success, manual-entry fallback, and completion after rejection.
2. **Investigate approval delays with managers as well as submitters.** Establish where time accumulates before choosing reminders or escalation as the solution.
3. **Prototype a lightweight mileage workflow with sales reps.** Test whether quick entry and weekly totals eliminate the notebook/spreadsheet workaround.
4. **Run SAP discovery in parallel with enterprise sales validation.** Treat it as a separate commercial decision—not automatically the lowest priority because only one participant raised it.
### Questions for Further Research
- What causes receipt rejection, and which failures can users recover from?
- Where do approvals stall, and what prompts managers to act?
- Why are sales reps using external mileage tools?
- Which SAP product, data flows, and integration requirements does the CFO need?
### Methodology Notes
This synthesis uses brief summaries, not full transcripts. Counts describe only these six interviews, not the wider customer base. Participants may not have been asked identical questions; an issue not mentioned should not be interpreted as an issue not experienced.