Repeatable Offer logo

Repeatable Offer

Community
duncan-buildroom
repeatable-offer

Offer-builder makes an offer irresistible. This one makes your service repeatable, so you stop quoting from scratch every time someone asks what it costs. Finds the part of your work that's the same on every job, then wraps it in a fixed name, a fixed scope, a fixed price, a fixed timeline, and a delivery checklist you run the same way every order. Use when the user says "make this repeatable", "I keep doing this custom for everyone", "package what I do", "turn my service into a product", "I'm quoting every job from scratch", "productize my service", "I'm stuck trading time for money", or "/repeatable-offer".

Overview

Publisherduncan-buildroom
Repositoryfreeskills
Skill namerepeatable-offer
Stars
65
Forks
15
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by duncan-buildroom on GitHub. Read the source before you install it.

Installation

Install the Repeatable Offer AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/duncan-buildroom/freeskills/tree/main/repeatable-offer
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/duncan-buildroom/freeskills.git /tmp/freeskills
mkdir -p .claude/skills
cp -r /tmp/freeskills/repeatable-offer .claude/skills/repeatable-offer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Repeatable Offer in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Repeatable Offer on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Repeatable Offer is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Repeatable Offer: sell the same thing twice

Custom work is exhausting because every sale starts at zero. You re-explain what you do, guess at a price, and then the job grows past what you agreed to. The fix is to find the part of the work that's the same on every job, put a box around it, and sell that box over and over. That's what "productizing" means: turning a service into something with edges, like a thing on a shelf.

The output is a one-page offer you can send to a buyer and also follow yourself while you deliver.

Personalization

This skill works in your brand voice. Before running, load the brand profile at ~/.claude/brand-profile.md.

  • If it doesn't exist, run the personalize skill first. Or just tell me your name, niche, offer, and audience, and I'll create it.
  • If a field this skill needs is blank, I'll ask one or two quick questions and save the answers back to the profile, so you only answer once.
  • Never invent facts or results about the user. Use only what's in the profile, or ask.

Steps

1. Find the repeatable core

Ask them to walk through the last 2 or 3 times they did this work, job by job. Then look for what was the same every time. That's the 80% that repeats no matter who the client is, and it's the actual product. The rest is noise that feels important because it was different.

Two questions do most of the work:

  • "What do you do on every single one of these, no matter who it's for?"
  • "What's the thing the client actually cares about at the end?"

Write the core as one sentence: "I take [input] and turn it into [outcome]." If they can't finish that sentence yet, keep asking about the last few jobs. Don't move on with a vague core, because everything after this is built on top of it.

2. Define one fixed deliverable

Now replace "it depends" with a concrete thing the buyer receives. Consulting is not a deliverable. A built website, a set of five posts, a working automation plus a video walkthrough: those are deliverables, because you can point at them.

  • Write out exactly what they get, as a short bulleted list.
  • Write what "done" looks like, so both sides know when it's finished.

That finish line matters more than it sounds. Most of the pain in custom work comes from nobody agreeing when the job ended.

3. Set a fixed timeline

A product has a delivery time. Give it one and say it plainly: "delivered in 7 days", "a 2 week sprint", "live within 48 hours".

Pick the realistic outer edge, not the best case. A timeline you beat makes you look good, and a timeline you miss costs you the referral. The timeline is also a selling point on its own, because most people who buy services have no idea when they'll get anything.

4. Draw the box around the scope

This is the hard step and the one people skip. Write down what is NOT included. Scope creep is when a job quietly grows past what was agreed, and it's the thing that turns a product back into custom work.

  • Name the requests you'll say no to.
  • Cap the variables with real numbers: "up to 5 pages", "one revision round", "one platform".
  • Take the extras people keep asking for and turn them into named add-ons with their own price. A paid add-on is a yes. A free extra is a leak.

End with three plain lists: included, not included, add-ons with prices.

5. Name it and price it

Give it a name that says the outcome, not the process. "Inbox Rescue" beats "Automation Consulting Package." Keep it short enough to say out loud.

Then write the one-line promise: "You get [deliverable] in [timeline], done for you."

Then put a fixed number on it. Price on what the outcome is worth to the buyer, not on how many hours it takes you, because hours punish you for getting faster. If they're stuck on the number, hand off to pricing-calculator. If they want to stack this into a bigger, harder to refuse offer with a guarantee and bonuses, that's offer-builder after this.

6. Pick how it gets delivered

Fulfillment just means how the work actually gets done and handed over. Pick one:

  • Do it yourself. They buy templates or a tool and run it themselves. Cheapest to deliver, scales the furthest.
  • Do it with you. You have a set process and calls where you guide them. Repeatable, higher touch, higher price.
  • Done for you. You run your fixed process on their behalf. Highest price, and you cap your slots so quality holds.

Then write the standard delivery steps, the same checklist run on every single order: intake, build, review, handoff. This checklist is the part that makes it repeatable in real life instead of on paper. It's also what you'd hand to the first person you hire.

Output: save it

Write the one-page offer to ~/offers/<product-name>.md (create ~/offers/ if needed, and turn the name into a filename, so "Inbox Rescue" becomes inbox-rescue.md).

The file contains: the repeatable core sentence, the deliverable spec, the timeline, the included and not included and add-on lists, the name plus one-line promise plus price, the fulfillment model, and the delivery checklist.

Tell them the path, then give one next action: send the one-line promise to one person who fits, and see what they ask about. The questions they ask are the parts of the box that aren't clear yet.

Example (input → output)

Input: "I do freelance automation help. Every job is different, I quote it off the top of my head, and the work always grows."

Output (saved to ~/offers/inbox-rescue.md):

  • Repeatable core: I take a small business's messy lead intake and turn it into one automatic pipeline.
  • Deliverable: a connected intake form, feeding a CRM (the tool that stores customer contacts), plus an automatic reply to every new lead, plus a short video walkthrough.
  • Done means: a test lead comes in and gets a reply without anyone touching it.
  • Timeline: live in 5 business days.
  • Included: one intake source, one CRM, one auto-reply sequence.
  • Not included: custom code, more than one brand, ongoing changes after handoff.
  • Add ons: extra reply sequence $200. Second location $400.
  • Name, promise, price: "Inbox Rescue. Your leads captured and answered automatically in 5 days, done for you. $1,200."
  • Fulfillment: done for you, 4 slots a month.
  • Delivery checklist: intake call, map their current flow, build it, test with sample leads, walkthrough and handoff.

Notes / edge cases

  • If nothing repeats across their last few jobs, they're not ready to productize this whole service yet. Pick the single request they get most often and box up that one first. One narrow product beats a flexible one that never gets sold twice.
  • Resist making the product do everything. A boring, narrow, repeatable offer outsells a clever custom one, because a buyer can understand it in ten seconds.
  • If they've only ever done this once, they're guessing at the core. Do the next job, take notes on what you actually did, then run this again with real material.
  • The finished one-pager does double duty. It's the sales page you send to buyers, and it's the checklist you follow while delivering, so both sides of the job stay the same every time.
  • Revisit it after five orders. By then you'll know which add-on people always buy, and that one usually belongs inside the box at a higher price.

Frequently asked questions

What does the Repeatable Offer AI skill do?

Offer-builder makes an offer irresistible. This one makes your service repeatable, so you stop quoting from scratch every time someone asks what it costs. Finds the part of your work that's the same on every job, then wraps it in a fixed name, a fixed scope, a fixed price, a fixed timeline, and a delivery checklist you run the same way every order. Use when the user says "make this repeatable", "I keep doing this custom for everyone", "package what I do", "turn my service into a product", "I'm quoting every job from scratch", "productize my service", "I'm stuck trading time for money", or "...

Why use Repeatable Offer on TypingMind?

Because you install it once and use it with any model. Repeatable Offer is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Repeatable Offer in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/duncan-buildroom/freeskills/tree/main/repeatable-offer. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Repeatable Offer?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Repeatable Offer?

As many as you like. As long as a model supports skills, you can use Repeatable Offer with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Repeatable Offer AI skill free?

It is published on GitHub by duncan-buildroom. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇