- LaunchNotes
- Posts
- You Shipped It. They Never Knew. Here's the Price Tag.
You Shipped It. They Never Knew. Here's the Price Tag.
Adam Wardlow
April 17th, 2026
TL;DR: We've covered what communication debt is and what it costs your team. Now it's time to measure yours — in five inputs, on the back of a napkin — and identify where to start fixing it.
Over the last two issues, we've built the case for the importance of monitoring and managing communication debt.
In Q4’25, we introduced the concept: the compound interest product teams pay when announcements are an afterthought. We showed how Microsoft found that 90% of users requested features they already had, how U.S. organizations lose $2 trillion annually to communication failures, and how the consequences — confused customers, overwhelmed support, features dying in obscurity — show up externally first.
In Q1’26, we turned inward: the same debt that loses customers also drives your best people out the door. Poor internal communication costs $26,000 per employee annually. It's the fourth-biggest factor in turnover. 61% of employees have considered leaving because of it. External comms debt loses customers. Internal comms debt loses the team that could win them back.
The natural next question is: how bad is my problem, specifically?
That's what this issue is about.
Not the concept. Not the industry statistics. Your number — how much comms debt your team is carrying right now, and where to start paying it down.
From concept to calculation
There's a number your company isn't tracking.
It's not CAC. Not NRR. Not sprint velocity.
It's the gap between what your product does and what your customers, sales team, and customer success team actually know about. And unlike most business problems, this one is straightforward to quantify.
The three places comms debt accumulates fastest — which we covered in depth in previous newsletters — are worth keeping in mind as you run your own numbers.
Missing announcements. Features ship. Nothing goes out. You assume customers will notice. They don't.
Undifferentiated announcements. One email to everyone. Enterprise customers and SMB customers get the same message. Developers and executives get the same message. Nobody feels like it's for them.
Internal communication gaps. CS finds out what shipped from customers. AEs pitch last quarter's features. Support answers questions about capabilities that were fixed months ago.
None of these feel catastrophic in the moment. Together, they're a revenue leak — and we can put a number on it.
Run the numbers on your own team
The easiest way to make comms debt real is to run the numbers on your own business. Here's what it may look like for a Series A product team.
Scenario: 100 customers, $50K ACV, 20 features shipped per quarter, 30% communicated.
A team ships 20 features per quarter — solid velocity. They communicate about 30% of what they ship. The big releases get announcements. The smaller releases, enhancements, and bug fixes don't get the same attention.
The numbers
INPUTS | Customers: 100 | ACV: $50,000 |
|---|---|---|
Features shipped per quarter: 20 | ||
Features communicated: 6 (30%) | Features not communicated: 14 (70%) | |
ASSUMPTIONS | 10% of customers with full product visibility will start an expansion conversation | The average expansion conversation is worth 20% of ACV |
The math
WHAT | HOW | OUTCOME |
|---|---|---|
Expansion opportunity pool | 100 customers × 10% | 10 customers |
Missed due to poor communication | 10 × 70% not communicated | 7 missed conversations |
Value per expansion conversation | $50,000 ACV × 20% | $10,000 potential NRR expansion |
Quarterly exposure | 7 × $10,000 | ~$70K potential NRR expansion/quarter |
Annual exposure | $70K × 4 quarters | ~$280K potential NRR expansion/annual |
The takeaway
At a $50K ACV with 100 customers, $280K in annual missed expansion revenue is real money. But the more important problem is the pattern itself. Every quarter a team ships without a defined communication process, the habit calcifies. By the time the company has 500 customers, the cost is compounding and the behavior is locked in.
The fix: Pick the one feature not communicated most likely to trigger an upgrade conversation. Write one targeted announcement to the customers it actually affects. Don't try to fix all 14 at once — build the muscle first.
What this looks like at renewal: CSMs are walking into renewals with customers who know about 6 of 20 features. The other 14 are invisible — which means the product looks 30% as valuable as it actually is. That's not a pricing problem. It's a communication problem.
Communication debt doesn't announce itself. It’s a leading indicator. It shows up quietly in your churn rate, your expansion numbers, your CSMs winging it on renewal calls. The good news: unlike many business problems, it's entirely within your control to fix.
If you missed our earlier issues on comms debt, you can find them here: The Hidden Cost of Communication Debt → and The Looming Internal Communications Crisis →
Next issue: Why low feature adoption isn't a product problem — and what it actually is.
Running the math on your own numbers and finding something surprising? Hit reply. We’d love to hear what you discover.
About LaunchNotes
LaunchNotes is a product communication platform that helps teams announce, distribute, and measure product updates. We provide the infrastructure for professional product communication - from customizable templates and multi-channel distribution to analytics and feedback collection - so your team can focus on building great products while ensuring your users stay informed and engaged.