Aetheria-Labs1/storefront-skills / skills/optimize
optimize
FlaggedScore an existing Lexsis page against the same page-type, design, proof, offer, asset and copy rules used to build pages, propose improvements as a strict optimization plan with real replacement copy and asset decisions, wait for approval, then apply the approved changes with version protection and hosted QA.
references/offers/offer-stacking.md
View on GitHub# Offer stacking
Build an offer a qualified visitor would feel foolish to refuse, using real
value rather than inflated claims. A stack answers the buyer's specific
blockers with bonuses, a guarantee, and reduced effort, so a low price is not
the only reason to buy. The price presentation rules, offer ledger, and
urgency rules still apply to every stack.
## Value score
Score each 1 to 5 from evidence (Hormozi, $100M Offers; practitioner framework,
not tested science):
| Lever | Raise it with |
|---|---|
| Dream outcome | The specific result this buyer wants, in their words |
| Perceived likelihood | Proof, guarantee, reviews, a plan for using the product |
| Time delay (lower is better) | Faster first result, delivery date, quick-start |
| Effort and sacrifice (lower is better) | Kits, refills, set-up, free returns, instalments |
Value = outcome x likelihood / (delay x effort). Improve the weakest lever
first. The framework assumes the product already works and sells; a stack does
not rescue a weak product.
## Build
1. List the top three blockers from reviews, support, and analytics.
2. Assign one item to each blocker: a bonus, a service, or a guarantee term.
3. Prefer items cheap to supply and valuable to the buyer: guides, samples,
refills, fit kits, priority support, extended returns.
4. Name each item by the job it does, not as "free gift".
5. Show the stack beside the price as a short list, then the total and the price.
6. Add one risk reversal the merchant has confirmed.
7. Add a real limit only if one exists, such as gift stock or a campaign end.
8. Check contribution margin after gift cost, shipping and returns.
## Rules
OS1. Every stack item removes a named blocker. Items that do not are removed.
OS2. Stated values are real selling prices of items also sold separately
(price-presentation PP1). Items not sold separately show no monetary value.
OS3. Every item, value, limit, and guarantee term has an offer-ledger row.
OS4. At most four items above the fold; one primary offer per page.
OS5. No fake countdowns, invented stock, or perpetual "today only".
OS6. Prefer a gift or bonus over a deeper discount on expensive goods, and test
it; do not assume it wins.
OS7. Regulated claims and subscriptions keep their full terms beside the offer.
## Evidence
| Finding | Tag | Source |
|---|---|---|
| Free item with an expensive purchase judged more valuable than the same item at a small discount | RESEARCH, read via press summary | Palmeira and Srivastava, Journal of Consumer Research: https://phys.org/news/2013-08-consumers-freebie-valuable-discounted-product.html |
| Bonus pack outsold an equivalent discount by 73% in a store test | RESEARCH, read via press summary | "When More Is Less", Journal of Marketing: https://retailwire.com/discussion/how-valuable-is-free |
| Free items do not reliably beat equivalent discounts | RESEARCH, mixed | https://duo.uio.no/handle/10852/18356 |
| Tiered gift lifts of 18 to 46% AOV | OPERATOR, unverified, hypothesis only | https://ithemelandco.com/blog/impact-of-free-gifts-on-aov/ |
| Free gifts showed no significant AOV or conversion lift in one store experiment | OPERATOR | https://sculpt.digital/case-study/impact-of-free-gift-promotions-on-aov/ |
| 64% of users look for shipping costs on the product page; 43% of sites omit them | RESEARCH | https://baymard.com/blog/show-shipping-costs-on-product-pages |
Measure stacks with a holdout: revenue per session, contribution margin, and
60-day repeat purchase together, never conversion alone.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |