How to Submit Feature Requests to Pipedrive That Actually Get Implemented

The Ultimate Guide to Pipedrive Feature Requests

Where to Submit Feature Requests:

Method 1: Pipedrive Ideas Board (Best)

1. Visit: ideas.pipedrive.com
2. Search if idea already exists (upvote instead of duplicating)
3. Click "Submit Idea"
4. Choose category (Sales, Marketing, Reporting, Mobile, etc.)
5. Write clear, detailed description
6. Submit and share with colleagues to get upvotes

Why this is best: Public voting system. Pipedrive prioritizes ideas with most votes.

Method 2: In-App Feedback

1. Click "?" icon in Pipedrive
2. Select "Give Feedback"
3. Choose "Feature Request"
4. Describe your idea

Pros: Direct to product team
Cons: No voting, harder to track status

Method 3: Account Manager (Enterprise Only)

• If you're on Enterprise plan with dedicated account manager
• They can escalate requests directly to product team
• Higher chance of consideration for large accounts

Method 4: Community Forums

• Post in Pipedrive Community forums
• Gauge interest from other users
• Pipedrive product managers monitor forums

How to Write Feature Requests That Get Approved:

1. Explain the PROBLEM, Not Just the Solution

❌ Bad example:

"Add a button to export deals to Excel with custom formatting."

✅ Good example:

"**Problem:** Our CFO needs weekly deal reports in a specific format for board meetings. Currently, I have to export from Pipedrive, then spend 30 minutes reformatting in Excel. **Impact:** This wastes 2 hours/month and risks manual errors. **Proposed solution:** Allow custom export templates where I can pre-define which fields to include, column order, and basic formatting. Then one-click export saves me 30 min/week."

2. Quantify the Impact

Include numbers:

• How many users affected?
• Time saved per week/month?
• Money saved or revenue increase?
• Current workaround cost?

Example:

"This would save our 15-person sales team 3 hours/month each = 45 hours/month = $2,250/month in productivity (at $50/hour)."

3. Show Demand

• Share request link with colleagues/network to get upvotes
• Reference how many users in your company need this
• Link to similar requests from community
• Mention if competitors have this feature

4. Provide Use Case Examples

Format:

• As a [role]
• I want to [do something]
• So that [achieve goal]

Example:

**As a** sales manager **I want to** see which team members are stuck on specific deal stages **So that** I can provide targeted coaching and prevent deals from stalling

5. Suggest Implementation (Optional)

• Show mockups or screenshots from similar tools
• Explain how it could work technically
• Note: Don't dictate exact solution - let Pipedrive design

What Increases Chances of Implementation:

✅ High Success Factors:

• High vote count: 100+ votes significantly increases priority
• Aligns with Pipedrive roadmap: Fits their strategic direction
• Benefits many users: Not niche or edge case
• Technically feasible: Doesn't require massive re-architecture
• Enterprise customer request: Large accounts get priority
• Competitive gap: If competitors have it, Pipedrive wants parity

❌ Low Success Factors:

• Duplicate of existing feature (you didn't search first)
• Very niche use case (affects <1% of users)
• Already possible via workaround/integration
• Conflicts with Pipedrive's product philosophy
• Would require breaking changes to existing features

Pipedrive's Product Development Cycle:

Typical timeline from request to release:

1. Submit idea: Day 0
2. Initial review by product team: 1-2 weeks
3. Community voting period: 1-6 months
4. Added to roadmap: If hits threshold (100-200 votes)
5. Discovery & design: 1-3 months
6. Development: 1-4 months (depends on complexity)
7. Beta testing: 1-2 months
8. Public release: Total: 6-12 months from idea to launch

Fast-track scenarios:

• Critical bug fix disguised as feature: 1-2 weeks
• Simple UI improvement: 1-2 months
• Quick win (easy to build, high impact): 2-3 months

How to Track Your Request:

1. Bookmark your idea on ideas.pipedrive.com
2. Enable email notifications for updates
3. Status labels:
   • "Under Review": Product team is evaluating
   • "Planned": Approved, on roadmap
   • "In Progress": Being developed
   • "Shipped": Released!
   • "Declined": Won't be built (includes reason)

Examples of Successful Feature Requests:

Example 1: Bulk Edit Custom Fields (2,547 votes → Shipped)

Original request: "Allow editing custom fields for multiple deals at once instead of one-by-one."

Why it succeeded: Clear problem, high demand, technically straightforward

Example 2: Deal Rotation (1,893 votes → Shipped)

Original request: "Automatically assign incoming leads to sales reps in round-robin fashion."

Why it succeeded: Many teams needed this, competitive gap

Example 3: Custom Dashboard Widgets (756 votes → Declined)

Original request: "Let us build our own custom chart types."

Why it failed: Technically complex, small percentage of power users would use it

What to Do If Your Request Is Declined:

1. Read the decline reason: Pipedrive explains why
2. Look for workarounds: Often they suggest alternative solutions
3. Consider third-party integrations: Zapier, Make, custom API
4. Re-submit with modifications: If you can address their concerns

Alternatives If Pipedrive Won't Build It:

1. Custom API Integration

• Build exactly what you need using Pipedrive API
• Hire developer or use no-code tools (Zapier, Make)

2. Marketplace Apps

• Check Pipedrive Marketplace for existing solutions
• Third-party developers often fill gaps

3. Switch CRMs

• If feature is critical and Pipedrive won't build it
• Evaluate if another CRM has it natively
• Consider switching cost vs benefit

Power User Tips:

1. Rally Support Before Submitting

• Discuss idea in community forums first
• Gauge interest before formal submission
• Have 10-20 people ready to upvote immediately

2. Tag Pipedrive Team Members

• Pipedrive employees are active in community
• Politely tag relevant product managers
• Don't spam, but one mention is okay

3. Share in LinkedIn/Twitter

• Post your feature request link
• Ask your network to upvote
• Use hashtag #PipedriveIdeas

4. Bundle Related Requests

• Instead of 5 small requests, combine into one cohesive feature
• Example: Instead of "Add filter A", "Add filter B", "Add filter C"
• Write: "Enhance filtering with A, B, C capabilities"

Red Flags That Will Get Your Request Ignored:

• ❌ Demanding/entitled tone ("You MUST add this or I'll cancel")
• ❌ No context (one-sentence request with no explanation)
• ❌ Duplicate without searching first
• ❌ Requesting complete CRM redesign (not realistic)
• ❌ Feature that only benefits you personally

Pro Tip: The absolute best way to get a feature built is to become a beta tester, provide excellent feedback on existing features, and build goodwill with the product team. They prioritize requests from engaged, constructive community members!