upsell-downsell-scripting
This skill enables the agent to create high-converting upsell and downsell scripts based on Russell Brunson's One-Time Offer (OTO) methodology. Use it to optimize order bumps, structure upsell pages, and implement effective downsell strategies without applying excessive pressure. Triggers: upsell script, downsell strategy, OTO, order bump, thank-you page optimization.
What this skill does
# Upsell Downsell Scripting
## Overview
This skill provides a comprehensive framework for creating and implementing highly profitable upsell and downsell sequences in any sales funnel. It is grounded in the proven methodologies of Russell Brunson, focusing on the concept of the One-Time Offer (OTO) to maximize customer lifetime value. By using this skill, you can strategically present additional offers to customers at the point of purchase, significantly increasing average order value and overall revenue. The core idea is to offer the right product, to the right person, at the right time, creating a seamless and value-driven buying experience.
**Keywords**: upsell, downsell, one-time offer, OTO, order bump, thank-you page, sales funnel optimization, customer lifetime value, average order value, post-purchase offer, complementary offer, tripwire.
## Discovery & Planning Questions
1. **Core Product Context:** What is the exact product the customer has just purchased, and what is its price?
2. **Primary Objective:** What is the main goal for this upsell sequence? (e.g., maximize profit, introduce a flagship product, increase customer lifetime value, liquidate inventory).
3. **Audience Profile:** Can you describe the customer who just bought the core product? What are their primary motivations and pain points?
4. **Proposed Offers:** What specific product(s) or service(s) are you considering for the main upsell (OTO) and the downsell?
5. **Offer Congruence:** How does the proposed upsell help the customer get more value from, or achieve results faster with, the core product they just bought?
6. **Pricing Strategy:** What are the intended price points for the upsell and downsell offers? Are you open to offering a payment plan for the downsell?
7. **Format and Medium:** Will this script be used for a Video Sales Letter (VSL), an on-page text script, or an email?
8. **Brand Voice & Tone:** What is the desired tone for the script? (e.g., high-energy and urgent, calm and reassuring, educational and authoritative).
9. **Urgency/Scarcity:** Is this a genuine one-time offer? If so, what is the reason for the scarcity (e.g., limited quantity, special introductory price, bonus availability)?
10. **Social Proof:** Do you have any customer testimonials, case studies, or data points related to the success of the upsell offer that can be included in the script?
## Core Frameworks
This agent operates based on **Russell Brunson's OTO (One-Time Offer) methodology**. The central principle is that the best time to sell to a customer is immediately after they have made a purchase, as they are in a "buying mood" and have already demonstrated trust in your brand. The framework consists of a series of strategically placed offers designed to increase the transaction value.
* **The Value Ladder:** The initial purchase is just the first step on a ladder of value. Each subsequent offer should ascend this ladder, providing more value and solving a larger problem for the customer.
* **Order Bump:** A low-friction, high-value offer presented on the checkout page, typically as a simple checkbox.
* **The OTO Script:** A specific script structure for video or text-based upsells that acknowledges the initial purchase, introduces the new opportunity, and creates a sense of urgency.
* **Downsells:** If a customer declines the OTO, a lower-priced or alternative offer is presented to still capture additional revenue.
* **Thank-You Page Optimization:** The final step in the funnel, used to reaffirm the customer's purchase and potentially present another low-risk offer.
## S-Tier Tactics (Must-Do)
* **Congruence is Key:** Every offer in the funnel must be logically connected to the previous one. The upsell should help the customer achieve the desired result of the initial purchase faster or more easily.
* **Single, Focused Offer:** Each upsell page should present only ONE offer. Avoid decision fatigue by not giving the customer multiple choices.
* **Use a Video Sales Letter (VSL):** For the main OTO, a VSL is highly effective. Use Russell Brunson's script to build excitement and clearly articulate the value.
* **"No, I don't want to..." Link:** The link to decline the offer should force the customer to acknowledge what they are giving up (e.g., "No, I don't want to get results twice as fast").
* **True Scarcity/Urgency:** The OTO must be a genuine one-time offer. If the customer can get the same deal later, it loses all power.
* **Stack the Value:** Overwhelm the customer with value. List out everything they get, including bonuses, and assign a monetary value to each item to anchor the price.
* **The "Why You Must Have This Now" Close:** Clearly explain why this offer is essential for them at this specific moment.
## A-Tier Tactics (Highly Effective)
* **The Order Bump "Stack":** The order bump should be a "no-brainer" offer, priced at 10-20% of the main product, that enhances the initial purchase.
* **Downsell to a Payment Plan:** If the OTO is declined, offer the same product but with a payment plan to overcome price objections.
* **Downsell to a "Lite" Version:** Offer a version of the OTO with fewer features or bonuses at a lower price.
* **Testimonials on Upsell Pages:** Include social proof from customers who have benefited from the upsell offer.
* **Progress Bar:** Show the customer where they are in the buying process to reduce anxiety and cart abandonment.
* **The "Future Pacing" Technique:** Help the customer visualize the success they will achieve by taking advantage of the offer.
* **Acknowledge the Original Purchase:** Start the upsell by congratulating them on their smart decision to buy the initial product.
## B-Tier Tactics (Good to Have)
* **Thank-You Page Offer:** Present a low-ticket, high-value offer on the thank-you page, such as a tripwire or a free-plus-shipping offer.
* **Countdown Timer:** Use a real countdown timer on the OTO page to reinforce urgency.
* **Exit-Pop Downsell:** If a user tries to leave the OTO page, trigger an exit-intent popup with the downsell offer.
* **Personalized Offers:** If possible, tailor the upsell based on the customer's purchase history or behavior.
## Common Mistakes to Avoid (D-Tier)
* **Irrelevant Offers:** Presenting an upsell that has no connection to the initial purchase. This breaks congruence and feels like a cash grab.
* **Multiple Offers on One Page:** This confuses the customer and leads to analysis paralysis.
* **False Scarcity:** Claiming an offer is a "one-time offer" when it's available elsewhere. This destroys trust.
* **High-Pressure Sales Tactics:** Using aggressive language or making the customer feel bad for declining the offer.
* **Making it Hard to Say No:** Hiding the "No, thank you" link or using deceptive design patterns.
* **Not Acknowledging the First Purchase:** Jumping straight into the next sale without validating the customer's initial decision.
* **Upselling Before the Core Purchase:** Never present an upsell before the customer has completed their initial transaction.
## Step-by-Step Workflow
1. **Analyze the Core Offer:** Understand the main product being sold. What problem does it solve? What is the desired outcome for the customer?
2. **Brainstorm Complementary Offers:** List potential products or services that would help the customer achieve the core offer's outcome faster, easier, or with greater success.
3. **Select the Order Bump:** Choose a high-value, low-cost item from the list that is an impulse buy. It should be a simple "yes" and directly enhance the main product.
4. **Select the OTO (Upsell #1):** Choose the most powerful offer from your list. This should be your "home run" offer that provides immense value. This is typically a larger, more comprehensive solution.
5. **Script the OTO VSL:** Use the following script structure:
* **Congratulate & Acknowledge:** "Congratulations on your purchase of [Core Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.