← Previous14 / 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 874 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/dae7c4f4a10695462fc3-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 minimal onboarding integration step with a white canvas, compact provider list and blue continuation action.
- **Restraint:** Brand/provider icons and fine dividers supply structure without an enclosing card.

### Page composition
- **Capture scale:** The source measures 2880 × 1824 pixels. A roughly 1440 × 912 CSS-pixel viewport at 2× scale is plausible but unverified.
- **Header utilities:** A small brand symbol sits at upper left and a thin progress indicator at upper right.
- **Content column:** A roughly 524-pixel-wide estimated CSS column is centered, with a back chevron just outside its left edge.
- **Sequence:** Large heading, two-line description, five provider rows and a lower-left Next step button.

### Information hierarchy
- **Task:** “Wire up video conferencing” is the dominant heading.
- **Context:** Supporting copy explains selecting a provider and calendar-built-in solutions.
- **Providers:** Zoom, Google Meet, Microsoft Teams, SquadCast and Whereby each pair a logo with title and one-line description.
- **Affordances:** Plus icons mark connectable options; information icons accompany some providers. Next step is distinct below the list.

### Typography
- **Family:** A clean sans serif is visible; exact identity is unverified.
- **Heading:** Approximately 32 estimated CSS pixels, bold, with compact line height.
- **Description:** Around 16 pixels with 24-pixel line height.
- **Rows:** Provider titles are around 14–15 pixels; descriptions are similar size but muted.
- **Action:** Approximately 14 pixels, semibold and white.

### Colors & surfaces
- **Measured palette:** ICC-aware sRGB sampling yields white #FFFFFF, dark navy #0F1828, blue #0065F4, divider #E3E7EB and muted text #687281/#495564.
- **Provider accents:** Familiar blue, green/yellow, purple, yellow and blush logo colors differentiate entries.
- **Treatment:** Rows are flat and separated by fine horizontal rules; the Next action is a small fully rounded blue pill.

### Components
- **Provider rows:** Each is roughly 94 estimated CSS pixels high, with a 32-pixel logo, two-line text block and right-aligned utility icon.
- **Connection controls:** Small plus signs sit at the far right; circled information icons provide a second quiet affordance.
- **Progress:** A short gray rounded track has a darker partially filled section.
- **Next step:** A roughly 108 × 40-pixel blue pill aligns to the column left.
- **Back:** A small left chevron appears beside the heading rather than in a separate footer.

### Visual rhythm
- **Rows:** Repeated icon/text/control alignment makes provider differences easy to compare.
- **Whitespace:** Broad side margins and generous top spacing isolate the task.
- **Dividers:** Fine rules create a regular cadence without card borders.

### Responsive
- **Recommendation:** Let the column fill viewport width minus 32–40 CSS pixels, wrapping descriptions while preserving right-side controls.
- **Recommendation:** Keep the heading readable and Next directly after the provider list on short screens. No mobile state is captured.

### Adaptation guidance
- **Preserve:** Retain explicit provider names, concise descriptions and distinct connect/info affordances.
- **Implement:** Label icon-only controls and show connected/loading/error states where applicable; behavior is unverified from the still.
- **Clarity:** Explain calendar-provided options in text rather than relying on provider icons alone.

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