← Previous15 / 28Next →

Attio Sync Email And Calendar

AttioCustomer relationship magic

Design with AI

Create a new design inspired by Attio Sync Email And Calendar, 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 974 words

# Design from Reference: Attio Sync Email And Calendar

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

## Reference

- **Product:** Attio
- **Category:** Account Setup
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/o/edb3d9da8f9f7d14eac5.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 restrained onboarding screen combines a white setup form with a pale illustrative data-flow panel.
- **Accent:** Bright blue connection buttons and a blue-outlined selected sharing option establish the active path.

### Page composition

- **Capture:** The source is 1440 × 821 pixels. Dimensions below approximate image pixels; CSS scale is unverified.
- **Frame:** A centered approximately 1130 × 690-pixel rounded panel sits beneath the Attio logo.
- **Left half:** Step 3/5, heading, explanation and three checkmarked benefits precede two sharing choices, provider buttons and a skip link.
- **Right half:** A gray diagram combines email/calendar and enrichment pills with connecting lines above a cropped contact-table illustration.
- **Footer:** Small copyright, privacy, support and sign-out links sit below the frame.

### Information hierarchy

- **Progress and task:** A small step indicator leads into a bold email/calendar synchronization heading.
- **Sharing choice:** A blue-outlined top option is selected; the second option remains neutral beneath it.
- **Connection actions:** Two equally prominent blue buttons offer Google and Microsoft, followed by a subdued continue-without-sync link.
- **Illustration:** The right panel explains enrichment visually without adding another competing form.

### Typography

- **Family:** A clean sans serif is used; exact identity is unverified.
- **Heading:** Approximately 20–22 pixels, bold with compact leading.
- **Reading text:** Explanatory copy and benefits are around 14 pixels with 20–22-pixel leading.
- **Options:** Titles are approximately 14 pixels and medium weight; smaller muted descriptions use around 12 pixels.
- **Actions/utilities:** Provider labels are around 14 pixels; footer links and step indicator are approximately 12 pixels.

### Colors & surfaces

- **Measured foundation:** White #FFFFFF forms the form/frame, while #EFEFEF supports the illustration background.
- **Measured selected surface:** Very pale blue #F6F9FE fills the selected option.
- **Measured action:** Blue #1977E6 appears in the provider-action palette.
- **Measured neutral:** #F0F0F0 and nearby #FDFDFD contribute subtle illustration/table surfaces.
- **Contrast relationship:** Dark headings and gray descriptions remain quieter than the blue actions and selection boundary.

### Components

- **Outer panel:** A fine light-gray border and approximately 20-pixel corner radius enclose two equal-width regions.
- **Sharing options:** Two stacked rows form a roughly 360-pixel-wide group; the selected upper row has a blue outline, pale fill and small descriptive icon.
- **Provider buttons:** Approximately 360 × 36 pixels, blue with white text, small branded marks and a subtle shadow.
- **Flow diagram:** Rounded white pills and small circular plus/down controls connect vertically, ending in branching lines toward the contact table.
- **Table illustration:** A partially cropped white grid includes muted placeholder rows, a few names/role/location examples and small toolbar pills.

### Visual rhythm

- **Left inset:** About 95 pixels separates the form content from the panel's left edge.
- **Grouping:** Benefits sit close to the introductory copy; larger gaps separate choice group, provider buttons and skip link.
- **Balance:** The diagram occupies the upper right while the table fills its lower half, balancing the left column's vertical stack.

### Responsive

- **Observed state:** Only a desktop split panel is supplied; mobile behavior is unverified.
- **Recommended flow:** Stack or hide the explanatory illustration before narrowing the choice and provider controls.
- **Recommended text:** Let sharing descriptions wrap without fixed-height clipping and retain clear selected-state borders.

### Adaptation guidance

- **Preserve decision order:** Explain benefits, present sharing scope and then offer provider connection.
- **Keep options explicit:** Maintain visible descriptions for both sharing levels rather than relying only on icons.
- **State fidelity:** Reproduce the selected top option and step indicator without inferring connection success or data-sharing behavior.
- **Accessibility:** Use labeled selection semantics, visible focus and provider-specific accessible action names.

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