Selected Work
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 controlled expense-review workflow that imports transaction data, flags duplicates and missing fields, maps vendors to categories and projects, assigns review statuses, and separates exceptions from export-ready transactions.
Business value: Faster review, stronger spending controls, clearer ownership, and less manual cleanup before reimbursement or accounting entry.
Built with: Excel · Python in Excel · Mapping tables · Exception reporting · Export-ready outputs
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, project, receipt or invoice.
Reimbursement, vendor bill, or organization-card purchase.
Required fields, approvals, duplicates, and supporting documentation.
Assign category and project using vendor and purpose rules.
Resolve exceptions and confirm coding before payment or posting.
Needs action
Missing documentation, incomplete fields, pending approval, or duplicate warnings.
Ready to proceed
Clean records ready for reimbursement, vendor billing, card matching, or ERP-ready 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 & controlled — changes in one statement flow through and impact the others.
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.