Written by:

Tony Yang

Share this post:

In our recent Mucker Growth Series webinar session, we invited Jeffrey Tjiok and Jack Benson from Simon-Kucher to break down how startups can build pricing into their DNA from day one.

They started off with a story about Google Glass and MoviePass to highlight the point that an innovative product can still fail without a sound monetization strategy. One launched at $1,500 with an interesting design that almost nobody asked for. The other offered unlimited movies for $9.95 a month — which, if you do the basic math of buying each ticket at $15, was never going to work. Both products made headlines. Both are gone. And they both failed for the exact same reason: monetization was an afterthought.

The big takeaway they drove home before diving into the content: price before product. Monetization isn’t something you figure out after you’ve built the thing. It’s something you think through as you’re building it — ideally even before.

With that set up, here’s a deep dive into the three major sections we covered.

Part 1: Building a Monetization Engine That Works

Price Model vs. Price Point — and Why the Model Matters More

When most founders think about pricing, they jump straight to the number. What should I charge? $49/month? $499? But there’s a compelling case that the how you charge — the price model — is actually more important than the how much you charge. Pricing is not about a single number; it is a system comprising Metrics (what you charge for), Structure (how you charge), and Price Point (the specific dollar amount).

Say you’re in the market for software that optimizes your company’s AWS spend. You’ve got two options, both projected to cost you $10K per year:

  • 1% of your annual cloud spend
  • 10% of every dollar saved

Both options result in the same total cost of ownership. But which one is an easier sell to your CFO? Option 2 by a mile. Why? Because the metric — the unit of value you’re charging on — is directly tied to the outcome the customer actually cares about. ProsperOps, a real company, has done exactly this. They only make money when you make money. That alignment changes the entire sales conversation.

Research has shown how fee framing affects customer preference even when the total cost is identical. On a $10 item, a flat $0.50 fee is strongly preferred. On a $200 item, a percentage-based fee suddenly looks more attractive. Same math, very different psychology. How you structure and present your pricing materially affects your ability to sell it.

The AI Pricing Problem (And One Emerging Answer)

One of the most critical shifts today—especially with the rise of AI—is moving from User-based to Outcome-based pricing. Simon-Kucher’s annual software study found that 76% of buyers signal acceptance for usage-based and outcome-based pricing models when it comes to AI specifically. That’s a meaningful shift away from pure seat-based models, which have dominated SaaS for years.

But here’s something that should make founders feel a little better: even the biggest players in AI are figuring this out in real time. 75% of agentic AI providers admit they’re unsure how to price their solution. Sam Altman literally said he personally chose a price and hoped it would make some money.

So if you’re an AI startup wrestling with this, you’re in good company.

One of the more interesting trends we’re seeing play out is the emergence of credit-based systems as a practical solution. Both Figma and Notion have moved in this direction:

Figma’s approach: Credits are provisioned based on your seat tier — more credits come with higher-tier seats. Those credits get drawn down based on the complexity of what you’re doing with AI. Changing a font? Maybe 30 credits. Generating an app from scratch? 100+. This gives Figma a way to monetize AI usage without exposing themselves to runaway costs, while also creating an upsell lever for higher-tier plans.

Notion’s approach: When they launched their custom AI agent a few weeks ago, they took a more dynamic approach. Because users can deploy the agent for almost anything, the credit drawdown varies based on information ingested, connected tools, number of workflow steps, model choice, and run frequency. The idea: Notion doesn’t want to lose margin on a use case they didn’t anticipate. So the credits flex with compute.

The practical insight here: fixed credit drawdown makes sense when you know the use case. If you’ve built an agent that does one specific thing — say, formats data into a structured schema — you can assign a fixed credit cost to that action. Dynamic drawdown makes sense when use cases are open-ended and hard to predict. As you learn how your customers actually use your product, you can move toward more specific, value-aligned metrics over time.

One more note on AI and COGS: if you’re offering AI functionality, you must run the math on your cost of goods sold. This is not optional. Software companies have largely been able to ignore COGS for years because margins were so good. AI changes that equation. Your pricing architecture needs to ensure that as customers use more of your product, you’re capturing an accretive margin — not bleeding out.

Choosing Your Pricing Strategy: Only Three Options

Before you can figure out the exact price point, you have to decide what you’re actually trying to achieve. There are three options:

Penetrate: Launch low to acquire market share fast, even at the expense of profitability. Think Amazon. This can be a smart play if you’re in a crowded market and need a foot in the door, or if network effects kick in at scale.

Maximize: Find the optimal price point that drives the most revenue or profit. You’ll intentionally sacrifice some customers who’d only buy at a lower price, but you’re optimizing for the business. This is the classic revenue-maximization play.

Skim: Start high to capture the premium willingness-to-pay from early adopters, then reduce price over time to expand market reach. Apple has done this for decades.

There’s no universally right answer — it depends on your market dynamics, competition, and business goals. But you have to pick one. Pricing without a strategy is just guessing.

How to Actually Find Your Price Point

Once you know your strategy, how do you get to the actual number? Here are two approaches, plus the most important one that founders almost always skip:

Approach 1: Just do it. Go out and talk to your customers and prospects about pricing. Bring it up earlier than feels comfortable. Jeff made the point that the earlier you have that conversation, the less it feels like a negotiation. If you’re asking “what would you pay for this?” during a sales call, you’ve waited too long. But if you’re asking while you’re still building, the conversation is much more honest.

“If you start with one customer, you’ve already done more than most founders,” Jeff said. One is better than zero. Ten is better than one. The data gets more useful as you add more conversations, but don’t let perfect be the enemy of good here.

Approach 2: Use methodology. For companies at scale, Simon-Kucher uses techniques like the Van Westendorp price sensitivity meter — a model that plots what percentage of customers find a given price “acceptable,” “expensive,” or “prohibitively expensive” across a range of price points. Where those curves intersect tells you a lot about psychological cliffs in your pricing. (The jump from $99 to $101, for example, can be dramatic even though it’s only $2.) Conjoint analysis goes even further, putting buyers into simulated purchase situations to measure value vs. price tradeoffs in real-time.

For most startups, don’t try to boil the ocean. A few good customer conversations plus some internal analysis gets you 80% of the way there. Go to market, observe the reaction, and adjust.

Key Takeaways for Building a Monetization Engine That Works

  • Fee Framing Matters: Customer preference can swing wildly based on how you “frame” a fee (e.g., 1% of spend vs. 10% of savings), even if the total cost is identical.
  • Align Metrics with Value: Move away from technical “cost to serve” metrics like compute time or storage. Instead, focus on outcomes, such as “number of resolved queries” or “completed tasks”.
  • Credit-Based Systems: Tools like Figma and Notion use credit-based systems where the “drawdown” varies based on task complexity (e.g., 30 credits to change a font vs. 100+ to generate an app), ensuring they monetize high-value AI workflows while maintaining low-entry access.

Your 30-Day Monetization Checklist

  • Create a long list of relevant price or fencing metrics that reflect the value of your offering. Start with first principles: what is the customer actually getting out of your product? What scales with that value?
  • Brainstorm your price model and determine whether another structure fits better — including whether a dual metric (e.g., seats + usage) better captures two distinct value vectors.
  • If you’re offering AI functionality, run the math on COGS. Make sure your price architecture captures an accretive margin as usage scales.
  • Talk to customers and prospects. Have honest conversations about how they’re gleaning value and how they’d prefer to buy. They often have better intuitions about the right metric than you do.
  • Decide your pricing strategy — penetrate, maximize, or skim — and ensure your price point works in concert with that goal.

Part 2: Packaging That Enables Land & Expand

One Size Fits None

A classic pricing mistake early-stage founders make is building a single offering and pricing it the same way for every customer. Patreon is a perfect illustration of why that doesn’t work.

Patreon — the membership platform for creators — used to charge a flat 5% on all payments, regardless of who the creator was or what they needed from the platform. On the surface, simple and fair. In practice, deeply misaligned.

Here’s why: on one end of the Patreon creator spectrum, you have someone like “Hypnotic Beast” — a creator who guides listeners through hypnotic sessions to become their spirit animal, with about 2,000 YouTube subscribers. What he needs is simple: a tip jar. A way for fans to support him. That’s it.

On the other end, you have Neil deGrasse Tyson (StarTalk). He has over a million YouTube subscribers, a radio show, a Netflix series. He’s not looking for a tip jar. He needs a platform that helps him manage his creative business, engage his fans at scale, run team accounts, and build a professional membership operation.

Same product. Radically different needs. A single tier and price serves neither of them well.

Patreon’s solution: differentiated packages (Lite, Pro, Premium) with platform fees that increase with feature depth and creator maturity — 5%, 8%, and 12% respectively. The fee structure enables Patreon to progressively capture more value as creators grow and rely more heavily on the platform’s advanced features.

The lesson isn’t to copy Patreon’s model. The lesson is: segment your customer base before you build your packaging. Who are you actually selling to? What do they need? What would they pay for? The answers to those questions should drive the architecture of your tiers.

How to Get Customers to Upgrade: The Zoom Playbook

Zoom is a masterclass in packaging for land-and-expand. Anyone can sign up for free. The free tier is genuinely useful — up to 40 minutes per meeting, 100 participants. It’s enough to get you hooked.

But if you use Zoom for professional purposes, 40 minutes isn’t enough. That’s a very natural friction point that pushes you toward Pro ($14.16/user/month). Once you’re on Pro, you get unlimited meeting time and a meaningful increase in AI Companion features. And if you need more participants or advanced admin controls, Business is waiting.

Two core mechanisms make this work:

Gate higher-value functionality into higher tiers. Don’t put your most valuable features in the free tier just because you want to drive adoption. If 80% of your value lives in the free product, getting customers to pay for the remaining 20% becomes an uphill battle. Be intentional about what you’re giving away.

Fence usage of high-value features. Give lower-tier users just enough of a premium feature to understand its value — and then cap it. Zoom’s free AI Companion is “limited in-meeting use.” Pro gives you unlimited in-meeting use plus third-party integrations. Users who find value in the limited version have a clear path to unlock more.

The LFK Framework: Leaders, Fillers, and Killers

So how do you actually decide what goes in which tier? Simon-Kucher uses a framework they call LFK Leaders, Fillers, and Killers — and used McDonald’s as an analogy.

Leaders are your Big Mac. The reason people come to you. The products or features most customers “must” have. High value, high adoption. Every tier should have a leader — but don’t put all your leaders in the same tier. Differentiate these across tiers rather than overstuffing one bundle.

Fillers are your fries. Most people like them. On their own, most people are not making a trip to McDonald’s just for fries. But bundled with the burger, they make the meal better and justify a higher price. In SaaS terms: features that are “nice to have,” that increase the appeal of a package without being the primary draw. These round out a package but don’t drive the primary purchase. Include enough fillers to make each tier feel complete, but not so many that you’re giving away value you could capture elsewhere.

Killers are your McDonald’s coffee. Some people love it. Some people hate it at any price. Putting coffee in a bundle that was supposed to be burger-and-fries actively makes that bundle less appealing to people who don’t want coffee. Killer features diminish the perceived value of a bundle. Keep them as add-ons or separate SKUs where only the people who want them will buy them.

If we apply this framework to Slack, it would look like this: the core chat function is the leader. AI summaries and automation are fillers — most users would find them valuable, and they make the product stickier. HIPAA compliance? Killer for most customers. Essential for healthcare companies, but it shouldn’t be bundled into a standard plan where it adds cost and complexity for everyone who doesn’t need it.

Where Does AI Fit in Your Packaging?

If you’re adding AI to an existing software product, you face the question every company is wrestling with: does AI go into every tier? Only premium tiers? As a standalone add-on?

Use a simple 2×2 matrix to think through it, based on two axes: expected customer adoption (how many of your customers will actually use this AI feature?) and differentiated business value (how meaningfully does this AI capability change outcomes for customers?).

  • High adoption, low differentiation → Democratize access, charge for usage. Something like an embedded summarization tool that most customers will use but that doesn’t dramatically differentiate your product from alternatives. Give access broadly, but meter it (credits, usage caps, etc.) so you can still capture value. Figma does this.
  • High adoption, high differentiation → Create a premium tier. If AI makes your product substantially better in a way your competitors can’t easily match and most customers want it, this is your justification for a new premium tier or a meaningful price increase. ServiceNow has done this.
  • Low adoption, high differentiation → Offer as an add-on. If it’s highly valuable but only to a subset of customers (think: AI-powered compliance monitoring for regulated industries), don’t bundle it where everyone pays for it. Price it as a separate add-on for those who need it. Intercom has gone this route.
  • Low adoption, low differentiation → Don’t build it (or at least, deprioritize it).

Twelve months ago, AI add-ons were common because AI was genuinely niche. Today, you’re seeing more convergence toward either integrating AI into existing packages or building new premium tiers around it. The add-on era isn’t over, but it’s shrinking.

Key Takeaways for Packaging That Enables Land & Expand

  • Gate Features Strategically: Use higher-value “Leaders” to incentivize upgrades.
  • Fence Usage: Allow lower-tier customers to “partially experience” premium features to drive informed upgrade decisions.
  • AI Packaging: Decide if AI should be an add-on, a premium tier feature, or democratized across all tiers via consumption charges.

Your 30-Day Packaging Checklist

  • Segment your customer base before building packaging. Know who you’re selling to and what each segment actually needs.
  • Deconstruct your offering into concrete building blocks. List every feature and capability you have.
  • Assess whether those building blocks are Leaders, Fillers, or Killers through the lens of your target segments. Customers will guide you — ask them.
  • Select the packaging structure that makes the most sense for your market: good/better/best tiers (if needs scale in a hierarchy) or a more modular structure (if different customers need different combinations).
  • Determine how AI slots in — add-on, included in higher-tier packages, or democratized with usage-based charging — based on expected adoption and differentiated value.

Part 3: Take Control of Your Customers’ Lifecycle

Pricing as a Behavioral Tool, Not Just a Revenue Lever

This last section is where a lot of founders leave money on the table. Pricing and packaging aren’t just decisions you make once at launch. They’re active tools you use throughout the entire customer lifecycle to shape behavior, drive adoption, and expand revenue. We’re talking about the “Land” (lower barriers, trigger commitment) and “Expand” (deliver value, engineer growth) strategy.

Land, Self-Serve Style: The Free Tier Decision

Most software companies offer some kind of free entry point. But “free tier” isn’t a single thing — it’s a spectrum of choices with very different tradeoffs:

Freemium: Part of your portfolio is always free. Notion and Canva do this. The benefit is that you’re educating customers through actual product usage and creating genuine stickiness. The risk is you give away too much value and make it hard to convert.

Free trial (no credit card required): HubSpot does this. You get the full (or substantial) experience for a limited time, then have to decide. High acquisition volume, genuine product exposure. The conversion moment requires active friction — the user has to make a decision.

Free trial (credit card required): ChatGPT and Duolingo do this. You filter out low-quality leads immediately, create stickiness during the trial, and — critically — automated conversion kicks in when the trial ends without user action. Lower acquisition volume but higher ARPU and lower churn.

Promotions and discounts: LinkedIn’s model. You offer a discounted or free first period, but payment is locked in upfront. Immediate revenue stream, creates upsell opportunities.

There’s no universal right answer. But the concept is this: the further down you go on this spectrum (toward credit card required, toward discounts), the higher your ARPU tends to be. The further up, the higher your acquisition and engagement. Your strategy (penetrate vs. maximize) should guide which end of this spectrum makes sense.

Here’s some practical advice on freemium design: give prospects enough to experience the value without giving away the house. This is harder than it sounds. If you put too much in the free tier because you want people to “really get it,” you undermine your own conversion path. Be deliberate about where the free tier ends.

Land, Sales-Led Style: The Paid Proof of Concept

For companies selling to mid-market or enterprise, freemiums and self-serve trials often don’t work. Larger organizations need more time, more customization, and a deeper evaluation before they’re willing to sign a contract.

The POC (proof of concept) model is the answer — but most companies design them poorly.

Many enterprise buyers would say: “I don’t love free trials because I don’t get enough time to figure out if it’s working for me.” “If a trial doesn’t have all the features, I’m not getting the full experience to assess if it’s going to work — we need a full evaluation.” “We would need at least 3-4 months to assess the value.”

The free trial model is fundamentally a mismatch for enterprise. They need a real evaluation — with their data, in their environment, long enough to see actual results.

Designing the Proof of Concept (POCs):

  • Scope: Focus on getting one team or one use case right, rather than going broad. A narrow, deep POC is more convincing than a shallow, wide one.
  • Timebox: 2-8 weeks with clear checkpoints. Anything longer and you’re functionally giving away functionality for free. Create urgency by defining the decision point upfront.
  • Success Criteria: Align with the customer on what “success” looks like before you go live. If this isn’t defined in advance, the POC becomes an open-ended evaluation with no natural endpoint.
  • Pricing: Charge 5-30% of ACV for the POC, with 100% of the pilot fee credited toward the full contract if they convert. This does two things: it ensures the customer has skin in the game (they’re not just kicking tires), and it removes the financial objection at conversion time. The pilot fee gets them to commit; the credit gets them to sign.
  • Mutual Commitments: Capture the customer’s investment, not just your own. This means weekly check-ins, data access, named stakeholders. POCs that don’t require anything from the customer are easy to deprioritize.
  • Exit: Have a plan for how the POC ends. Ideally, you’ve built in a time-boxed incentive (a discount, an added feature) to convert to a production contract at the moment of decision.

Expand: Implementation as a Revenue Line

Here’s a mindset shift that surprises a lot of founders: charging for implementation isn’t just okay — it’s often the right call.

Too many startups treat implementation as a cost of sales, something they absorb to get the deal over the line. But charging for it accomplishes two things: it reduces your customer acquisition cost, and it actually makes customers more likely to succeed with your product. When customers invest in getting set up properly, they take it more seriously.

There are three ways to structure implementation pricing:

Option A — One-time implementation fee: Fixed dollar amount per deployment, separate line item. Simple, easy to understand, works best when setup effort doesn’t vary dramatically across customers.

Option B — Packaged onboarding: Different onboarding packages priced based on customer size and needs. More complex, but captures more willingness to pay from larger customers who need more support.

Option C — Unit-based onboarding: Fee scales with units of effort (per integration, per workspace, per data source configured). This is the right model when human effort varies dramatically and starts approaching custom SOW territory.

For most startups, we recommend starting with A or B — something productized enough that you can deliver it consistently without burning out your team.

Four best practices regardless of which structure you choose:

  1. Make it a SKU. Call it an implementation fee, not “free onboarding.” Put it on the quote as a line item. If it’s not named and priced, it doesn’t feel like a service worth having.
  2. Define scope fences and change orders. Be clear about what’s included. The moment a customer asks for something outside scope, you have a change order conversation — not a concession.
  3. Communicate value, not hours. “Go-live in 30 days” beats “20 hours of onboarding support.” Customers buy outcomes, not time.
  4. Structure your discounting. Decide in advance when you’ll waive the fee — large logo, multi-year deal, strategic partner — and hold the line everywhere else.

Expand: Customer Success as a Revenue Line

The last lever — and one of the most underutilized in early-stage companies — is charging for customer success tiers.

Okta is a good example – they have three success tiers:

  • Basic (included for all paying customers under $20K ARR): Access to their online training and knowledge base, 24/5 support.
  • Silver (15% of ARR for customers with $20K-$200K subscription spend): One Expert Learning Pass, 24/7 support, customized recommendations and self-guided resources.
  • Gold (25% of ARR, required for customers over $200K subscription spend): Six Expert Learning Passes, success planning and roadmap alignment tailored to your goals, specialized expertise to reduce third-party costs, fastest response times.

Okta isn’t giving away CSM time and expertise to be nice. They’ve built a tiered structure that makes the value of each level explicit, ties it to measurable outcomes (103% ROI, $805K NPV for Gold tier, per their data), and captures meaningful incremental revenue from it.

For founders: the win-win framing here matters. Structured customer success gives customers greater realized value and clearer outcomes tied to usage. It gives you higher product stickiness, lower churn, and a real revenue line. Done right, it’s not a cost center — it’s a profit center.

Key Takeaways for Taking Control of Your Customers’ Lifecycle

  • Land: For freemium, self-serve PLG motions, give prospects enough to experience the value without giving away the house. For enterprise deals, leverage paid Proofs of Concept (POCs). Charge a flat fee (5–30% of ACV) to ensure they have “skin in the game,” and credit it back if they sign a full contract.
  • Implementation as a SKU: Stop giving away “free onboarding”. Whether it’s a one-time fee or unit-based onboarding, charging for implementation reduces CAC and accelerates the time to value.
  • Customer Success: Treat success plans as revenue-generating levers that increase stickiness and lower churn.

Your 30-Day Customer Lifecycle Checklist

  • Design your free tier with care. Give prospects enough to experience the value without giving away the house. Be deliberate about where free ends and paid begins.
  • Build your default POC offering and monetization strategy so that when an enterprise prospect asks for an evaluation, you know exactly what you’re offering, what it costs, and how it converts.
  • Select the implementation pricing structure that best fits your market, then build the infrastructure to operationalize it consistently.
  • Determine what ongoing customer success you can feasibly manage, then package and communicate the value of it explicitly. Don’t give away CSM resources for free — name them, price them, and make the ROI case.

Putting It All Together

If there’s a single takeaway across everything covered, it’s this: make monetization a priority in how you build your company. Not something you figure out after you’ve shipped the product. Not something that gets finalized during your first sales negotiation. Something you’re actively thinking about from day one — right alongside your product roadmap.

The metrics you charge on should reflect how customers actually get value from your product. The packages you build should reflect the real differences in how different segments use and value your product. The way you structure POCs, implementation fees, and customer success tiers should reflect the full economics of your customer relationships — not just the initial sale.

Pricing done well isn’t about squeezing customers. It’s about creating structures that align what you charge with what customers get — which makes every conversation easier and every relationship more durable.

Share this post:

Tags:

About the Author

Scroll to Top

Submit Your Company