Odoo — CRM demo

CRM & SalesSee it livedemo5.odoo.com

A CRM pipeline groups opportunities by stage, with stage totals and compact cards showing value, customer, tags, and ownership.

Odoo — CRM demo — captured interface — Viewport capture · opening screen

Public demo · 2026-09-05Open full image ↗

Why this pattern works

Sales pipelines that need to connect deal status with value and the next operational context.

Design notes

Surface: Odoo public Demo Company CRM Pipeline.
Navigation: CRM module links above a shared search, filters, and view switcher.
Layout: Four status columns with summarized value above opportunity cards.
Density: High on cards, balanced by clear columns and whitespace between stages.
Color: Light gray canvas, white cards, restrained status colors and tags.
Type: Compact sans deal titles and metadata with stronger currency values.
Pattern: Show stage totals and card-level context together so the board supports both overview and action.
States: Populated sample pipeline in a public demo; no deals were edited or moved.
Don't: Do not overload cards with every CRM field or communicate stage exclusively through color.

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: Odoo — CRM demo
Source: https://demo5.odoo.com/odoo/crm
Swipefile reference: https://swipefile.design/ref/saas-ui-odoo-crm/
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 interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Odoo public Demo Company CRM Pipeline.
- nav: CRM module links above a shared search, filters, and view switcher.
- layout: Four status columns with summarized value above opportunity cards.
- density: High on cards, balanced by clear columns and whitespace between stages.
- color: Light gray canvas, white cards, restrained status colors and tags.
- typography: Compact sans deal titles and metadata with stronger currency values.
- pattern: Show stage totals and card-level context together so the board supports both overview and action.
- states: Populated sample pipeline in a public demo; no deals were edited or moved.
- dont: Do not overload cards with every CRM field or communicate stage exclusively through color.

Useful for: Sales pipelines that need to connect deal status with value and the next operational context.

## 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 interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Sales pipelines that need to connect deal status with value and the next operational context.

Odoo — CRM demo

Make it your own

Keep exploring