← Previous15 / 25Next →

SavvyCal Account Setup

SavvyCalScheduling Software Your Recipients Will Love

Design with AI

Create a new design inspired by SavvyCal Account Setup, 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 602 words

# Design from Reference: SavvyCal Account Setup

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

## Reference

- **Product:** SavvyCal
- **Category:** Account Setup
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/a27cb0f8ef6302fe9e91-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:** Minimal calendar-connection step with white canvas, dark navy type and compact blue controls.

### Page composition

- **Capture:** 2880 × 1642 screenshot pixels; estimated 2× CSS scale.
- **Structure:** Tiny logo upper left and progress indicator upper right; narrow centered content with Back chevron, title/help, connected account, calendar toggle list, add-account row and Next step.

### Information hierarchy

- **Priority:** Connect your calendars heading explains the goal. Account identity and per-calendar selection precede the primary progression action.

### Typography

- **Family:** Sans serif; exact family unverified.
- **Estimated CSS sizes:** Heading 32px, explanatory copy 16px, row labels 14px and action 14px.

### Colors & surfaces

- **Measured palette:** White #FFFFFF, blue #0065F4, dark navy #0F1828, rules #E3E7EB, off-state gray #99A3B0 and secondary text #495564.

### Components

- **Elements:** Provider logo, sync/delete icons, blue/gray switches, eye/hidden-eye indicators, Add a calendar account dropdown and blue pill Next step.
- **Estimated geometry:** Content width approximately 524px, 32px toggle rows, 40px primary action and thin section rules.

### Visual rhythm

- **Spacing:** Compact nested calendar rows sit within a much larger white canvas; separators isolate account addition and progression.

### Responsive

- **Suggested adaptation:** Use fluid width and 24px gutters, wrap account names and preserve trailing icon access. Mobile behavior is not shown.

### Adaptation guidance

- **Transfer:** Keep account-level and calendar-level controls visually distinct, with explicit visibility and busy-time choices.

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