What do you dislike about Pipedrive?
1. Activity Organization Inside Deals - Inside the deal window, there’s no way to organize or filter activities by type. Instead, you’re presented with one long, sloppy list of every activity that has ever happened on the deal. There should be a better way to separate or filter calls (inbound/outbound), emails, notes, sms or other activity types.
2. Leads and Deals Have Inconsistent Functionality - Leads and deals share the same custom fields, but leads lack much of the functionality available to deals.
For example: Math functions can be performed on deals but not leads. Deals have a changelog, but leads do not. This results in agents stealing leads and other agents editing lead information with no way of tracing who did it.
3. Automations Are Extremely Basic
- The automation system is very limited and does not have proper branching.
- Automations can only be triggered by a single action, which often forces you to create duplicate workflows that perform the exact same function.
- For example, if you have a "Scheduled" stage, you need two identical automations: One for when a deal is created directly in the Scheduled stage and another for when an existing deal is moved into the Scheduled stage.
4. The Platform Is Designed Around Manual Activities Instead of Automated Cadences - The system feels heavily designed around agents manually creating activities rather than businesses running structured, automated follow-up cadences. This makes building even relatively simple sales or follow-up sequences unnecessarily complicated.
5. No Way to Add or Remove Someone From Another Automation - There's no way to add or remove someone from another automation. Because of that, you have to repeatedly check the lead’s status before practically every action in a workflow.
For example, say you have a "New Lead" cadence that works like this:
Day 1: Create Call 1 → Lead doesn’t answer → Send an email and schedule Call 2 → Call 2 is marked complete → Send another email and schedule Call 3. If the lead is no longer active or has moved to another stage, there’s no way to simply remove them from the original automation. Instead, you have to add a condition such as “If lead still exists” before every subsequent action. Otherwise, the workflow will continue creating Call 3, sending additional emails, and performing the rest of the scheduled actions even though that lead should no longer be receiving them.
6. Custom Address Fields Do Not Include ZIP Codes - Custom address fields use the Google Maps API to prepopulate an address while you type, but the resulting address does not include the ZIP code. Developers have previously stated that this is simply “how the Google API works.” However, I was able to code a solution to retrieve the ZIP code in less than three minutes.
7. Inconsistencies Across the Platform and API - There are numerous inconsistencies throughout both the platform and the API.
For example: Some API endpoints require V1. Others require V2. Data is returned in inconsistent formats depending on the endpoint. Similar objects and functions behave differently throughout the platform. Review collected by and hosted on G2.com.
