The repeatable-offer skill: stop quoting every job from scratch

Every sale starts at zero. You re-explain what you do, guess a number off the top of your head, and then the job quietly grows past what you agreed to. Three months of that and you're busy and tired and nothing compounds.

The repeatable-offer skill fixes the part underneath all of it. It walks you through your last two or three jobs, finds what was the same every single time, and wraps that part in a fixed name, a fixed deliverable, a fixed timeline, a fixed price, and a written list of what you're not doing. Productizing is the word for it: taking a service and giving it edges, like a thing on a shelf.

One of the 55 free skills in our freeskills repo. The one-pager it writes does double duty, because it's the thing you send a buyer and the checklist you follow while you deliver.

Skills sit in a directory Claude Code checks when it starts. Copy this one across with the three lines below and it turns into a slash command.

Open a fresh Claude Code session, or restart it, and the skill is live. That's the entire setup. Nothing to configure and no API keys.

Type /repeatable-offer. It asks you to walk through the last two or three times you did this work, job by job, and then looks for what was identical across all of them. Expect it to push here. It wants your core written as one sentence, in the shape of taking one kind of input and turning it into one outcome, and it won't move on while that sentence is still vague.

Then it does the step most people skip: writing down what is not included. It caps the variables with real numbers and turns the extras people keep asking for into named add-ons with their own prices. A paid add-on is a yes, and a free extra is a leak.

A good first result: a file in ~/offers/ named after the product, holding the core sentence, the deliverable, what "done" means, the timeline, the included and not-included and add-on lists, the name and one-line promise and price, how it gets delivered, and the standard checklist you run on every order. Then send that one-line promise to one person who fits and see what they ask about. The questions are the parts of the box that aren't clear yet.

The raw material is your last few jobs. Describe them the way you'd describe them to a friend.

If the work always expands after they've paid, bring the specific requests that do it. Those become the not-included list and the add-ons.

A name that says the outcome sells better than one that says the process. Ask for the naming pass on its own if the rest is already settled.

Here's what it does to your service, said the way you'd say it to a friend who's drowning in custom work.

1. 1Hook: if you quote every job from scratch, you're doing it wrong. This free skill turns your repeat work into one named package with a fixed price.
2. 2Step 1: you walk it through your last two or three jobs.
3. 3Step 2: it finds the part you did on every single one, which is the actual product, and writes it as one sentence.
4. 4Here's the move that makes it repeatable.
5. 5Step 3: it fixes the deliverable, the timeline, and the price, and writes down what you're not doing so the job can't quietly grow.
6. 6There's one more piece, and you'll use it on every order.
7. 7Step 4: it writes the delivery checklist you run each time, which is what makes this repeatable in real life instead of on paper.
8. 8Transformation: the next person who asks what it costs gets a number and a delivery date in one message. And you deliver it the same way you delivered the last one, which is when this work finally stops being exhausting.
9. 9Close: it's free, and it's one of 55 in that repo. Getting the offer live and getting people in front of it is Claude Code Club, $9 a month. Link's below.

Tonight: run it on the request you get most often, not on your whole service. One narrow offer that sells twice beats a flexible one that never sells the same way once.