Prompt 644 words Copy
# Design from Reference: Pivot Customer Story
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:** Customer Stories
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/c875e89c93b9211e09ee-1600.webp)
- **Source:** https://www.pivotapp.ai/customers/pennylane
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:** Clean editorial reading layout on white, with pale yellow quote callouts and one dark sticky CTA card as the only heavy element.
### Page composition
- **Capture:** 2880 × 11222 screenshot pixels; 2× CSS scale (1440px viewport).
- **Structure:** Breadcrumb; gray hero with tags and headline left, photo right; three-column body (customer rail left, article centre, sticky CTA right); four H2 sections with bullets and quote callouts; "Keep exploring" row of three story cards; centered closing CTA; gradient footer.
### Information hierarchy
- **Priority:** Headline and photo, customer facts in the rail, then the narrative. Quotes are the most visually prominent body element.
### Typography
- **Families:** Roobert for headings, DM Sans for body.
- **CSS scale:** Hero headline 36px, H2 28px bold, body 14px with 1.6 line-height, rail labels 12px.
### Colors & surfaces
- **Palette:** Hero #F4F4F4, body #FFFFFF, text #060609 and #464646.
- **Accents:** Quote callouts in pale yellow #FBFBC9 with a bold attribution, lime and mint tag chips, black sticky card with outlined pill.
### Components
- **Elements:** Tag chips, customer fact list with value chips, social share icons, quote callouts, bulleted lists, sticky CTA card, story cards with big metrics.
- **Geometry:** Article column about 400px, rail about 200px, sticky card about 200px; 8–12px radii.
### Responsive
- **Mobile capture:** Rail moves above the article, sticky card becomes an inline block, story cards stack.
### Adaptation guidance
- **Transfer:** Keep a before / search / results / end structure, surface customer facts in a side rail and use coloured quote callouts for proof. Replace names, quotes and numbers with real ones.
## 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
