← Previous9 / 40Next →

Sellx Integrations

SellxSales engagement platform

Design with AI

Create a new design inspired by Sellx Integrations, with your own content.

1Content

2Fidelity to the reference

Keeps its visual language, rearranges freely around your content.

3Your brand Optional

Use the reference style

Brand nameColorsFontsGuidelines

4Output

Prompt 959 words

# Design from Reference: Sellx Integrations

Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.

## Reference

- **Product:** Sellx
- **Category:** Integrations
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/f6cbd5234db15dcd4b96-1600.webp)

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:** A spacious account-settings interface with pale blue-gray surroundings, white surfaces and restrained dark controls.
- **Brand distinction:** A large serif page heading contrasts with sans-serif navigation and integration cards.

### Page composition
- **Capture scale:** The source is 2880 × 2078 pixels. A roughly 1440 × 1039 CSS-pixel page at 2× scale is plausible but unverified.
- **Shell:** A narrow icon rail occupies the far left. A white account menu sits beside it, below the Manage Account heading.
- **Content panel:** A large rounded white surface at right contains an Integrations heading, short explanation and a request-integration control.
- **Grid:** Five integration cards form two columns and three rows, with the last card alone at left. A small chat launcher floats at bottom right.

### Information hierarchy
- **Page title:** Manage Account is the largest text, set in a bold serif.
- **Section:** Integrations is selected as a dark row in the account menu and repeated as the main panel heading.
- **Cards:** Each card presents a logo/icon, integration name, optional BETA label, short explanation and lower-right connection action.
- **Utilities:** Request integration sits alongside a small prompt at the panel's upper right, visually separate from the available integrations.

### Typography
- **Families:** The page heading uses a serif; the remaining interface uses a rounded sans serif. Exact identities are unverified.
- **Scale:** Page title is around 34 estimated CSS pixels, bold; section heading is about 24 pixels, medium weight.
- **Cards:** Integration names are around 16 pixels, semibold; descriptions and buttons are approximately 14 pixels with 21-pixel line height.
- **Metadata:** BETA and request-helper copy are around 11–12 pixels, muted.

### Colors & surfaces
- **Measured palette:** ICC-aware sRGB sampling yields white #FFFFFF, workspace #F3F7FB, pale action fill #E6ECF5 and dark text/selection #080F16.
- **Logo accents:** Orange, cyan and blue appear in partner logos while the surrounding cards remain neutral.
- **Edges:** Thin pale blue borders outline cards with roughly 12-pixel estimated CSS radii; the large panel and menu have similarly soft corners.

### Components
- **Account menu:** Icon-and-label rows use generous vertical spacing. Integrations is a near-black rounded selection; a divider precedes Log out.
- **Integration cards:** Roughly 435 × 234 estimated CSS pixels, with 32-pixel inner padding and a quiet bordered surface.
- **Available types:** Custom Email, HubSpot, Salesforce, Calendly and Chilipiper each have their own logo and description; two CRM entries show BETA markers.
- **Actions:** Pale blue rounded buttons combine a plus icon and explicit action label, aligned consistently near card bottoms.
- **Icon rail:** Monochrome navigation symbols, a notification count and avatar form a narrow persistent utility column.

### Visual rhythm
- **Grid:** Approximately 24-pixel gaps separate cards; headings and explanations share a common inset.
- **Whitespace:** Large blank areas inside cards separate descriptions from actions, making each connection path easy to scan.
- **Alignment:** Card title rows align horizontally despite varied logo shapes; action buttons share a lower-right anchor.

### Responsive
- **Recommendation:** Collapse the icon/account menus and stack integration cards into one column when two cards become too narrow.
- **Recommendation:** Let the request prompt wrap above the grid and retain comfortable button tap targets. No mobile state is shown.

### Adaptation guidance
- **Preserve:** Retain the serif page title, restrained pale workspace, consistent card structure and explicit connection labels.
- **Build:** Use one integration-card component supporting optional beta state and varied logos without shifting alignment.
- **Clarity:** Keep partner descriptions concise and use accessible labels for icon-only rail controls; connection behavior is not verified by the screenshot.

## 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 imageAttach it to your message: assistants can’t open image links.

Build it in

Opening a tool copies the screenshot so you can paste it with your prompt.