Asana

SaaS MarketingVisit siteasana.com

A large headline is surrounded by small connected work labels and avatars, while provider buttons and an email field make the first account step visible.

Asana — captured interface — Viewport capture · opening screen

Source capture · 2026-09-05Open full image ↗

Forms & onboarding

Why this pattern works

Collaboration software connecting an abstract teamwork promise to a concrete signup path.

Design notes

Mood: Collaborative and approachable
Colors: White, black, pink, small multicolor accents
Type: Large clean sans display with a colored phrase
Layout: Centered message and account choices, framed by a loose network of work labels
Motion: Static opening-screen capture. Visit the source to study transitions and interactive behavior.
Texture: Thin connector lines, small avatars, and rounded UI fragments
Don't: Adapt the hierarchy to your own product and content; use your own identity and imagery.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Asana
Source: https://asana.com/
Swipefile reference: https://swipefile.design/ref/saas-asana/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- mood: Collaborative and approachable
- colors: White, black, pink, small multicolor accents
- typography: Large clean sans display with a colored phrase
- layout: Centered message and account choices, framed by a loose network of work labels
- motion: Static opening-screen capture. Visit the source to study transitions and interactive behavior.
- texture: Thin connector lines, small avatars, and rounded UI fragments
- dont: Adapt the hierarchy to your own product and content; use your own identity and imagery.

Useful for: Collaboration software connecting an abstract teamwork promise to a concrete signup path.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Collaboration software connecting an abstract teamwork promise to a concrete signup path.

Asana

Make it your own

Keep exploring