Finance & Analysis

Verified against ChatGPT · 2026-08-08

Surface cost-reduction levers before headcount cuts become the default answer

Builds a structured audit of a specific cost line that separates one-time savings from recurring ones and forces non-headcount options onto the table before layoffs get proposed as the easy fix.

ChatGPT (GPT-5.1)5 fillable variables

The prompt

Ready to copy — highlighted parts are example details you can swap.

You are helping me build a cost-reduction analysis for one specific expense line before it goes to my leadership team, and I want headcount reduction to be the last option considered, not the first one that gets written down because it's the easiest to model.

EXPENSE LINE
Third-party SaaS tooling across the growth and support teams

CURRENT ANNUAL SPEND
$412,000/year across 34 active vendor contracts

TARGET REDUCTION
18% reduction ($74,000/year) by Q1

WHAT WE'VE ALREADY TRIED
Already consolidated two overlapping analytics tools last year; annual renewal negotiations already happen every renewal cycle

CONSTRAINTS I CANNOT VIOLATE
Cannot touch the tools the support team uses for SLA-tracking; no new multi-year lock-in contracts

HOW TO STRUCTURE THE AUDIT
First, break the expense line into its actual cost drivers rather than treating it as one number — ask me for the components you need if I haven't given them, since a vendor contract, a usage pattern, and a headcount cost inside the same line item respond to completely different levers. For each driver, generate savings options across four categories in this order: renegotiate or consolidate (same output, lower unit price), reduce usage or scope (same price, less consumed), substitute (a cheaper way to get the same outcome), and eliminate (stop doing it entirely) — only after exhausting those four should headcount appear as a fifth category, and it must appear explicitly labeled as last-resort with a one-line reason it's being included at all. For every option, state whether the saving is one-time or recurring, since a leadership team conflating a one-time vendor credit with a permanent run-rate reduction is the single most common way a cost-cutting plan quietly fails to hold in month four. Flag any option that conflicts with something I've already tried or a constraint I gave you, rather than silently including it. Do not invent a specific vendor name, contract term, or negotiated discount percentage — where you'd need a real number to make an option concrete, mark it as an input I need to supply.

WHAT NOT TO DO
Do not default to "reduce headcount by X%" as a shortcut when a real analysis of the other four categories hasn't been done — that's the exact failure mode this prompt exists to prevent. Do not present a savings estimate as precise when it depends on a negotiation outcome you can't know.

OUTPUT FORMAT
A table with columns: Lever, Category, Estimated Annual Impact (one-time vs recurring), What Has To Be True For This To Work, Risk. End with a one-paragraph recommended sequence — which levers to pull first based on speed to impact versus effort — and a closing line noting this is a structuring aid for your own review, not a substitute for sign-off from whoever owns the budget.

Customize

Optional — swap in your own details for the highlighted parts above.

Why this works

The ordering instruction — four non-headcount categories before headcount is even allowed to appear — exploits a specific, predictable behavior in how GPT-5.1 responds to open-ended cost-reduction requests: when a model isn't given a forced sequence, it tends to reach for the single largest, most legible line item first, which in most org budgets is compensation, producing a headcount-cut recommendation by default rather than because it's actually the best option. Forcing the model to work through renegotiate, reduce usage, substitute, and eliminate before headcount can appear means those cheaper, lower-risk, non-people levers actually get evaluated on their own merits instead of being skipped past. Separating one-time from recurring savings addresses the most common way a cost-cutting plan looks good in the boardroom slide and then fails to hold: a one-time vendor credit or a deferred renewal gets summed into the same annual number as a genuinely recurring reduction, and three months later finance is asking why the run rate didn't actually move. Requiring "what has to be true for this to work" per lever forces the plan to surface its own hidden assumptions — a renegotiation lever that assumes the vendor has slack to give, a usage-reduction lever that assumes a team will actually change behavior — rather than presenting a savings number as if it were already secured. Instructing the model not to invent a specific negotiated discount percentage matters because a model asked to model savings will otherwise happily produce a plausible-sounding 15% vendor discount with no basis, which reads as confident but is fabricated, and someone building a real board slide off that number would be building on nothing.

What you get back

Lever: Consolidate 3 overlapping analytics tools into 1 | Category: Renegotiate/Consolidate | Impact: ~$28,000/yr, recurring | Requires: confirming feature parity with the support team before cancellation | Risk: migration effort in Q1. Lever: Downgrade seat tiers for inactive SaaS logins | Category: Reduce usage | Impact: ~$9,000/yr, recurring | Requires: an active-usage audit per tool | Risk: low.

Verified against

ChatGPT GPT-5.1 · 2026-08-08

Changelog

  • 2026-08-08 Initial publish, verified against ChatGPT GPT-5.1.

Need this built into your business?

If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.

EXPLORE WHAT SCULT BUILDS
All Finance & Analysis prompts

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY