← Previous25 / 49Next →

Remote Onboarding Successfully Completed

RemoteHR platform for global teams

Design with AI

Create a new design inspired by Remote Onboarding Successfully Completed, 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 1,082 words

# Design from Reference: Remote Onboarding Successfully Completed

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

## Reference

- **Product:** Remote
- **Category:** Success
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/811c22a4909c50c5c4c0-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

- **Style:** Calm application onboarding-success screen with a centered confirmation and one clear next action.
- **Character:** Pale cool-gray workspace, nearly white header, dark navy text and a saturated blue success/action accent.
- **Surface treatment:** Flat composition without a central card, decorative illustration or heavy shadows.

### Page composition

- **Capture scale:** 2880 × 1630 image px. CSS estimates assume an unverified 2× capture, approximately 1440 × 815 CSS px.
- **Header:** Approximately 104 px high, with Remote logo at left and utility/account controls aligned right.
- **Confirmation placement:** A narrow centered stack occupies the middle of the content area, beginning around y=295 CSS px.
- **Success mark:** Large outlined circle with blue check sits above the message.
- **Message:** Two-line personalized completion headline is followed by two shorter lines of muted reassurance.
- **Next action:** A blue Go to dashboard pill sits beneath the copy.
- **Surroundings:** Broad empty margins keep the success state isolated; no sidebar, footer or additional onboarding steps are visible.

### Information hierarchy

- **State emphasis:** The circular check communicates completion before the headline is read.
- **Primary message:** Bold personalized text states that onboarding is complete.
- **Supporting tone:** Smaller gray copy expresses partnership and encouragement without adding another task.
- **Primary action:** Go to dashboard is the sole central action.
- **Account context:** Header metadata identifies the signed-in user and organization; it remains much quieter than the confirmation.
- **Evidence limit:** No dashboard contents, completion requirements or post-click behavior are shown.

### Typography

- **Family:** Rounded modern application sans serif; exact identity is unverified.
- **Headline:** Approximately 28 px, semibold, with 34–36 px leading and centered alignment.
- **Supporting copy:** Approximately 16 px with 24 px leading, regular weight.
- **Button:** Approximately 14–15 px medium, centered in the pill.
- **Header metadata:** Approximately 12–13 px for name and smaller role/organization line.
- **Measurement limit:** Values are visual CSS estimates under the assumed 2× capture.

### Colors & surfaces

- **Workspace:** Sampled sRGB #F3F4F8 supplies the pale cool-gray main canvas.
- **Header:** Sampled #F8FCFF supplies a nearly white cool surface.
- **Primary blue:** Sampled #0062FF appears in the check and dashboard action.
- **Text:** Sampled #0E141B is a dark navy-black reference; #485966 supplies supporting blue-gray.
- **Success ring:** Sampled #C3D7FD supplies the pale blue circular outline.
- **Neutral details:** Sampled #E2E9EF appears among subtle header/avatar tones.

### Components

- **Success icon:** Approximately 96 px diameter, thick pale-blue outline, pale center and medium-weight blue check.
- **Dashboard button:** Approximately 160 × 40 px, fully rounded ends, blue fill and white label.
- **Brand:** Blue symbol and dark Remote wordmark sit together at the header's left.
- **Utility icons:** Small outline briefcase, help and notification symbols precede the account block; a tiny red notification dot is visible.
- **Account block:** Pale circular initials avatar, stacked identity text and a down chevron.
- **Header divider:** Fine cool-gray horizontal line separates navigation from the workspace.

### Visual rhythm

- **Centering:** Icon, headline, support copy and action share one vertical axis.
- **Spacing:** About 32–40 px separates icon from heading, smaller gaps connect text lines and about 32 px precedes the button.
- **Whitespace:** Large open areas above, beside and below the confirmation keep the page calm.
- **Accent restraint:** Blue is reserved for brand and success/action elements.

### Responsive

- **Evidence limit:** Only desktop is shown; recommendations below are not observed behavior.
- **Content recommendation:** Maintain centered alignment with 20–24 px side padding and natural headline wrapping.
- **Header recommendation:** Collapse secondary utilities or shorten account metadata when space is limited.
- **Action recommendation:** Keep the dashboard action easily reachable with at least a 44 px effective touch target.
- **Accessibility recommendation:** Announce success and provide visible keyboard focus on the next action; these behaviors are not verified by the screenshot.

### Adaptation guidance

- **Preserve clarity:** Confirm the actual completed process and offer one obvious next destination.
- **Use real state:** Personalize only from genuine account data and avoid claiming completion prematurely.
- **Retain restraint:** Use a simple success symbol, concise message and one brand-colored action.
- **Adapt tone:** Replace the supporting sentence with language appropriate to the target product.
- **Avoid invented destinations:** Link to the real post-onboarding route rather than assuming a dashboard exists.

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