The Take
The biggest hidden cost in a subscription business is losing customers without anyone making a clear decision about it. Last week, I talked about how reorders work. This week, I discovered a type of churn I hadn’t noticed before.
Last week, I suggested ranking features based on how they affect retention, not just how they sound in meetings. This week, a new benchmark revealed a whole group of customers I’d missed: those who leave because their card expired, not by choice.
One number really caught my attention: in subscription-box businesses, up to 68% of cancellations happen without the customer choosing to leave. It’s often a failed or expired card, or a billing error. The system fails, and you lose the customer. For boxes priced between $10 and $25, involuntary churn is about 1.3% per month. For boxes at $250 and up, it drops to about 0.18%. At $39, you’re right in the range where payment issues cause the most churn.
The real challenge is how you handle that number. Involuntary churn is a problem for the growth team, something you fix later with a dunning tool once you have enough customers. But solutions like card-updater support, automatic retries for failed charges, and a pause button instead of cancel are decisions you make when you build the product. They’re easy to add early and much harder to add later. It might look like an operations task for next year, but it’s actually a decision you need to make now.
There’s another important number: 52% of people who canceled a subscription last year did so because they weren’t using it. If you offer a pause instead of a cancel option, pause usage jumps by 337%. So the two main reasons customers leave a card you could have updated, and a subscription you could have paused, are both things you can design for early, or end up paying for later.
When you plan your first build, the obvious features stand out: the storefront, checkout, and product pages. The billing system sits in the background and can seem optional. But in your profit and loss statement, it’s not optional; it’s your retention model. Make sure payment resilience and a pause option are part of your first milestone, even before anything you’d show off in a demo.
This week, as I write the scope for my own first build, I realized I was putting all three of these features into phase two. They actually belong in phase one. I’m reminding myself: the churn you don’t notice still counts, and you decide how much of it you’ll accept before you even start building the storefront.
Spice Route Signal
Connected packaging reached 81.2% adoption this month. Now, the chip on the package isn’t the main story anymore; the real focus is on where that chip leads.
Appetite Creative’s fifth annual connected-packaging survey just came out, and the numbers are clear. Adoption is at 81.2%, and skepticism is down to 7.7%. Around 92.3% of professionals think the category will keep growing, and 83.3% are planning QR-code campaigns this year. The hardware is keeping up: on August 12, a tag maker made its NFC inlays smaller than a pencil eraser, so even tiny or oddly shaped packages can use them now.
Think about that adoption number from an investor’s perspective. When four out of five brands already have a chip under the label, saying ‘our jar has a chip’ doesn’t set you apart; it’s just the baseline now. I spent a year explaining why tapping mattered, but that’s no longer needed. The market has moved on.
What’s still uncommon is what happens after someone taps. Connected packaging gets average scan rates of 14% or more, compared to just 0.1% for regular digital ads, and people spend about three minutes per interaction. That’s a huge opportunity, but only if what you offer is worth those three minutes. An ingredient panel isn’t enough. A story about a farm, a cultural journey, or a one-click reorder could be. Now, the focus should be on creating a great destination, not just having the technology.
[Source: Appetite Creative fifth annual Global Connected Packaging Survey (adoption 81.2%, skepticism 7.7%, scan rate 14% vs 0.1%), via LBBOnline, Aug 2026; Identiv ID-Tiny miniaturized NFC inlay expansion, via Packaging Insights, Aug 12 2026.]
From the Trenches
For 59 days, the co-packer conversation was waiting on their end. This week, it came back to me, and I almost let it sit again.
Let’s start with some good news: there’s real progress this week. The co-packer finally replied after 59 days, so now it’s my turn to respond. The issue she mentioned can be fixed with one email: I need to send the cut sizes and ingredient quantities from the spec she already has, fix a small misunderstanding, and ask about the minimum run volume instead of committing to a number I’m not ready for. One reply could reopen a conversation I thought was over.
The bigger risk for the whole project is the lids. The deposit for the cap mold has finally cleared, so now the only thing left is to email the lid supplier with two questions: when does production start, and when will it ship? I’ve written the email, but I haven’t sent it. For two weeks, this has been the most important email on my list, and it’s still sitting in my drafts. The only thing holding it up now is me.
There’s also a small financial task. I need to reconcile a $644 payment to the label printer, which should only take ten minutes. The report that would confirm it has been sitting unread since Monday. If the payment went through, I release the second invoice and don’t need to send anything else. But I still haven’t checked the report.
And there’s one more thing that connects back to The Take. After signing the developer contract last week, I still need to send him a definition of done for the first milestone. This is the real decision of the week, not just another task. It’s where I choose whether payment resilience and a pause option go into milestone one or get pushed to later. It’s a message that would take ten minutes, but I keep putting it off.
None of these tasks make for a good photo: an unsent reply, an unread report, a scope I haven’t written. But each one is a small action that stands between me and a much bigger milestone. That’s why they’ve taken up my whole week.
From the Rack
Fenugreek gives a blend its signature smell, but it’s the one seed most people can’t identify by name.
Fenugreek is the subtle backbone of The Silk Road. The seeds are small, hard, and amber-colored. On their own, they taste harsh and a bit bitter, with a smell somewhere between maple and burnt sugar. If you toast them too long, they turn acrid and can ruin the whole pan. Nobody eats fenugreek for pleasure, but it’s the scent that tells your nose ‘this is a real blend’ before you can name any other spice. Leave it out, and the mix feels flat and one-dimensional, even if you can’t say exactly what’s missing.
Here’s the lesson from the spice rack: your billing system is like fenugreek. In a subscription business, features like failed-payment retries, card updaters, and pause buttons are the hidden backbone. No customer signs up because your billing is great, but if you leave these out, your business slowly loses its structure, one expired card at a time. The most important ingredient is rarely the one you advertise. Find your fenugreek and build it first.
On My Desk
<!– Masthead: use the fixed “The PM’s Spice Rack” logo image at the top of every issue. No per-issue feature image. –>
The PM’s Spice Rack, Issue #20
August 14, 2026 | The Product Manager’s Journal
The Take
The biggest hidden cost in a subscription business is losing customers without anyone making a clear decision. Last week, I talked about how reorders work. This week, I discovered a type of churn I hadn’t noticed before.
Last week, I suggested ranking features based on how they affect retention, not just how they sound in meetings. This week, a new benchmark revealed a whole group of customers I’d missed: those who leave because their card expired, not by choice.
One number really caught my attention: in subscription-box businesses, up to 68% of cancellations happen without the customer choosing to leave. It’s often a failed or expired card, or a billing error. The system fails, and you lose the customer. For boxes priced between $10 and $25, involuntary churn is about 1.3% per month. For boxes at $250 and up, it drops to about 0.18%. At $39, you’re right in the range where payment issues cause the most churn.
The real challenge is how you handle that number. Involuntary churn is a problem for the growth team, something you fix later with a dunning tool once you have enough customers. But solutions like card-updater support, automatic retries for failed charges, and a pause button instead of cancel are decisions you make when you build the product. They’re easy to add early and much harder to add later. It might look like an operations task for next year, but it’s actually a decision you need to make now.
There’s another important number: 52% of people who canceled a subscription last year did so because they weren’t using it. If you offer a pause instead of a cancel option, pause usage jumps by 337%. So the two main reasons customers leave a card you could have updated, and a subscription you could have paused, are both things you can design for early, or end up paying for later.
When you plan your first build, the obvious features stand out: the storefront, checkout, and product pages. The billing system sits in the background and can seem optional. But in your profit and loss statement, it’s not optional; it’s your retention model. Make sure payment resilience and a pause option are part of your first milestone, even before anything you’d show off in a demo.
This week, as I write the scope for my own first build, I realized I was putting all three of these features into phase two. They actually belong in phase one. I’m reminding myself: the churn you don’t notice still counts, and you decide how much of it you’ll accept before you even start building the storefront.
Spice Route Signal
Connected packaging reached 81.2% adoption this month. Now, the chip on the package isn’t the main story anymore; the real focus is on where that chip leads.
Appetite Creative’s fifth annual connected-packaging survey just came out, and the numbers are clear. Adoption is at 81.2%, and skepticism is down to 7.7%. Around 92.3% of professionals think the category will keep growing, and 83.3% are planning QR-code campaigns this year. The hardware is keeping up: on August 12, a tag maker made its NFC inlays smaller than a pencil eraser, so even tiny or oddly shaped packages can use them now.
Think about that adoption number from an investor’s perspective. When four out of five brands already have a chip under the label, saying ‘our jar has a chip’ doesn’t set you apart; it’s just the baseline now. I spent a year explaining why tapping mattered, but that’s no longer needed. The market has moved on.
What’s still uncommon is what happens after someone taps. Connected packaging gets average scan rates of 14% or more, compared to just 0.1% for regular digital ads, and people spend about three minutes per interaction. That’s a huge opportunity, but only if what you offer is worth those three minutes. An ingredient panel isn’t enough. A story about a farm, a cultural journey, or a one-click reorder could be. Now, the focus should be on creating a great destination, not just having the technology.
[Source: Appetite Creative fifth annual Global Connected Packaging Survey (adoption 81.2%, skepticism 7.7%, scan rate 14% vs 0.1%), via LBBOnline, Aug 2026; Identiv ID-Tiny miniaturized NFC inlay expansion, via Packaging Insights, Aug 12 2026.]
From the Trenches
For 59 days, the co-packer conversation was waiting on their end. This week, it came back to me, and I almost let it sit again.
Let’s start with some good news: there’s real progress this week. The co-packer finally replied after 59 days, so now it’s my turn to respond. The issue she mentioned can be fixed with one email: I need to send the cut sizes and ingredient quantities from the spec she already has, fix a small misunderstanding, and ask about the minimum run volume instead of committing to a number I’m not ready for. One reply could reopen a conversation I thought was over.
The bigger risk for the whole project is the lids. The deposit for the cap mold has finally cleared, so now the only thing left is to email the lid supplier with two questions: when does production start, and when will it ship? I’ve written the email, but I haven’t sent it. For two weeks, this has been the most important email on my list, and it’s still sitting in my drafts. The only thing holding it up now is me.
There’s also a small financial task. I need to reconcile a $644 payment to the label printer, which should only take ten minutes. The report that would confirm it has been sitting unread since Monday. If the payment went through, I release the second invoice and don’t need to send anything else. But I still haven’t checked the report.
And there’s one more thing that connects back to The Take. After signing the developer contract last week, I still need to send him a definition of done for the first milestone. This is the real decision of the week, not just another task. It’s where I choose whether payment resilience and a pause option go into milestone one or get pushed to later. It’s a message that would take ten minutes, but I keep putting it off.
None of these tasks make for a good photo: an unsent reply, an unread report, a scope I haven’t written. But each one is a small action that stands between me and a much bigger milestone. That’s why they’ve taken up my whole week.
From the Rack
Fenugreek gives a blend its signature smell, but it’s the one seed most people can’t identify by name.
Fenugreek is the subtle backbone of The Silk Road. The seeds are small, hard, and amber-colored. On their own, they taste harsh and a bit bitter, with a smell somewhere between maple and burnt sugar. If you toast them too long, they turn acrid and can ruin the whole pan. Nobody eats fenugreek for pleasure, but it’s the scent that tells your nose ‘this is a real blend’ before you can name any other spice. Leave it out, and the mix feels flat and one-dimensional, even if you can’t say exactly what’s missing.
Here’s the lesson from the spice rack: your billing system is like fenugreek. In a subscription business, features like failed-payment retries, card updaters, and pause buttons are the hidden backbone. No customer signs up because your billing is great, but if you leave these out, your business slowly loses its structure, one expired card at a time. The most important ingredient is rarely the one you advertise. Find your fenugreek and build it first.
On My Desk
Churnkey is on my radar this week. Churnkey caught my attention because it addresses the exact problem I talked about in The Take.o file under phase two. Failed-payment recovery with smart retries, card-updater support, and a cancel flow that offers a pause before it offers a goodbye. Reading through it while writing my own milestone scope made the point sharper than any benchmark did: involuntary churn is a product surface, not a billing afterthought, and somebody built a company on the gap between those two ideas.
What stands out is how they look at the problem. Most teams see a failed charge as just an accounting issue and a cancel click as a lost customer. Churnkey treats both as design problems you can fix. You don’t need to buy their product to learn from this. If your solution to churn is a tool you add later, the cheaper fix is usually a decision you could have made from the start.
That’s the Rack
Thanks for reading Issue #20. I’m Dan Blizinski, founder of Trevean Spice and the writer behind The Product Manager’s Journal. I focus on PM frameworks grounded in real experience building things, not just theory.
New here? Grab the free Startup PM Toolkit. Five frameworks I actually use, not just talk about.
What’s one part of your billing system you’ve been putting off until phase two? Reply and let me know—I read every message.
The PM’s Spice Rack is published weekly on The Product Manager’s Journal and on LinkedIn. Subscribe to get it in your inbox.
What stands out is how they look at the problem. Most teams see a failed charge as just an accounting issue and a cancel click as a lost customer. Churnkey treats both as design problems you can fix. You don’t need to buy their product to learn from this. If your solution to churn is a tool you add later, the cheaper fix is usually a decision you could have made from the start.
That’s the Rack
Thanks for reading Issue #20. I’m Dan Blizinski, founder of Trevean Spice and the writer behind The Product Manager’s Journal. I focus on PM frameworks grounded in real experience building things, not just theory.
New here? Grab the free Startup PM Toolkit. Five frameworks I actually use, not just talk about.
What’s one part of your billing system you’ve been putting off until phase two? Reply and let me know—I read every message.
Leave a Reply