Promo Codes

Setup Fee Codes — Legacy / Do Not Use

Usage counts may be stale; check Stripe for current redemption totals.

Monthly Discount Codes — General

Usage counts may be stale; check Stripe for current redemption totals.

Partner / Referral Codes

Partnership Property Codes (70 Properties)

All codes: $100/mo off × 4 months (repeating). Stripe coupon W8K6JWCH. 6-month revenue: $1,396. 12-month revenue: $3,188.

Slug rules: Lowercase, no spaces, no hyphens, no special characters. Must be unique across all entries.

Demo page: mystoragevalet.com/promo/sample exists as a demo-only preview for partnership outreach. SAMPLE appears in the website’s PROPERTIES object but is not a real Stripe promotion code — the code block is hidden and the CTA routes to the partnerships contact form. See Partnerships > Sample Demo Page.

Partner Marketing Assets (Print Collateral)

Each property folder holds 4 PDFs on the v6 “Operation Midnight Teal” brand, each carrying a scannable QR to that property’s /promo/{slug} page: Postcard and Flyer, each in a print-shop version (bleed + crop marks) and a home-print version.

Engine (stays in iCloud): ~/Documents/storagevalet/Marketing/Collateral/promo-cards-v6/

• Generate: ./make-property-assets.sh <slug> <CODE> "<Name>" → 4 PDFs in output/<slug>/
• Publish to Drive (human-friendly names + rebuild _INDEX.csv): ./publish-to-drive.sh (all properties in partners.txt) or ./publish-to-drive.sh <slug> "<Name>" (single)

⚠ The Google Drive desktop app must be running for published files to upload to the cloud (open -a "Google Drive") — it does not auto-launch. If newly published assets aren’t appearing online, check that first.

Press-grade print files (press-ready.sh)

The two print-shop PDFs are automatically normalized into true press-ready files by press-ready.sh (Ghostscript), which runs inside make-property-assets.sh right after render. It tags every page with a proper TrimBox + BleedBox (so a professional RIP knows the exact cut line), embeds all fonts, sets /prepress quality, and applies no image downsampling. Ghostscript is in the shared Brewfile; if it is missing the script prints a notice and leaves the PDFs un-normalized.

Page geometry (0.125 in / 9 pt bleed): postcard page 450×306 pt (6.25×4.25 in) → TrimBox [9 9 441 297]; flyer page 630×810 pt (8.75×11.25 in) → TrimBox [9 9 621 801]; BleedBox is the full page in both. Standalone use: ./press-ready.sh <in.pdf> <out.pdf> <card|flyer> [--cmyk].

Live as of Jun 4, 2026 — 7 partner properties: Willow Bridge — The Jordan, Mariners Landing, Artisan Series, 1125 Jefferson; Advance Realty — The Harlow, The Bexley, Edge Lofts. Pre-construction 1404 Willow and 1417 Adams are intentionally excluded until they open. Codes/pages source of truth: the property-code table above + sv-website/promo/index.html + Stripe coupon W8K6JWCH.

Runbook — Create a Promo Set for a Property (any offer)

The canonical, AI-executable playbook for standing up everything a property needs: a working promo code, a live trackable page, and print-ready cards — for whatever offer is being tested. It is deliberately instruction-driven, not hard-automated: a Claude Code session runs it from the inputs you give, so the offer can vary per experiment without changing any tooling.

What you provide

• Property name + slug (lowercase, no spaces or hyphens — see slug rules in Technology).
• The offer being run — e.g. “$100/mo off × 4 months” (the standard intro), “$75/mo × 6”, “first month free”, “20% off × 6”.
• Optional: an experiment label if you’re A/B-testing offers across properties.

Steps (a Claude Code session runs these)

1. Pick or create the offer’s coupon. If it’s the standard intro ($100/mo × 4), reuse W8K6JWCH. For a new offer to test, create the coupon first, with a recognizable name:

   stripe coupons create -d name="$75 off x 6mo" \
     -d amount_off=7500 -d currency=usd \
     -d duration=repeating -d duration_in_months=6

   (amount_off is in cents; use -d percent_off=N for a percentage, or -d duration=once for a one-time discount.)
2. Create the property’s promotion code on that coupon, tagged for cohort analysis:

   stripe promotion_codes create -d coupon=<COUPON> -d code=<CODE> \
     -d metadata[property_slug]=<slug> -d metadata[property_name]="<Name>" \
     -d metadata[offer]="<offer name>" -d metadata[experiment]="<label>"

   The metadata is what makes the cohort measurable later. Idempotency check: python3 stripe-promo-sync.py (audit) or stripe promotion_codes list -d code=<CODE> confirms it isn’t already there. For the standard offer across many properties at once, stripe-promo-sync.py --create makes every missing code in one pass.
3. Switch the promo page on. Add the property to the PROPERTIES object in sv-website/promo/index.html, commit + push (Vercel auto-deploys in ~60s). This makes /promo/{slug} live — the URL the QR encodes (?src=qr) and where the promo_page_view analytics event fires. Full technical steps + slug rules: Technology → Promo Page Architecture → Adding a New Property (technology.html).
4. Generate + publish the assets from the iCloud engine:

   cd ~/Documents/storagevalet/Marketing/Collateral/promo-cards-v6
   python3 sync-properties.py                      # reconcile from index.html
   ./make-property-assets.sh <slug> <CODE> "<Name>"  # 4 press-ready PDFs
   ./publish-to-drive.sh <slug> "<Name>"           # if a partner we distribute to

5. Verify end to end. python3 stripe-promo-sync.py shows the property OK (active on its coupon); /promo/{slug} returns HTTP 200 and the QR decodes to the right page (both covered by sales-engine-check.sh).

Measuring offers & cohort LTV

Because each offer is its own coupon and every code carries metadata, you can compare offers cleanly with no extra tooling:

• Top of funnel (analytics): promo_page_view / promo_cta_click by code + src → which properties and offers draw scans and clicks.
• Conversion + LTV (Stripe): a redeemed code applies its coupon to the customer’s subscription. Group customers by coupon (the offer) or promotion code (the property) → MRR, months retained, churn, realized revenue = that cohort’s LTV over time.
• On demand: ask a Claude Code session to “pull the cohort / LTV breakdown for offer X” — it queries Stripe subscriptions + invoices alongside GA4. No standing dashboard required. (Customer→code attribution lives in Stripe today; a promo_code column on the customer record is a planned enhancement.)

Engine-local quick version (the “one prompt”): promo-cards-v6/PROPERTY-MARKETING-PROCESS.md. Changing the standard intro offer requires founder sign-off; running a new experimental offer alongside it does not.

Founder Personal Codes — Zach

Founder Personal Codes — Mary

Redemption Tracking

Planned metrics for each code:

• Total redemptions — How many times the code has been used
• Active subscribers — Current customers who used this code
• Churned subscribers — Former customers who used this code
• Revenue generated — Total and average revenue per redemption
• Conversion rate — Checkout starts vs. completions with code
• Campaign attribution — Which marketing channel drove usage