Proposals . Agency OS

What it does

Turns a live deal into a document a prospect can say yes to. It writes one proposal for one named prospect: their problem in their language, the outcome they get, the scope of what is included and what is not, proof pulled only from your cleared claims, the investment framed against the value rather than dropped as a bare number, and one clear next step. When the deal only needs a short-form quote, a scope of work or an engagement letter outline, it writes that instead. Offers, pricing, guarantee, tiers and your voice all come from the workspace brain, so nothing is re-asked and nothing is invented. It hands back a finished draft plus a marked list of anything you must confirm or fill before it goes out. You review and send. It never sends, signs or commits on your behalf.

Say this to start

This skill has no button. You start it by saying what you want. Any of these will do it:

> write a proposal for [prospect name]

> draft a quote for this deal

> put together a scope of work

> outline an engagement letter

> help me frame the price for this deal

When to reach for it

a discovery call went well and the prospect asked for something in writing
you write every proposal from scratch and each one takes an evening
a deal needs a quote, SOW or engagement letter, not a full pitch deck
the price is right but you keep presenting it badly, as a bare number with nothing in front of it
a prospect asked what results you get, and you want that answered with real proof, not improvised claims
you need a version of your standard offer tailored to one named prospect and their situation

When NOT to use it

If you actually want	Use this instead
designing the offer itself: the deliverable stack, tiers, guarantee, bonuses or price points	`offer-architect`
the live sales conversation: discovery questions, objection handling, call follow-up strategy	`sales-closer`
a standalone persuasive asset such as an email sequence, landing page or cold outreach	`legendary-copywriters`
a final pre-ship quality and proof check before the proposal goes out	`critique`
deciding whether to take the deal at all, or how to position it strategically	`/board-meet`

Before you start

What you need	Why
`offer-output.md` and `positioning.md` with your offers, pricing, value stack, guarantee and tiers	every price in the draft is pulled from here; a price the brain does not state is never invented, it comes back marked for you to confirm, so if the offer is not designed yet the skill sends you to offer-architect first	Required
Who the prospect is and what problem they came to you with	this is the one thing the brain cannot know; if the core problem or requested scope is missing, the skill asks one tight question before drafting rather than guessing	Required
`verified-claims.md` populated with consented proof	every result, testimonial or named client in the draft must trace to a cleared entry in this registry, matched to this business; an empty registry means placeholder markers instead of proof	Required
`owner-profile.md` and `voice-profile.md`	the draft is written to sound like you, not like a template; without them you get a competent but generic voice you will want to edit harder	Optional
A decision on which offer this deal is, if you run more than one	the skill confirms rather than assumes; knowing it up front saves a question	Optional

How it runs

Loads the brainReads offer-output.md and positioning.md for offers, pricing, value stack, guarantee and tiers, owner-profile.md and voice-profile.md for how you sound, and verified-claims.md for what proof is cleared. Then reads learnings.md, filtered to proposal entries plus cross-skill patterns, and applies what past drafts taught it, mentioning any adaptation in one line.
Asks the minimumOne question if it needs one: who is this proposal for, and what problem did they come to you with. If you run more than one offer it confirms which one this deal is. It does not re-ask anything the brain already holds.
Opens on the problem, not the priceThe draft leads with the prospect's problem and the outcome they get, in their language, before any number appears. A price with no value in front of it reads as expensive, so the investment is framed against the cost of the problem or the value of the outcome, the way your offer is positioned.
Draws the scope with edgesStates plainly what is included and what is not. Only items your offer file actually contains appear as included; nothing gets promised that the brain does not back.
Prices from the brain onlyUses your exact prices as written. If the prospect asked about something you have not priced, it appears as a named option marked [CONFIRM: pricing] rather than a guessed figure. If your offer is scoped in conversation rather than fixed, the draft says the engagement is scoped to their situation instead of inventing a number.
Gates the proofPulls only claims cleared as ok-as-stated in verified-claims.md, matched to this business. A pending claim gets flagged for you to confirm before send. A missing claim leaves a marked placeholder such as [your real result here] or a proof gap note, never an invented result.
Hands back the draft plus the gapsYou get the finished proposal first, top to bottom, then a short list of what needs you before it can go out: a detail to confirm, a price decision, a proof point to clear. Open loops are named, never passed silently.
Learns from what you changeAfter the draft it asks how it landed: shipped as-is, minor edits, or major rewrite, and logs the answer to learnings.md. Notes that recur get applied to future proposals automatically.

What you get

A complete proposal draft: the prospect's problem, the outcome, the scope with boundaries, cleared proof, the investment framed against value, and one clear next step
A short-form quote, scope of work or engagement letter outline when that is all the deal needs
A version tailored to the specific prospect, written in your voice
A clearly marked list of everything you must confirm or fill before sending: [CONFIRM] items, pending proof and open loops
The draft in the terminal by default, or saved as a file if you ask for one
A learnings.md entry after your rating, so the next proposal starts from what this one taught it

Honest limits

Read this before you rely on it

Proof comes only from your own verified-claims.md registry, and only from entries cleared as ok-as-stated for this business. If the registry has nothing relevant, the draft carries a placeholder and a pointer to the registry, not a manufactured result. A prospect asking for niche-specific proof you do not have gets an honest gap marker, never an invented case study.
Anything the brain has not priced comes back marked [CONFIRM], not invented. That is the point: a made-up figure in a proposal becomes a commitment you did not make.
It ends at a draft. You review it, you send it, you sign it. The skill never sends, commits or negotiates on your behalf, so budget the final read before anything leaves your hands.
Run the draft through the critique skill before it goes out. That pre-ship pass is a separate step, not something this skill does silently for you.
The draft is only as good as the offer behind it. A vague offer-output.md produces a vague scope, and no amount of proposal polish fixes an offer that was never designed.

Where people go wrong

The mistake	Do this instead
Asking it to price something your offer file does not contain	Price it in offer-architect first, or let the draft carry `[CONFIRM: pricing]` and decide before you send. A number improvised into a proposal is a number you now have to honour.
Deleting the proof gap markers and typing in a result from memory	Go get the real number and clear it into `verified-claims.md`. A confident, false specific in a signed proposal is the fastest way to lose the deal and the trust behind it.
Moving the price to the top because the prospect asked what it costs	Keep the problem and outcome in front of the number. The prospect can skip ahead; the frame is there for the moment they weigh the figure.
Softening the scope boundaries to seem accommodating	Keep the not-included lines in. A proposal without edges becomes a dispute about what was promised, and the dispute always costs more than the deal.
Ending on three options so the prospect can choose	End on one next step: accept, book the call, or sign. Three options is a decision you have handed to someone who was ready to say yes to one.
Sending the first draft straight from the terminal	Read it, resolve every `[CONFIRM]` and gap marker, and run `critique` as the pre-ship gate. The draft is the start of your review, not the end of it.

Worth knowing

The marked placeholders are the feature, not a failure. Suppose your offer file prices a funnel build at $3,000 and a content retainer at $1,200 a month (invented numbers for illustration), and the prospect also asked about ad management you have never priced. The right draft uses the two real prices exactly, and ad management appears as a named next-step option marked [CONFIRM: pricing]. That marker is the skill refusing to commit you to a figure you never set.