no payment requirednone
Factory
Leave with a stack recommendation and a Claude Code skill export.
success
/factory
buyer receives
- On-page stack result
- Downloadable Claude Code skill file
Checkout map
Checkout should open a delivery packet, not a dead-end receipt.
This is the revenue control room: provider status, product ID env keys, success redirect targets, delivery artifacts, analytics events, and launch blockers for every GenCreator offer.
Selected checkout contract
Activation Engine
statusno payment required
buy resolver/activate
success route/activate
fulfillment api/api/products/fulfillment?product=activation-engine
analytics eventactivation_engine_started
product id envnot required
checkout url envnot required
Product checkout contracts
Every product needs a payment event, success route, and delivery artifact.
The route does not pretend checkout is live. It names exactly what is missing so Whop, Stripe, delivery email, and analytics can be wired without ambiguity.
no payment requirednone
Creation Engine
Leave with a usable creation packet, assistant prompt, approval path, and next product or community handoff.
success
/create
buyer receives
- Creation packet
- Markdown export
- Assistant prompt
- MCP plan
no payment requirednone
Activation Engine
Leave with the next seven operating moves, exportable markdown, assistant prompt, and the exact route into product, community, or Studio.
success
/activate
buyer receives
- Seven-day activation plan
- Markdown export
- Assistant prompt
- Product path
no payment requirednone
Self-Serve Kit Composer
Leave with a markdown or JSON kit that routes the creator into the right product, community review, and assistant prompt.
success
/products/kit
buyer receives
- Generated kit
- Markdown export
- Assistant prompt
- MCP resource list
no payment requirednone
Skill Pack Library
Download one skill file, read the right MCP resources, and produce one artifact or approval record in the first sitting.
success
/products/skill-packs
buyer receives
- Skill files
- Prompt contracts
- MCP resources
- Education lessons
no payment requirednone
Creator OS Contract
Understand the exact sequence to diagnose, package, install, operate, practice, orchestrate, and add human judgment.
success
/products/creator-os
buyer receives
- Brand primitives
- Product sequence
- Diagnostics
- MCP resources
no payment requirednone
Brand Social System
Leave with logo rules, type decisions, platform formats, carousel and video shot systems, a social template sheet, and an MCP-ready packet generator.
success
/brand/social
buyer receives
- Logo rules
- Typography foundation
- Social format matrix
- Carousel systems
no payment requirednone
Creator Intelligence System
Leave with one routed operating packet that makes the scalable digital product, community path, and 1:1 boundary clear.
success
/intelligence
buyer receives
- Product decision
- Markdown export
- MCP plan
- Skill path
no payment requirednone
Product Offer System
Leave with a packaged offer that names the first artifact, proof required, checkout truth, support line, launch assets, and assistant prompt.
success
/products/offers
buyer receives
- Offer ladder
- Markdown export
- Delivery contract
- Launch assets
no payment requirednone
Creator Readiness Diagnostic
Leave with an operating score, weakest layer, product path, Eve prompt, MCP resources, and community handoff.
success
/products/diagnostic
buyer receives
- Operating score
- Weakest layer
- Product path
- Eve prompt
no payment requirednone
Learning Path Engine
Leave with modules, skill packs, MCP resources, product handoff, proof-loop entry, and a clear 1:1 escalation rule.
success
/learn
buyer receives
- Learning path
- Markdown export
- Skill pack path
- MCP plan
no payment requirednone
Community Proof Loop Engine
Leave with a community post draft, five-beat proof loop, stage handoff, MCP resources, and the next route.
success
/community/proof-loop
buyer receives
- Review request
- Weekly proof loop
- Community post draft
- Assistant prompt
no payment requirednone
Community OS
Leave with the room status, proof loop, pricing and offers route, membership blockers, assistant prompt, and Studio escalation rule.
success
/community/os
buyer receives
- Operating room state
- Markdown export
- Offer bridge
- GTM moves
no payment requirednone
Campaign Studio
Leave with a usable campaign packet, assistant prompt, draft-only schedule payload, and a clear review question.
success
/campaigns
buyer receives
- Campaign packet
- Markdown export
- Assistant prompt
- Approval task
needs provider productWhop
Creator Vault Kit
Fill one vault row, one proof row, and one approval rule in under ten minutes.
success
/products/checkout/success?product=creator-vault-kit
buyer receives
- Vault schema
- Voice rule worksheet
- Offer map
- Proof table
needs provider productWhop
Campaign Pack System
Turn one signal into a short approval-safe campaign brief before opening a scheduler.
success
/products/checkout/success?product=campaign-pack-system
buyer receives
- Signal intake
- Campaign brief
- Platform drafts
- Reply bank
needs provider productWhop
Agent and MCP Pack
Give an assistant the GenCreator role, safety modes, tool map, and first approval task.
success
/products/checkout/success?product=agent-mcp-pack
buyer receives
- Assistant role
- Tool modes
- MCP endpoint
- Install bundle
plannedWhop
GenCreator.community
Enter with one artifact, one question, one weekly proof loop, and the room state that routes pricing, offers, and Studio.
success
/products/checkout/success?product=gencreator-community
buyer receives
- Community OS packet
- Weekly proof loop
- Source pulse ritual
- Review thread entry
plannedapplication
Studio
Get a review path for the offer, campaign, and agent workflow already in motion.
success
/create
buyer receives
- Creator Mission entry
- No application or payment implied
Selected fulfillment path
Buyers should know what happens after payment.
The success route can be used as the redirect target for Whop products later. Until provider products exist, it stays an honest preview of delivery.
Step 1Start from a creation packet
Step 2Choose the audience and constraint
Step 3Generate the activation plan
Step 4Export markdown or JSON
Step 5Route into product, community, or Studio