← Previous18 / 18

Pirsch Analytics Signup

Pirsch AnalyticsPrivacy-friendly analytics

Design with AI

Create a new design inspired by Pirsch Analytics Signup, 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 887 words

# Design from Reference: Pirsch Analytics Signup

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

## Reference

- **Product:** Pirsch Analytics
- **Category:** Sign Up
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/f5b2d2db4cb84b720def-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:** Simple warm-cream trial signup screen with black typography, mint-green actions and a compact two-column form/benefit composition.
- **Emphasis:** Large whitespace and the absence of a card keep the registration task direct.
- **Scale:** The image measures 2880 × 1642 px. Dimensions below estimate a 1440 × 821 CSS layout at 2× scale; device ratio and zoom are unverified.

### Page composition
- **Header:** Small black brand left; existing-account prompt and mint login button right.
- **Main block:** A centered area begins with a trial heading and one-line reassurance.
- **Form:** A narrow left column contains email, dark verification widget, green Continue button and small legal copy.
- **Benefits:** Three large check-led statements stack in the right column.
- **Footer:** A small centered copyright line sits below the form; the remainder is blank cream.

### Information hierarchy
- **Offer:** The bold trial headline leads, with no-card-required reassurance below.
- **Task:** Email and human verification precede Continue.
- **Benefits:** Three concise statements provide reassurance alongside the form.
- **State:** Email is empty and verification unchecked; no registration outcome is visible.

### Typography
- **Family:** Rounded neutral sans-serif; exact identity is unverified.
- **Heading:** Approximately 30–32 CSS px, medium-to-bold.
- **Benefits:** Around 24–26 px, medium weight.
- **Controls:** Approximately 16 px; helper/legal copy about 13–14 px.
- **Footer:** Small muted text around 11–12 px.

### Colors & surfaces
- **Measured background:** ICC-aware sRGB sampling yields #F9F5EC and closely related #F7F5EC cream tones.
- **Measured action:** Mint #41D199 appears in buttons/check circles.
- **Measured dark:** #333333 is prominent in the verification widget; #000000 appears in text.
- **Measured neutral:** #707070 is muted copy; #FFFFFF fills the email control.
- **Depth:** Flat fills and small corners dominate, without substantial shadows.

### Components
- **Email field:** Approximately 320 × 48 CSS px white rectangle with small corners and placeholder.
- **Verification:** A dark CAPTCHA-style widget contains an unchecked square and small service branding.
- **Continue:** Matching-width mint button, about 48 px high, with centered black caption.
- **Benefit markers:** Small mint circles with black checks precede each statement.
- **Login:** Compact green rounded rectangle in the upper-right header.
- **Legal links:** Dark inline privacy/terms text contrasts with muted surrounding copy.

### Visual rhythm
- **Main alignment:** Heading/form share a left axis; benefits form a parallel vertical stack.
- **Spacing:** Compact field/widget/button gaps contrast with broad surrounding whitespace.
- **Benefits:** Equal row spacing makes three promises easy to scan.
- **Footer pause:** Copyright is separated from legal copy by a generous gap.

### Responsive
- **Evidence limit:** Only desktop is shown; recommendations follow.
- **Columns:** Stack benefits beneath the form on narrow screens.
- **Controls:** Preserve readable email/CAPTCHA sizing and large Continue target.
- **Header:** Wrap the account prompt without obscuring login.

### Adaptation guidance
- **Reusable pattern:** Pair a low-friction trial form with three concise benefit statements.
- **State clarity:** Provide explicit verification/error feedback and distinguish trial messaging from completed signup.
- **Accessibility:** Use a visible email label, CAPTCHA alternatives and semantic legal links.
- **Visual restraint:** Keep cream/mint palette and generous space focused on the task.

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