public routed page
3D Dream Revenue MVP
Turn a dream-world idea into a premium-ready SEELE experience.
This page is the first public shell for the PRD: a conversion-focused surface that explains the fantasy, frames the value, and pushes the user into the upgrade path with minimal friction.
3D-first conceptUpgradeable flowConversion-oriented shellFeature preview ready
Current branch status
Testable landing shell ready for reviewconversion flow steps
cross-worker upgrade CTA
Why now
The concept needs a reviewable surface before it needs more words.
The PRD already defines the direction. What was missing was a branch environment with a concrete public page, so discussion can happen on structure, offer, and user motion instead of on abstract descriptions.
A visual fantasy sells faster than a spec sheet
The landing page should make the dream concrete in seconds: emotional hook first, mechanics second, upgrade path third.
The route to payment must be obvious
Readers should understand what they get for free, what premium unlocks, and where to go next without searching across the product.
Public traffic needs a stable shell
This page gives the PRD a branch environment and a testable public surface, so review can happen on something real instead of on text alone.
Flow
A simple path from fantasy to monetization
The landing flow is deliberately short: hook the imagination, preview the transformed result, then hand off to the upgrade surface without burying the value proposition under filler copy.
Imagine the scene
Lead with a short prompt-like fantasy: the user pictures a dream world, character, or story hook immediately.
Preview the transformation
Show the promise of turning that idea into a polished interactive output instead of leaving it as a vague creative concept.
Upgrade to unlock the full experience
Drive to the premium path with a clear CTA that explains the value exchange rather than hiding the revenue step.
Revenue logic
The upgrade step is part of the product story
This MVP does not pretend the monetization layer is separate. The page is built so acquisition, product value, and premium conversion read as one continuous narrative.
Fast emotional hook
A landing page built to stop the scroll and frame the offer before the user starts comparing tools.
Clear premium handoff
The upgrade path is treated as part of the experience, not as a disconnected afterthought.
Reviewable test branch
Product, design, and growth can now evaluate the concept in a feature-preview environment.
FAQ
Answers for the current branch phase
Enough detail for product review now, without overclaiming unfinished backend or payment work.
Is this already the full 3D Dream product?
No. This pass creates the first conversion-oriented public shell, not the full generation or payment system.
Why place it in apps/site instead of apps/web?
Because the current ask is a public-facing acquisition and conversion surface. The actual upgrade experience can still live in the web app.
Why does the CTA use a plain link?
Because `/upgrade` belongs to a different runtime surface. A full-page navigation is the safe path for branch preview and deployment.