Prompt 659 words Copy
# Design from Reference: Pivot Partners 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:** Partners Page
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/e8d60f577ab6e42bf362-1600.webp)
- **Source:** https://www.pivotapp.ai/company/partners
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: off-white canvas, glowing lime-to-cyan orb, crisp white logo chips, then a motion-blurred photographic band carrying the form.
### Page composition
- **Capture:** 2880 × 8912 screenshot pixels; 2× CSS scale (1440px viewport).
- **Structure:** Centered hero with badge, headline, intro and an orb surrounded by four partner logo chips; "Ways to partner" with three tall cards; "Why teams partner" with three outlined benefit cards; full-bleed photo band with copy left and a white form card right; gradient footer.
### Information hierarchy
- **Priority:** Invitation and ecosystem visual, partner types for self-selection, benefits, then the application form.
### Typography
- **Families:** Roobert for headings, DM Sans for body.
- **CSS scale:** Hero 44px centered, section headings 32px, card titles 14px semibold, body 12–14px, form placeholders 11px.
### Colors & surfaces
- **Palette:** Page #FAFAFA, cards #FFFFFF and #F4F4F4, dark card photographic teal, text #060609 and #464646.
- **Accents:** Gradient orb, lime and mint gradient card, lime #F0FF00 Submit button, gradient-dot badges.
### Components
- **Elements:** Floating logo chips, three partner-type cards with mini visuals (logo cluster, referral flow, project UI), outlined benefit cards with small gradient icons, form card with two-column rounded inputs, select field, textarea and consent line.
- **Geometry:** Content about 1140px wide, cards about 270px wide and 330px tall, radii 8–12px, form card about 380px wide.
### Responsive
- **Mobile capture:** Logo chips tuck around the orb, cards stack, form fields go single column under the copy.
### Adaptation guidance
- **Transfer:** Show your ecosystem visually in the hero, give each partner type its own card style and end with a form that asks for the partner type context. Use real partner logos only with permission.
## 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.