Files
skills/public/offers.html
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

269 lines
23 KiB
HTML
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<!doctype html>
<html lang="en"><head>
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
<title>offers</title>
<meta name="color-scheme" content="dark">
<style>
/* Committed to one visual world: a dark instrument panel. No light variant —
the dot field and the hairline rules only read on black, and a naive
inversion would wash both out. Every colour is painted explicitly so the page
never borrows a host background. */
@font-face{font-family:'Zen';src:url('/fonts/Zen-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen';src:url('/fonts/Zen-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Pixel Square';src:url('/fonts/ZenPixel-Square.woff2') format('woff2');font-style:normal;font-display:swap}
:root{
--ink:#f4f4f2; --soft:#9c9c98; --faint:#6a6a66; --ground:#000; --panel:#0a0a0a;
--line:#232323; --line-hi:#3a3a3a; --accent:#f4f4f2;
--font-zen-sans:'Zen',-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif;
--font-zen-mono:'Zen Mono',ui-monospace,"SF Mono",SFMono-Regular,Menlo,Consolas,monospace;
--font-zen-pixel-square:'Zen Pixel Square',monospace;
--mono:var(--font-zen-mono);
--sans:var(--font-zen-sans);
/* Controls are pills and surfaces are soft, as on hanzo.ai. */
--r:999px; --r-soft:14px;
}
*{box-sizing:border-box}
html{-webkit-text-size-adjust:100%}
body{margin:0;background:var(--ground);color:var(--ink);font-family:var(--sans);
font-size:16px;line-height:1.65;-webkit-font-smoothing:antialiased}
.wrap{max-width:60rem;margin:0 auto;padding:0 1.75rem}
/* The dot field. A halftone made of one repeating radial-gradient, faded out
along the diagonal by a mask so it reads as a wave rather than wallpaper. */
/* No overflow clip here: the dot field is inset to the box already, and a clip
would cut off the copy-prompt menu. */
.hero{position:relative;border-bottom:1px solid var(--line)}
.hero::before{content:"";position:absolute;inset:0;
background-image:radial-gradient(var(--line-hi) 1px, transparent 1px);
background-size:7px 7px;
-webkit-mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
pointer-events:none}
.hero .wrap{position:relative;padding-top:5.5rem;padding-bottom:4rem}
nav{border-bottom:1px solid var(--line)}
nav .in{max-width:60rem;margin:0 auto;padding:1.1rem 1.75rem;display:flex;
justify-content:space-between;align-items:center;gap:1rem}
.brand{font-family:var(--mono);font-size:.85rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--ink);text-decoration:none;
display:inline-flex;align-items:center;gap:.6rem}
.brand i{font-style:normal;color:var(--faint)}
.mark{width:1.15em;height:1.15em;display:block;flex:0 0 auto}
nav a.up{font-family:var(--mono);font-size:.72rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--soft);text-decoration:none}
nav a.up:hover{color:var(--ink)}
h1{font-family:var(--mono);font-size:clamp(2rem,5.4vw,3.4rem);line-height:1.12;
letter-spacing:-.02em;margin:0 0 1.1rem;font-weight:500;text-wrap:balance}
h1 em{font-style:normal;color:var(--faint)}
.lede{color:var(--soft);font-size:1.05rem;max-width:52ch;margin:0 0 2.25rem}
.btns{display:flex;flex-wrap:wrap;gap:.7rem;margin:0 0 .5rem;align-items:center}
.btn{display:inline-flex;align-items:center;gap:.5rem;font-family:var(--mono);
font-size:.72rem;letter-spacing:.14em;text-transform:uppercase;
padding:.8rem 1.4rem;border:1px solid var(--line-hi);border-radius:var(--r);
color:var(--ink);text-decoration:none;background:transparent;cursor:pointer;
line-height:1.2;font-weight:400}
.btn:hover{background:#141414;text-decoration:none;border-color:var(--soft)}
.btn.solid{background:var(--ink);color:#000;border-color:var(--ink)}
.btn.solid:hover{background:#d8d8d4}
.btn .chev{width:.7em;height:.7em;flex:0 0 auto;transition:transform .15s ease}
.btn[aria-expanded="true"] .chev{transform:rotate(180deg)}
/* Copy-prompt selector. Each row copies the prompt for its own target. */
.copy{position:relative;display:inline-flex}
.menu{position:absolute;top:calc(100% + .5rem);left:0;z-index:20;min-width:21rem;
background:var(--panel);border:1px solid var(--line-hi);border-radius:var(--r-soft);
padding:.4rem;display:flex;flex-direction:column;
box-shadow:0 12px 32px rgba(0,0,0,.75)}
.menu[hidden]{display:none}
.mi{display:flex;align-items:center;gap:.7rem;width:100%;text-align:left;
padding:.62rem .8rem;border:0;border-radius:calc(var(--r-soft) - .35rem);
background:transparent;color:var(--ink);font-family:var(--mono);font-size:.76rem;
letter-spacing:.04em;text-decoration:none;cursor:pointer;line-height:1.3;
white-space:nowrap}
.mi:hover,.mi:focus-visible{background:#181818;outline:none}
.mi .mark{width:1.05rem;height:1.05rem;color:var(--soft)}
.mi:hover .mark{color:var(--ink)}
.mi u{margin-left:auto;color:var(--faint);text-decoration:none;font-size:.68rem;
letter-spacing:.1em;text-transform:uppercase}
/* Works-with bar: one scrolling row, name and mark per agent. */
.strip{border-bottom:1px solid var(--line);background:var(--panel)}
.strip .in{max-width:60rem;margin:0 auto;padding:.9rem 1.75rem;display:flex;
align-items:center;gap:1.25rem;font-family:var(--mono);font-size:.72rem;
letter-spacing:.1em;text-transform:uppercase;color:var(--faint)}
.strip b{color:var(--soft);font-weight:400;flex:0 0 auto;
border-right:1px solid var(--line);padding-right:1.25rem;align-self:stretch;
display:flex;align-items:center}
.bar{display:flex;align-items:center;gap:.5rem;flex:1 1 auto;min-width:0;
overflow-x:auto;scrollbar-width:none;scroll-snap-type:x proximity;
-webkit-overflow-scrolling:touch;
-webkit-mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent);
mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent)}
.bar::-webkit-scrollbar{display:none}
.agent{display:inline-flex;align-items:center;gap:.45rem;flex:0 0 auto;
padding:.4rem .85rem;border:1px solid var(--line);border-radius:var(--r);
color:var(--soft);white-space:nowrap;scroll-snap-align:start;
text-decoration:none;background:var(--ground)}
.agent:hover{color:var(--ink);border-color:var(--line-hi);text-decoration:none}
.agent .mark{width:.95rem;height:.95rem}
h2{font-family:var(--mono);font-size:1.1rem;letter-spacing:-.01em;margin:2.75rem 0 .75rem;font-weight:500}
h3{font-size:1rem;margin:2rem 0 .5rem;font-weight:600}
h4,h5,h6{font-size:.94rem;margin:1.5rem 0 .5rem;font-weight:600}
p{margin:0 0 1rem;max-width:70ch}
ul,ol{margin:0 0 1rem;padding-left:1.35rem;max-width:70ch}
li{margin:.22rem 0}
a{color:var(--ink);text-decoration:underline;text-underline-offset:3px;
text-decoration-color:var(--line-hi)}
a:hover{text-decoration-color:var(--ink)}
a:focus-visible{outline:1px solid var(--ink);outline-offset:3px}
code{font-family:var(--mono);font-size:.85em;background:var(--panel);
border:1px solid var(--line);border-radius:5px;padding:.1em .36em}
pre{background:var(--panel);border:1px solid var(--line);padding:1rem 1.1rem;
border-radius:var(--r-soft);overflow-x:auto;margin:0 0 1.25rem}
pre code{background:none;border:0;padding:0;font-size:.82rem;line-height:1.7}
blockquote{margin:0 0 1rem;padding-left:1rem;border-left:1px solid var(--line-hi);color:var(--soft)}
hr{border:0;border-top:1px solid var(--line);margin:2.5rem 0}
table{border-collapse:collapse;width:100%;margin:0 0 1.25rem;font-size:.92rem;
display:block;overflow-x:auto}
th,td{border:1px solid var(--line);padding:.5rem .7rem;text-align:left}
.curl{display:block;background:var(--panel);border:1px solid var(--line);
border-radius:var(--r-soft);padding:.95rem 1.1rem;font-family:var(--mono);
font-size:.8rem;color:var(--soft);overflow-x:auto;margin:0 0 2.5rem;
white-space:pre;line-height:1.9}
.curl b{color:var(--ink);font-weight:400}
.curl i{font-style:normal;color:var(--faint)}
/* index */
#q{width:100%;padding:.85rem 1.2rem;font-family:var(--mono);font-size:.85rem;color:var(--ink);
background:var(--panel);border:1px solid var(--line);border-radius:var(--r);margin:0 0 .6rem}
#q::placeholder{color:var(--faint);text-transform:uppercase;letter-spacing:.1em;font-size:.72rem}
#q:focus{outline:none;border-color:var(--soft)}
#count{color:var(--faint);font-family:var(--mono);font-size:.72rem;letter-spacing:.1em;
text-transform:uppercase;margin:0 0 2rem}
.cat{margin:2.5rem 0 .5rem;font-family:var(--mono);font-size:.7rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);border-bottom:1px solid var(--line);
padding-bottom:.45rem}
.row{display:block;padding:.6rem .9rem;margin:0 -.9rem;border-bottom:1px solid var(--line);
border-radius:var(--r-soft);text-decoration:none}
.row:hover{background:#0a0a0a}
.nm{font-family:var(--mono);font-size:.84rem;color:var(--ink);display:block}
.ds{color:var(--soft);font-size:.9rem;display:block;margin-top:.12rem}
footer{margin-top:4rem;padding:2rem 0 4rem;border-top:1px solid var(--line);
color:var(--faint);font-size:.85rem}
footer a{color:var(--soft)}
.fmap{display:grid;gap:1.75rem;grid-template-columns:repeat(auto-fit,minmax(11rem,1fr));
margin:0 0 2rem;font-size:.85rem}
.fmap b{display:block;font-family:var(--mono);font-size:.68rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);font-weight:400;margin:0 0 .6rem;
border-bottom:1px solid var(--line);padding-bottom:.4rem}
.fmap a{display:inline-block;color:var(--ink);text-decoration:none;margin:.3rem .35rem 0 0}
.fmap a:hover{text-decoration:underline}
.fmap div{color:var(--faint);line-height:1.5}
.fend{border-top:1px solid var(--line);padding-top:1.25rem;font-size:.82rem}
@media (max-width:640px){
.hero .wrap{padding-top:3.25rem;padding-bottom:2.75rem}
.btns{gap:.5rem}
.btn{padding:.75rem 1.15rem;font-size:.68rem}
.copy,.copy .btn{width:100%;justify-content:center}
.menu{left:0;right:0;min-width:0}
.strip .in{flex-direction:column;align-items:flex-start;gap:.6rem;padding:.9rem 1.75rem}
.strip b{border-right:0;padding-right:0}
.bar{width:100%}
}
</style>
<link rel="alternate" type="text/markdown" href="/offers.md">
<link rel="icon" href="/favicon.svg">
<link rel="canonical" href="https://hanzoskills.com/offers">
</head>
<!-- Reading this with a machine? Every page here is also plain markdown.
This one: https://hanzoskills.com/offers.md
Index: https://hanzoskills.com/llms.txt
Corpus: https://hanzoskills.com/all.md
Append .md to any path for the markdown twin. -->
<body>
<nav><div class="in">
<a class="brand" href="/"><svg class="mark" viewBox="0 0 67 67" fill="currentColor" aria-hidden="true"><path d="M22.21 67V44.6369H0V67H22.21Z"/><path d="M66.7038 22.3184H22.2534L0.0878906 44.6367H44.4634L66.7038 22.3184Z"/><path d="M22.21 0H0V22.3184H22.21V0Z"/><path d="M66.7198 0H44.5098V22.3184H66.7198V0Z"/><path d="M66.7198 67V44.6369H44.5098V67H66.7198Z"/></svg> HANZO<i>SKILLS</i></a>
<a class="up" href="/">All skills</a>
</div></nav>
<div class="wrap">
<h1>offers</h1><p class="lede">When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions &#x27;offer,&#x27; &#x27;offer design,&#x27; &#x27;build an offer,&#x27; &#x27;grand slam offer,&#x27; &#x27;irresistible offer,&#x27; &#x27;value stack,&#x27; &#x27;bonus stack,&#x27; &#x27;guarantee,&#x27; &#x27;risk reversal,&#x27; &#x27;money-back guarantee,&#x27; &#x27;scarcity,&#x27; &#x27;urgency,&#x27; &#x27;high-ticket offer,&#x27; &#x27;productize a service,&#x27; &#x27;naming an offer,&#x27; &#x27;payment plan,&#x27; &#x27;down-sell,&#x27; &#x27;upsell offer,&#x27; or &#x27;why isn&#x27;t my offer converting.&#x27; Best for services, agencies, courses, coaching, info products, high-ticket B2B, and direct-response. If you run pure self-serve SaaS, read pricing first — tiers and packaging do more work there. For price level itself (tiers, freemium, value metric), see pricing. For the page that presents the offer, see copywriting. For the launch moment, see launch. For sales collateral, see sales-enablement.</p><h1>Offer Design</h1>
<p>You are an expert in offer construction. Your goal is to help the user build offers that move — not by writing better copy on a worse offer, but by improving the offer itself.</p>
<h2>Before Starting</h2>
<p><strong>Check for product marketing context first:</strong> If <code>.agents/product-marketing.md</code> exists (or <code>.claude/product-marketing.md</code>, or the legacy <code>product-marketing-context.md</code> filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.</p>
<hr>
<h2>Core Philosophy</h2>
<p><strong>The offer is the thing, not the page.</strong> Better copy on a weak offer compounds slowly. A stronger offer with average copy converts immediately. Most &quot;we need better copy&quot; requests are actually &quot;we need a better offer&quot; requests in disguise.</p>
<p>This skill exists because the rest of the repo handles the <em>expression</em> of an offer — <code>copywriting</code> writes the sales page, <code>cro</code> optimizes the conversion path, <code>pricing</code> sets the tier structure, <code>launch</code> orchestrates the moment, <code>paywalls</code> shapes the upgrade prompt. None of them ask the deeper question: <strong>is the offer underneath any of that actually good?</strong></p>
<h3>When this skill matters</h3>
<p>You sell:</p>
<ul><li><strong>Services</strong> — consulting, freelance, agency retainers, productized services</li><li><strong>Courses</strong> — async, cohort-based, live</li><li><strong>Coaching</strong> — 1:1, group, mastermind</li><li><strong>Info products</strong> — guides, swipe files, templates, communities</li><li><strong>High-ticket B2B</strong> — $5K+ ACV with a sales conversation</li><li><strong>Direct-response</strong> — e-com promo offers, infomercial-style, paid-traffic-to-VSL</li></ul>
<h3>When <code>pricing</code> does more of the work</h3>
<p>You sell:</p>
<ul><li><strong>Self-serve SaaS</strong> with tiered subscriptions — the levers are mostly tier structure, value metric, and packaging; offer construction (bonuses, guarantees) is secondary</li><li><strong>Marketplaces</strong> — the offer is structural, not constructed</li></ul>
<p>Skim this skill in those cases for the value equation framing, then go to <code>pricing</code>.</p>
<hr>
<h2>The Value Equation</h2>
<p>The single most useful frame for offer design. Originally from Alex Hormozi&#x27;s <em>$100M Offers</em> — internalized broadly across direct-response and creator-economy training since.</p>
<pre><code> Dream Outcome × Perceived Likelihood of Achievement
Value = ─────────────────────────────────────────────────────────
Time Delay × Effort &amp; Sacrifice</code></pre>
<p>You move the four levers like this:</p>
<p>| Lever | What it means | How to increase value | |-------|---------------|-----------------------| | <strong>Dream outcome</strong> ↑ | What the customer actually wants | Connect to the bigger goal behind the surface ask. Specify and name it. | | <strong>Perceived likelihood</strong> ↑ | Do they believe they&#x27;ll get it | Proof (case studies, named customers, data), guarantees, methodology specificity | | <strong>Time delay</strong> ↓ | How long until result | Faster onboarding, faster first win, faster end-to-end timeline | | <strong>Effort &amp; sacrifice</strong> ↓ | What it costs them in time/work/risk besides money | Done-for-you, simpler process, fewer decisions, lower learning curve |</p>
<p><strong>Implication for offer construction</strong>: most &quot;lower the price&quot; requests are actually &quot;raise the numerator or lower the denominator&quot; requests. Price is the comparison, not the value.</p>
<p><strong>For the full framework, examples, and how to diagnose which lever is broken:</strong> see <a href="references/value-equation.md">references/value-equation.md</a></p>
<hr>
<h2>The Anatomy of a Complete Offer</h2>
<p>A complete offer has six components. Skip any one and conversion suffers.</p>
<p>| # | Component | Question it answers | |---|-----------|---------------------| | 1 | <strong>Core deliverable</strong> | What do they get? | | 2 | <strong>Bonus stack</strong> | What else do they get that makes the core feel undervalued? | | 3 | <strong>Guarantee</strong> | What happens if it doesn&#x27;t work? | | 4 | <strong>Scarcity / urgency</strong> | Why now, not later? | | 5 | <strong>Name</strong> | What is this thing called? | | 6 | <strong>Price + payment structure</strong> | What do they pay and how? |</p>
<p>Most weak offers fail on bonuses (none), guarantees (none or wrong type), or scarcity (none, or fake). Most aggressive-to-the-point-of-cringe offers fail on guarantee (over-promising) or scarcity (fake countdown timers).</p>
<p><strong>For the full anatomy with worked examples:</strong> see <a href="references/offer-anatomy.md">references/offer-anatomy.md</a></p>
<hr>
<h2>Reference Library</h2>
<p>| Reference | When to read | |-----------|--------------| | <a href="references/value-equation.md">value-equation.md</a> | Diagnosing which lever is broken on a stuck offer | | <a href="references/offer-anatomy.md">offer-anatomy.md</a> | Building a complete offer from scratch | | <a href="references/guarantee-design.md">guarantee-design.md</a> | Picking the right type of guarantee for your business model | | <a href="references/bonus-stacking.md">bonus-stacking.md</a> | Adding bonuses that raise perceived value without devaluing the core | | <a href="references/scarcity-urgency.md">scarcity-urgency.md</a> | Creating <em>real</em> scarcity (and avoiding the fake patterns that destroy trust) | | <a href="references/offer-formats.md">offer-formats.md</a> | Format playbooks by business type — service, course, coaching, info product, SaaS lead magnet, agency retainer, high-ticket B2B | | <a href="references/examples.md">examples.md</a> | Anonymized worked examples — before/after for each business type |</p>
<hr>
<h2>The Diagnostic Loop</h2>
<p>When the user says &quot;my offer isn&#x27;t converting&quot; or &quot;I want to improve my offer&quot;:</p>
<ol><li><strong>Identify the business type</strong> — service, course, coaching, info product, SaaS, agency, B2B. The right playbook is type-specific.</li><li><strong>State the current offer in plain language</strong> — name, price, what they get, guarantee, deadline. Write it down even if it lives in scattered places now.</li><li><strong>Run the value equation</strong> — score each of the four levers 1–10. The lowest is the binding constraint.</li><li><strong>Audit the anatomy</strong> — which of the six components is missing or weak?</li><li><strong>Pick one lever to fix this iteration</strong> — don&#x27;t rebuild everything. The biggest lever is usually the one currently scoring lowest.</li><li><strong>Draft the changed component</strong> — new bonus, new guarantee, new scarcity, new name, new payment plan</li><li><strong>Project the lift, honestly</strong> — most single-component changes deliver 10–40% conversion lift. Anyone promising 5x is selling something. Two consecutive iterations on different levers can stack to 2–3x.</li></ol>
<hr>
<h2>When NOT to Use Offer-Design Tactics</h2>
<p>Some offer patterns work but cost more than they&#x27;re worth:</p>
<ul><li><strong>Manipulative scarcity</strong> — fake countdown timers, &quot;only 3 spots left&quot; lies. Short-term lift, long-term trust collapse. Don&#x27;t.</li><li><strong>Over-promising guarantees</strong> — &quot;double your revenue or refund + $1,000.&quot; Refund risk eats margin; the few cases that fail nuke your reputation publicly.</li><li><strong>Bonus inflation</strong> — stacking $50K of &quot;bonuses&quot; on a $497 product so it &quot;feels like a steal.&quot; Sophisticated buyers see this. Treat bonuses as additive, not exaggerated.</li><li><strong>Course-bro aesthetic on a serious product</strong> — Gold logos, &quot;secret method,&quot; fake urgency. Pattern-matches to scam. Wrong room.</li></ul>
<p>The repo voice: opinionated, but honest. Building offers well doesn&#x27;t mean building offers loud.</p>
<hr>
<h2>Banned Vocabulary</h2>
<p>When drafting offer language (sales pages, emails, headlines), avoid:</p>
<ul><li><strong>&quot;Game-changing,&quot; &quot;revolutionary,&quot; &quot;disruptive,&quot; &quot;next-level,&quot; &quot;10x&quot;</strong> — pattern-matches to AI slop / course-bro</li><li><strong>&quot;Secret,&quot; &quot;hidden,&quot; &quot;what they don&#x27;t want you to know&quot;</strong> — clickbait</li><li><strong>&quot;Limited time&quot; with no actual time limit</strong> — lying</li><li><strong>&quot;Worth $X&quot; or &quot;$Y value&quot; with no comparable</strong> — inflation</li><li><strong>&quot;100% guaranteed&quot; without specifying conditions</strong> — legally and brand-wise risky</li></ul>
<p>Use specific numbers, named customers, concrete outcomes, real timelines. Specificity beats superlatives.</p>
<hr>
<h2>Related Skills</h2>
<ul><li><strong>pricing</strong> — for price levels, tier structure, value metric, packaging, freemium</li><li><strong>copywriting</strong> — for the page that presents the offer</li><li><strong>cro</strong> — for optimizing the conversion path the offer travels through</li><li><strong>launch</strong> — for the moment you ship the offer</li><li><strong>paywalls</strong> — for in-app upgrade-prompt versions of an offer</li><li><strong>sales-enablement</strong> — for the deck and one-pager that carry the offer into a sales conversation</li><li><strong>emails</strong> — for the email sequence that warms up the offer</li><li><strong>marketing-psychology</strong> — for the cognitive biases that make offers land or bounce</li></ul>
<footer>
<div class="fmap">
<div><b>Build</b>
<a href="https://hanzo.app">hanzo.app</a> app builder
<a href="https://hanzo.codes">hanzo.codes</a> code with an agent
<a href="https://hanzoskills.com">hanzoskills.com</a> what an agent reads</div>
<div><b>Run</b>
<a href="https://console.hanzo.ai">console.hanzo.ai</a> cloud console
<a href="https://api.hanzo.ai">api.hanzo.ai</a> the API</div>
<div><b>Account</b>
<a href="https://hanzo.id">hanzo.id</a> sign in
<a href="https://pay.hanzo.ai">pay.hanzo.ai</a> top up
<a href="https://billing.hanzo.ai">billing.hanzo.ai</a> invoices and usage</div>
<div><b>Company</b>
<a href="https://hanzo.ai">hanzo.ai</a> canonical
<a href="https://hanzo.ventures">hanzo.ventures</a> ventures</div>
</div>
<div class="fend"><a href="/offers.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
</footer>
</div></body></html>