← Previous17 / 24Next →

Wiza Invite Team Members

WizaThe future of prospecting

Design with AI

Create a new design inspired by Wiza Invite Team Members, 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 849 words

# Design from Reference: Wiza Invite Team Members

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

## Reference

- **Product:** Wiza
- **Category:** Invite Team Members
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/1311fab3a30ceb8dc03c-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 team-management page is dimmed under a compact invitation modal, with white controls, slate copy and purple actions.
- **Evidence:** The original is 2880 × 1630 pixels. CSS dimensions assume an unverified 2× capture density.

### Page composition

- **Background:** Top navigation and credit indicators sit above a team table with search/filter, one member and pagination.
- **Modal:** A centered approximately 384 × 430-pixel panel contains title, explanation, role selector, permission hint, email text area and two bottom actions.
- **Utility:** A purple chat launcher remains visible in the lower-right corner.

### Information hierarchy

- **Invitation task:** Invite users is the modal heading, followed by confirmation-email guidance.
- **Role scope:** The selected User role precedes a muted information strip describing its permissions.
- **Recipients/action:** A populated text area sits above Go back and the purple Invite users action.

### Typography

- **Modal roles:** Heading is approximately 16 pixels semibold; explanatory copy, labels and field text are around 14 pixels with 20-pixel leading.
- **Actions:** Compact button labels are roughly 12–13 pixels semibold.
- **Identity:** A neutral sans-serif is visible; exact family is unverified.

### Colors & surfaces

- **Measured composite:** ICC-to-sRGB sampling identifies #8B91A1 as the dominant dimmed backdrop, with #898FA1 and #898F9F nearby variations.
- **Measured modal:** #FFFFFF defines the panel and #F7F8FA the supporting information strip.
- **Accents:** Vivid purple fills the primary action and chat button; slate text and pale outlines organize controls.
- **Depth:** The modal uses small radii and a pronounced soft lower shadow; backdrop colors are composites rather than base application tokens.

### Components

- **Role select:** Full-width rounded outlined control around 38 pixels tall with a right chevron.
- **Permission hint:** A pale strip includes an information icon and single-line explanation.
- **Recipients:** A roughly 336 × 98-pixel text area has a thin border, small radius and resize grip.
- **Actions:** Go back is a simple text control at left; Invite users is a compact purple button at right.

### Visual rhythm

- **Modal inset:** Approximately 24 pixels of padding align title, fields and actions.
- **Grouping:** The role label/select/hint form one cluster, separated from the recipient area by a modest gap.
- **Focus:** Overlay contrast keeps the team table subordinate.

### Responsive

- **Observed scope:** Only a desktop invitation state is visible; dropdown options and submission results are not shown.
- **Recommended layout:** Fit the modal within padded viewport bounds and allow vertical scrolling.
- **Recommended access:** Keep focus inside the dialog, label the recipient field and provide clear validation/confirmation feedback.

### Adaptation guidance

- **Invitation pattern:** Explain email delivery, show role permissions next to selection and separate recipients from final actions.
- **Content handling:** Use safe sample recipients rather than copying personal addresses.
- **Implementation:** Verify font/density and role definitions; describe this as a modal state without assuming an invitation has been sent.

## 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.