Pipedrive is the rare B2B product whose main screen you can describe in one sentence: a kanban board of deals, left to right, from first contact to closed. Everything else in the product is either feeding that board or reporting on it. That clarity is the reason it grew from a Tallinn startup into one of Europe's best known SaaS companies, and it is also the source of most of its rough edges.
Disclaimer
Independent teardown, no affiliation with Pipedrive. Observations are based on the publicly available product and trial experience at the time of writing. Products change; treat specifics as a snapshot, the patterns as the point.
What Pipedrive gets right
1. The pipeline is the home screen
Most CRMs open on a dashboard: charts, widgets, a to-do list, a feed. Pipedrive opens on the work. The pipeline view answers the only question a salesperson has at 9am, "what is moving and what is stuck", without a single click. Deal cards carry the value, the owner, and a colour-coded status of the next activity, so the board reads as a heat map of attention.
The lesson for any SaaS: the home screen should be the object your user thinks in. For sales that is the deal. For a design tool it is the file. For a support product it is the queue. Dashboards are for managers, and managers are rarely the daily user.
2. Activity-based selling is enforced by the UI, not the manual
Pipedrive's philosophy is that you control activities, not outcomes, so the product nags you into always having a next step scheduled on every open deal. A deal with no planned activity gets a warning marker; a deal that has sat too long "rots" visually. This is behavioural design done with restraint: no gamification, no confetti, just a card that looks slightly unwell until you decide what happens next.
3. Drag and drop that means something
Moving a card between stages is the primary action, and it is fast, forgiving, and reversible. Dropping into the final stage prompts the won/lost decision inline rather than opening a form. The interaction cost of the most common action is close to zero, which is what a daily-use tool should optimise for above everything else.
4. Quick add from anywhere
The global add button and the inline "add deal" affordance at the top of each stage mean a rep never has to leave context to capture something. Speed of capture is where CRMs win or lose adoption, and Pipedrive clearly knows it.
Where the friction sits
1. Filters and saved views hide their power
The filter system is genuinely capable, but it lives behind a small control that looks like a secondary option. New users work a single default view for weeks before discovering they can save a "my deals, this quarter, over 10k" view and pin it. The most powerful feature of the pipeline is the least discoverable one.
2. Settings sprawl
As the product grew, custom fields, pipelines, automations, permissions, and integrations accumulated into a settings area that reads like a filing cabinet. Each screen is fine; the whole is hard to navigate because the information architecture grew by accretion rather than design. This is the classic scale-up tax, and it is visible.
3. The deal detail page tries to be everything
Open a deal and you get contacts, activities, notes, emails, files, products, and history in one long, dense page. It is complete, which is good, but the hierarchy flattens: the next scheduled activity, arguably the single most important fact, does not visually outrank a file attached three months ago.
4. Feature accretion in the left nav
Leads inbox, Deals, Projects, Campaigns, Products, Insights, and more. Each addition made commercial sense; together they dilute the "we are the pipeline company" story the home screen tells so well. A new user sees a general-purpose suite, which is a harder thing to fall in love with.
What I would change first
- Promote saved views to first-class tabs above the pipeline. Make "My deals", "Team", and a user's own saved views visible by default. Discoverability of filters is the cheapest retention win on the board.
- Give the deal page a fixed "next step" header. Value, stage, owner, and the next scheduled activity pinned at the top, with the long feed below. The card on the board already knows what matters; the detail page should agree.
- A guided settings map. Not a redesign, a wayfinding layer: group settings by job ("set up how deals move", "set up who sees what") rather than by object. Same screens, new front door.
Takeaways for SaaS founders
- Pick the one object your user thinks in and make it the home screen. Earn the dashboard later.
- Make your product's philosophy visible in the interface. Pipedrive's "always have a next step" is a UI state, not a blog post.
- Watch for accretion. Every feature that makes sense on its own still costs clarity in aggregate, and clarity was the original product.
Next in this series: an HR platform, where the tension is between employee self-service and admin power. If there is a European product you want torn down, tell me.
