Prompt 641 words Copy
# Design from Reference: Pivot Use Cases
Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.
## Reference
- **Product:** Pivot
- **Category:** Use Cases
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/b987f8fa841c0e259155-1600.webp)
- **Source:** https://www.pivotapp.ai/solutions/finance
Analyze the attached screenshot first. If no image is attached, open the screenshot link; if neither is accessible, ask for it rather than guessing.
## Visual Design Context
### Overall aesthetic
- **Character:** Pivot's enterprise minimalism tuned for an executive audience: photographic hero with gradient wash, white problem cards, dark teal bands and big numbers.
### Page composition
- **Capture:** 2880 × 18290 screenshot pixels; 2× CSS scale (1440px viewport).
- **Structure:** Full-bleed photo hero with floating chips and role switcher; logo marquee; three problem cards with UI snippets; dark split band with workflow diagram; photo and copy split; four metric tiles; angled gradient into a dark AI section with prompt and orb; three role photo cards; FAQ; closing statement; gradient footer.
### Information hierarchy
- **Priority:** Role-specific promise, finance pains, the connected record, outcomes, AI agent, then other stakeholders and objections.
### Typography
- **Families:** Roobert for headings, DM Sans for body.
- **CSS scale:** Hero 40px white centered, section headings 28–32px, metrics 40px, card titles 13px semibold, body 12–14px.
### Colors & surfaces
- **Palette:** Page #FAFAFA, dark #011515, cards #FFFFFF and #F4F4F4.
- **Accents:** Lime and teal photo wash, gradient wedge, glowing orb, mint chips.
### Components
- **Elements:** Role dropdown chip, floating feature chips, problem cards with mini UI, workflow node diagram, metric tiles, prompt bar, role photo cards with captions, FAQ accordion.
- **Geometry:** Content about 1140px wide, 3- and 4-column grids, 12px radii.
### Responsive
- **Mobile capture:** Chips hide around the hero, cards and metric tiles stack, role cards go one per row.
### Adaptation guidance
- **Transfer:** Build role pages around that role's inherited pain, one proof band of numbers and a nod to the rest of the buying committee. Add a role switcher to link sibling pages.
## Content
**Instructions:**
Generate realistic example content that fits the selected design reference.
Create appropriate headlines, descriptions, labels, buttons, and supporting copy based on the type of interface being designed.
If a product or business description is provided, use it to guide the content.
Otherwise, invent a plausible fictional SaaS product appropriate for the reference.
Keep the content concise, coherent, and visually balanced.
Do not present fictional statistics, customer names, or testimonials as verified facts.
## Design Direction
**Instructions:**
Use the reference screenshot as the main source of visual inspiration rather than a strict layout template.
Preserve its most distinctive design characteristics, such as typography, visual rhythm, color relationships, component treatments, and overall aesthetic.
Feel free to modify section arrangements, proportions, spacing, and individual components to better suit my content.
Introduce original design decisions where they improve usability, composition, or brand consistency.
The result should clearly reflect the reference's visual language without looking like a direct reproduction.
Follow the visual identity of the reference design.
Use its typography, color palette, component styling, and overall aesthetic as the primary design direction.
Do not introduce an unrelated visual identity.
## Output
**Instructions:**
Generate a high-fidelity visual mockup of the requested interface.
Present the design as a polished, realistic website or product UI screenshot.
Prioritize visual composition, typography, spacing, colors, alignment, and component details.
Use the available image-generation or visual-design capabilities.
Do not replace the mockup with source code, a written design specification, or a textual description.
If direct visual generation is unavailable, clearly explain the limitation.
## Constraints
- Use the actual screenshot as the primary visual reference.
- Preserve essential messaging and factual accuracy.
- Prioritize visual quality and consistency.
- Do not invent unsupported product claims.
- Adapt structure and copy length for visual balance. Reference image Attach it to your message: assistants can’t open image links. Open in ChatGPT ↗ Open in Claude ↗
Build it in Lovable ↗ v0 ↗ Figma Make ↗
Opening a tool copies the screenshot so you can paste it with your prompt.
SaaSFrame
