Financial Scenario Simulator

Overview

Built for a real, specific financial situation and designed as a system to revisit as real numbers change, not a one-time answer. Four tabs, meant to be read in order: a financial-literacy guide (the why), a six-step strategy framework (the what and when), a slider-driven month-by-month simulator (the how much and by when), and a deliberately separate tracker for non-emergency savings goals. Four principles shaped every decision: sequence matters more than any single tactic; show the math instead of just stating a conclusion; keep the user in the decision-making seat rather than prescribing one right answer; and plain language without being condescending.

Ownership

• Independent, self-directed project applying MBA coursework to something real and usable, not left as classroom material.
• I personally designed the simulation engine's logic: independent per-debt amortization with an auto-snowball option, three-phase contribution step-ups with individual toggles, a two-account retirement model that correctly separates an employer-matched 401k from an unmatched IRA, and a deliberate choice to exclude a 529 college fund from the net-worth total since it's the child's money, not the household's.
• I built a second, fully sanitized copy of the tool specifically so it could be shared as a public work sample, with every personal financial detail stripped out and rewritten in general terms — a deliberate decision to separate personal and shareable material.

Proof

• The tool is live and publicly usable, not a mockup — charts are rendered directly on HTML canvas with no external charting library, so the tool works fully offline.
• A full authored methodology write-up documents the tax modeling, the amortization and auto-snowball engine, the retirement account structure, and the return assumptions used (deliberately conservative relative to the underlying funds' historical average).
• Real, cited historical market statistics are used throughout, sourced to named outlets.

Outcome

• A complete, still-live, still-usable product — not an abandoned draft — including a version deliberately sanitized for public sharing.
• The explanatory writing throughout doubles as evidence of clear, plain-language technical writing.
• No adoption or usage metrics exist yet; the outcome evidence here is the artifact's completeness and quality, not usage data.