mcpField

sales-digital-products

github.com/sales-skillsMarketing & growth78 installs
Repository

About sales-digital-products

A strategy skill for creators planning or improving sales of ebooks, courses, templates, software, and other digital products. It covers validation, pricing, delivery, launches, and platform choice, with guidance across multiple selling platforms.

Key features

  1. 01Product-market fit validation
  2. 02Pricing and launch planning
  3. 03Delivery and upsell strategies
  4. 04Platform-specific selling guidance
  5. 05Audience and process assessment

Use cases

  1. 01Testing demand before building a product
  2. 02Choosing a sales platform for a digital download
  3. 03Planning a course or ebook launch

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sales-skills/sales --skill sales-digital-products

After installing, type/sales-digital-productsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
learnings.md
platform-guide.md
platforms.md

Details

From the project README

Digital Product Sales

Help the user sell digital products — ebooks, templates, courses, downloads, software, presets, and printables. Covers product-market fit, pricing strategy, delivery, upsells, launch playbooks, and platform selection. This skill is tool-agnostic but includes platform-specific guidance.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

Ask the user:

  1. What type of digital product?

    • A) Ebook / guide / PDF
    • B) Templates / swipe files / spreadsheets
    • C) Online course / video training
    • D) Software / SaaS / plugins
    • E) Design assets (presets, fonts, icons, mockups)
    • F) Audio (music, sound effects, podcasts)
    • G) Printables / planners
    • H) Community access / paid group
    • I) Not sure yet — need help deciding
  2. Where are you in the process?

    • A) Idea stage — haven't built anything yet
    • B) Product is built — need to sell it
    • C) Already selling — want to optimize or scale
    • D) Want to add digital products to an existing business
  3. Do you have an existing audience?

    • A) Yes — newsletter, social, or community (approximate size?)
    • B) No — starting from scratch
    • C) Small audience (<1,000) but growing

Step 2 — Strategy and approach

Product-market fit for digital products

Validation before building:

  1. Pre-sell: Offer the product at a discount before it exists. If 10+ people pay, build it.
  2. Waitlist: Landing page with email capture. 100+ signups = strong signal.
  3. Free version: Give away a mini version (checklist from the ebook, 1 lesson from the course). Track engagement.
  4. Audience polling: Ask your list "Would you pay $X for Y?" — but weigh actions over words.

High-demand digital product categories:

  • "Done for you" templates (save time) — highest conversion
  • Skill-building courses (increase earning power) — highest price point
  • Creative assets (presets, fonts, mockups) — volume play
  • Knowledge products (ebooks, guides) — lower price, higher volume
  • Tools/software (calculators, apps) — recurring revenue potential

Step 3 — Platform-specific guidance

Read references/platform-guide.md for detailed pricing strategy, launch playbook, delivery methods, upsell frameworks, platform comparisons, and revenue benchmarks.

Read references/platforms.md for platform-specific selling guidance — MailerLite, Gumroad, Sellfy, Printful, Printify, CustomCat, and SendOwl (fees, plan gates, delivery/protection, tax/MoR status, and automation surface). Read only the section matching the user's platform; for platform setup/integration, route to the dedicated /sales-{platform} skill.

Step 4 — Actionable guidance

Gotchas

  1. Don't build before validating — pre-sell or waitlist first. 50% of digital products never sell because the creator assumed demand. Even a simple "buy now, get it in 2 weeks" test is better than 3 months of silent building.

  2. Platform fees vary wildly — Gumroad free tier takes 10%, Lemon Squeezy takes 5%, Kit takes 0.6%, WooCommerce takes 0%. At $10K+ in annual sales, the difference is hundreds to thousands of dollars. Model your fees before committing.

  3. Courses need ongoing maintenance — a $497 course creates support expectations. Budget time for Q&A, community management, and content updates. Ebooks and templates are lower-maintenance products to start with.

  4. Price anchoring works both ways — if you launch at $19, it's very hard to raise to $99 later with the same audience. Launch at a higher price and discount strategically rather than starting low.

  5. Tax compliance is real — selling digital products internationally triggers VAT/GST obligations in the EU, UK, Australia, etc. Use a merchant of record (Lemon Squeezy, Paddle) or handle it yourself. Don't ignore this.

  • Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.

Before recommending a specific platform skill

This skill covers a strategy domain across many platforms. Before pointing the user to any specific platform skill (any /sales-{platform} listed in ## Related skills, e.g., /sales-mailshake, /sales-klaviyo, /sales-apollo), read that platform skill's actual SKILL.md first. The 1-line description in ## Related skills is enough to identify a candidate — it's not enough to commit to it or to write a prompt that invokes it well.

How to read it:

  • If ~/.claude/skills/{skill-name}/SKILL.md exists locally, Read it.
  • For sales-* skills, WebFetch directly from this repo: https://raw.githubusercontent.com/sales-skills/sales/main/skills/{skill-name}/SKILL.md — e.g., for sales-mailshake: https://raw.githubusercontent.com/sales-skills/sales/main/skills/sales-mailshake/SKILL.md.
  • For non-sales-* skills (third-party), look up {org}/{repo} in ~/.claude/skills/sales-do/references/skill-sources.md if installed and fetch the same skills/{skill-name}/SKILL.md path under that repo.

After reading, ground your recommendation in something concrete from the SKILL.md (its scope, a sub-flow, its argument-hint shape, or a "Do NOT use for..." negative trigger). Align any generated invocation with the platform skill's argument-hint. If the platform skill turns out not to fit the user's situation, swap to another or handle the question here directly rather than recommending a poor fit.

Related skills

  • /sales-checkout — Checkout page optimization (upsells, order bumps, payment plans, cart abandonment)
  • /sales-membership — Membership sites and online courses (recurring access, content dripping)
  • /sales-newsletter — Newsletter monetization (paid subscriptions, sponsorships)
  • /sales-audience-growth — Growing your audience (lead magnets, referrals, cross-promotion)
  • /sales-email-marketing — Email marketing (launch sequences, nurture campaigns)
  • /sales-funnel — Sales funnel strategy (landing pages, conversion paths)
  • /sales-mailerlite — MailerLite platform help (digital product sales, paid newsletters)
  • /sales-kit — Kit platform help (Kit Commerce setup)
  • /sales-groove — Groove.cm platform help (GrooveSell, GroovePages)
  • /sales-beehiiv — Beehiiv platform help (digital products, paid subscriptions, newsletter monetization)
  • /sales-podia — Podia platform help (courses, downloads, memberships, coaching, email)
  • /sales-payhip — Payhip platform help (digital downloads, courses, memberships, coaching, store builder, API)
  • /sales-gumroad — Gumroad platform help (digital products, license keys, Discover marketplace, API, webhooks)
  • /sales-lemonsqueezy — Lemon Squeezy platform help (payments, subscriptions, license keys, tax compliance as merchant of record)
  • /sales-sellfy — Sellfy platform help (creator storefront: digital products, print-on-demand merch, subscriptions; 0% fee with annual sales-volume caps; PDF stamping; webhooks + Zapier, no REST API; not a MoR)
  • /sales-print-on-demand — POD provider selection strategy (Printful vs Printify vs CustomCat vs Gelato vs Gooten vs SPOD — fulfillment model, margins, shipping geography, branding, sample vetting)
  • /sales-printful — Printful platform help (print-on-demand merch fulfillment; REST API v2 + signed webhooks, mockup generator, store connectors; Free vs Growth plan; SKU/sync-variant and failed-order troubleshooting)
  • /sales-printify — Printify platform help (broker-network POD: 1,300+ products, ~141 print providers; REST API + OpenAPI spec, HMAC-signed webhooks, API sales channel; provider quality vetting; Free vs Premium)
  • /sales-customcat — CustomCat platform help (budget US print-on-demand; lowest base prices + 1–3 day production, no private-label branding, US-only; REST API with read/write keys + 6 unsigned webhook topics; Lite vs Pro plan)
  • /sales-sendowl — SendOwl platform help (delivery-security-first: download-limit/expiry links, PDF stamping, license keys, subscriptions, drip; REST API + HMAC-signed webhooks; subscription pricing with annual order/sales caps, no free tier)
  • /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do

Examples

Example 1: First digital product

User says: "I want to create and sell my first ebook about freelance copywriting" Skill does: Recommends validation via pre-sale to newsletter, suggests $29 pricing with bundle option ($49 with template swipe file), compares Kit Commerce vs Gumroad for delivery, provides launch email sequence Result: User has a validated product idea, pricing strategy, platform choice, and 7-day launch plan

Example 2: Platform selection

User says: "I'm selling a Notion template pack — should I use Gumroad or Lemon Squeezy?" Skill does: Compares fees (Gumroad 10% free tier vs Lemon Squeezy 5%), tax handling (LS is merchant of record), checkout experience, and discovery features. Recommends Lemon Squeezy for international sales, Gumroad for discovery. Result: User makes an informed platform choice based on their priorities

Example 3: Course launch

User says: "I have a 3,000-subscriber list and want to launch a $297 course on data analytics" Skill does: Designs a 4-week launch sequence (tease → waitlist → early-bird → open → close), recommends payment plan option ($3 × $107), suggests Kit Commerce or Podia, provides revenue projection (3K × 2% = 60 sales = $17,820) Result: User has a complete launch plan with email sequence, pricing, and revenue targets

Troubleshooting

Low conversion on product page

Symptom: Traffic to product page but <1% conversion Cause: Weak value proposition, no social proof, price not justified, too many options Solution: Add testimonials (even from beta testers). Show the transformation ("before → after"). Add a money-back guarantee. Remove distracting navigation. Test a lower entry price with an upsell.

High refund rate (>10%)

Symptom: Sales coming in but refund requests exceed 10% Cause: Product doesn't match the sales page promise, or product quality is low Solution: Survey refund requesters (what did they expect?). Align sales copy with actual product content. Add a "getting started" email immediately after purchase. Consider a lower price point if expectations are too high.

Can't get first 10 sales

Symptom: Product is live but not selling Cause: No audience, no launch event, or selling to wrong people Solution: Don't rely on organic discovery. Email your list with a dedicated launch sequence (not just a mention). Offer founding member pricing (50% off first 20 buyers). Ask 5 people personally to buy and give feedback. If you have no audience, use /sales-audience-growth first.

Comments

Markdown supported