Prompt 636 words Copy
# Design from Reference: Pivot Integrations 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:** Integrations Page
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/effb9557edf0a3fc7fd5-1600.webp)
- **Source:** https://www.pivotapp.ai/platform/erp-integrations
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:** Bright and systematic: off-white canvas, floating app bubbles and a 3D isometric object in the hero, then a dark gradient band and a long, tidy logo directory.
### Page composition
- **Capture:** 2880 × 23508 screenshot pixels; 2× CSS scale (1440px viewport).
- **Structure:** Split hero (copy left, app icon bubbles right); differentiator split with isometric platform; angled lime-to-teal wedge into a dark band with three integration category cards; searchable directory grouped by category; FAQ; resource cards; closing statement; gradient footer.
### Information hierarchy
- **Priority:** Native ERP connection story first, grouped capabilities second, full directory last for evaluators who want to check their tools.
### Typography
- **Families:** Roobert for headings, DM Sans for body.
- **CSS scale:** Hero 40px, section headings 28–32px, category headings 18px, logo labels 10px, body 12–14px.
### Colors & surfaces
- **Palette:** Page #FAFAFA, dark band #011515, logo tiles #FFFFFF with hairline borders.
- **Accents:** Lime #F0FF00 bubble, mint and cyan 3D surfaces, full-width angled gradient wedge.
### Components
- **Elements:** Circular app bubbles, isometric 3D platform, category cards with mini UI previews and status chips, search input, square logo tiles in a 5-column grid, FAQ accordion.
- **Geometry:** Logo tiles about 60px square with 8px radius, directory 5 columns, category headings with 40px top spacing.
### Responsive
- **Mobile capture:** Directory goes to 3 columns, category cards stack, hero bubbles shrink beside the headline.
### Adaptation guidance
- **Transfer:** Pair a narrative section on why your integrations are different with a searchable, categorised logo directory. Only list integrations you really support.
## 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
