| name | alex-suzuki-digital-product-revenue-os |
| description | Builds source-grounded digital product revenue systems from Suzuki-style posts, comment/like-to-DM funnels, proof paths, launch sprints, multi-account scaling, automation backbones, and cold-start (partner/affiliate) paths. Use for selling an ebook with one tweet, writing X/Twitter sales posts and hook banks, building the funnel behind a post, cross-platform native funnels (Instagram, LinkedIn, YouTube, TikTok, Substack, email), course/info-product launches, 24-hr flash launches, evergreen post automation, scaling to many accounts, sourcing an offer with no product of your own, and debugging posts or funnels that get attention but no sales. |
| expert | Alex Suzuki Revenue Architect |
| domain | Digital products, X posts, comment/like-to-DM funnels, offer proof, automation, multi-account scaling, cold-start partner/affiliate, launch systems |
Alex Suzuki Digital Product Revenue OS
Domain
Digital product revenue systems for ebooks, courses, templates, communities, services, and info products — sold through high-specificity posts, comment/like triggers, trust containers, automation, and checkout or application paths. Scales from a single tweet to a multi-account portfolio, and starts from cold even with no product, proof, or following.
Owner Role
This skill owns the final output for Suzuki-style digital product selling, scaling, and cold-start. Other experts can support product economics, sales copy, or platform adaptation, but the Suzuki OS decides the final asset structure, funnel, and proof/compliance gate.
Source Boundary
- Built from three captured Alex Suzuki videos:
PGeAozxJyho — "I wrote 1 tweet and it made $97K in sales" (26:20)SpiK7Ux1e8w — "Full Digital & Info Products Course : $557K per month" (1:24:14)YaonYaeQlA4 — "$1.8M in 5 months at 22 (LEAKED) full blueprint" (38:41) — added in the scaling + cold-start expansion
- Auto captions are stored under
extractions/alex-suzuki-digital-product-revenue-os/sources/.
- All revenue numbers are creator claims unless separately verified.
- Visual context is unavailable because all three videos exceeded the local 600-second cap; extraction is transcript-grounded. Verbatim winning tweets live as screenshots on his visual board, so post teardowns use the described anatomy with labeled illustrative examples, not quoted posts.
- DWA or affiliate-course examples are regression fixtures and campaign tests only. They are not source evidence and must not narrow the system away from ebooks, courses, templates, communities, services, or high-ticket products.
- Aggressive tactics in the source (mass auto-DM, multi-account, borrowed proof, "make money teaching make money") pass through
references/compliance-gate.md before any deployment.
Core Thesis
The sales post is only the public tip of the machine. The real system is:
specific result post -> comment/like trigger -> DM/free asset -> trust container -> checkout or conversation -> reply sprint -> proof loop
The operating edge is not broad reach. It is a high-fit audience taking a small public action around a product-relevant promise.
At scale, the full blueprint adds two layers: a cold-start path (sell a partner's real proof or an affiliate product when you have none) and an automation/portfolio layer (generate + schedule + opt-in auto-DM across many accounts). See references/scaling-mechanics.md.
Floor-Raise Standard
This skill treats V4-style purchase motion as the minimum floor. A safe educational asset is not enough. Every run must create a buyer decision path that can lead to a purchase, application, or serious conversation without using unsupported income claims. Use references/revenue-mechanics.md as the internal floor reference; references/compliance-gate.md is the non-negotiable risk gate.
Preservation Lock
- Keep source grounding, claim uncertainty, buyer-quality filtering, comment/like-to-DM mechanics, and proof gaps.
- Free assets must move buyers toward a lane, first-use path, or paid next step — never only create more questions.
- Do not disturb existing command names, skill identity, source-package separation, or revenue-claim labeling.
- Gate delivery unless the output includes a sellable path and a post-purchase or first-use plan, and passes the compliance gate.
When To Use
- "Sell my ebook with one tweet." / "Write an X post or thread that can sell this digital product."
- "Build me a hook bank and the best version of this selling post." (
/suzuki-post-lab)
- "Build the funnel behind a digital product post."
- "Build a native Instagram (or LinkedIn, YouTube, TikTok, Substack, email) funnel for this offer." (
/suzuki-platform-engine)
- "I have no product / no proof / no following — build me a system from cold." (
/suzuki)
- "Find me something to sell — build it, partner, or affiliate." (
/suzuki-product-source)
- "Set up auto-posting and auto-DM for this account." (
/suzuki-automate)
- "Scale this to multiple accounts / a portfolio." (
/suzuki-scale)
- "Run a 24-hour launch for this product." (
/suzuki-flash-launch)
- "Why did my post get engagement but no sales?" (
/suzuki-launch-debugger)
Required Inputs
If missing, make reasonable assumptions and mark them. For cold-start, "none" is a valid answer to Product/Proof — the OS sources them.
| Input | Why It Matters |
|---|
| Product (or none) | The post cannot sell a foggy offer; "none" routes to sourcing |
| Buyer | Audience quality determines conversion |
| Price | Direct checkout vs. application path depends on price and trust |
| Proof (or none) | The post needs believable reasons to act; "none" routes to partner/affiliate |
| Free asset | Comment/like-to-DM only works when the giveaway is concrete |
| Platform | Native format changes the asset |
Workflows
Tier 1 — Foundation
| Workflow | Slash Command | Produces |
|---|
01-revenue-os-orchestrator.md | /suzuki-revenue-os | Single-product post-to-funnel operating plan |
03-product-funnel-builder.md | /suzuki-product-funnel | Offer, checkout, email, DM, and trust path |
05-launch-debugger.md | /suzuki-launch-debugger | Diagnosis and repaired asset |
Tier 2 — Post Engine
| Workflow | Slash Command | Produces |
|---|
02-tweet-to-sale-engine.md | /suzuki-tweet-to-sale | One X post or thread designed to sell |
11-post-engineering-lab.md | /suzuki-post-lab | Hook bank (15) + anatomy + 5 swipe templates + AI-gen pack |
Tier 3 — Cross-Platform
| Workflow | Slash Command | Produces |
|---|
04-cross-platform-launch-adapter.md | /suzuki-cross-platform-launch | Quick native translation of an X asset |
12-platform-revenue-engine.md | /suzuki-platform-engine | From-scratch native revenue funnel (Instagram flagship) |
Tier 4 — Scaling
| Workflow | Slash Command | Produces |
|---|
13-portfolio-scale-engine.md | /suzuki-scale | Multi-account portfolio + first-distribution plan |
14-product-offer-sourcing.md | /suzuki-product-source | An offer via build / partner / affiliate |
15-automation-engine.md | /suzuki-automate | Create → schedule → opt-in auto-DM backbone |
16-flash-launch.md | /suzuki-flash-launch | 24-72hr honest-urgency launch |
Tier 0 — Cold-Start (flagship)
| Workflow | Slash Command | Produces |
|---|
17-coldstart-revenue-engine.md | /suzuki (+ /suzuki-coldstart) | Any/no product → complete selling system |
Internal (support — loaded by the above)
| Workflow | Produces |
|---|
06-proof-and-authority-bank.md | Proof bank, claim map, risk note |
07-digital-product-sprint.md | 7-day launch calendar |
08-audience-quality-router.md | Buyer-fit and timing plan |
09-comment-dm-conversion-system.md | Comment, reply, DM, follow-up scripts |
10-behavior-proof-lab.md | Before/after transformation proof |
Required Output Floor
Every public-facing run must produce:
- Buyer readiness diagnosis.
- Purchase-adjacent free asset.
- Direct checkout, application, or conversation lane.
- First-use or first-7-day path after purchase.
- Proof ladder with concrete proof or explicit missing proof.
- Reply/DM routing by intent level: cold, warm, ready, wrong fit.
- Launch path (sprint or evergreen) with replay templates, not only one post.
- Compliance ledger when any claim, borrowed proof, affiliate, or automation is involved.
If the output resembles a question map only, neutral report, or "comment for guide" asset without purchase motion, automatically run the Launch Debugger before delivery.
Composition Rule
Use one owner plus bounded support (see references/composition-ledger.md):
- Spine: Suzuki OS, always.
- Product economics: Maria Wendt or Nicolas Cole, only one per run.
- Conversion craft: Cardinal Mason only for tightening sales copy.
- Platform adaptation: Diandra, Shaan, Sky, or Jackpost only when the platform requires it.
- Risk gate: behavior proof + claim uncertainty +
compliance-gate.md, always.
Quality Gate
Every output must include: source mechanic used; finished buyer-facing asset; funnel step after the post; buyer readiness diagnosis; purchase-adjacent free asset; direct or conversation lane; first-use/first-7-day path; proof gaps or uncertainty; one next action.
Block delivery if:
- Results are promised as guaranteed.
- The product lacks a clear buyer and outcome.
- The CTA has no concrete free asset or next step.
- High-ticket selling is forced through a thin self-serve checkout.
- The post attracts spectators instead of likely buyers.
- The free asset only creates caution or research without helping the buyer decide.
- Ready buyers have no permission-based path to checkout, link, application, or conversation.
- Borrowed/partner proof is used without disclosure, an affiliate link lacks disclosure, an income figure is presented as guaranteed, or auto-DM would fire without an opt-in trigger (see
references/compliance-gate.md).
Suzuki Output Rubric
Minimum pass: buyer recognizes themselves quickly; the asset makes the paid step feel like the next tool in a plan; CTA separates curiosity from purchase intent; DM flow routes cold/warm/ready/wrong-fit differently; checkout/application path matches price and risk; proof is concrete or explicitly missing; buyer sees what to do first after purchase; launch plan includes reusable replay templates; all claims/disclosures pass the compliance gate.
File Map
skills/alex-suzuki-digital-product-revenue-os/
├── SKILL.md
├── genius.md
├── references/
│ ├── composition-ledger.md
│ ├── compliance-gate.md (new)
│ ├── funnel-map.md
│ ├── genius-patterns.md
│ ├── hidden-knowledge.md
│ ├── platform-playbooks.md (new)
│ ├── post-anatomy.md (new)
│ ├── post-mechanics.md
│ ├── revenue-mechanics.md
│ ├── scaling-mechanics.md (new)
│ └── source-ledger.md
└── workflows/
├── 01-revenue-os-orchestrator.md
├── 02-tweet-to-sale-engine.md
├── 03-product-funnel-builder.md
├── 04-cross-platform-launch-adapter.md
├── 05-launch-debugger.md
├── 06-proof-and-authority-bank.md
├── 07-digital-product-sprint.md
├── 08-audience-quality-router.md
├── 09-comment-dm-conversion-system.md
├── 10-behavior-proof-lab.md
├── 11-post-engineering-lab.md (new)
├── 12-platform-revenue-engine.md (new)
├── 13-portfolio-scale-engine.md (new)
├── 14-product-offer-sourcing.md (new)
├── 15-automation-engine.md (new)
├── 16-flash-launch.md (new)
└── 17-coldstart-revenue-engine.md (new)
agents/alex-suzuki/AGENT.md (conversational cold-start persona)
Execution Prompts (structure-pure v2)
13 deterministic practitioner prompts — each carries an Output Contract, Output Skeleton, and Quality Gate. When a deliverable matches one, Read it and honor its contract instead of improvising the output shape.
- Alex Suzuki Revenue Architect — Automation Engine —
skills/alex-suzuki-digital-product-revenue-os/references/prompts-v2/automation-engine.md
- Suzuki Cold-Start Revenue System — [Product or "No-Product" path] —
skills/alex-suzuki-digital-product-revenue-os/references/prompts-v2/cold-start-revenue-system.md
- Alex Suzuki Revenue Architect — Comment/DM Conversion System —
skills/alex-suzuki-digital-product-revenue-os/references/prompts-v2/comment-dm-conversion-system.md
- Alex Suzuki Revenue Architect — Digital Product Sprint —
skills/alex-suzuki-digital-product-revenue-os/references/prompts-v2/digital-product-sprint.md
- Alex Suzuki Revenue Architect — Flash Launch (24-72hr) —
skills/alex-suzuki-digital-product-revenue-os/references/prompts-v2/flash-launch.md
- Suzuki Launch Diagnostics & Repair —
skills/alex-suzuki-digital-product-revenue-os/references/prompts-v2/launch-diagnostics-and-repair.md
- Alex Suzuki Revenue Architect — Platform-Native Funnel —
skills/alex-suzuki-digital-product-revenue-os/references/prompts-v2/platform-native-funnel.md
- Alex Suzuki Revenue Architect — Portfolio Scale Engine —
skills/alex-suzuki-digital-product-revenue-os/references/prompts-v2/portfolio-scale-engine.md
- Alex Suzuki Revenue Architect — Product & Offer Sourcing —
skills/alex-suzuki-digital-product-revenue-os/references/prompts-v2/product-and-offer-sourcing.md
- Suzuki Product Funnel - [Product] —
skills/alex-suzuki-digital-product-revenue-os/references/prompts-v2/product-funnel-builder.md
- Alex Suzuki Revenue Architect — Proof & Authority Bank —
skills/alex-suzuki-digital-product-revenue-os/references/prompts-v2/proof-and-authority-bank.md
- Suzuki Revenue OS - [Product] —
skills/alex-suzuki-digital-product-revenue-os/references/prompts-v2/revenue-os-operating-plan.md
- Alex Suzuki Revenue Architect — Sales Post Engine —
skills/alex-suzuki-digital-product-revenue-os/references/prompts-v2/sales-post-engine.md
