A Fee Section That Holds Its Price
Structures pricing as scope choices with consequences attached, so the conversation stops being a line-by-line argument about your rates.
What it is for
A price list invites a line-by-line negotiation; a set of scope choices does not. This builds the fee section around one recommended option, with genuinely optional items marked as optional and a consequence sentence on each, and the payment terms sitting next to the number instead of three pages later. It also names where a procurement reviewer will push, and what you would have to remove to justify a discount.
The skill
Turn this into the pricing section of a proposal. The goal is a buyer who chooses a scope, not a buyer who negotiates a line. What we are selling: [...] Our price and how it is built: [...] What they can drop without breaking the work: [...] What they cannot drop: [...] Payment terms we actually want: [...] Rules: 1. Lead with one recommended option. Two alternatives at most. Three named options beat a menu of eleven rows. 2. Do not itemise our internal labour. Hours on a table invite an argument about hourly rates. Price deliverables and outcomes. 3. Anything genuinely optional goes in as an optional line the client turns on or off. Anything that is not optional must not look optional. 4. Every optional line gets one sentence saying what changes if they leave it out — scope, timeline or risk. A consequence, not a sales sentence. 5. Attach the terms to the number, in the same section: payment schedule, what triggers each invoice, currency, tax treatment, and the date the price expires. 6. State what is out of scope and how a later request is handled. One line, no threat in it. Write the section, then tell me: - the sentence a procurement reviewer will use to ask for a discount - what I would have to remove from the scope to justify giving one Never show a discount without removing something. A price that drops for free tells the buyer the first price was invented.
How to install it
1. Open the tool and start a new conversation, project or template. 2. Paste the text below wherever the tool keeps standing instructions — usually called system prompt, instructions, or persona. 3. Save it so it applies to every run rather than a single message.