Blog
Notes on value distribution: getting what your product team builds to the customers and prospects it matters to.
Fewer, better messages to your customers
Why a frequency cap and a relevance gate protect deliverability and trust, and why most accounts should hear nothing about most releases.
6 min readTell customers what a change did for them, in their own numbers
How to measure what a release did in each customer's own data, when the number is honest enough to send, and what to say when you can't measure.
6 min readYour champion has to sell you again every year
The person who bought your product defends that budget every year. Here is what proof they can actually use looks like, and how to write it for the forward.
5 min readRenewing with proof: the brief that should open every renewal call
Silent churn starts long before the renewal date. A renewal brief built on what improved for the account changes the first five minutes of the call.
6 min readClosing the loop on feature requests: tell the people who asked
When a requested feature ships, the people who asked rarely hear it from someone they know. A practical process to capture, match and tell them.
6 min readAI moved the bottleneck from building to adoption
AI coding tools made shipping cheaper. Getting each customer to notice and use what shipped is now the slow part, and launch playbooks don't cover it.
6 min readReopening closed-lost deals with product changes
Most lost deals were lost to timing, not missing features. A relevant product change gives your rep an honest reason to reach back out.
5 min readWhy your release notes don't reach the people who need them
Release notes fail on distribution, not writing. Keep the changelog as the record and send each account a short note about what changed for them.
5 min readThe value distribution gap: why customers stop noticing what you ship
Your team ships every week, but each customer's picture of the product freezes at the last demo. Here is why that gap forms and how to close it per account.
6 min read