PayFlow: Real-Time Payment Analytics for Small Business Owners

PayFlow is a payment analytics dashboard for small business owners who need to understand their cash flow without hiring an accountant. I joined as the sole product designer when the startup had a functional MVP but users were overwhelmed by data density. My challenge was transforming complex financial metrics into an intuitive interface that non-technical founders could actually use. Working with a team of 3 engineers and a product lead, I spent 5 months redesigning the core dashboard experience, focusing on progressive disclosure and contextual insights that help users make faster business decisions.

Small business owners were drowning in spreadsheets and disconnected payment tools. They needed to track revenue across Stripe, PayPal, and Square, but each platform showed data differently. PayFlow aggregated everything into one dashboard, but the initial design dumped 40+ metrics onto a single screen. Users told us they felt more confused after logging in than before. The real problem wasn't missing data, it was information overload. Business owners wanted quick answers to simple questions like "Am I making money this month?" and "Which customers haven't paid?" but had to dig through charts and tables to find answers.

• The dashboard showed every possible metric at once, creating cognitive overload. Users couldn't distinguish critical information from nice-to-have stats. Heat maps revealed they only looked at 6 metrics regularly but had to scroll past 40 others. I needed to prioritize information without hiding functionality that power users might need later.

• Financial data is inherently complex, but our users weren't accountants. Terms like "net revenue" and "payment velocity" meant nothing to them. Charts showed trends but didn't explain what actions to take. I had to translate financial jargon into plain language while maintaining accuracy for users who did understand the terminology.

• Business owners check their dashboard at different times for different reasons. Morning checks focus on overnight transactions, while end-of-month reviews need historical trends. The static layout couldn't adapt to these varying contexts. I needed to design a system that surfaced relevant information based on timing and user behavior patterns.

• When payment issues occurred, users needed immediate alerts, not passive notifications. A failed transaction could mean a lost customer, but the original design buried alerts in a notification center. I had to balance urgency with avoiding alert fatigue, ensuring critical issues got attention without overwhelming users with minor updates.

• I introduced a card-based layout where each metric lived in its own container. The top row showed the 4 most critical metrics (revenue today, pending payments, failed transactions, top customer). Users could customize which cards appeared and rearrange them. Advanced metrics lived in an expandable "More Insights" section, reducing initial cognitive load by 70%.

• Every metric got a plain-language explanation and contextual tooltip. Instead of "Net Revenue: $12,450," I wrote "You made $12,450 after fees this month." Charts included annotations like "Your best day was Tuesday" with a small info icon explaining why. This dual-layer approach served beginners while letting experts toggle to technical view.

• I designed a smart summary section that changed based on time of day and recent activity. Morning logins showed overnight transactions and today's forecast. End-of-week visits highlighted weekly trends and upcoming payments. The system learned from user behavior, surfacing the metrics they checked most often. This made the dashboard feel personalized without requiring manual configuration.

• Critical alerts appeared as banner notifications at the top of the dashboard with clear action buttons. Failed payments got a red banner with "Retry Payment" CTA. I implemented a three-tier system: critical (immediate action needed), important (review soon), and informational (FYI only). Users could snooze non-critical alerts, preventing notification fatigue while ensuring urgent issues got immediate attention.