Prompt 657 words Copy
# Design from Reference: Pivot About Page
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:** About Page
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/7d7c8fbc2874278dfd7e-1600.webp)
- **Source:** https://www.pivotapp.ai/company/about-us
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:** Editorial, people-first version of Pivot's enterprise minimalism: off-white canvas, generous whitespace, the signature lime-to-cyan gradient used only as soft halos, and photography carrying the emotion.
### Page composition
- **Capture:** 2880 × 21898 screenshot pixels; 2× CSS scale (1440px viewport).
- **Structure:** Centered hero with gradient halo and black pill CTA, full-width rounded video block, marquee of customer logos, large two-tone statement, founding story in a narrow centered column flanked by two tilted photos, mission section, four stat tiles, Series B split card (photo left, copy right), three investor logo tiles, 3-column leadership portrait grid, "Join our team" CTA, press card carousel, closing statement and gradient footer.
### Information hierarchy
- **Priority:** Each band opens with a small green-dot pill label (Our story, Mission and vision, Investors, Leadership Team, Resources) above a medium-weight heading; long-form copy is centered and narrow to read like an article.
### Typography
- **Families:** Geometric grotesk for headings, neutral sans for body (declared in CSS as Roobert and DM Sans).
- **CSS scale:** Hero 56px, section headings 40px and 32px, stat numbers 48px, body 16px, labels 12px; headings medium weight, tight tracking.
### Colors & surfaces
- **Palette:** Page #FAFAFA, text near-black #0B0B0B, secondary gray #6B6B6B, accent gradient lime #D8F64A to cyan #3EE6D2, black pill buttons.
- **Surfaces:** White cards with 8px radius and hairline borders for stats, investors and press; portraits on a dark teal-black studio background for a uniform grid.
### Components & patterns
- Pill section labels with a gradient dot, black and outline pill buttons, stat tiles with a large number and small caption, logo marquee, portrait cards with LinkedIn link, press cards with publication logo and headline, carousel arrows.
## 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
