For AI Agents
Hand your agent this brief or the ReUI MCP, not a screenshot. Installs with a ReUI Pro or Ultimate license.
When to use
- A sales team's deal work: a pipeline board, a deal grid, a forecast call or the record of one deal
- The contact side of sales: a contacts directory, an activity log across accounts and a CSV import
- A sales overview of open pipeline, weighted forecast and win rate above the open deals
When not to use
- Cards for tasks or tickets moved across columns, with no deal value or close date: use the Kanban Board blocks
- A records table with sorting, paging and row selection, outside a sales context: use the Base blocks
- A side panel for one record that is not a deal, such as an order or a user: use the Sheet blocks
Agent notes
- Each block sizes its page with
min-h-svh, orh-svhon the Deal Desk, in page.tsx or its root component; size it from your app shell instead - Every change lives in
useStateor auseReducerstore and resets on reload; no block calls an API or writes to storage
Third-party API docs
- Sonner v2: API reference, docs, used by 8 of 9 blocks
- TanStack Table v9: API reference, docs, used by 4 of 9 blocks
- dnd kit v6: API reference, docs, used by 3 of 9 blocks (these are the Legacy docs; dndkit.com's default docs cover the newer @dnd-kit/react, a different API)
- React DayPicker v9: API reference, docs, used by 2 of 9 blocks
- Recharts v3: API reference, docs, used by 1 of 9 blocks
- date-fns v4: docs, used by 1 of 9 blocks
- Base UI v1: API reference, docs, llms.txt, used by 1 of 9 blocks
https://web.dev.reui.io/blocks/solutions/crm.mdsearch({ query: "crm", type: "block", category: "crm" })Shadcn CRM Blocks: A Full Pipeline, Not a Sample Set
This is not a sampler of CRM ideas. The 9 blocks are a screen for each job a CRM has to do: a dashboard to report on, a board to work, a directory to search, a record to open, a log to read, an importer to get your data in, a workspace that shows the whole book of deals as a table, a board, a calendar and a timeline, a forecast call that measures the quarter against its target, and a deal desk for working one deal at a time beside the buyer conversation.
The deal detail sheet, the 4 view workspace, the forecast call and the deal desk share a single stage ladder, Qualified, Discovery, Proposal and Negotiation, then Closed Won or Closed Lost, and the dashboard's open-deals grid uses Discovery, Proposal and Negotiation from it. The forecast call also runs on the same deal record and store as the 4 view workspace, so data wired into one fits the other. The kanban board keeps its own 6 lanes, from Qualified through Security and Procurement to Closed-Won, set in its data file for you to rename.
All of it is React and Tailwind source installed through the shadcn CLI, built on ReUI DataGrid, Kanban, Gantt, EventCalendar, Timeline, Filters, Frame, and Stepper with shadcn Card, Sheet, Avatar, and Progress.
All CRM Blocks
Open any block on its own page for a live preview, the components it is built from, and the install command.
- Pipeline Dashboard Sales Pipeline CRM Dashboard with Metric Charts and Open-Deals Grid
- Deal Board CRM deal pipeline kanban board with risk signals and confidence scores
- Contacts Directory CRM Contacts Grid with Bulk Owner Assignment and Detail Sheet
- Deal Sheet CRM Deal Detail Sheet with Inline Stage Select and Win Probability
- Activity Timeline CRM Activity Timeline with Day Buckets, Type and Owner Filters
- CSV Import Five-Step CRM CSV Import Wizard with Column Mapping and Validation
- Pipeline Workspace CRM Deal Pipeline Workspace with Table, Board, Calendar and Timeline Views
- Forecast Call CRM Forecast Call Workspace with Call Lanes, Rep Rollups and Target Attainment
- Deal Desk CRM Deal Desk with Deal Queue, Stage Path, Line Items and Buyer Conversation
The 9 Screens and How They Connect
Getting data in is usually the reason a CRM prototype dies. The CSV import wizard handles it in 5 steps with column mapping, per-row validation counts, and explicit duplicate handling, so the first 1,000 contacts arrive without anyone writing a migration script.
Working the pipeline happens on the kanban board, where deals move across 6 stages carrying risk signal, value, close date, confidence, and owner. Finding a person happens in the contacts grid, with Filters, sortable columns, and a selection bar that assigns an owner or adds the selected contacts to a list, and a row opens a contact detail sheet. Inspecting one deal happens in the detail sheet, where an inline stage Select drives the win-probability Progress, with the deal team, an activity timeline, and open tasks in the same panel.
Reporting closes the loop. The dashboard tracks pipeline value, forecast, and win rate above a dense open-deals grid with search, sort, stage filters, and row actions, while the activity log groups every touch into Today, Yesterday, and This week buckets with type and owner filters, collapsible detail panels, and outcome badges.
Managing the whole book is the workspace. One set of deals grouped under its accounts is the same set on a stage board, on a calendar of next activities and close dates, and on a timeline of open to close windows, with search, filters, inline edit, drag, and undo shared across all 4 views.
Calling the quarter is the forecast call. Its board lanes are the rep's call, Not called, Pipeline, Best case and Commit, followed by Closed Won, Closed Lost and Omit, and dragging a card between call lanes rewrites the call. Each lane in the call shows its share of the target, and the table bands the same deals by rep with Won, Commit, Best case and Pipeline columns that roll up on every band. Above both, won plus commit is measured against the quarter target with the attainment, the week of the quarter, a linear pace and the gap, and 4 hygiene chips flag slipped close dates, deals with no next step, rotting deals and overdue activity.
Working one deal at a time is the deal desk. A queue with a stage filter and a Cmd+K search sits beside the open deal, where a Stepper stage path, an owner select and Mark Won or Mark Lost move it on, the deal value is summed from its line items, and each stage, owner or close change raises a toast with Undo. The third pane holds the buyer conversation, with a composer for an email, a note or a logged call, and a second tab with the owner's pipeline.
Sized for Founders and Agencies, Not for a CRM Vendor
These are the screens a startup, an agency, or an internal sales team actually opens, at the density those teams work at. The forecast call measures the whole team against one quarter target, a single number in its data file, and nothing here assigns territories or splits that target into per-rep quotas. Those planning rules belong with your data rather than in a component library.
What that buys you is a category you can review in an afternoon and adopt in a day. Read every block, keep the ones you want, delete the rest, and you have not inherited an opinionated CRM framework in the process.
Restyle and Rewire
- A shared stage ladder Qualified to Negotiation, then Closed Won or Closed Lost, in the detail sheet, the 4 view workspace, the forecast call and the deal desk.
- Real interactions Multi-select bulk owner assignment and add-to-list on the contacts grid, drag across stages on the board and across call lanes on the forecast call, row actions on the deals grid.
- 8 styles, 2 bases Install on Base UI or Radix in any of the 8 ReUI styles so the CRM inherits your existing radius, density, and color scale.
- Yours after install The shadcn CLI copies source into your repo, so renaming a stage or adding a custom field is a normal edit in a file you own.
Related Shadcn Solutions Block Categories
- Bookings Blocks (3 blocks) Appointment and service admin for agencies that book work as well as close it.
- Users Blocks (7 blocks) Team, role, and invitation screens for giving reps the right access to the pipeline.
- Billing Blocks (9 blocks) Invoice builder, plan catalog, and subscription grids for what happens after a deal is marked won.
- Analytics Blocks (9 blocks) Cohort, funnel, and adoption reports if you want to see what those new accounts do next.
- Inventory Blocks (11 blocks) Stock, supplier, and reorder visibility for sales teams quoting against physical availability.
All Shadcn Block Groups
Browse the full ReUI Shadcn blocks library by product surface. Each group bundles category-level blocks you can mix and match across your project.
- Shadcn Application Blocks (303) Browse 303 Shadcn Application blocks across 23 categories.
- Shadcn Data Grid Blocks (47) Browse 47 Shadcn Data Grid blocks across 9 categories.
- Shadcn Charts Blocks (52) Browse 52 Shadcn Charts blocks across 10 categories.
- Shadcn Solutions Blocks (76) Browse 76 Shadcn Solutions blocks across 11 categories.
- Shadcn AI & Agents Blocks (22) Browse 22 Shadcn AI & Agents blocks across 3 categories.
- Shadcn eCommerce Blocks (87) Browse 87 Shadcn eCommerce blocks across 13 categories.
- Shadcn Marketing Blocks (67) Browse 67 Shadcn Marketing blocks across 8 categories.
Frequently Asked Questions
Is this enough blocks to build a real CRM UI?
Can I use just the kanban board on its own?
How do I connect the CRM screens to my database?
Will the CRM match my existing shadcn app?
Start building with ReUI Pro today.
Every Pro block, every style, and every future addition, with one license for unlimited projects.
From $249, once. Lifetime updates.