We wrote up the SaaS "customer newsletter" case, plus a 15-minute ratio to price your own gap

Posting something we published this week for anyone here running a SaaS company or a company newsletter.

The premise: most SaaS teams ship 15 to 40 meaningful items a quarter and send their full customer list somewhere between zero and two emails explaining any of them. The changelog is complete, accurate, and visited by nobody.

The diagnostic in the post is the part worth stealing. Count the items you shipped last quarter that a customer would care about. Count the sends that told your whole list about any of them. Divide. That's your Ship-to-Tell ratio, and it's almost always a single digit. Everything under 100% is value you paid to build and then didn't distribute.

The post connects that gap to three dashboards: adoption (Pendo's data puts rarely-or-never-used features at 80% of the average product), renewals (the budget holder renews on what they remember, and they were never in the product), and expansion (an expansion dollar cost $0.20 to a new-customer dollar's $1.13 in the Pacific Crest survey, but only if the customer knows the upgrade exists).

Full post: https://blog.heynews.co/saas-customer-newsletter/

If your company ships weekly and announces almost nothing, run the ratio and tell me what you got. Happy to talk through what a first issue looks like for anyone weighing it.