PromptSharp › Daily briefs › Finance › August 24, 2026

Finance prompt of the day

August 24, 2026 · for Investment banking, sales & trading, equity research, FP&A. One sharp, copy-paste prompt — free, every weekday.

You are a modeling analyst designing a scenario/sensitivity analysis for [model/decision]. I will give the model's key drivers and base-case outputs. Produce:
1. The 2 variables that should be the AXES of a sensitivity table (the ones the output is most sensitive to) and why.
2. A designed sensitivity TABLE structure (ranges, step sizes) that a reader can act on, using only my base-case inputs.
3. THREE named scenarios (e.g. base, downside, upside) with the coherent set of assumptions behind each — not just a single input flexed.
4. The interaction effects a one-variable sensitivity would miss.
Do not populate outputs I can't derive from your inputs; mark those cells "model".

Rules: Do not invent, estimate, or extrapolate any figure — if a number is not in what I give you, write "not provided" and flag it. Mark every claim I should verify externally before relying on it. Never use, infer, or request material non-public information (MNPI) or client-confidential data.

What changed for Finance

How to run “Scenario & sensitivity table design”, step by step

The situation this prompt is built for: You want a well-designed sensitivity/scenario table that shows what actually drives the outcome. Below is exactly what to feed it and what comes back — no model-specific tricks, it runs the same in any chat AI.

What each placeholder does

Demo profile for the example fills: an equity research associate on a mid-cap sector coverage team, working in Excel, a chat AI model, and your firm's data terminal. Swap in your own context — or save it once at /profile and copied prompts arrive pre-filled.

• [model/decision] — this is the input the whole output quality hangs on. Each part narrows the answer: model; decision. Demo fill: your own model/decision — one or two concrete lines beats a paragraph of vague context. Leave it vague and the model pads with boilerplate; make it concrete and every section downstream sharpens.

What the model hands back

The prompt forces a fixed deliverable shape, so you get a document, not a ramble:

1. The 2 variables that should be the AXES of a sensitivity table (the ones the output is most sensitive to) and why.
2. A designed sensitivity TABLE structure (ranges, step sizes) that a reader can act on, using only my base-case inputs.
3. THREE named scenarios (e.g. base, downside, upside) with the coherent set of assumptions behind each — not just a single input flexed.
4. The interaction effects a one-variable sensitivity would miss.

Why this structure works

Most sensitivity tables flex the wrong variables one at a time; choosing the true value drivers as axes and building coherent multi-variable scenarios is what makes the analysis decision-useful.

On Pro, the axis choices and scenario framing are tuned to your model type and the drivers your investment committee focuses on, from your profile.

When to use it — and when not to

Reach for it when

• You want a well-designed sensitivity/scenario table that shows what actually drives the outcome.
• You can actually supply the inputs it asks for ([model/decision]) — this prompt is an amplifier for real context, not a substitute for it.
• You need the output in a shape you can forward as-is — the fixed structure above is the point.

Skip it when

• You don’t yet have the source material — the prompt is built to refuse to fake it. Its own guardrail: “Do not invent, estimate, or extrapolate any figure — if a number is not in what I give you, write "not provided" and flag it.” With nothing to work from, you’ll get a list of “not provided” flags, which is honest but not useful. Collect the inputs first.
• The task is genuinely one sentence long — a structured prompt earns its overhead when the output has parts. For quick one-off questions, just ask.

Adapting today’s prompt for adjacent roles

“Scenario & sensitivity table design” sits in the Financial Analysis & Modeling lane of the finance pool. If your seat is one desk over, these are the same craft-move rebuilt for the neighbouring workflow — pulled from the same curated pool, each free in full at its permalink:

You are a leveraged-finance analyst running a QUICK LBO feasibility screen on [TARGET: EBITDA, growth, margin, capex, expected entry multiple, prevailing leverage…

You are a relative-value trader pressure-testing a pair trade: LONG [A] / SHORT [B], rationale [describe]. Produce: 1. The thesis restated in one sentence, plus the…

You are a buy-side analyst writing an EARNINGS PREVIEW for [TICKER, report date]. I will give consensus, recent developments, and the thesis. Produce: 1. The 4-6 KPIs…

Common failure modes (and the fixes)

• Failure: letting the model drift past the prompt’s own guardrail — “Do not invent, estimate, or extrapolate any figure — if a number is not in what I give you, write "not provided" and flag it.” Fix: keep that line in when you edit the prompt; it exists because this is exactly where outputs go wrong without it.
• Failure: letting the model drift past the prompt’s own guardrail — “Mark every claim I should verify externally before relying on it.” Fix: keep that line in when you edit the prompt; it exists because this is exactly where outputs go wrong without it.
• Failure: letting the model drift past the prompt’s own guardrail — “Never use, infer, or request material non-public information (MNPI) or client-confidential data.” Fix: keep that line in when you edit the prompt; it exists because this is exactly where outputs go wrong without it.
• Failure: filling [model/decision] with a vague summary. The output can only be as specific as this input — generic context in, generic deliverable out. Fix: paste raw specifics (real names, real numbers, real constraints), then trim the model’s output, not your input.
• Failure: accepting the first pass. Fix: reply with one line — “now cut everything that is generic to any company and keep only what is specific to mine” — the cheapest quality doubling available.

Where AI is landing for investment banking right now

Context for today’s prompt, from the same screened sources the daily brief reads. Our read, with sources linked — the pattern across items like these is consistent: the professionals getting leverage from AI are the ones feeding it real working context, which is exactly the muscle today’s prompt trains.

• [a16z Podcast] Why Medical AI Needs a Referee | Protege's Engy Ziedan (podcast) — Daisy Wolf and Eva Steinman are joined by Engy Ziedan, co-founder and Chief Scientific Officer of Protege, to discuss why medical AI has a measurement problem, and why scoring…
• Beyond Prompt Engineering: A Systematic Analysis of Prompt Lexical Sensitivity and Its Impacts on Quality (arxiv) — Large Language Models (LLMs) exhibit extreme sensitivity to surface-level prompt variations, in which minor lexical changes can trigger disproportionate performance fluctuations.…

Quick answers

Is “Scenario & sensitivity table design” free to use?

Yes — every weekday issue of the PromptSharp Finance publishes one full pool prompt free on the web, and it stays free in the archive. Pro is the daily full prompt set, personalization, and MCP delivery — not a paywall on this page.

Which AI model does this prompt work with?

Any of them. Every PromptSharp prompt is model-agnostic plain text — ChatGPT, Claude, Gemini, Copilot, or a local model. No plugins, no custom GPTs; paste and run.

How is the finance prompt of the day chosen?

Deterministic rotation over the curated finance pool — currently 75 prompts across 5 sections — the same single source the paid brief reads. Same date, same prompt: the archive never silently changes under you.

What goes in the [BRACKETED] placeholders?

Your context — the walkthrough above covers each one. The short rule: the more concrete the fill (real names, numbers, constraints), the sharper the output. Save your details once at /profile and web copies arrive pre-filled.

How do I get this in my inbox instead?

The capture form above — PromptSharp Finance status is honest: live briefs send every weekday; pre-launch verticals email their free list the day the email edition starts.

More daily AI prompt briefs

The same free weekday format, tuned to other crafts:

• PromptSharp CPG Brief — for Brand managers, category managers, insights & shopper teams
• PromptSharp Marketing Brief — for Brand and growth marketers, agency strategists, content leads
• PromptSharp Sales Brief — for AEs, SDRs, sales leaders, RevOps
• PromptSharp Consulting Brief — for Management consultants, corporate strategy, biz-ops
• PromptSharp Product Brief — for PMs, product ops, founders wearing the PM hat
• PromptSharp Dev Brief — for Software engineers, tech leads, engineering managers
• PromptSharp Vibe Coding Brief — for Founders, PMs, designers, analysts — anyone building real software with AI without an engineering background
• PromptSharp C-suite Brief — for CEOs, CFOs, CMOs, CTOs, COOs and their chiefs of staff
• PromptSharp Law Brief — for Solo & small-firm attorneys, litigation & transactional associates, in-house counsel
• PromptSharp Personal Finance Brief — for Anyone running their own money — budgets, investing, taxes, and the rent-vs-buy / home-buying decisions that dwarf every other line item
• PromptSharp Career Brief — for Job seekers, career changers, anyone negotiating an offer
• PromptSharp Focus Brief — for Anyone who wants external structure for deep work — ADHD-friendly by design
• PromptSharp Learning Brief — for Self-directed learners — languages, skills, certifications, exam prep
• PromptSharp Health & Fitness Brief — for Anyone training, eating better, or building durable habits
• PromptSharp Travel Brief — for Trip planners — itineraries, deals, points, family logistics
• PromptSharp Students — for College students (undergrad + grad) — study, research, essays with integrity, exam prep, applications
• PromptSharp Trading — for Self-directed retail traders and active investors — risk and position-sizing thinking, regime awareness, journal review, bias-checking, earnings prep. Your own account, your own process.

← 2026-08-21 · All Finance issues