Case Studies
Representative finance systems, models, and reporting outputs built from operational and financial data. Client information and source data have been anonymized.
CASE STUDY 01
Business problem: Expense submissions, receipts, reimbursements, and approvals were fragmented across email and spreadsheets, creating duplicate transactions, missing documentation, inconsistent coding, and manual follow-up.
What I built: A self-serve expense tool that captures and submits expenses in seconds. Behind the scenes, transactions are auto-categorized, synced to QuickBooks, and routed for reimbursement or credit card matching, giving event organizers real-time visibility into spend against budget.
Business value: Faster submission, more consistent reimbursement, real-time visibility into spend against budget, and far less manual review.
Built with: Next.js · Supabase · QuickBooks API · Automated categorization
Representative prototype based on a real finance-operations workflow.
A controlled workflow for intake, validation, coding, review, and accounting-ready output.
Vendor, date, amount, purpose, receipt or invoice.
Reimbursement, vendor bill, or organization card purchase.
Required fields, approvals, duplicates, documentation.
Assign category and project using vendor rules.
Resolve exceptions, confirm coding before posting.
Vendor, date, amount, purpose, receipt or invoice.
Reimbursement, vendor bill, or organization card purchase.
Required fields, approvals, duplicates, documentation.
Assign category and project using vendor rules.
Resolve exceptions, confirm coding before posting.
Missing documentation, incomplete fields, or duplicate warnings.
Clean records ready for reimbursement or export.
Human review remains in the loop before payment, reimbursement, or accounting entry.
Representative workflow based on a real finance-operations process.
CASE STUDY 02
Business problem: Fragmented opportunity-level data made it difficult for leadership to consistently evaluate bookings, sales team performance, timing, segment economics, and geographic concentration.
What I built: A cleaned reporting model and executive dashboard combining opportunity level data into consistent management views.
Business value: Faster reporting, clearer revenue visibility, and a more reliable understanding of performance drivers.
Built with: Data cleanup · Mapping logic · KPI design · Executive reporting
CASE STUDY 03
Business problem: Leadership needed one controlled model linking operating performance, liquidity, working capital, financing needs, and balance sheet movement.
What I built: An integrated income statement, cash flow statement, and balance sheet driven by operating assumptions, working capital logic, financing activity, and integrity checks.
Business value: Clearer visibility into liquidity, burn, working capital, financing needs, and balance sheet risk.
Built with: Financial modeling · Cash forecasting · Working capital modeling · Balance sheet controls · Scenario analysis
A controlled model connecting operating performance, cash flow, and balance sheet movement.
Key Inputs
↓
Connected & ControlledChanges in one statement flow through and impact the others.
Management Outputs
Cash runway and near-term capacity
Operating cash consumption
Timing of cash tied up in operations
Funding requirements and timing
Impact of operating choices
Built to support clearer planning, cash visibility, and balance sheet integrity.