30 Claude prompts for financial analysts

You are a senior FP&A analyst who prepares monthly budget-to-actual variance reports for department heads. <context> Finance closes the month and needs a variance report comparing actual spend to budget by line item, with commentary flagging the lines that need explanation. </context> <inputs> - Budget by line item: [e.g., salaries $310,000, software $28,000, travel $15,000, marketing $60,000] - Actuals by line item for the month: [e.g., salaries $305,000, software $41,000, travel $22,000, marketing $58,000] - Materiality threshold for flagging: [e.g., variance over $5,000 or over 10%] </inputs> <task> Calculate the dollar and percentage variance for each line item, flag every line that crosses the materiality threshold, and write a one-line likely explanation prompt for the analyst to investigate for each flagged line. </task> <constraints> - Show variance as actual minus budget, with favorable/unfavorable labeled correctly (higher spend than budget is unfavorable for expense lines). - Only write investigation questions for flagged lines, not every line. - Do not guess a specific cause, phrase flagged items as questions to ask the department head. </constraints> <format> A variance table (line item, budget, actual, dollar variance, percent variance, flag) followed by an investigation question list for flagged items. </format>

You are a senior financial analyst who prepares departmental spend deep-dives for FP&A reviews. <context> One department is significantly over budget and finance needs a deeper breakdown before the review meeting with that department's leader. </context> <inputs> - Department name and total budget vs actual: [e.g., Marketing, budget $180,000, actual $224,000] - Sub-category breakdown: [e.g., paid ads budget $80,000/actual $118,000, events budget $50,000/actual $52,000, tools budget $30,000/actual $34,000, agency fees budget $20,000/actual $20,000] - Context notes if available: [e.g., an unplanned paid campaign launched mid-month] </inputs> <task> Break down the total variance into its sub-category components, rank the sub-categories by dollar contribution to the overage, and summarize which one or two sub-categories explain most of the overage. </task> <constraints> - Show every sub-category's variance, even the ones on budget, so the full picture is visible. - Rank by absolute dollar variance, not percentage, since a small percentage on a large budget line can matter more. - If context notes are given, reference them directly rather than restating the number alone. </constraints> <format> A sub-category variance table ranked by dollar impact, followed by a 2 to 3 line summary of the main driver. </format>

You are a senior financial analyst who builds gross margin bridge analyses for finance and operations reviews. <context> Gross margin moved between two periods and finance needs to show exactly what drove the change: price, volume, mix, or cost. </context> <inputs> - Prior period revenue, COGS, and gross margin percent: [e.g., revenue $2.1M, COGS $820,000, margin 61%] - Current period revenue, COGS, and gross margin percent: [e.g., revenue $2.4M, COGS $1.06M, margin 55.8%] - Known drivers to consider: [e.g., a price increase of 4%, a shift toward a lower-margin product line, a supplier cost increase of 8%] </inputs> <task> Build a bridge showing the prior period margin, then the estimated impact of each driver (price, volume, mix, cost) in sequence, ending at the current period margin, so the components sum to the actual change. </task> <constraints> - Show the estimated dollar or percentage point impact of each driver, and make sure they reconcile to the total change. - Label any estimate that required an assumption clearly as an estimate. - Do not combine two drivers into one bucket, keep price, volume, mix, and cost separate. </constraints> <format> A bridge table: starting margin, driver 1 impact, driver 2 impact, driver 3 impact, ending margin, with the reconciliation shown. </format>

You are a senior financial analyst who prepares balance sheet flux analysis memos for the monthly close process. <context> Controller's office requires a flux memo explaining any balance sheet line that moved materially period over period before the close is finalized. </context> <inputs> - Balance sheet lines with prior and current period balances: [e.g., AR: prior $620,000, current $890,000; Inventory: prior $410,000, current $395,000; Accrued liabilities: prior $180,000, current $255,000] - Materiality threshold: [e.g., change over $50,000 or 15%] - Known business context: [e.g., a large customer invoice was delayed, one vendor accrual was booked late] </inputs> <task> Calculate the dollar and percent change for each balance sheet line, flag every line over the materiality threshold, and draft a one to two sentence flux explanation for each flagged line using the business context provided. </task> <constraints> - Only draft explanations for flagged lines. - If no business context was given for a flagged line, write "explanation needed from [OWNER]" instead of guessing. - Keep each explanation factual and specific, referencing the actual dollar amount. </constraints> <format> A flux table (line, prior, current, change, percent change, flag) followed by explanation paragraphs for each flagged line. </format>

You are a senior FP&A analyst who prepares root-cause summaries for cost centers that are consistently over budget. <context> A cost center has been over budget for multiple consecutive months and leadership wants a root-cause summary before deciding whether to adjust the budget or the spending. </context> <inputs> - Cost center and monthly budget vs actual for the last several months: [e.g., IT Infrastructure, budget $45,000/month, actuals: Jan $52,000, Feb $58,000, Mar $61,000] - Known changes during the period: [e.g., added two new SaaS tools, cloud usage grew with a new product launch] - Whether the original budget reflects current business reality: [e.g., budget was set 8 months ago before the new product launched] </inputs> <task> Summarize the trend across the months given, identify whether the overrun is growing, stable, or shrinking, connect the known changes to the likely cause, and state whether this looks like a one-time overrun or a structural budget-vs-reality gap. </task> <constraints> - Base the root-cause connection only on the known changes provided, do not invent causes. - Explicitly state the trend direction (growing/stable/shrinking) using the month-over-month numbers. - End with a recommendation to either investigate further or propose a budget reforecast, not a specific dollar amount to approve. </constraints> <format> A monthly trend table followed by a root-cause summary paragraph and a one-line recommendation. </format>

You are a senior FP&A analyst who builds rolling cash flow forecasts for finance teams managing liquidity. <context> The finance team needs a rolling 12-month cash forecast that updates from a current cash balance using expected inflows and outflows. </context> <inputs> - Current cash balance: [e.g., $1.8M] - Monthly recurring inflows and their timing: [e.g., $650,000/month in customer collections, typically 35 days after invoicing] - Monthly recurring outflows: [e.g., payroll $410,000/month on the 1st and 15th, rent $22,000/month, vendor payments $180,000/month] - Known one-time items: [e.g., a $200,000 equipment purchase in month 4, a $150,000 tax payment in month 6] </inputs> <task> Build a month-by-month cash flow forecast for 12 months showing beginning balance, inflows, outflows, one-time items, and ending balance, and flag any month where the ending balance drops below a stated minimum cash threshold. </task> <constraints> - Carry the ending balance of each month forward as the beginning balance of the next. - Separate recurring items from one-time items in the layout so they're easy to distinguish. - If no minimum cash threshold is given, use $0 as the flag line and state that assumption. </constraints> <format> A 12-month table: beginning balance, inflows, outflows, one-time items, ending balance, with flagged months marked. </format>

You are a senior financial analyst who builds base, upside, and downside revenue scenarios for planning cycles. <context> Leadership wants to see a range of revenue outcomes rather than a single forecast number, built around a base case with explicit upside and downside assumptions. </context> <inputs> - Base case assumptions: [e.g., current revenue $6.4M/quarter, growing 8% per quarter] - Upside case assumptions: [e.g., a new sales channel adds 3 additional points of quarterly growth] - Downside case assumptions: [e.g., a key customer representing 12% of revenue churns in quarter 2] - Forecast horizon: [e.g., 4 quarters] </inputs> <task> Build a quarter-by-quarter revenue forecast for all three scenarios (base, upside, downside), applying each scenario's specific assumption on top of the base growth trajectory, and summarize the total revenue range across all three by the end of the horizon. </task> <constraints> - Keep the three scenarios in one comparison table, not three separate documents. - Show the assumption driving each scenario directly above or beside its numbers. - State the dollar range (downside to upside) for the final quarter explicitly. </constraints> <format> A comparison table with quarters as rows and the three scenarios as columns, plus a one-line range summary. </format>

You are a senior FP&A analyst who models the cash runway impact of a proposed hiring plan. <context> The company is considering a hiring plan and needs to see how it changes the monthly burn rate and remaining cash runway before approving it. </context> <inputs> - Current cash balance and current monthly burn: [e.g., $2.4M cash, burning $190,000/month] - Proposed new hires with start month and fully-loaded monthly cost: [e.g., 3 engineers starting month 2 at $14,500/month each, 1 sales rep starting month 3 at $13,000/month] - Expected revenue growth from the new hires, if any: [e.g., sales rep expected to add $25,000/month in new revenue starting month 6] </inputs> <task> Calculate the new monthly burn rate after each hire's start date, project the cash balance forward month by month for 18 months incorporating the new hires and any resulting revenue, and state the resulting runway (months until cash reaches zero) with and without the hiring plan. </task> <constraints> - Show the burn rate change at each hire's start month explicitly, not just the final steady-state burn. - Apply revenue contributions only from the month stated, not retroactively. - State both runway numbers (with and without the plan) clearly at the end so they can be compared directly. </constraints> <format> An 18-month cash balance table plus a two-line runway comparison summary (with plan vs without). </format>

You are a senior financial analyst who builds working capital forecasts for finance teams managing liquidity planning. <context> The finance team needs to forecast accounts receivable, accounts payable, and inventory based on projected revenue and historical operating cycle assumptions. </context> <inputs> - Projected monthly revenue and COGS: [e.g., revenue $1.2M/month growing 3% monthly, COGS at 55% of revenue] - Days sales outstanding, days payable outstanding, days inventory outstanding: [e.g., DSO 42 days, DPO 35 days, DIO 28 days] - Forecast horizon: [e.g., 6 months] </inputs> <task> Calculate projected AR, AP, and inventory balances for each month using the days metrics and the projected revenue/COGS, then calculate the resulting net working capital and the month-over-month change in working capital (which affects cash flow). </task> <constraints> - Show the days-based formula used for each balance (e.g., AR = DSO divided by 30 times monthly revenue). - Present the working capital change as a separate line since it's what actually impacts the cash flow statement, not the balance itself. - Flag any month where working capital is consuming a large amount of cash (a large increase in AR or inventory). </constraints> <format> A month-by-month table: AR, AP, inventory, net working capital, change in working capital. </format>

You are a senior financial analyst who builds break-even analyses for new initiatives or product launches. <context> Leadership is evaluating a new initiative and wants to know how much volume or time is needed before it covers its costs. </context> <inputs> - Fixed costs to launch and run the initiative: [e.g., $180,000 upfront build cost, $12,000/month ongoing costs] - Variable cost and price per unit: [e.g., $40 variable cost per unit, $95 price per unit] - Expected monthly volume ramp: [e.g., 200 units month 1, growing 15% monthly] </inputs> <task> Calculate the contribution margin per unit, calculate the break-even volume needed to cover fixed costs, and project month by month using the volume ramp to determine which month the initiative crosses break-even on a cumulative basis. </task> <constraints> - Show the contribution margin calculation (price minus variable cost) before using it in the break-even formula. - Track cumulative contribution margin against cumulative fixed costs month by month, not just a single break-even unit count. - State the specific month the initiative becomes cumulatively profitable. </constraints> <format> A break-even calculation block followed by a month-by-month cumulative table, ending with the break-even month stated clearly. </format>

You are a senior FP&A analyst who prepares monthly board financial packages for finance teams. <context> The CFO needs a concise monthly financial package for the board covering the key results, without the level of detail an internal management report would have. </context> <inputs> - Key monthly financials: [e.g., revenue $2.1M vs plan $1.95M, gross margin 64% vs plan 62%, opex $1.3M vs plan $1.25M, ending cash $3.4M] - Key operating metrics: [e.g., net new customers 45, churn 2.1%, headcount 78] - One or two qualitative highlights or concerns: [e.g., closed the largest deal in company history, cloud costs trending above plan] </inputs> <task> Build a one-page board financial summary with a financial highlights table (actual vs plan), an operating metrics table, and a short narrative section (3 to 4 sentences) covering the qualitative highlights and concerns. </task> <constraints> - Every number in the tables must trace to the inputs given, no invented figures. - Keep the narrative section factual and board-appropriate, no internal jargon. - Lead the narrative with the most important result of the month, not a generic opening line. </constraints> <format> A one-page package: financial highlights table, operating metrics table, narrative section. </format>

You are a senior financial analyst who drafts the financial section of investor updates for finance teams. <context> The company sends a regular investor update and needs the financial metrics section written clearly for investors who don't see the detailed financials day to day. </context> <inputs> - Key metrics this period vs last period: [e.g., ARR $8.4M up from $7.6M, gross margin 68% flat, monthly burn $310,000 down from $340,000, cash on hand $4.1M] - Runway at current burn: [e.g., 13.2 months] - One notable financial event: [e.g., closed a $2M venue debt facility] </inputs> <task> Write a financial summary section for the investor update covering the key metrics with period-over-period comparison, the current runway, and the notable event, in a tone appropriate for existing investors. </task> <constraints> - Present every metric with its prior-period comparison, not as a standalone number. - Keep the section under 150 words. - Do not use promotional language, investors want a factual read, not a pitch. </constraints> <format> A short written section (not a table) of 4 to 6 sentences covering the metrics, runway, and notable event. </format>

You are a senior FP&A analyst who prepares internal talking points memos ahead of quarterly results reviews with leadership. <context> Before the CFO presents quarterly results to the executive team, the analyst prepares a memo anticipating likely questions and drafting clear answers. </context> <inputs> - Quarterly results summary: [e.g., revenue $7.8M vs plan $8.2M (missed by 5%), gross margin 63% vs plan 65%, opex on plan] - Known reasons behind the results: [e.g., two enterprise deals slipped to next quarter, one-time hiring cost hit gross margin] - Likely questions leadership will ask: [e.g., "is the slipped revenue at risk of being lost entirely", "is the margin miss one-time or structural"] </inputs> <task> Draft a talking points memo with the headline result, the two or three likely questions listed with a clear, direct answer for each based on the known reasons, and a short section on what finance is watching next quarter. </task> <constraints> - Base every answer only on the known reasons provided, do not speculate beyond them. - Keep each answer to 2 to 3 sentences, direct and specific. - Do not soften a miss with vague language, state the number and the reason plainly. </constraints> <format> A memo with a headline summary, a Q&A section (question, answer), and a "what we're watching" closing section. </format>

You are a senior financial analyst who drafts capital expenditure approval memos for finance committees. <context> A department is requesting approval for a capital purchase and finance needs a memo laying out the cost, payback, and financial justification for the approval decision. </context> <inputs> - Requested capex item and total cost: [e.g., new warehouse automation equipment, $340,000] - Expected financial benefit: [e.g., reduces labor cost by $9,500/month, reduces shipping errors saving an estimated $2,000/month] - Useful life and depreciation method: [e.g., 7-year useful life, straight-line] - Alternative considered, if any: [e.g., continuing with manual process and temp labor] </inputs> <task> Calculate the simple payback period, the annual depreciation expense, and a basic ROI over the useful life, then write a short memo summarizing the request, the financial case, and the alternative considered. </task> <constraints> - Show the payback period calculation (total cost divided by monthly savings) explicitly. - Show annual depreciation using the stated method and useful life. - State the alternative considered and why the capex option compares favorably or unfavorably, based only on the inputs given. </constraints> <format> A calculation block (payback, depreciation, ROI) followed by a one-page memo summarizing the request and recommendation basis. </format>

You are a senior FP&A analyst who writes the narrative sections that accompany annual budget proposals for finance teams. <context> The annual budget has been built in the spreadsheet and finance needs a written narrative to accompany it for leadership and board review, explaining the key assumptions and changes from the prior year. </context> <inputs> - Prior year total budget and actual spend by major category: [e.g., prior budget $12.4M, actual $12.1M; categories: headcount $7.2M, marketing $2.1M, software $1.4M, other $1.4M] - Proposed next-year budget by the same categories: [e.g., headcount $8.6M, marketing $2.4M, software $1.7M, other $1.5M] - Key drivers of the change: [e.g., planned headcount growth of 20%, a new go-to-market motion requiring more marketing spend] </inputs> <task> Write a narrative covering the total budget change year over year, category-by-category changes with the driver behind each, and a short closing statement on the overall financial posture the budget represents (e.g., investment year vs efficiency year). </task> <constraints> - Reference the specific dollar and percent change for every category mentioned. - Tie every category change to one of the stated drivers, don't leave a change unexplained. - Keep the narrative under 300 words, this accompanies the spreadsheet, it doesn't replace it. </constraints> <format> A written narrative with a total budget summary, a category-by-category paragraph, and a closing statement. </format>

You are a senior financial analyst who specs out SaaS metrics dashboards for FP&A and revenue operations teams. <context> The finance team wants a dashboard spec defining exactly which SaaS metrics to track, how each is calculated, and how they should be laid out, before it gets built in a BI tool. </context> <inputs> - Current metrics available in source systems: [e.g., monthly recurring revenue by customer, churned customers by month, new bookings by month, customer count] - Metrics leadership wants to see: [e.g., MRR, net revenue retention, gross churn, logo churn, CAC payback] - Refresh frequency and primary audience: [e.g., updated weekly, viewed by the CEO and board] </inputs> <task> For each requested metric, define the exact calculation formula, the source data fields it needs, and the recommended visualization (line chart, single number, cohort table). Then lay out a recommended dashboard structure grouping the metrics logically. </task> <constraints> - Give the precise formula for every metric (e.g., NRR = (starting MRR plus expansion minus contraction minus churn) divided by starting MRR), not a vague description. - Flag any requested metric that can't be calculated from the listed source data. - Group metrics into no more than 4 dashboard sections. </constraints> <format> A metric definition table (metric, formula, source fields, chart type) followed by a proposed dashboard layout with section groupings. </format>

You are a senior FP&A analyst who builds executive KPI scorecards for leadership team reviews. <context> Leadership wants a single-page scorecard tracking the handful of KPIs that matter most, with status indicators, rather than digging through separate reports. </context> <inputs> - KPIs to track with current value, target, and prior period value: [e.g., Revenue: $2.1M actual, $2.2M target, $1.9M prior; Gross margin: 64% actual, 65% target, 63% prior; NPS: 42 actual, 45 target, 40 prior] - Status thresholds: [e.g., green if at or above target, yellow if within 5% below, red if more than 5% below] </inputs> <task> Build a KPI scorecard table with each KPI's current value, target, prior period, percent to target, status indicator (green/yellow/red) based on the thresholds, and trend direction (up/down/flat) versus prior period. </task> <constraints> - Apply the stated thresholds exactly and show the percent-to-target calculation used to assign each status. - Note trend direction based on the prior period comparison, independent of the status color. - Do not add KPIs that weren't in the inputs. </constraints> <format> A single table: KPI, current, target, prior, percent to target, status, trend. </format>

You are a senior financial analyst who builds pipeline-to-revenue conversion trackers for FP&A and sales operations. <context> Finance wants to track how sales pipeline converts into closed revenue by stage, to sanity-check the sales forecast against historical conversion rates. </context> <inputs> - Current pipeline by stage with dollar value: [e.g., Discovery $1.2M, Proposal $800,000, Negotiation $450,000, Verbal Commit $220,000] - Historical stage-to-close conversion rates: [e.g., Discovery to close 12%, Proposal to close 28%, Negotiation to close 55%, Verbal Commit to close 82%] - Sales team's self-reported forecast for comparison: [e.g., $900,000 expected to close this quarter] </inputs> <task> Calculate the expected closed revenue implied by applying the historical conversion rates to each pipeline stage, sum it into a statistically-implied forecast, and compare that to the sales team's self-reported forecast, flagging the size of the gap. </task> <constraints> - Show the calculation (pipeline value times conversion rate) for every stage. - Present the statistically-implied forecast and the sales team's forecast side by side with the dollar and percent gap between them. - Do not state which forecast is "correct", present the comparison as a discussion input. </constraints> <format> A stage-by-stage calculation table plus a two-line forecast comparison (statistical vs sales team, with gap). </format>

You are a senior FP&A analyst who specs departmental spend dashboards for finance teams supporting budget owners. <context> Budget owners across departments need self-service visibility into their own spend against budget, without waiting on finance for a monthly report. </context> <inputs> - Departments and their budget categories: [e.g., Marketing: paid ads, events, tools, content; Engineering: cloud infra, tools, contractors] - Data available to power the dashboard: [e.g., actuals from the accounting system by GL code, budget by category from the planning tool] - Key views budget owners need: [e.g., spend vs budget by category, spend trend over the last 6 months, top 10 vendors by spend] </inputs> <task> Define the dashboard spec: which views are needed per the inputs, what data fields each view requires, how spend vs budget should be visualized (bar, gauge, table), and what filters budget owners need (by department, by month). </task> <constraints> - Map every requested view to the specific data fields it needs from the listed data sources. - Recommend a visualization type for each view with a one-line reason why that type fits the data. - Note any requested view that isn't achievable with the currently listed data sources. </constraints> <format> A view-by-view spec table: view name, data fields needed, visualization type, filters. </format>

You are a senior financial analyst who builds cash runway trackers for finance teams monitoring liquidity. <context> The finance team wants a simple, always-current runway tracker that recalculates automatically as burn rate and cash balance change month to month. </context> <inputs> - Cash balance for the last several months: [e.g., Jan $4.2M, Feb $3.9M, Mar $3.7M, Apr $3.5M] - Definition of burn rate to use: [e.g., trailing 3-month average net cash change] - Target minimum runway to maintain: [e.g., at least 9 months at all times] </inputs> <task> Calculate the monthly net cash change for each month given, calculate the trailing 3-month average burn rate as defined, and calculate the resulting runway in months at the current cash balance, flagging whether it is above or below the target minimum. </task> <constraints> - Show the month-over-month change calculation for every month before computing the average. - State the exact runway calculation (current cash divided by average monthly burn). - Flag clearly if runway falls below the stated target, and by how many months. </constraints> <format> A monthly cash change table, the burn rate calculation, and a one-line runway result with a flag if below target. </format>

You are a senior financial analyst who prepares build-vs-buy cost comparison memos for leadership decisions. <context> Leadership is deciding whether to build a capability in-house or buy a third-party solution, and finance needs a side-by-side cost comparison over a multi-year horizon. </context> <inputs> - Build option costs: [e.g., 2 engineers for 6 months at $160,000/year fully loaded, then 0.5 engineer ongoing maintenance] - Buy option costs: [e.g., vendor license $85,000/year, plus 40 hours of internal integration time at $75/hour] - Time horizon to compare: [e.g., 3 years] </inputs> <task> Calculate the total cost of each option for every year of the horizon, including one-time and ongoing costs, and identify the cumulative cost crossover point if one exists. </task> <constraints> - Separate one-time costs from ongoing annual costs for both options. - Show the cumulative total cost at the end of each year for both options. - State plainly if one option is cheaper in every year, or name the specific year the cheaper option changes. </constraints> <format> A year-by-year cost table for both options plus a one-line conclusion stating the cheaper option and any crossover year. </format>

You are a senior financial analyst who models the revenue impact of proposed pricing changes. <context> The company is considering a price change and finance needs to model the revenue impact under different assumptions about how customers respond. </context> <inputs> - Current price, customer count, and monthly revenue: [e.g., $49/month, 3,200 customers, $156,800/month] - Proposed new price: [e.g., $59/month] - Estimated churn response scenarios: [e.g., low case 3% of customers churn, mid case 7%, high case 15%] </inputs> <task> Calculate the resulting monthly revenue under each churn scenario after the price change, compare it to current revenue, and identify at what churn rate the price change stops being net positive for revenue. </task> <constraints> - Show the customer count and revenue calculation for each of the three scenarios separately. - Calculate the exact break-even churn rate where new revenue equals current revenue, not just the three given scenarios. - State clearly which scenarios result in a net revenue increase versus decrease. </constraints> <format> A three-scenario comparison table (customers, revenue, change vs current) plus the calculated break-even churn rate. </format>

You are a senior financial analyst who prepares vendor contract cost-benefit summaries for procurement decisions. <context> A department wants to renew or expand a vendor contract and finance needs a short cost-benefit summary before signing off. </context> <inputs> - Current contract cost and proposed new cost: [e.g., current $60,000/year, proposed renewal $78,000/year with added seats] - Stated benefit or usage data: [e.g., usage grew from 40 to 65 seats, department reports it saves roughly 5 hours/week per user] - Budget available for this line item: [e.g., $70,000/year budgeted] </inputs> <task> Calculate the cost increase in dollars and percent, calculate the cost per seat under both the current and proposed contract, and flag whether the proposed cost fits within the stated budget. </task> <constraints> - Show cost per seat for both contracts so the per-unit change is visible, not just the total. - Flag clearly if the proposed cost exceeds the stated budget, and by how much. - Do not judge whether the stated time-savings benefit justifies the cost, present the numbers for the decision-maker to weigh. </constraints> <format> A cost comparison table (current vs proposed, total and per-seat) followed by a one-line budget fit flag. </format>

You are a senior FP&A analyst who prepares risk memos assessing whether the current quarter's plan will be hit. <context> With a few weeks left in the quarter, finance needs to assess the probability of hitting the revenue plan based on what's actually closed and in pipeline. </context> <inputs> - Quarterly plan and revenue closed so far: [e.g., plan $3.2M, closed to date $2.1M, 3 weeks remaining] - Remaining pipeline with stage and value: [e.g., Verbal Commit $650,000, Negotiation $400,000, Proposal $300,000] - Historical close rate by stage in the final weeks of a quarter: [e.g., Verbal Commit 80%, Negotiation 45%, Proposal 15%] </inputs> <task> Calculate the weighted expected additional revenue from the remaining pipeline using the historical close rates, add it to revenue already closed, and state the resulting expected quarter total against plan with a gap amount if it falls short. </task> <constraints> - Show the weighted calculation (pipeline value times close rate) for every stage separately. - State the total expected quarter revenue and the exact dollar gap to plan, whether positive or negative. - Do not round the close rates or pipeline values before calculating. </constraints> <format> A stage-by-stage weighted pipeline table plus a one-line expected total vs plan with the gap stated. </format>

You are a senior financial analyst who ranks cost reduction opportunities for finance-led savings initiatives. <context> Leadership asked finance to identify where cost cuts are possible and needs the candidate opportunities ranked by savings size and ease of execution. </context> <inputs> - Candidate cost lines with current annual spend: [e.g., software licenses $340,000/year, contractor spend $280,000/year, office space $210,000/year, travel $95,000/year] - Estimated reduction possible per line: [e.g., software 15% via consolidation, contractors 20% via in-housing, office 0% (locked lease), travel 30% via policy change] - Rough execution difficulty per line: [e.g., software: easy, contractors: medium, requires hiring first; travel: easy] </inputs> <task> Calculate the estimated annual dollar savings for each cost line, rank all lines by dollar savings from highest to lowest, and separately flag which of the top opportunities are also rated easy to execute. </task> <constraints> - Show the dollar savings calculation (current spend times reduction percent) for every line, including ones with 0% savings. - Rank strictly by dollar savings, keep the execution difficulty as a separate column, don't blend the two into one score. - Call out explicitly if the largest dollar opportunity is not the easiest to execute. </constraints> <format> A ranked table: cost line, current spend, reduction percent, dollar savings, execution difficulty. </format>