TL;DR: Connected packaging has gone mainstream: nearly half of brands now put a QR code and an NFC chip on the same package, and the sales lift is becoming an expectation rather than an edge. If a funded competitor can copy your headline feature in a quarter, it was never your moat. Run every “differentiator” through the Copy Clock, and spend your scarce weeks on the parts you can’t demo.
TL;DR: Connected packaging has gone mainstream: nearly half of brands now put a QR code and an NFC chip on the same package, and the sales lift is becoming an expectation rather than an edge. If a funded competitor can copy your headline feature in a quarter, it was never your moat. Run every “differentiator” through the Copy Clock, and spend your scarce weeks on the parts you can’t demo.
Monday morning, before coffee had done anything useful, my market brief opened with a number that sat me down. Nearly half of consumer brands now put both a QR code and an NFC chip on the same package. A 2026 survey from Appetite Creative, a connected-packaging studio, put it at 47.1 percent (eCommerce Times). [VERIFY: 47.1% figure and that the survey is Appetite Creative’s, via eCommerce Times.]
I’ve spent months building a smart spice jar. You simply tap your phone’s sensor on the lid, and the jar reveals where the spice was grown, when it was ground, and the farmer who cultivated it. The tap feature is what I showcase during demonstrations, as it’s the element that often elicits an “oh, that’s clever’ response from viewers.
And my own brief was telling me that the tap has become just ordinary.
What I felt for about ten minutes was a small panic at the thought of watching your best trick become everyone’s baseline. Then I went back to something I already knew and had let myself forget. The feature you demo is almost never the feature that defends you.
We tend to focus on the demo-able feature because it’s the most visible. It photographs well, fits into a launch video, and the competitor can easily replicate it by the next quarter. The more flashy the feature, the shorter its competitive advantage lasts. I had previously believed that the most copyable aspect of my product was also the most defensible.
The Copy Clock
For every feature you’re tempted to call a differentiator, start a clock. One question sets it: how long would a competitor with money and motivation need to ship the same thing?
That’s the whole instrument. The number it gives back tells you what you’re actually holding.
Short clocks are table stakes. Anything you can demo in ten seconds usually has a short clock, because anything that reads instantly to a customer reads just as fast to a rival product team. The tap is a short clock. So is the AI chat box bolted onto a recipe app. I spent a week last month tearing down “AI spice” and “AI recipe” startups, and most of them were a chatbot in a chef’s hat. ChatGPT raised the floor in that category overnight, and the founders who had built their “type ingredients, get a recipe” mostly hadn’t noticed the floor had moved out from under the whole pitch.
Long clocks are moats. These are the parts you can’t fit in a ten-second demo: the supply you control, the preference data that compounds every time someone uses the product, the trust you earned one honest interaction at a time, the farmer who picks up the phone because he knows you. None of those screenshots works well. All of it takes a competitor years to reproduce, if they can start at all.
The connected packaging data makes the split concrete. Trade write-ups peg the sales lift from a tap or scan at 5-12% (QR Insights). A result like that is good news right up until it becomes typical. Once most of your category can claim it, the lift stops being an advantage and turns into the price of admission. The tap earns its keep. It just stopped being the reason anyone should choose me over the brand on the shelf next to mine.
Why do we keep defending the wrong layer?
A while back, I wrote about the Product Onion, the idea that a product has layers: the core problem at the center, then strategy, then features, then experience, then marketing on the outside. Features sit near the surface. The core problem and the strategy sit at the center.
Competitors copy from the outside in. They can see your features, so they take your features. They cannot see your strategy or the trust you’ve banked, so those are the last things to fall, if they fall at all. When you pour your scarce weeks into polishing an outer layer, you’re hardening the part of the onion that was going to get peeled anyway.
Maybe that sounds obvious written down. It did not feel obvious at 6 a.m. with a number telling me my favorite feature had gone mainstream. The pull toward the demo-able thing is strong because it’s where the applause is.
What gives a feature a long clock
When I look at the products that held their ground in my category, the long clocks come from a few specific places, and almost none of them are the result of clever engineering.
The owned supply is the heaviest one. A rival can buy the same dispenser and the same chip. He cannot buy my relationship with a grower he’s never met or a contract he can’t see. The defensibility lives in what I own that he’d have to go build from scratch.
Data that compounds is the quiet one. A recommendation trained on real flavor preferences gets better the longer it runs, and a competitor starting today starts at zero, no matter how good his model is. Time is doing work for you that money can’t shortcut.
Trust is the slowest and the most durable. It’s the freshness claim I’ll actually honor, the story behind the jar that turns out to be true when someone checks. You can’t demo trust. You can only accumulate it, and that’s exactly why it lasts.
What I’m doing this week
This week, I handed a build team the structure for our jar’s web experience, and I caught myself about to spend the good hours making the tap demo a little slicker. The Copy Clock stopped me. The tap is a short clock. Polishing it is rearranging the part of the product that a competitor will match, regardless.
So I’m running my own roadmap through the clock before I hand anything off. The provenance layer, the farmer stories, the refill model that makes leaving cost something: those are the long clocks, and those get my scarce weeks. The tap ships solid, and I stop fussing with it. I would rather be the brand whose moat a competitor can see clearly and still can’t cross.
If you’re building something right now, you probably have a favorite feature too. The one you open the demo with. Be a little suspicious of it. The applause it gets is real, and so is the speed at which someone else can earn the same applause.
FAQ
What’s the difference between a feature and a moat? A feature is something your product does. A moat is a reason a competitor can’t easily do the same thing. Plenty of great features are not moats, because a funded rival can ship them in a quarter.
How do I run the Copy Clock on my own product? List everything you call a differentiator. For each one, estimate honestly how many months a competitor with money and motivation would need to match it. Anything under about a quarter is table stakes. The long clocks are your real defensibility, even if they’re harder to show off.
Isn’t a table-stakes feature still worth building? Usually, yes. Table stakes are the price of being in the game, and skipping them loses deals. The mistake isn’t building them. It’s mistaking them for your advantage and spending your best time there.
What actually gives a feature a long copy clock? Most often one of three things: supply you control, data that compounds the longer customers use the product, or trust you’ve earned over time. None of them demo well, which is part of why they hold.
What’s the one thing I should do this week? Take your headline feature, the one in your demo, and estimate its copy clock out loud. If a competitor could match it in a quarter, move some of this week’s hours to the part of your product you can’t fit in a ten-second demo.
Related: The Product Onion in real product building and The Subtraction Audit.
Leave a Reply