Convert Cross Sell Page
Author post-purchase cross-sell pages: lateral product offer to existing customer, with...
Install
npx skills add FerroxLabs/wayland --skill convert-cross-sell-page -g -a claude-code -y- Repository
- FerroxLabs/wayland616
- Category
- Design
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Author post-purchase cross-sell pages: lateral product offer to existing customer, with relevance framing and tight Method-applied copy. Emits brief + paste-ready HTML/CSS. Use when the user has a customer who completed a flagship purchase (and any OTO sequence) and a related product the customer would benefit from. Not for immediate post-checkout upsells (see /convert oto-page) or downsells (see /convert downsell-page) and not for pre-purchase cold-traffic pages.
Convert Cross-Sell Page - Post-Purchase Lateral Offer
"The cross-sell isn't an upsell. The buyer's already mid-implementation on the first thing. The job here is to show them the next product they'll naturally need - not to extract more dollars while the wallet's open."
This skill builds the post-purchase cross-sell page: a related, lateral offer to an existing customer who's already past the OTO/downsell sequence.
When to Use
Trigger phrases: cross sell page, post-purchase upsell, related product page, convert cross-sell, /convert cross-sell <product>.
Use when:
- The customer has completed flagship + any immediate OTO/downsell sequence.
- A related (not duplicate, not upgrade) product genuinely fits their next step.
- The user wants to maximize LTV without breaking trust.
Cross-sells fire days-to-weeks after purchase, often from email - not seconds after checkout.
When NOT to Use
- Immediate post-checkout upgrade →
/convert oto-page. - OTO recovery →
/convert downsell-page. - Pre-purchase cold sales page →
/convert sales-page. - Thank-you page secondary stack →
/convert thank-you-page. - Auditing existing cross-sell →
/convert audit.
Inputs
Required:
- What they already own - the flagship + any OTO/downsell items purchased.
- The cross-sell product - must be lateral (not the same thing they own at a higher tier).
- Implementation timing - where the customer is in their journey (week 1? month 3? after the first result?). Cross-sell copy hinges on this.
- One person + Nerve, post-purchase version - the new pain that emerged because of the first product's success. "You implemented [flagship]. Now you've got [new problem the cross-sell solves]."
Optional:
- Voice continuity from the flagship + earlier funnel.
- Existing customer Snapshot proof.
out_path- defaults viabuild_report_path.


