Naomi Ionita on Monetisation, Freemium Strategy, and the Modern Growth Stack

Naomi Ionita is a partner at Menlo Ventures focused on early-stage SaaS. She was previously an early growth leader at Evernote (10 to 100 million users) and VP of Growth at Invoice2go. She helped establish Reforge’s early growth curriculum and is one of the few investors whose operating background is specifically in product-led growth and monetisation.

Key ideas

Three monetisation mistakes: waiting too long to charge, underpricing (especially by offering a single tier), and setting pricing and never revisiting it. Each compounds over time; the third is the most common.
Match price to value metric: the right pricing unit is the unit of value the customer derives from the product. Usage-based pricing (API calls, documents created, invoices sent) creates a natural escalator — customers who use more pay more — and aligns the business’s incentive with the customer’s growth.
Day-one vs day-100 features: premium features should be things a new user can appreciate immediately. Advanced functionality that only makes sense after weeks of use belongs in an upsell tier, not in the initial free-vs-paid decision.
Single-player to multiplayer is the growth chasm: products that remain antisocial — usable by one person without any interaction with others — cap their growth potential. Crossing this chasm changes acquisition (referrals), retention (shared workflows), and monetisation (seat- and team-based pricing) simultaneously.
The Modern Growth Stack is an emerging software category: PLG infrastructure (product-led sales, experimentation, billing/metering, AI-powered go-to-market) that is maturing the same way the modern data stack did.

Episode content

When to start charging

Naomi argues that the cost of not charging early is higher than most founders expect. Giving a product away for free cheapens it in users’ eyes — people attribute a value proportional to what they pay. The absence of a price signal also removes the most important feedback loop: whether users value the product enough to pay for it.

The common counter-argument is that freemium builds a top of funnel. Naomi accepts this — she was at Evernote when freemium was at its peak — but distinguishes between freemium (a deliberate strategy to use free users as an acquisition channel) and free (giving away a product because you have not thought hard enough about monetisation). Freemium works when the free product is genuinely useful but the paid product provides a step change in value. It fails when the free product is so good that users feel guilty but not motivated enough to pay.

One survey finding from Evernote stuck with her: “I feel guilty” was one of the top reasons users upgraded to premium. If guilt is a leading purchase driver, the free version is too good and the paid version is not differentiated enough.

Pricing process

Naomi’s recommended process for setting initial prices:

Form a pricing committee: cross-functional, including product, growth, sales, and finance. Pricing decisions belong to no single department.
Talk to customers: understand which features they value most (relative ranking, not absolute) and their willingness to pay for different bundles. Use the Van Westendorp method — four survey questions that identify the price-too-cheap, good-value, expensive-but-acceptable, and too-expensive thresholds.
Identify your value metric: the unit of value customers get from your product. Seat-based pricing (legacy SaaS) is not wrong, but usage-based pricing aligns incentives better when there is a natural consumption unit.
Think about the customer journey: what does a new user value on day one? What do they only value at day 100? Segment the pricing around this journey rather than around arbitrary feature tiers.
Test geographically: before rolling out a pricing change in the US, test in Canada or Australia. The market is large enough to provide signal; the blast radius of a pricing mistake is bounded.

The Envoy story

Larry Gadea, founder of Envoy (visitor management), was in a conversation with a prospective enterprise customer that was going well. In the moment, he decided to charge ten times his normal price. The prospect accepted without hesitation. Gadea’s lesson: he had been wildly underpriced and had not found the ceiling.

Naomi uses this story to illustrate that most companies are underpriced, and that enterprise sales conversations are the fastest way to find the ceiling. She recommends that roughly 20–30% of enterprise deals result in price-based rejections — that is the signal that you are pricing near the upper bound.

Modern Growth Stack

Naomi’s investment thesis at Menlo centres on what she calls the Modern Growth Stack: the category of software tools that enable product and growth teams to do their work — specifically, the workflows that product data enables once it is in the data warehouse.

The thesis is structured around three themes:

Data: reverse ETL tools (Hightouch, Census) break down data silos and give business teams direct access to product data without querying through data scientists.

Workflow: purpose-built tools for growth work (experimentation platforms, personalization engines, billing and metering systems) replace the internal tooling that companies like Invoice2go had to build in-house. This frees engineering capacity for product differentiation.

Impact: the clearest ROI story in software — a 1% improvement in monetisation has 4× the bottom-line impact of a 1% improvement in acquisition (ProfitWell data). Tools that improve monetisation directly can quantify their ROI.

Product-led sales is the most mature segment of the Modern Growth Stack. Companies like Endgame and Pocus help PLG businesses convert free users to enterprise contracts by surfacing product usage signals to sales teams.

Evernote’s failure

Naomi is candid about where Evernote went wrong. The product was great at being a personal second brain — but it was philosophically antisocial. It was designed for one person, and it never built the collaborative workflows that would have driven organic expansion across teams and organisations.

The lesson: you cannot retrofit collaboration. A product that was built single-player cannot become multiplayer by adding sharing features after the fact. The architecture, the UX, and the mental model must be collaborative from the start. Products that solve this — Figma, Notion, Linear — grew because collaboration was not a feature but a design premise.

Figma’s trajectory illustrates the single-player-to-multiplayer bridge done right: give away design to individual designers for free (broad adoption, organic love), then monetise when design spreads across engineering, product, and marketing teams. The team and enterprise pricing unlocked naturally because the product was built for that transition.