Skip to content
Finance · Playbook

Lead with the cost of waiting. Put the amount where the approver can find it.

A one-page internal budget request built from your item, amount, and the problem it solves, ordered the way an approver actually decides.

IncludedNative Claude Skill + plain .md for ChatGPT, Gemini & every LLM
100 Playbooks in the catalogDelivered as Claude Skill + plain .mdReviewed Nov 11, 2026Instruction-only · verifiable

Most budget requests open with enthusiasm and end with a number. The approver then builds the case themselves, and they build it from the cost side. The cheaper alternative they were already thinking of never gets answered, and the request comes back with questions or a quiet no.

Budget Request puts the problem first, then what waiting costs, then the return you expect and one signal to check at 90 days. It names the smaller option you considered, marks every estimate as an estimate, and ends with the amount and the exact decision you need.

What you get

What it produces.

  • →A one-page request in approver order: problem, cost of waiting, return, alternatives, amount
  • →A two-line summary the approver can forward unedited
  • →One measurable 90-day signal to report back on
  • →A check from the approver's chair before you send it
Who it's for
  • ✦Team leads asking a finance lead or owner for spend
  • ✦Small-business operators justifying a tool, hire, or equipment purchase
  • ✦Anyone whose requests keep returning with questions
What's included
  • →budget-request.zip: a native Claude Skill. Upload to Settings → Skills in Claude, or unzip to ~/.claude/skills/
  • →budget-request-skill.md: plain markdown. Works in ChatGPT Custom GPTs, Gemini, Claude Projects, agent system prompts, anywhere
  • →A README inside the zip with install steps for Claude, ChatGPT, and Gemini
Delivery
Emailed within 60 seconds of payment
Compatibility
Claude, ChatGPT, Gemini, any LLM
License
One-time purchase, yours to keep
Sample output

What it does with a real question.

The brief

I'm the support operations manager and I need to request $68,000 to hire one more Tier 2 support agent before our Q3 launch on August 4. Ticket backlog has grown from 120 to 410 open since March, average first response is now 19 hours versus our 8-hour target, and two agents have given notice. The request goes to our VP of Operations on Friday.

Lead with the cost, not the headcount. Your VP will decide on what this costs to leave alone, so the first line should read: "Open tickets have grown from 120 to 410 since March, first response is 19 hours against an 8-hour target, and two agents have given notice." That is the problem with its cost attached, and it should come before the $68,000 appears anywhere.

The weak spot is the cost of waiting. Right now it is implied, so price it. The August 4 launch will add volume to a queue that is already more than three times its March size, and two resignations mean capacity falls just as demand rises. Say that plainly, and add whatever you can verify about what late responses are costing: escalations, churn risk on named accounts, overtime. Label any figure you estimated as an estimate, with its source.

Then give the VP a test they can check. Pick a measurable target for 90 days after the hire starts, such as first response back under 8 hours, and commit to reporting it. Also expect the obvious objection: why not cover the departures with contractors or overtime? Give that one line of honest treatment, including where it would be reasonable.

Next move: before Friday, pull the current weekly ticket inflow and the two departing agents' handled volume, so the capacity gap is a number rather than a feeling. Close the request with a single decision: approve $68,000 by a date that lets the hire start before August 4.

The full Playbook runs the whole procedure and writes the complete deliverable, not this excerpt.

Written by claude-sonnet-5-5 with this Playbook loaded, 2026-10-11. Checked automatically for length and for copied framework text.

One-time purchase
$12.99
Yours to keep
No subscription · free updates within v1.x

Works as a Claude Skill (.zip) and as a plain .md for ChatGPT, Gemini & every LLM
Delivered to your email within 60 seconds · Secured by Stripe
Price includes UK VAT where applicable

Questions

Before you buy.

How is this different from just asking Claude directly?

Asked cold, Claude writes a persuasive memo that leads with benefits. This builds the request in the order an approver decides: cost of the problem, cost of waiting, expected return, alternatives, then the amount. It also forces every figure to be sourced or labeled as an estimate.

How is this different from a Tool?

Playbooks are systematically produced to a fixed template and priced accordingly ($12.99). Tools are hand-built, one at a time, and go deeper ($39 to $199). A Playbook gives you a reliable method for routine work; a Tool is for when the judgment matters more than the format.

Will this work with ChatGPT, Gemini, and other LLMs?

Yes. You get a native Claude Skill (.zip) that auto-invokes in Claude, plus a plain .md you can paste into a ChatGPT Custom GPT, a Gemini system prompt, or any LLM. The procedure travels with the file.

Can I share this with my team?

It's licensed for your own personal and professional use. The output it produces is yours to circulate. To put the Playbook itself in the hands of a whole team, email hello@authority.md about team licensing.

What if it doesn't work for me?

If the file hasn't been delivered, or arrives defective or empty, we refund in full: see our refund policy.

Finance Playbooks are writing and structuring aids. They are not financial, tax, or accounting advice. Check figures, policies, and anything with legal or tax consequences with a qualified professional.

More Finance Playbooks

Other Playbooks.