Clean Gradient System for SaaS

You are a senior product designer and frontend prototyper designing Clean Gradient System for SaaS.
Create the product concept itself, not a meta prompt, placeholder wireframe, or generic SaaS template.

Goal:
Create a high-fidelity visual system prototype for gradient system that feels clean, credible, and ready for a senior product designer to refine.

Layout requirements:
- Start with the primary user goal and make the first viewport immediately useful.
- Name the product and make its core offer obvious in the first screen.
- Use real product copy, clear hierarchy, and specific interface details instead of placeholder text.
- Define the main sections, controls, cards, tables, or screens needed for the concept.
- Keep spacing, typography, and component density appropriate for a real web or mobile product.
- Invent one plausible product name, target user, and primary job-to-be-done before choosing layout.
- Make the first viewport a usable product surface, not a generic hero or decorative mockup.
- Include realistic domain copy, sample data, labels, prices, metrics, commands, tokens, messages, or records where the interface needs them.
- Specify the actual controls the user can operate and the state changes each control should trigger.
- Define one signature visual or interaction that could only belong to this product concept.
- Before finalizing, compare the direction against generic SaaS defaults such as text-left/mockup-right heroes, dashboard sidebars, repeated rounded cards, one-color gradients, and vague AI glow effects; revise anything that feels generic.
- For visual systems, show token names, swatches, usage counts, contrast guidance, selected states, copy/export affordances, and a right-side or bottom inspector.

Visual direction:
- Style: clean.
- Category: Gradients and Visual Systems.
- Industry context: SaaS.
- Choose one restrained visual system with a named type scale, one strong accent, and accessible contrast.
- Use purposeful layout composition, distinctive product details, intentional typography, and clear visual rhythm instead of repeated rounded cards.
- Use media only when it makes the product more concrete: royalty-free stock images or video, generated bitmap assets, canvas/WebGL motion, or CSS/SVG animation are all acceptable if they serve the concept.
- Avoid generic stock filler, decorative clutter, vague AI-themed effects, copyrighted logos, and fake image placeholders.

Interaction and responsive notes:
- Include selected, hover, disabled, loading, success, error, and empty states where relevant.
- Describe or implement what changes when primary controls are used.
- Explain how the layout adapts from desktop to mobile without losing the primary action.
- Keep the output focused, copy-ready, and practical for a first-pass design.
- Respect reduced-motion needs for animation-heavy concepts.

Output format:
- If the tool can output code, return one complete standalone responsive HTML prototype with internal CSS and JavaScript.
- If the prototype is being generated for this site, include one unobtrusive link back to the source prompt detail page.
- If the tool cannot output code, return a structured design brief with sections for purpose, layout, visual system, interaction states, responsive behavior, and implementation constraints.
- If media is used, include descriptive alt text, loading/fallback behavior, and only use assets that are free to display or generated specifically for the concept.
- Do not include lorem ipsum, placeholder screenshots, fake image boxes, or explanatory text outside the designed experience.