Prompt 920 words Copy
# Design from Reference: Customer.io Goals And Experiences Set Up
Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.
## Reference
- **Product:** Customer.io
- **Category:** Account Setup
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/f3af68e9ce84f6db811e-1600.webp)
- **Source:** https://fly.customer.io/post_registration/role
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 questionnaire with a dark teal brand bar, pale workspace and compact centered white card.
- **Focus:** A simple role-selection grid and one Next action keep the page task-oriented.
### Page composition
- **Capture scale:** The source is 2880 × 1630 pixels. A roughly 1440 × 815 CSS-pixel viewport at 2× scale is plausible but unverified.
- **Header:** A dark full-width strip, approximately 47 estimated CSS pixels high, contains the white Customer.io logo at left.
- **Card:** A centered white panel around 480 × 407 estimated CSS pixels begins near y=168, with approximately 24-pixel padding.
- **Form layout:** Title, subtitle and question precede a two-column, five-row choice grid. Next aligns at bottom right. A small reCAPTCHA badge is visible at the viewport's lower right.
### Information hierarchy
- **Title:** “Your goals and experience” is the dominant card text.
- **Context:** A muted setup subtitle precedes the medium-weight question about the user's work.
- **Choices:** Ten equally styled role options include marketing, product, sales, technical, operations, design, research and Other.
- **Continuation:** The dark Next button is visually distinct; no choice is visibly selected in this capture.
### Typography
- **Family:** A clean sans serif is visible; exact identity is unverified.
- **Title:** Approximately 24 estimated CSS pixels, semibold, with a 29-pixel line height.
- **Form text:** Subtitle and options are around 14 pixels with 20-pixel line height; the question is slightly heavier.
- **Action:** Next is around 14 pixels, semibold and white.
### Colors & surfaces
- **Measured palette:** ICC-aware sRGB sampling yields #F8F9F9 for the workspace, #FFFFFF for the card, #1B2C2D for the header and #00282C for the primary button.
- **Secondary tones:** #3B4F50 appears in muted text, while #EAF0F1 provides quiet outlines.
- **Treatment:** The card has a thin pale border and small corners around 4 pixels, without a pronounced shadow.
### Components
- **Choice buttons:** Each outlined option is approximately 213 × 39 estimated CSS pixels, with left-aligned text, 12-pixel horizontal padding and small rounded corners.
- **Grid:** Two equal columns have a narrow gap around 4–6 pixels, with similarly tight vertical spacing.
- **Next:** A roughly 86 × 37-pixel dark teal rectangle sits below the choices with about 16-pixel top spacing.
- **Brand bar:** A compact white symbol/wordmark is aligned approximately 16 pixels from the left edge.
### Visual rhythm
- **Whitespace:** Large empty workspace margins isolate the card and reduce distraction.
- **Internal cadence:** Title/subtitle are closely paired; a larger gap separates them from the question, then a compact repeated option grid follows.
- **Alignment:** All card copy and option edges share a left inset, while the action is right aligned.
### Responsive
- **Recommendation:** Keep the card within viewport width minus 32 CSS pixels and reduce the choice grid to one column where labels would otherwise crowd.
- **Recommendation:** Preserve generous option tap targets and ensure the bottom badge does not overlap form actions. No mobile state is shown.
### Adaptation guidance
- **Preserve:** Retain the compact card, equal role choices and clear continuation action.
- **Implement:** Use accessible grouped selection semantics and an explicit selected state; the still image does not establish selection behavior.
- **Hierarchy:** Keep supporting copy quiet and avoid adding extra navigation to this focused onboarding step.
## 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 image Attach it to your message: assistants can’t open image links. Open in ChatGPT ↗ Open in Claude ↗
Build it in Lovable ↗ v0 ↗ Figma Make ↗
Opening a tool copies the screenshot so you can paste it with your prompt.
SaaSFrame
