Financial Planning Cases: The Actual Work Behind the Numbers
Most people think financial planning is just spreadsheets and projections. It isn't. The real work lives in how you present a case to someone who either trusts you completely or suspects you are selling something. I have sat across the table from both types and learned quickly that the spreadsheet does not win arguments. The framing does. When I first started doing client-facing work, I made the mistake of leading with the model. I had a beautiful DCF build, sensitivity tables, Monte Carlo outputs, the whole thing. The client looked at it for exactly three seconds and asked me to simplify. He did not want to see the mechanics. He wanted to know whether his retirement timeline held up and what he should do about it next quarter. So I rebuilt the entire presentation around outcomes, not inputs.Cases In Financial Planning Analysis And Presentation
The difference between a case that lands and one that bounces off sits in three areas: structure, specificity, and the way you handle uncertainty. Beginners bury uncertainty in footnotes. They should be front and center. I remember a specific situation with a 54-year-old client who wanted to retire at 62. His portfolio was 70 percent equities, heavily concentrated in one employer stock that made up 18 percent of his total assets. The standard model said he would run out of money at 78 under a 4 percent withdrawal assumption. Most planners would then show him a sequence-of-returns risk chart and call it a day. That is where people lose trust. The chart is technically correct but emotionally useless. My workaround was to flip the timeline. Instead of showing the retirement cliff at 78, I showed him four specific years where his probability of shortfall hit above 30 percent: ages 59, 62, 66, and 71. Then I mapped every one of those risk years to a concrete action he could take right now. The first year required adjusting his vesting schedule. The second required trimming the employer stock over 18 months. The third meant delaying Social Security by two years. The fourth was about switching to a guards-and-riders withdrawal strategy instead of a flat percentage. He left the meeting with four dated to-dos instead of one vague anxiety. That is what a proper case looks like in practice.
How to Build the Case Before You Open Any Model
Most people open their modeling tool first. That is backwards. The model follows the story, not the other way around. If you cannot explain the situation in three plain sentences before you touch the spreadsheet, your assumptions are probably hiding something. Start by writing down the client question. Not the financial question, the real one. Is it “can I afford this?” “will I outlive my money?” “is this trade-off worth it?” The answer to that question determines your entire structure. A “can I afford this” case is radically different from a “will I outlive my money” case even if they use identical input data. I have seen cases fail because the planner built the wrong kind of analysis for the wrong kind of question. Someone asked whether they could buy a vacation home and got a full retirement shortfall model. That does not answer the question. It answers a different question dressed up as the original one.
The Structure That Actually Works
Do not use the standard intro-definition-method-example-conclusion format. Your audience does not need a textbook. They need a narrative that respects their attention span and gives them something actionable by the end. Here is the order I use now after burning through years of bad presentations. I lead with the current state, then the pressure points, then the decision paths, then the mechanics, and finally the next steps. This is inverted compared to most training materials, but it mirrors how people actually think about money problems. Current state comes first because it builds immediate credibility. List the assets, income streams, debts, and projected liabilities in plain language. No jargon. If you have to use a term like “liquidity-adjusted net worth,” define it in the same sentence or rewrite the phrase entirely.
Get the Full Details
Pressure points are where the friction lives. These are the specific moments in time where cash flow could break, where assumptions could reverse, or where an event could change everything. A client in their late 40s with a variable income and two kids in college faces very different pressure points than a 61-year-old couple with fixed pensions and no debt. Do not conflate the two. Decision paths are the branches. Every real financial case has multiple viable routes, not one right answer. Present at least two and preferably three, each with its own risk profile, cash flow impact, and trade-offs. I once had a client who only saw one path because I had not shown him the alternatives. He signed up for a plan that looked optimal on paper but fell apart when his business income dropped in year two. That mistake cost him six months of stress and a revised plan he did not want. The mechanics come after the narrative because that is when people care about the numbers. A model shown without context is noise. A model shown after the story is evidence. This shift alone usually changes how long the client spends looking at your sensitivity tables. Before, they ignored them entirely. After, they ask about the 10th percentile outcome.
Next steps are not a summary. They are a dated action list with names, deadlines, and decision checkpoints. “Review quarterly” is not a next step. “Call us by March 15 to decide on the Roth conversion window” is a next step.
Common Mistakes That Kill Credibility
The biggest mistake is over-precision. Planners love showing five decimal places in IRR calculations and presenting them as if the number means something. It does not. A withdrawal rate of 3.847 percent implies a level of accuracy that no model actually possesses. Round to two decimals at most. The client does not need to know whether their success probability is 72.3 percent or 72.7 percent. They need to know whether it is above or below 70. Another mistake is hiding the base case inside a cloud of scenarios. Present the most likely outcome first, clearly labeled, then show the upside and downside cases. When everything is one scenario among many, nothing feels real. When the base case is explicit, the alternatives have weight. I also see too many cases that confuse correlation with causation in their assumptions. A planner might tie healthcare costs directly to inflation and ignore the fact that medical inflation often decouples from CPI during certain economic cycles. This is a niche point but it matters when you are modeling a 20-year horizon. The difference can be 15 to 25 percent in total projected healthcare spending depending on which inflation curve you pick. If you do not tell the client which curve you used, you are not being transparent. You are being careless.
Tools That Save Time Without Replacing Judgment
There are tools that genuinely help here. Python builds with libraries like pandas and numpy cut modeling time from hours to minutes. But the speed advantage means more time for judgment calls, not fewer. When I used Excel for everything, I had less time to think about whether the assumptions were sane because I was still building the engine. For visualization, Plotly and Matplotlib produce decent static outputs, but the interactive dashboards are where the real value sits in a live client meeting. Being able to adjust a slider for withdrawal rate and watch the probability of success shift in real time changes the conversation entirely. The client stops asking abstract questions and starts asking specific ones like “what happens if I retire two years later.” One caveat: do not let the tool become the product. I have watched planners spend more time making their dashboard look pretty than checking whether the underlying assumptions were defensible. A messy model with solid logic beats a beautiful model with fragile logic every single time. Clients eventually notice when the numbers do not match their intuition. A dashboard cannot hide that gap.
When the Standard Approach Fails Completely
There are cases where traditional financial planning analysis hits a wall. Self-employed professionals with highly variable income are one. The standard withdrawal strategy breaks down when income swings plus or minus 40 percent year to year. A flat percentage withdrawal creates cash crunches in low years and leaves money on the table in high years. The workaround I use is a band-based withdrawal system. Define a lower band, an upper band, and a target band. In years where income falls below the lower band, withdrawals drop to a pre-set floor. In years above the upper band, excess cash flows into a reserve bucket. The model then shows smoothed consumption over time instead of volatile payouts. This adds complexity but the complexity is honest. It reflects the actual constraint rather than pretending the constraint does not exist. Another hard case is clients with illiquid assets making up more than 30 percent of net worth. Real estate, private equity, closely held business interests. The standard models assume you can sell or borrow against these at fair market value on demand. That assumption fails in stress scenarios. I usually run a separate liquidity contingency analysis alongside the main projection, assuming it takes 12 to 24 months to liquidate the illiquid portion at a 15 to 25 percent discount. This changes the sequence-of-returns calculation significantly, especially for clients near retirement.
How to Handle the Conversation When the Number Is Bad
Sometimes the case does not work. The client cannot retire when they want to with their current savings rate. They cannot fund the education they envisioned. They cannot afford the lifestyle they assume. This is the hardest part of the job because most planners either soften the news too much or deliver it like a hammer. The approach that works is direct but not dramatic. State the gap plainly. Then reframe it as a set of choices rather than a verdict. “You are short by about 18 percent of your target income at retirement. Here are the four ways we close that gap, and here is the trade-off each one requires.” Then show the client picking the path that matches their values, not just their risk tolerance. I learned this from a mentor who had a habit of asking a specific question when a case broke. He would say “which part of this story do you want to change.” Not “what do you want to give up.” Not “can you work longer.” The question was deliberate. It gave the client agency over the narrative instead of making them feel like a problem to be solved.
A Note on Documentation and Review
Every case should leave a paper trail that survives the meeting. I write a one-page executive summary after each session. Not the full model. One page. Current situation, key pressures, chosen path, three risks, next action with date. This forces clarity and gives the client something to take home. Most clients will lose 80 percent of the meeting details within 48 hours if you do not give them something concrete to reference. The summary also protects you. If a client later claims you recommended something you did not, you have a dated document. This is not about litigation. It is about precision. People misremember conversations. A one-page summary locks in what was actually discussed. When a case goes through review, I treat the review as a stress test of the assumptions, not the conclusion. The client will challenge the outcome because it is visible. They will not challenge the assumption that healthcare costs grow at 6.5 percent per year because that number lives inside a footnote. That footnote is where the real work happens. Question every growth rate, every discount factor, every withdrawal assumption as if someone will try to break it. They will.
What This Looks Like in Practice
A typical case session runs about 75 minutes. The first 20 minutes are gathering and confirming the current state. The next 25 minutes are mapping pressure points and decision paths. The following 20 minutes are showing the model and walking through outcomes. The last 10 minutes are locking in next steps with dates. If the session runs longer than that, the client is usually processing the information in real time, which is fine. If it runs shorter, you probably skipped a step. Most planners who finish in 30 minutes have not covered the decision paths thoroughly enough. The client leaves feeling informed but unable to act. Follow-up timing matters too. The standard quarterly review is often too late for time-sensitive decisions. Roth conversion windows, tax law changes, market dislocations, and family events do not wait for your scheduled check-in. I usually set ad-hoc review triggers in the case file itself. If the client’s business revenue drops below a threshold, or if they receive an inheritance, or if a child starts college, those events trigger a review regardless of the calendar.
This is not theory. It is the structure I now use for almost every case, with variations depending on the client profile. The variations are where the expertise lives. The structure is what keeps the work reproducible.
