Key takeaways
- An update matters to a prospect only if it touches a problem they named.
- One feature per email; a release list buries the one that counts.
- It works best for reopening stalled deals and earlier objections.
- Describe what the feature lets them do, not how it was built.
When is a product update a reason to reach out
A product update is a good reason to reach out when it removes an objection the prospect raised, closes a gap they asked about or makes a stalled evaluation worth restarting. In those cases the email is news to them, not a newsletter.
It is a weak reason when the update matters to you but not to them, or when the prospect never got far enough to have a view. For cold contacts, lead with their problem and mention the feature only if it is the clearest example.
How to find who cares about a new feature
Search your notes and lost deals for the problem the feature solves. Prospects who said 'come back when you can do this' are the first list; those who stalled on a related concern come next.
Check each account's notes before you send, because the person may have chosen another tool since or the need may have gone. New feature outreach to someone who has moved on only shows you did not look.
How a what's new email for prospects differs from a customer announcement
A prospect email reconnects the update to a decision they put off, while a customer announcement tells existing users how to use something. The prospect version is shorter, personal and ends with a question about their situation, not a link to release notes.
Send customer announcements from your product or marketing team, and prospect emails from the seller who held the original conversation.
What mistakes do B2B teams make in feature announcement emails
The commonest mistake is writing about the product rather than the prospect's problem. Others are easy to slip into as well:
- Implying you remember a conversation you never had.
- Announcing a feature before it is generally available, or without saying it is in beta.
- Bundling five updates so the one that matters gets lost.
- Promising results from the feature that you cannot yet show.
How to use a product update in outreach, step by step
Start from the people who asked for the change, not from the release notes.
- Find the prospects who named the problem the update solves, in your notes and lost deals.
- Check each account is still a fit and the contact is still there.
- Write one sentence linking their earlier concern to the change.
- Say what the feature now lets them do, and whether it is in beta.
- Ask one question about whether it changes anything, rather than asking for a demo.
The product update email
Send it to a prospect who raised the problem this update solves. Change the first paragraph first, so it states their concern accurately.
Subject: [the capability they asked about] is now in [product]
Hi [first name],
When we spoke in [month], you said [the concern or gap they raised] was the main reason [company] held off. That stayed with me.
Since [date], [product] [what the update does, in one sentence]. For your team, that would mean [what it lets them do now].
Does that change anything on your side, or has the priority moved on since? Either answer is useful to know.
Best wishes,
[your name]
If the feature is in beta, say so in the third paragraph. Leave other releases out; one update per email keeps the reason clear.
Where Pebbles Ai fits
- CapabilityProspecting & customer recordsNotes and deals in the CRM, in Beta, hold what each prospect said when they paused, so you can find who asked for the change. If those records live in Attio or Pipedrive, the assistants read them through MCP.
- CapabilityOutreach contentAn assistant drafts the update email for each prospect in chat, in the personality you choose, and saves the drafts in your connected Gmail or Outlook mailbox for you to check.
Common questions
Should you send a product update to cold prospects?
Rarely. A cold prospect has no context for the update, so lead with their problem and use the feature as one example.
How often should a prospect hear about product updates?
Only when an update touches their problem, which may be once or twice a year. Regular release emails belong in a newsletter they opted into.
Will Pebbles Ai follow up if the prospect does not reply?
Not on its own. Pebbles Ai does not schedule follow-ups; when you ask, an assistant drafts one from the thread, and sending follows your execution mode.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .
