PipeDesk CRM

Before any visual design, the two core flows were laid out in low fidelity on the real layout: the pipeline board on the web, and the path from a deal to its next stage on the phone.

Four decisions carried the board: (1) one switcher for board, list, calendar and timeline over the same deals; (2) the count and total value in every stage header; (3) cards that show stage, priority, close date, value and source at a glance; (4) adding a deal right where it belongs.

The board is where the day starts. Deals are dragged between stages, and the same deals open as a list, a calendar of closing dates or a timeline, without losing the filters.

Each card answers the questions a manager asks in a pipeline review, so the weekly review takes minutes instead of an hour.

Mobile is not a smaller web app. It keeps what matters between meetings: today’s activities, the deals closing this week, moving a stage, logging a call, and filters that fit a thumb.

Both apps share one component library and the same tokens, so a deal, a contact or a goal looks and behaves the same everywhere.

Analytics, team dashboards and goals turn the pipeline into a forecast managers can trust, and proposals are generated from the deal itself, with products, pricing and terms in one document.

The copilot was designed as a colleague, not as a chat window. It reads the pipeline, points out deals at risk and suggests the next step, and every suggestion shows where it came from, so the seller decides with context.

On the forecast screen the same logic explains the number: which deals hold the quarter and which ones depend on a single contact.

Sellers update the CRM between meetings, with one hand and little time. On the phone, moving a deal is a single gesture and a call turns into a summary with suggested actions, so the record is done before the next visit.

Managers needed to answer two questions without opening a spreadsheet: are we going to hit the goal, and who needs help. Goals, performance and ranking use the same components as the rest of the product, so the reading is immediate.

Speed is the feature. In a CRM, every second saved on an update is data that finally gets in, and better data is what managers are really paying for.

Designing web and mobile together, from the same model, kept the two from drifting apart and made the phone part of the system, not an afterthought.