Day One vs Day 100 Feature Packaging
Free the features that create the aha moment; monetize the features whose value only emerges at scale.
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 3
- Confidence
- 90%
A packaging heuristic for deciding what belongs in free versus paid. Day One features deliver value in the very first session and drive habit formation, so they should be free. Day 100 features are advanced functionality whose value depends on accumulated data, scale, or collaboration — push these into a paid tier and monetize them via upsell.
Origin
Developed by Naomi Ionita from a pricing-and-packaging experiment at invoice2go where the team rebalanced plans around this distinction.
Core principles
- 01The core utility that produces the aha moment must be free to collapse time-to-value
- 02Advanced value that requires scale or accumulated data is a later upsell, not a first-session feature
- 03Don't waste a new user's cognitive load asking them to appreciate features they can't yet benefit from
How to run it
- 1
Identify the Day One aha feature
Pinpoint the core utility that makes a first-time user say they will never go back to the old way. This is the path to habit formation and it belongs in the free plan.
Pro tip Also keep any feature that drives virality or network effects free — those users manage your CAC by driving organic growth.
- 2
Isolate the Day 100 features
Separate out advanced functionality whose value is derived from having a certain scale of data in the platform or from more mature usage. New users cannot appreciate these yet.
Watch out Surfacing Day 100 features to brand-new users adds cognitive load and clutters the value they came for.
- 3
Map packaging to the user journey
Push Day 100 features into a more advanced Pro tier and monetize them down the road via upsell, so the pricing page tracks how a user's value grows over time rather than dumping a gnarly feature matrix on them.
Pro tip Keep pricing simple — map plans to the journey from single-player to multiplayer to team to enterprise.
Watch out Avoid the SaaS pricing page that is a laundry list or gnarly matrix of features; it obscures the upgrade path.
In the wild
By rebalancing pricing and packaging around Day One versus Day 100 features, invoice2go doubled the upgrade rate from the Starter plan to the Pro plan while simultaneously raising the Pro plan price roughly 30%.
→ Twice as many upgrades at a ~30% higher price — a rare compounding win that normally fights the inverse relationship between price and conversion.
Common mistakes
Putting advanced features in front of new users
Day 100 features whose value depends on scale confuse first-time users and add cognitive load instead of accelerating the aha moment.
Making the pricing page a feature laundry list
A gnarly matrix of functionality hides the natural upgrade journey; simple packaging mapped to the user lifecycle converts better.
Is it for you?
Best for
PLG and freemium product teams deciding what to gate behind a paid tier
Not ideal for
Products whose core value only materializes at scale, where there is no obvious free Day One hook
From the transcript
“what is a day One Premium feature what is a premium feature that you can get value from the very first time you engage with…”
“we actually doubled our upgrade rate from our starter plan to our Pro Plan while also increasing the price of the Pro Plan”
“those you shouldn't waste through cognitive load for your users to have to even understand or try to appreciate when they're first getting going push…”
From the episode
How to price your product
Naomi Ionita (Menlo Ventures)