The proposal-writer skill: send it before the interest cools

Someone talked to you. They're interested. They said "can you put that in writing?" and now it's been three days and the document doesn't exist.

That gap is where a lot of first sales die. Interest fades fast, and a proposal that lands four days late has to rebuild the whole conversation from scratch. The proposal-writer skill closes the gap the same day. You paste whatever notes you have, even bullet points typed on your phone in the car, and it writes a document short enough to read in two minutes: where the buyer is now in their own words, what's different once it's fixed, a countable list of what they get, the timeline, then the price.

It's one of the 55 free skills in our freeskills repo, and it's the one you run after the conversation, not before.

A skill is a folder with instructions in it. Drop this folder into your Claude Code skills directory with these three lines and it becomes a command you can run from any project.

Start a new Claude Code session, or restart the one you have open, and it's ready. Setup ends there. No keys to paste, no config file.

Type /proposal-writer and paste your notes. Rough is fine. It reads them looking for three load-bearing pieces: the buyer's problem, the scope of the work, and your price. If any of those three are missing it stops and asks, because it won't guess a price and it won't invent scope on your behalf.

It also won't put a quote in the buyer's mouth. If you didn't write down their exact phrasing, it writes the problem section plainly from your notes instead of making up something they said.

A good first result: a file at ~/proposals/ named after the client and dated, containing the problem, the outcome, the deliverables, the timeline, a small price table, a guarantee if you have one you're happy with, and one next step written as a sentence the buyer can act on in ten seconds. Then it offers to write the short email that goes with it, so the document doesn't arrive naked.

This is the main run. Dump everything you remember, in any order.

The section describing where the buyer is now decides everything else. If it reads generic, the price won't land no matter what the number is.

A proposal sitting in an attachment with no message around it gets opened slower. Ask for the covering note in the same session.

Here's the spoken version of what it does with your notes and why the price stops feeling scary.

1. 1Hook: your proposal takes three days because you're starting from a blank page. This free skill starts from your call notes and finishes it tonight.
2. 2Step 1: you paste your notes from the call.
3. 3Step 2: it pulls out the buyer's problem in the words they used, not the words you'd use.
4. 4That's where most proposals already go wrong.
5. 5Step 3: it writes what's different for their business once the work is done. Then it lists exactly what they get, so your price is attached to a list they can count.
6. 6Then it does something odd with the price.
7. 7Step 4: the price goes at the end, after they already want it, and the whole thing closes on one next step the buyer can do in ten seconds.
8. 8Transformation: you stop losing deals to the three days it takes you to write the document. The person who was interested on Tuesday gets it on Tuesday.
9. 9Close: it's free, and there are 54 more like it in that repo. What to say when they reply, and how to get more of these conversations, is Claude Code Club at $9 a month. Link below.

Tonight: find the last conversation you never followed up on, run the skill on whatever notes you kept, and send it before you go to bed.