top of page

Understanding Everyday Expense Tracking Behavior

Expense tracking often fails not because people lack access to tools, but because those tools don't fit naturally into the way people work. For small business owners and entrepreneurs, capturing receipts, organizing expenses, and retrieving financial information often becomes a fragmented process spread across multiple apps, folders, and manual workflows.

​

This project explores how business owners manage expense tracking in their day-to-day routines, where friction occurs in their existing workflows, and how insights from these behaviors can inform a more intuitive receipt management experience.

Understanding the Problem

Imagine you own a business and its tax season. It's time to track your expenses for the year and file your taxes for the business.  You are now searching for a receipt needed for a critical tax deduction, only to realize it’s lost or buried among dozens of emails and paper slips.

 

This real-world challenge highlights a broader behavioral problem: how freelancers and small business owners capture, organize, and retrieve financial information in everyday life.  

​

The Problem for small businesses during tax season:

​

  • Expense tracking is fragmented and time-consuming, often relying on folders, email searches, and spreadsheets.

  • Critical receipts are frequently lost, resulting in missed tax deductions.

  • Manual tracking increases stress and is prone to human error.

  • Existing digital tools often overwhelm users with unnecessary features, creating friction instead of support.

​

To investigate this problem, I conducted qualitative research with freelancers and small business owners to understand their behaviors, pain points, and unmet needs. Insights from this research directly informed the design of wireframes, prototypes, and interactive solutions. This case study walks through my process, from defining the problem and conducting research to synthesizing insights, iterating on designs, and validating solutions through usability testing.

Research Approach & Methods of Inquiry

01: Interviews

Conducted 6+ semi-structured interviews with freelancers and small business owners. Focused on understanding daily routines, cognitive load during expense tracking, and common pain points.

 

Questions were designed to uncover not only what participants do, but why they make certain choices.

02: Contextual Inquiries

Observed participants in real-life tracking situations, reviewing receipts, email organization, and spreadsheet usage, to capture workflow inconsistencies and breakdowns.

 

This helped identify the points where tracking habits fail and what environmental or contextual factors influence behavior.

03: Usability Test

Tested wireframes and interactive prototypes with 5 users to validate whether proposed designs addressed the real-world pain points identified in research.

 

Sessions focused on efficiency, error reduction, and cognitive load during receipt capture and retrieval.

User Insight: Business Owners

I conducted 7 user interviews and observational studies with freelancers and independent contractors to understand their workflow. 
 

  • Interviews were chosen to capture nuanced behaviors and motivations not visible in analytics.

  • Contextual inquiry allowed observation of habitual breakdowns that users could not verbalize.

  • Usability testing validated whether solutions aligned with natural workflows rather than assumed workflows.



Insights from data synthesis shows that users spend an average of 5+ hours/month organizing receipts, with some major pain points as listed:

​

  • Receipts are scattered across email, paper, and apps, and sometimes it can be difficult to stay organized

  • With busy business seasons, its easy to forget to track small purchases.

  • ​With receipts and expenses scattered across apps, this can sometimes bring anxiety during tax season due to missing info.

Pre-validation: v.1

The initial prototype version was designed with regular users in mind; people who want to track their own everyday expenses, not businesses or freelancers. However, upon further research and validation with business owners, insights provided clearer direction for which user groups will value this product the most.

Feature Title

Share your feature information here to attract new clients. Provide a brief summary to help visitors understand the context and background.

Feature Title

Share your feature information here to attract new clients. Provide a brief summary to help visitors understand the context and background.

Feature Title

Share your feature information here to attract new clients. Provide a brief summary to help visitors understand the context and background.

Insights and Tradeoff

  • Manual entry and categorization were time-consuming and error-prone.

  • Users wanted automatic extraction of receipt details and found it more useful for business expenses.

  • Email receipts require consolidation.​

  • Additional needs included monthly summaries, alerts for missing receipts, and reminders for tax season.

​

To solve for this, i explored 3 core solutions:

  1. OCR Receipt Capture to automatically extract vendor, date, amount and other details.

  2. Smart Categorization to predict expense type; allowing users to confirm or adjust if categorized incorrectly.

  3. Automated Insights & Summaries that generates monthly reports and highlights missing receipts.

​

Explore

Smart Categorization: 

Predicts expense type; users can confirm or adjust.

01

 OCR Receipt Capture:

Automatically extracts vendor, date, and amount.

02

Automated Insights & Summaries: 

Generates monthly reports, highlights missing receipts.

03

Feature Prioritization

Based on observed behavioral patterns, the design focused on reducing effort at the point of capture and supporting inconsistent user habits rather than forcing rigid workflows.

Enables immediate capture at the moment of interaction, addressing the tendency for users to delay or forget manual entry.

Quick Capture

Consolidates and organizes digital receipts automatically.

Smart Inbox

Visual overview of expenses, flagged anomalies, and proactive insights.

Monthly Dashboard

Easily send receipts or reports to accounting software.

Export & Share

Impact & Result

A reduction in the average time spent managing receipts has decreased the monthly administrative burden for freelancers from 5 hours to 30 minutes per month, meaning users can focus on billable work instead of admin — a 90% time savings, allowing satisfied businesspeople to focus on what truly matters. 

​

  1. Allowing users to capture receipts on the go without losing data.

  2. Business owners can manage multi-client expenses digitally with minimal effort.

Considerations for Future Iterations

  • While automation reduced manual effort, users needed clear confirmation states to trust that the system was working correctly.

  • Users consistently prioritized speed over advanced categorization, which reinforced the decision to keep the scanning flow minimal.

  • Conducting usability testing early in the process helped identify friction points before visual polish or feature expansion. This prevented unnecessary complexity and allowed design decisions to stay focused on real user needs rather than assumptions.

info@mysite.com
123-456-7890
500 Terry Francois Street,
San Francisco, CA 94158

  • Instagram
  • Facebook
  • X
  • LinkedIn
  • TikTok

Let's Work
Together

Contact Me

Home

About

Contact

© 2025 by Comfort Survival. Made with Wix Studio™

Let's Work
Together

info@mysite.com
123-456-7890
500 Terry Francois Street,
San Francisco, CA 94158

Home

About

Contact

  • Instagram
  • Facebook
  • X
  • LinkedIn
  • TikTok

© 2025 by Comfort Survival. Made with Wix Studio™

Sharing, bookmarking and saving for later

Usability testing surfaced a clear pattern: educators wanted to save resources for later, share them with colleagues, and quickly judge whether a resource was worth their time — how long an activity would take, how much prep it required, and whether it matched their provincial curriculum.

​

To solve for this, I designed a bookmarking feature that surfaces the key decision-making information at a glance — estimated time, prep level, and curriculum relevance — so educators can judge fit before clicking in, rather than digging through a resource to find out. I also added a lightweight social proof signal, showing how many educators had engaged with a resource that week, to help teachers gauge quality and relevance quickly when browsing unfamiliar content.

Status Request Updates

Usability testing also revealed that educators had no visibility into the status of their outreach requests once submitted — the only way to check progress was to email customer service directly and wait for a reply, often leaving educators uncertain whether their request had even been received.

​

To solve for this, I designed a real-time notification system that surfaces status updates directly within the dashboard, removing the need for educators to leave the platform or wait on email. This also benefited customer service staff, who could update a request's status directly and have that change reflected instantly for the educator — closing the communication loop for both sides rather than just one.

Screenshot 2026-07-28 at 11.13.56 AM.JPEG

Technical reality shaped the design

Upon developement of MVP 1.0, Drupal wasn't reliably pulling data into content cards. Canvas LMS didn't integrate cleanly, so course progress couldn't be shown as planned — this shaped fallback states and what moved to v2.

Navigating stakeholder tension

Stakeholders wanted a unified login and brand consistency with the main website — a real tension with the dashboard's own interaction needs.

Outcome: validated by users, paused by stakeholders

When tested with real educators, the MVP was well received — but stakeholders didn't yet have enough confidence to launch, given its limited scope. Rather than a failure, this became a structured pause: feedback from both educators and stakeholders is now shaping a second iteration that addresses the original technical limitations and stakeholder concerns directly.

bottom of page