CRM UI Design: 5 Screens and the Patterns That Work

Christoph Bogatzki, Cluma
Christoph Bogatzki
•
14
min read
A woman moves a card on a wall board of four columns while a man watches and Mumble, a tall black hovering monster with two white eyes, looks across at the column that has filled up.
A smiling designer shows a printed app layout to Giggles, a small Cluma monster sitting on her desk
Get a design team that ships every 48 hours

Senior-led design for SaaS teams, one flat monthly price per module.

Thanks, you're in. Here's your next step:
Book a call
Something went wrong. Please check your email and try again.

CRM UI design is the work of making five screens fast to read and quick to act in: the dashboard, the sales pipeline, the contact record, the activity feed and settings. Pattern guides for CRM interfaces put movable widget cards on the dashboard, tabs on the contact record and a live feed of what changed [1], with role-based views that hide what a role doesn't need [2].

Shipped products show what that looks like. Pipedrive runs its deal pipeline as a Kanban board with drag and drop [3], HubSpot’s contact record card carries call, email and note actions [4], Attio rebuilt its record pages on one context layer [5], and Salesforce describes a single customizable dashboard [6].

If you hire the work out, a CRM-specialist studio quotes per project and says a typical engagement starts from three months [7]. Published subscription prices run $4,599 to $11,999 a month [8] and $1,199 to $1,999 a month [9]. Every price here was read on 9 November 2026.

We take each screen in turn below: what the person on it is trying to do, the pattern that works, a shipped CRM that already does it, and the mistakes that send a team back to a spreadsheet. Then who can design it, and what five named options charge. It sits with the rest of our guides for SaaS teams.

One thing first. Cluma publishes this guide and appears in the provider table below on the same basis as everyone else, with its own published price [12]. Nothing here ranks the options against each other. You get each one’s facts, and you do the choosing.

What is CRM UI design?

CRM UI design is interface design for a system where several roles work the same customer data all day, which makes it a different job from designing a marketing site or a consumer app. Three things set it apart.

None of the three is about taste. They are all about load.

Records are dense. One contact can hold emails, calls, product usage and billing at once, and Attio built its record pages on a context layer that pulls exactly those four together [5].

Roles differ. A rep, a manager and an admin all open the same deal and need different things off it, which is why the recommended practice is to fit dashboards and workflows to a role and hide what that role doesn't need [2].

And the work repeats. The same eight actions happen fifty times a day, so a second of friction isn't a second. It's a habit your team forms against the tool.

Dense, multi-role and repetitive. Design for all three or none of them holds.

Role-based views are what follows from all three. Decide per role what each screen shows before you decide how it looks. Which modules exist, and where a field lives inside them, is a structural question, and our guide to information architecture for SaaS products is the deeper method for that part.

Get that order wrong and you end up styling a screen nobody agreed on.

That leaves five screens carrying a CRM, and here's what each one owns.

ScreenWhat the user is doing thereThe pattern that worksA shipped product that shows it
DashboardReading the day in one lookMovable, resizable widget cardsSalesforce, customizable dashboard [6]
Sales pipelineMoving deals between stagesKanban board with drag and dropPipedrive, pipeline view [3]
Contact recordFinding one customer’s historyTabs over one long pageAttio, redesigned record pages [5]
Activity feedSeeing what changed since yesterdayGrouped real-time streamAttio, Activities feed [5]
SettingsSetting roles and field rulesA clear role matrixNo named public example

How should a CRM dashboard be designed?

A CRM dashboard should be a grid of independent cards the user can rearrange, each one answering a single question, with the set of cards decided per role.

The card is the unit. Every widget sits in a card that can be moved, resized or configured on its own, which lets someone build the view their job actually needs [1]. The cards that carry most of the load are your headline numbers, a pipeline snapshot, the activity feed, the task list and recently viewed records [1]. Keep the numbers as plain figures or simple charts [1], and let each one drill through to the rows behind it [2].

Salesforce frames the same screen as one simple, secure and customizable dashboard holding purchase history, order status and outstanding service issues [6]. That's a vendor describing its own product, and it's also a fair reminder of what the screen is for: one place where the state of a customer is visible without opening anything.

One card, one question. That rule alone settles most dashboard arguments.

Here's the honest limit. A dashboard that shows everything to everyone is the default outcome, because every stakeholder asks for one more card and nobody owns removals.

The fix is the role decision, made once per role and written down: hide what that role doesn't need [2].

Ask your reps what they would take off the dashboard, not what they want added to it.

What makes a sales pipeline screen work?

A sales pipeline screen works when a rep can see where every deal stands without clicking, and move one with a drag. Pipedrive describes its pipeline as Kanban boards with drag and drop to move deals and tasks down the sales funnel, giving a clear, customizable view of every deal, stage and activity [3]. The promise it attaches to that view is a complete picture of each deal’s position in the sales cycle, so a rep can spot opportunities and bottlenecks [3]. Buyers describe the screen the same way. HubSpot publishes a customer saying the deal board is awesome and that being able to visualise a sales pipeline is one of the best parts of the product [4].

What no vendor decides for you is the hierarchy on the card. Stage, priority and deadline all compete for the same glance, and the recommended practice is to use colour, size and spacing so all three of them land at once [2]. Add quick actions on the card itself and clear stage indicators [2], and the board reads before anyone reads it.

Your stage count is a design decision too. Keep it low enough that the whole board fits one screen.

Colour does the stage, weight does the priority, position does the deadline.

That's the test for this screen. Someone glances at it from across the room and can tell you which column is backing up.

What belongs on a contact record?

A contact record holds everything you know about one customer, so the design question isn't what to include. It's how to split it.

Attio markets redesigned record pages that put all your data right where you need it, built on a context layer that logs emails, calls, product usage and billing automatically [5]. HubSpot keeps the actions on the record itself: its own contact record card shows contact information next to calling, emailing, note-taking and property history [4]. Both products answer the same need. The record is where work happens, not only where data rests.

The structural pattern that keeps it usable is tabs. A contact record can carry tabs for Details, Activities, Notes and Related Deals, which breaks a heavy page into chunks instead of one scroll [1]. Breadcrumbs earn their place here too, because a CRM is deep enough that people lose their position in it [1].

If your record needs a scrollbar to show its own tabs, you have too many of them.

Inside the record, forms carry the risk. Show only the fields that apply, using progressive disclosure, and validate while someone types instead of after they save [2].

What those tabs get called is a research question, not a writing one. Our guide to card sorting for SaaS navigation is the method for settling labels with the people who'll use them.

How should the activity feed and settings work?

The activity feed should be a grouped real-time stream of what changed, and settings should make roles, permissions and field rules legible to whoever administers them. Two screens, one section, because the second one is short by design and almost always built last.

Start with the feed. It carries new leads, logged calls, updated contacts and closed deals as they happen, and that stream is what makes a shared pipeline readable to a team instead of to one rep [1]. Attio calls its version Activities and sets the bar at capturing anything that moves a deal [5].

A feed that lists forty identical rows is a log file with a nicer font.

Raw chronology is where feeds fail. The recommended pattern groups related emails and calls together and puts a quick-add composer for notes and tasks right in the timeline [2], so reading the history and adding to it are the same screen.

Settings is the screen teams leave until last and the one admins live in. Two patterns here are documented rather than assumed. Permissions want a clear role matrix with field-level security, so who can see and change what is visible on one screen [2]. Data hygiene wants an import wizard with smart field mapping, plus deduplication and merge flows that can't lose a record [2].

Your admins will notice a settings screen somebody actually designed. Nobody else will.

Past those two we found no named public example and no sourced pattern for a CRM settings screen, so we left the row above blank instead of guessing. A CRM design engagement treats that configuration work as part of the interface, not after it [7].

What are the most common CRM UI design mistakes?

The four mistakes that cost the most are inconsistency between modules, no support for power users, accessibility left out, and a dashboard nobody can change. None of them is a visual problem, which is why repainting the screens doesn't fix them.

We put inconsistency first because it compounds. Filters, forms and modals on the Contacts page should behave exactly as they do on Deals, and on every other page, or people relearn the interface each time they switch [2]. That's a component problem, not a screen problem, and our explainer on what a design system is covers the fix.

Power users are second. A CRM interface has to support the people in it all day with bulk actions, keyboard shortcuts and auto-saving, so repetitive work stops feeling repetitive [2]. Accessibility is third, and it's specific: ARIA attributes on tables, full keyboard navigation, screen reader support [2]. A CRM is mostly tables, which puts it at the centre of that work.

Tables are the whole job here. Treat them as the main interface, not as filler.

Fourth is control. A central CRM can feel to a rep like losing the agency a spreadsheet gave them, and letting people customise their dashboard and drag widgets where they want them is what gives it back [10].

All four end in the same place. A CRM that makes someone feel stupid, frustrated or overwhelmed gets rejected whatever the engineering behind it is worth, because adoption is a psychological outcome before it's a technical one [10].

Watch one of your reps work for an hour and all four turn up on their own. Which is also the argument for testing your screens before they exist. Put a clickable version in front of the reps who'll live in it, and our rundown of AI prototyping tools for SaaS teams covers the quick ways to do that.

Who can design your CRM UI, and what does it cost?

You're choosing between two shapes: a scoped project from a studio that quotes per engagement, or a monthly design subscription you keep running while the product changes. We list four named providers plus Cluma because those five publish enough on their own sites to compare. Every figure below was read on 9 November 2026.

Every row below is that company's own published claim, so weigh each one against your own scope.

ProviderWhat it isPublished priceWhat you getHow long
CiedenCRM-specific design serviceQuoted per project [7]Analysis, CRM UI/UX, prototyping, testingFrom three months
ElekenDedicated product designer$4,599, $6,599 or $11,999 a month [8]One or two designers, unlimited tasksTwo-month minimum
Duck.DesignBroad design subscription$1,199, $1,899 or $1,999 a month [9]UI/UX sits in the middle tierCancel anytime
Adam Fard UX StudioSubscription or fixed-price projectQuoted after a form [11]Unlimited UX and UI tasks, revisionsTwo-day task turnaround
ClumaOngoing product design module$4,995 a month [12]User flows, wireframes, web app UI, design systemsOne request at a time

Cieden: a CRM-specific design engagement

Cieden is the one option here with a dedicated CRM design service page. It says a typical engagement starts from three months and may include business analysis, CRM UI/UX design, prototyping and usability testing, with the estimate prepared once requirements are reviewed [7]. Its stated method maps user roles, business rules, data flows, integrations and daily tasks before any UI, and its named solutions include accounts and contacts management, visual sales pipelines, information architecture and data visualization [7]. No price appears on the page.

Everything in this section comes off each company's own live pages, never a roundup.

Best fit: you're rebuilding a whole CRM and want research and usability testing inside the same engagement.

Eleken: a dedicated product designer by the month

Eleken sells designer capacity instead of a project. A part-time designer is $4,599 a month, a full-time designer $6,599, and two full-time designers $11,999, each tier with unlimited design tasks and revisions [8]. The minimum contract is two months, there's a three-day free trial, and you can pause or cancel anytime. Every tier includes the guidance of the Head of Design plus a go-to person for operational needs [8]. The service is SaaS product design in general, not a CRM-specific offer.

Best fit: you have continuous screen work and want the same designer in it every week.

Duck.Design: a broad subscription with UI/UX in the middle tier

Duck.Design runs three tiers. Visual is $1,199 a month for day-to-day graphic design, Creative Suite is $1,899 and carries UI/UX and mobile app design plus a UI/UX performance review, and Build is $1,999 for no-code development [9]. All plans list unlimited requests and revisions, a Trello board, native source files, a seven-day money-back guarantee and cancel anytime [9]. Those are the one-month rates, and the page offers 10% off at three months and 20% off at six [9].

Best fit: your CRM screens are one of several design needs and your budget starts lower.

Adam Fard UX Studio: a quoted subscription or a fixed-price project

Adam Fard UX Studio lists a DesignStream subscription with unlimited UX and UI tasks, unlimited revisions, a two-day turnaround and project management, alongside fixed-price projects for revamping a complex product [11]. No price is published. Every option on the pricing page ends in a form, so the number arrives after a conversation about scope, and no CRM-specific service is named there [11].

Best fit: you want a quote shaped around your own scope and you're comfortable starting with a call.

Cluma: CRM screens inside an ongoing design module

Cluma sells no CRM product and no one-off CRM audit, so take this for what it is: CRM screens are work inside a monthly product design module. That module is $4,995 a month and covers user flows, wireframes, mobile and web app UI, design systems and prototypes [12]. The page names complex, multi-state, role-based app UI as its own scope, which is the shape a CRM has, and it delivers developer-ready handoff with specs and assets [12]. Cluma designs the screens and your developers build them.

One request is in progress at a time with the rest queued, everyday tasks come back in about 48 hours, and bigger product work moves milestone by milestone with progress roughly every 48 hours [12]. A senior designer owns direction and signs off on every screen. You can pause anytime, and billing stops when you do [12].

Best fit: you want your screens designed and kept moving month after month. If what you want is one fixed-scope CRM project with research and usability testing inside it, the first option above is built for that and this one isn't.

Where this guide stops

Read the limits before you act on any of it.

Five limits worth knowing. Every price, timeline and feature claim here is the company’s own published statement, read on 9 November 2026, and we tested none of it ourselves.

The four CRMs are named as examples of patterns, not as a product recommendation. We measured nothing inside them, and every claim about them comes off their own current pages.

Most design providers in this space publish no price at all, so four named providers plus Cluma is our set, not the market. The settings screen has no named public example above, because none of the sources we read described one. That gap is real, and it also happens to be the screen most CRM teams give the least design time to, which is part of why nobody publishes an example of one.

None of that makes the five options above wrong for you. It makes them a starting shortlist.

And Cluma publishes this guide and is one of the options listed in it, on the same basis as the other four.

So the screens are the easy part to specify and the hard part to keep moving, which is where the choice above actually lands. If your CRM is a live product that changes every month, the work is ongoing and not a project with an end date, and you can see what a saas ui ux design agency covers on a flat monthly rate before you commit to anything. Design only, with your developers building from the handoff [12].

References

  1. eSEOspace, The Best UI Patterns for CRM Applications, published 9 January 2026 and read 09.11.2026. Behind the movable, resizable widget cards, the five cards a CRM dashboard carries, the record tabs for Details, Activities, Notes and Related Deals, the breadcrumbs, and the real-time feed of new leads, logged calls, updated contacts and closed deals. A design agency writing in its own field, so it's practitioner guidance, not research.
  2. Design Studio UI/UX, 8 CRM UX Design Best Practices & How to Design a CRM?, updated 9 July 2026 and read 09.11.2026. The source for most of the pattern advice here: role-based dashboards that hide what a role doesn't need, drill-through on dashboard numbers, visual emphasis on pipeline stages, priorities and deadlines, quick actions on pipeline cards, progressive disclosure and live validation in record forms, grouped activity timelines with a quick-add composer, the role matrix with field-level security, the import wizard and merge flows, the consistency rule across Contacts and Deals, bulk actions and keyboard shortcuts, and the ARIA, keyboard and screen reader checks. Also a design agency writing in its own field, so treat it as practitioner guidance.
  3. Pipedrive, Sales pipeline, read 09.11.2026. Where the Kanban boards with drag and drop, the clear and customizable view of every deal, stage and activity, and the complete view of a deal’s position used to spot bottlenecks come from. It's the product’s own feature page, describing what it offers.
  4. HubSpot, CRM, read 09.11.2026. Carries the contact record card with contact information alongside calling, emailing, note-taking and property history, and the customer line that the deal board is awesome and visualising a sales pipeline is one of the best parts of the product. The product’s own page, and that quote is a customer the company chose to publish.
  5. Attio, home page, read 09.11.2026. Where the redesigned record pages, the context layer logging emails, calls, product usage and billing, and the Activities feed that captures anything moving a deal come from. The product’s own page, and its changelog dates both the record pages and Activities to 29 October 2026, so they're recent work.
  6. Salesforce, What is CRM?, read 09.11.2026. Behind the single, simple, secure and customizable dashboard holding purchase history, order status and outstanding service issues, plus the clear pipeline view it gives sales reps. The company’s own explainer, written at the level of the category, so it describes what a CRM gives a business and not one named screen.
  7. Cieden, CRM Design Services, read 09.11.2026. Source of the engagement starting from three months, what it may include, the estimate prepared after requirements are reviewed, the method of mapping roles, business rules, data flows and daily tasks first, and the solutions list naming accounts and contacts management, visual sales pipelines, information architecture and data visualization. The studio’s own page, and it publishes no price, so there's no figure to compare until you've had the call.
  8. Eleken, Pricing, read 09.11.2026. Source of the $4,599, $6,599 and $11,999 monthly tiers, the unlimited design tasks and revisions, the two-month minimum, the three-day free trial, the pause and cancel terms, and the Head of Design guidance with a go-to person for operational needs. The studio’s own page, and its service is SaaS product design in general, not a CRM-specific offer.
  9. Duck.Design, Pricing, read 09.11.2026. Source of the $1,199 Visual, $1,899 Creative Suite and $1,999 Build tiers, the UI/UX and mobile app design and performance review in the middle tier, the unlimited requests and revisions, Trello board, native source files, seven-day money-back guarantee and cancel-anytime terms, and the 10% and 20% discounts at three and six months. The studio’s own page, and UI/UX work is one part of a broad subscription.
  10. eSEOspace, The Psychology Behind CRM Design: Making It User-Centric, published 9 January 2026 and read 09.11.2026. Behind the loss-of-agency effect when a spreadsheet gives way to a central CRM, the customisable dashboard and draggable widgets that hand control back, and the argument that a CRM which makes a user feel stupid, frustrated or overwhelmed gets rejected whatever the backend is worth. A design agency’s own article, and the argument is qualitative, with no adoption figure attached.
  11. Adam Fard UX Studio, Pricing, read 09.11.2026. Carries the DesignStream subscription with unlimited UX and UI tasks, unlimited revisions, a two-day turnaround and project management, the fixed-price projects for revamping a complex product, and the form that stands in for a published number. The studio’s own page, and it names no CRM-specific service.
  12. Cluma, uShip and Pricing, read 09.11.2026. Source of the $4,995 monthly module price, the user flows, wireframes, mobile and web app UI, design systems and prototypes it covers, the complex multi-state role-based app UI scope, the developer-ready handoff with specs and assets, the one active request with the rest queued, the about 48 hours on everyday tasks and progress roughly every 48 hours on bigger work, the senior sign-off, and the pause terms. Cluma publishes this guide and is one of the options listed in it, on the same basis as the other four.
Christoph Bogatzki, Cluma
Christoph Bogatzki

Founder of Cluma. I write these guides so SaaS teams can buy and run design with fewer surprises.

Connect on LinkedIn

Related guides from Cluma

Information Architecture for SaaS Products: Structure That Holds
Product & UX
11
 min read
How to structure a SaaS product: flat, nested or hub and spoke navigation, where settings belong, and how to test it before you ship.
Christoph Bogatzki
Christoph Bogatzki
October 21, 2026
Card Sorting for SaaS Navigation: 5 Steps, 15 Users
Product & UX
13
 min read
Card sorting for a SaaS product in five steps: pick the cards, choose open or closed, run 15 users, and read the clusters into your navigation.
Christoph Bogatzki
Christoph Bogatzki
November 3, 2026
What Is a Design System? Definition and 5 Examples
Product & UX
11
 min read
A design system is one shared set of standards, components and patterns your team designs from. Here are the five parts, each with a public example.
Christoph Bogatzki
Christoph Bogatzki
November 14, 2026
AI Prototyping Tools for SaaS: Figma and Free Tiers
Product & UX
11
 min read
Five AI prototyping tools for SaaS teams: which ones import from Figma, what each free tier allows, and the first paid price. Checked November 2026.
Christoph Bogatzki
Christoph Bogatzki
November 14, 2026