The prompts, schemas, and token economics behind every asset.
Each asset is one generateObject call against a Zod schema. The schema enforces shape; the system prompt enforces voice and constraints; the user prompt is hydrated from open-money-stack.yml. Nothing in production reads free-form model output.
Platform-layer call
platformBundleSchemaPlatform-layer narrative across all products.master_narrative (200-1200)bundled_pitch (150-900)icp_to_product_map[≥2]cross_product_table[≥2]You are a senior PMM building the platform-level narrative for a multi-product B2B platform. Output four parts: a master narrative, a bundled pitch (why the stack > the parts), an ICP-to-product map, and a cross-product table. Reference only the products listed. Use product ids exactly as provided.
Platform: Polygon Open Money Stack Category: Onchain money-movement infrastructure One-liner: API-driven money movement on blockchain settlement — issuance, liquidity, settlement, and interop in one stack. Positioning statement: For fintechs, neobanks, PSPs, and enterprises that need programmable dollar rails at internet scale, the Polygon Open Money Stack is the API-driven money-movement infrastructure that combines deep stablecoin liquidity (PoS), cross-chain settlement (AggLayer), sovereign issuer chains (CDK), and verifiable execution (zkEVM) into one stack. Unlike Tron (single-rail, no programmability), Circle (issuer-only, USDC-only), or Solana Pay (single-chain), the Polygon Stack gives builders a programmable, multi-asset, multi-chain platform with the regulatory posture banks and PSPs require. Bundled value: The point of the stack is not any single product — it is that issuance, liquidity, settlement, and interop compose into one API surface. A neobank can issue on CDK, source liquidity from PoS, settle through AggLayer, and prove compliance with zkEVM — all without integrating four vendors. ICP segments: - fintech: Fintechs & neobanks — Series B–E companies needing programmable dollar rails for treasury, payouts, and embedded finance. - psp: PSPs & payment platforms — Payment service providers and Stripe-class platforms expanding into stablecoin acceptance and settlement. - enterprise: Enterprise issuers — Banks, fintechs, and platforms that need their own permissioned chain for tokenized cash or compliance reasons. - builder: Builders & app teams — Teams building consumer payments apps, marketplaces, or crypto-native fintech products on EVM. Products: - agglayer (AggLayer): Unified liquidity and shared state across heterogeneous chains via pessimistic proofs. | ICPs: fintech,psp,enterprise | top competitor: Optimism Superchain - cdk (Polygon CDK): Deploy your own zk-powered chain that connects to AggLayer at launch. | ICPs: enterprise,fintech | top competitor: Arbitrum Orbit - polygon-pos (Polygon PoS): The largest non-Tron stablecoin EVM home — battle-tested for global payments and fintech use cases. | ICPs: fintech,psp,builder | top competitor: Tron - zkevm (Polygon zkEVM): EVM-equivalent zk-rollup for use cases that require cryptographic settlement guarantees. | ICPs: enterprise,fintech | top competitor: zkSync Era Voice traits: direct, evidence-based, technical-credible, ships at 80%. Forbidden words (never use): unlocks, revolutionary, paradigm shift, next-generation, world-class, best-in-class, leverage, synergy. Reference voice: Stripe's docs voice meets Cloudflare's blog voice. Specific, opinionated, evidence-led.
Per-product calls — Polygon CDK
onePagerSchemaSingle-product one-pager — drops into a deck or PDF.headline (≤80)subheadline (≤180)problem (≤280)solution (≤320)features[3-4]proof[2-4]cta{primary, secondary}You are a senior product marketing writer working from a positioning source of truth. Generate copy that could ship without editorial review. Be specific, concrete, and concise. Never invent numbers, customers, or claims not present in the supplied context. When a forbidden word is listed, do not use it under any inflection. Output: a one-pager structured for a single product, ready to drop into a deck.
Generate the one-pager for Polygon CDK. Platform: Polygon Open Money Stack — API-driven money movement on blockchain settlement — issuance, liquidity, settlement, and interop in one stack. Platform positioning: For fintechs, neobanks, PSPs, and enterprises that need programmable dollar rails at internet scale, the Polygon Open Money Stack is the API-driven money-movement infrastructure that combines deep stablecoin liquidity (PoS), cross-chain settlement (AggLayer), sovereign issuer chains (CDK), and verifiable execution (zkEVM) into one stack. Unlike Tron (single-rail, no programmability), Circle (issuer-only, USDC-only), or Solana Pay (single-chain), the Polygon Stack gives builders a programmable, multi-asset, multi-chain platform with the regulatory posture banks and PSPs require. Bundled value: The point of the stack is not any single product — it is that issuance, liquidity, settlement, and interop compose into one API surface. A neobank can issue on CDK, source liquidity from PoS, settle through AggLayer, and prove compliance with zkEVM — all without integrating four vendors. Product: Polygon CDK (Sovereign chain dev kit, status ga) One-liner: Deploy your own zk-powered chain that connects to AggLayer at launch. Job-to-be-done: Spin up a sovereign chain — for a regulated bank, a tokenized RWA issuer, a high-throughput consumer app — with the proving, gas-token, and compliance levers you need, while inheriting Polygon's liquidity and interop. ICPs (ids): enterprise, fintech Differentiators: - Sovereign control of gas token, throughput, validators, and compliance gates. - AggLayer connection at launch — no isolated-chain bootstrap problem. - zk-proving stack inherited; no need to build your own prover or sequencer. - Compliance and KYC modules built for regulated issuers. Competitors: - Arbitrum Orbit: Orbit is OP-stack only and settles into Arbitrum One. CDK is zk-native and settles via AggLayer into a heterogeneous-chain ecosystem. CDK fits issuer chains that need regulatory finality; Orbit fits gaming/social chains that need Arbitrum's existing tooling. - OP Stack / Superchain: OP Stack ties you to optimistic fault proofs and 7-day withdrawals. CDK gives zk finality and shorter settlement guarantees, which matters for regulated cash and tokenized RWA use cases. - ZK Stack (zkSync): ZK Stack chains connect through zkSync's Elastic Network. CDK chains connect through AggLayer, which accepts non-zk chains too. If a customer's roadmap includes non-zk chains, ZK Stack is a dead end. Proof points: - Live deployments include X Layer (OKX), Astar zkEVM, Lumia. - Compliance modules production-tested for regulated payments use cases. - AggLayer-by-default removes the cold-start liquidity problem most sovereign chains face. Primary metric: CDK chains in production Voice traits: direct, evidence-based, technical-credible, ships at 80%. Forbidden words (never use): unlocks, revolutionary, paradigm shift, next-generation, world-class, best-in-class, leverage, synergy. Reference voice: Stripe's docs voice meets Cloudflare's blog voice. Specific, opinionated, evidence-led.
landingBlockSchemaLanding-page block — hero, features, social proof, FAQ.hero{headline, subheadline, ctas}features[3-4]socialProof (≤280)faq[3-4]You are a senior product marketing writer working from a positioning source of truth. Generate copy that could ship without editorial review. Be specific, concrete, and concise. Never invent numbers, customers, or claims not present in the supplied context. When a forbidden word is listed, do not use it under any inflection. Output: a landing-page block (hero, features, social proof, FAQ) for the product page.
Generate the landing-page block for Polygon CDK. Keep the hero headline benefit-led, not feature-led. Platform: Polygon Open Money Stack — API-driven money movement on blockchain settlement — issuance, liquidity, settlement, and interop in one stack. Platform positioning: For fintechs, neobanks, PSPs, and enterprises that need programmable dollar rails at internet scale, the Polygon Open Money Stack is the API-driven money-movement infrastructure that combines deep stablecoin liquidity (PoS), cross-chain settlement (AggLayer), sovereign issuer chains (CDK), and verifiable execution (zkEVM) into one stack. Unlike Tron (single-rail, no programmability), Circle (issuer-only, USDC-only), or Solana Pay (single-chain), the Polygon Stack gives builders a programmable, multi-asset, multi-chain platform with the regulatory posture banks and PSPs require. Bundled value: The point of the stack is not any single product — it is that issuance, liquidity, settlement, and interop compose into one API surface. A neobank can issue on CDK, source liquidity from PoS, settle through AggLayer, and prove compliance with zkEVM — all without integrating four vendors. Product: Polygon CDK (Sovereign chain dev kit, status ga) One-liner: Deploy your own zk-powered chain that connects to AggLayer at launch. Job-to-be-done: Spin up a sovereign chain — for a regulated bank, a tokenized RWA issuer, a high-throughput consumer app — with the proving, gas-token, and compliance levers you need, while inheriting Polygon's liquidity and interop. ICPs (ids): enterprise, fintech Differentiators: - Sovereign control of gas token, throughput, validators, and compliance gates. - AggLayer connection at launch — no isolated-chain bootstrap problem. - zk-proving stack inherited; no need to build your own prover or sequencer. - Compliance and KYC modules built for regulated issuers. Competitors: - Arbitrum Orbit: Orbit is OP-stack only and settles into Arbitrum One. CDK is zk-native and settles via AggLayer into a heterogeneous-chain ecosystem. CDK fits issuer chains that need regulatory finality; Orbit fits gaming/social chains that need Arbitrum's existing tooling. - OP Stack / Superchain: OP Stack ties you to optimistic fault proofs and 7-day withdrawals. CDK gives zk finality and shorter settlement guarantees, which matters for regulated cash and tokenized RWA use cases. - ZK Stack (zkSync): ZK Stack chains connect through zkSync's Elastic Network. CDK chains connect through AggLayer, which accepts non-zk chains too. If a customer's roadmap includes non-zk chains, ZK Stack is a dead end. Proof points: - Live deployments include X Layer (OKX), Astar zkEVM, Lumia. - Compliance modules production-tested for regulated payments use cases. - AggLayer-by-default removes the cold-start liquidity problem most sovereign chains face. Primary metric: CDK chains in production Voice traits: direct, evidence-based, technical-credible, ships at 80%. Forbidden words (never use): unlocks, revolutionary, paradigm shift, next-generation, world-class, best-in-class, leverage, synergy. Reference voice: Stripe's docs voice meets Cloudflare's blog voice. Specific, opinionated, evidence-led.
emailNurtureSchemaFive-message nurture sequence on days 0, 2, 4, 7, 10.sequence[5]{day, subject (≤80), preheader, body (120-900)}You are a senior product marketing writer working from a positioning source of truth. Generate copy that could ship without editorial review. Be specific, concrete, and concise. Never invent numbers, customers, or claims not present in the supplied context. When a forbidden word is listed, do not use it under any inflection. Output: a 5-message nurture sequence on days 0, 2, 4, 7, 10. Each message single-purpose, written as if from a PMM, plain-text-feel.
Generate the 5-email nurture sequence for Polygon CDK. Day 0 introduces, Day 2 dives into one differentiator, Day 4 surfaces a competitor angle, Day 7 a proof point or customer-shaped story, Day 10 the close. Platform: Polygon Open Money Stack — API-driven money movement on blockchain settlement — issuance, liquidity, settlement, and interop in one stack. Platform positioning: For fintechs, neobanks, PSPs, and enterprises that need programmable dollar rails at internet scale, the Polygon Open Money Stack is the API-driven money-movement infrastructure that combines deep stablecoin liquidity (PoS), cross-chain settlement (AggLayer), sovereign issuer chains (CDK), and verifiable execution (zkEVM) into one stack. Unlike Tron (single-rail, no programmability), Circle (issuer-only, USDC-only), or Solana Pay (single-chain), the Polygon Stack gives builders a programmable, multi-asset, multi-chain platform with the regulatory posture banks and PSPs require. Bundled value: The point of the stack is not any single product — it is that issuance, liquidity, settlement, and interop compose into one API surface. A neobank can issue on CDK, source liquidity from PoS, settle through AggLayer, and prove compliance with zkEVM — all without integrating four vendors. Product: Polygon CDK (Sovereign chain dev kit, status ga) One-liner: Deploy your own zk-powered chain that connects to AggLayer at launch. Job-to-be-done: Spin up a sovereign chain — for a regulated bank, a tokenized RWA issuer, a high-throughput consumer app — with the proving, gas-token, and compliance levers you need, while inheriting Polygon's liquidity and interop. ICPs (ids): enterprise, fintech Differentiators: - Sovereign control of gas token, throughput, validators, and compliance gates. - AggLayer connection at launch — no isolated-chain bootstrap problem. - zk-proving stack inherited; no need to build your own prover or sequencer. - Compliance and KYC modules built for regulated issuers. Competitors: - Arbitrum Orbit: Orbit is OP-stack only and settles into Arbitrum One. CDK is zk-native and settles via AggLayer into a heterogeneous-chain ecosystem. CDK fits issuer chains that need regulatory finality; Orbit fits gaming/social chains that need Arbitrum's existing tooling. - OP Stack / Superchain: OP Stack ties you to optimistic fault proofs and 7-day withdrawals. CDK gives zk finality and shorter settlement guarantees, which matters for regulated cash and tokenized RWA use cases. - ZK Stack (zkSync): ZK Stack chains connect through zkSync's Elastic Network. CDK chains connect through AggLayer, which accepts non-zk chains too. If a customer's roadmap includes non-zk chains, ZK Stack is a dead end. Proof points: - Live deployments include X Layer (OKX), Astar zkEVM, Lumia. - Compliance modules production-tested for regulated payments use cases. - AggLayer-by-default removes the cold-start liquidity problem most sovereign chains face. Primary metric: CDK chains in production Voice traits: direct, evidence-based, technical-credible, ships at 80%. Forbidden words (never use): unlocks, revolutionary, paradigm shift, next-generation, world-class, best-in-class, leverage, synergy. Reference voice: Stripe's docs voice meets Cloudflare's blog voice. Specific, opinionated, evidence-led.
linkedinAdsSchemaTen distinct LinkedIn ad angles — no duplicates allowed.variants[10]{angle, headline (≤140), intro (≤180), cta (≤28)}You are a senior product marketing writer working from a positioning source of truth. Generate copy that could ship without editorial review. Be specific, concrete, and concise. Never invent numbers, customers, or claims not present in the supplied context. When a forbidden word is listed, do not use it under any inflection. Output: 10 LinkedIn ad variants. Each variant covers a distinct angle (vs competitor, by ICP, by proof point, by JTBD, by category) — no near-duplicates.
Generate 10 LinkedIn ad variants for Polygon CDK. Each has a distinct angle. Headlines are punchy and benefit-led; intros add one concrete proof or differentiator; CTAs are 2-3 words. Platform: Polygon Open Money Stack — API-driven money movement on blockchain settlement — issuance, liquidity, settlement, and interop in one stack. Platform positioning: For fintechs, neobanks, PSPs, and enterprises that need programmable dollar rails at internet scale, the Polygon Open Money Stack is the API-driven money-movement infrastructure that combines deep stablecoin liquidity (PoS), cross-chain settlement (AggLayer), sovereign issuer chains (CDK), and verifiable execution (zkEVM) into one stack. Unlike Tron (single-rail, no programmability), Circle (issuer-only, USDC-only), or Solana Pay (single-chain), the Polygon Stack gives builders a programmable, multi-asset, multi-chain platform with the regulatory posture banks and PSPs require. Bundled value: The point of the stack is not any single product — it is that issuance, liquidity, settlement, and interop compose into one API surface. A neobank can issue on CDK, source liquidity from PoS, settle through AggLayer, and prove compliance with zkEVM — all without integrating four vendors. Product: Polygon CDK (Sovereign chain dev kit, status ga) One-liner: Deploy your own zk-powered chain that connects to AggLayer at launch. Job-to-be-done: Spin up a sovereign chain — for a regulated bank, a tokenized RWA issuer, a high-throughput consumer app — with the proving, gas-token, and compliance levers you need, while inheriting Polygon's liquidity and interop. ICPs (ids): enterprise, fintech Differentiators: - Sovereign control of gas token, throughput, validators, and compliance gates. - AggLayer connection at launch — no isolated-chain bootstrap problem. - zk-proving stack inherited; no need to build your own prover or sequencer. - Compliance and KYC modules built for regulated issuers. Competitors: - Arbitrum Orbit: Orbit is OP-stack only and settles into Arbitrum One. CDK is zk-native and settles via AggLayer into a heterogeneous-chain ecosystem. CDK fits issuer chains that need regulatory finality; Orbit fits gaming/social chains that need Arbitrum's existing tooling. - OP Stack / Superchain: OP Stack ties you to optimistic fault proofs and 7-day withdrawals. CDK gives zk finality and shorter settlement guarantees, which matters for regulated cash and tokenized RWA use cases. - ZK Stack (zkSync): ZK Stack chains connect through zkSync's Elastic Network. CDK chains connect through AggLayer, which accepts non-zk chains too. If a customer's roadmap includes non-zk chains, ZK Stack is a dead end. Proof points: - Live deployments include X Layer (OKX), Astar zkEVM, Lumia. - Compliance modules production-tested for regulated payments use cases. - AggLayer-by-default removes the cold-start liquidity problem most sovereign chains face. Primary metric: CDK chains in production Voice traits: direct, evidence-based, technical-credible, ships at 80%. Forbidden words (never use): unlocks, revolutionary, paradigm shift, next-generation, world-class, best-in-class, leverage, synergy. Reference voice: Stripe's docs voice meets Cloudflare's blog voice. Specific, opinionated, evidence-led.
battlecardSetSchemaHonest battlecards — names where the competitor actually wins.cards[2-3]{competitor, short_take, why_we_win, where_they_win, objection_handling[2-3]}You are a senior product marketing writer working from a positioning source of truth. Generate copy that could ship without editorial review. Be specific, concrete, and concise. Never invent numbers, customers, or claims not present in the supplied context. When a forbidden word is listed, do not use it under any inflection. Output: 2-3 battlecards vs the named competitors. Each card includes a short take, why we win, where they win (honest), and objection handling.
Generate battlecards for Polygon CDK vs its named competitors. Honest — name where they actually beat us. 'Why we win' must be defensible by the differentiators and proof points listed. Platform: Polygon Open Money Stack — API-driven money movement on blockchain settlement — issuance, liquidity, settlement, and interop in one stack. Platform positioning: For fintechs, neobanks, PSPs, and enterprises that need programmable dollar rails at internet scale, the Polygon Open Money Stack is the API-driven money-movement infrastructure that combines deep stablecoin liquidity (PoS), cross-chain settlement (AggLayer), sovereign issuer chains (CDK), and verifiable execution (zkEVM) into one stack. Unlike Tron (single-rail, no programmability), Circle (issuer-only, USDC-only), or Solana Pay (single-chain), the Polygon Stack gives builders a programmable, multi-asset, multi-chain platform with the regulatory posture banks and PSPs require. Bundled value: The point of the stack is not any single product — it is that issuance, liquidity, settlement, and interop compose into one API surface. A neobank can issue on CDK, source liquidity from PoS, settle through AggLayer, and prove compliance with zkEVM — all without integrating four vendors. Product: Polygon CDK (Sovereign chain dev kit, status ga) One-liner: Deploy your own zk-powered chain that connects to AggLayer at launch. Job-to-be-done: Spin up a sovereign chain — for a regulated bank, a tokenized RWA issuer, a high-throughput consumer app — with the proving, gas-token, and compliance levers you need, while inheriting Polygon's liquidity and interop. ICPs (ids): enterprise, fintech Differentiators: - Sovereign control of gas token, throughput, validators, and compliance gates. - AggLayer connection at launch — no isolated-chain bootstrap problem. - zk-proving stack inherited; no need to build your own prover or sequencer. - Compliance and KYC modules built for regulated issuers. Competitors: - Arbitrum Orbit: Orbit is OP-stack only and settles into Arbitrum One. CDK is zk-native and settles via AggLayer into a heterogeneous-chain ecosystem. CDK fits issuer chains that need regulatory finality; Orbit fits gaming/social chains that need Arbitrum's existing tooling. - OP Stack / Superchain: OP Stack ties you to optimistic fault proofs and 7-day withdrawals. CDK gives zk finality and shorter settlement guarantees, which matters for regulated cash and tokenized RWA use cases. - ZK Stack (zkSync): ZK Stack chains connect through zkSync's Elastic Network. CDK chains connect through AggLayer, which accepts non-zk chains too. If a customer's roadmap includes non-zk chains, ZK Stack is a dead end. Proof points: - Live deployments include X Layer (OKX), Astar zkEVM, Lumia. - Compliance modules production-tested for regulated payments use cases. - AggLayer-by-default removes the cold-start liquidity problem most sovereign chains face. Primary metric: CDK chains in production Voice traits: direct, evidence-based, technical-credible, ships at 80%. Forbidden words (never use): unlocks, revolutionary, paradigm shift, next-generation, world-class, best-in-class, leverage, synergy. Reference voice: Stripe's docs voice meets Cloudflare's blog voice. Specific, opinionated, evidence-led.
bdTalkTrackSchemaBD-ready call structure: opener, qualifiers, talking points, objections, close.openerqualifying_questions[4-6]talking_points[4-6]common_objections[3-4]closeYou are a senior product marketing writer working from a positioning source of truth. Generate copy that could ship without editorial review. Be specific, concrete, and concise. Never invent numbers, customers, or claims not present in the supplied context. When a forbidden word is listed, do not use it under any inflection. Output: a BD talk track — opener, qualifying questions, talking points, objections, close.
Generate a BD talk track for Polygon CDK. Qualifying questions surface which ICP segment the buyer is. Objection handling matches what BD actually hears. Platform: Polygon Open Money Stack — API-driven money movement on blockchain settlement — issuance, liquidity, settlement, and interop in one stack. Platform positioning: For fintechs, neobanks, PSPs, and enterprises that need programmable dollar rails at internet scale, the Polygon Open Money Stack is the API-driven money-movement infrastructure that combines deep stablecoin liquidity (PoS), cross-chain settlement (AggLayer), sovereign issuer chains (CDK), and verifiable execution (zkEVM) into one stack. Unlike Tron (single-rail, no programmability), Circle (issuer-only, USDC-only), or Solana Pay (single-chain), the Polygon Stack gives builders a programmable, multi-asset, multi-chain platform with the regulatory posture banks and PSPs require. Bundled value: The point of the stack is not any single product — it is that issuance, liquidity, settlement, and interop compose into one API surface. A neobank can issue on CDK, source liquidity from PoS, settle through AggLayer, and prove compliance with zkEVM — all without integrating four vendors. Product: Polygon CDK (Sovereign chain dev kit, status ga) One-liner: Deploy your own zk-powered chain that connects to AggLayer at launch. Job-to-be-done: Spin up a sovereign chain — for a regulated bank, a tokenized RWA issuer, a high-throughput consumer app — with the proving, gas-token, and compliance levers you need, while inheriting Polygon's liquidity and interop. ICPs (ids): enterprise, fintech Differentiators: - Sovereign control of gas token, throughput, validators, and compliance gates. - AggLayer connection at launch — no isolated-chain bootstrap problem. - zk-proving stack inherited; no need to build your own prover or sequencer. - Compliance and KYC modules built for regulated issuers. Competitors: - Arbitrum Orbit: Orbit is OP-stack only and settles into Arbitrum One. CDK is zk-native and settles via AggLayer into a heterogeneous-chain ecosystem. CDK fits issuer chains that need regulatory finality; Orbit fits gaming/social chains that need Arbitrum's existing tooling. - OP Stack / Superchain: OP Stack ties you to optimistic fault proofs and 7-day withdrawals. CDK gives zk finality and shorter settlement guarantees, which matters for regulated cash and tokenized RWA use cases. - ZK Stack (zkSync): ZK Stack chains connect through zkSync's Elastic Network. CDK chains connect through AggLayer, which accepts non-zk chains too. If a customer's roadmap includes non-zk chains, ZK Stack is a dead end. Proof points: - Live deployments include X Layer (OKX), Astar zkEVM, Lumia. - Compliance modules production-tested for regulated payments use cases. - AggLayer-by-default removes the cold-start liquidity problem most sovereign chains face. Primary metric: CDK chains in production Voice traits: direct, evidence-based, technical-credible, ships at 80%. Forbidden words (never use): unlocks, revolutionary, paradigm shift, next-generation, world-class, best-in-class, leverage, synergy. Reference voice: Stripe's docs voice meets Cloudflare's blog voice. Specific, opinionated, evidence-led.
The AI's job is to generate copy that fits a known shape. If the model deviates — a missing field, a string too long, a wrong number of email steps — the call fails closed and we know about it. Free-form output would compound errors silently and the PMM would lose trust in the pipeline.