All posts
2 min readby Romiel Inolino

Pipedrive Nova drafts CRM updates from sales calls, but a rep approves every change. That design choice is the story

PipedriveCRMsales automationAImeeting intelligence

Pipedrive built an AI notetaker that refuses to write to your CRM without permission. Good.

What happened

Pipedrive's Nova, an AI meeting intelligence tool built into the CRM, is generally available worldwide and included in all Pipedrive plans at no extra cost.

It works in three stages. Before a meeting, it pulls together deal history, emails and past conversations already logged in Pipedrive. During the meeting, it records through the desktop app or a visible notetaker in Google Meet, Zoom and Microsoft Teams. Afterward, it produces a transcript, a summary and next steps, and suggests CRM updates such as deal stage, value and expected close date. The rep reviews, edits and approves each change before it is saved. Admins get access controls, and users can configure participant consent and notification settings.

Australian proptech company Snug piloted it and says Nova saves its six-person sales team 30 minutes to an hour per meeting. Pipedrive's own research found 47% of sales professionals say follow-ups or CRM updates often take more than 24 hours, and only 23% would be very comfortable with AI completing tasks without review.

My take

A common Pipedrive setup is a separate notetaker, then a Zapier or Make flow that parses the summary and pushes fields into deals. If Nova covers that for free, that whole chain is a candidate for retirement, which means fewer API keys, fewer moving parts and fewer silent failures.

The approval step is the right default. AI that writes deal values straight into the pipeline will eventually write a wrong one, and forecasts built on that data inherit the error.

What I would check before switching:

  • Downstream triggers. Approved stage changes still fire your existing automations, so make sure those flows expect them.
  • Field mapping. Confirm Nova's suggestions land in the fields your reports actually use.
  • Consent. Configure participant notifications to match the rules where your clients operate.
  • Adoption. If reps skip the approval, the data stays stale. Track it.

More posts