SaaStr Podcast #073, Part 2: David Skok, General Partner @ Matrix Partners Discusses How To Gain Different ACVs From the Same Product

If you have ever stared at your pricing page like it personally insulted you, welcome. You are among friends. One of the smartest ideas from SaaStr Podcast #073, Part 2 is that a SaaS company does not always need a brand-new product to unlock bigger contracts. Sometimes the same core product can support wildly different annual contract values, or ACVs, depending on how you package it, price it, sell it, and expand it.

That is the magic David Skok gets at. The product may be the same at its heart, but the value customers receive is not always the same. A small startup with five users, a mid-market team with multiple departments, and a global enterprise with security reviews, procurement, and rollout plans are not buying the same business outcome, even if they are buying the same software. One wants speed. Another wants scale. The biggest one wants scale, control, compliance, and fewer headaches before the next board meeting.

So no, “different ACVs from the same product” is not a trick. It is not pricing wizardry, smoke, mirrors, or some dark SaaS art practiced only by finance teams in windowless conference rooms. It is a discipline. And when it is done well, it creates better expansion revenue, stronger retention, and a healthier path to growth.

What ACV Really Means in SaaS

ACV, or annual contract value, is the yearly value of a customer contract. In plain English, it tells you how much a contract is worth to your business on an annualized basis. That sounds simple, because it is. But the implications are huge. A company with a $2,000 ACV can rarely support the same sales motion, onboarding effort, or customer success model as a company with a $50,000 or $250,000 ACV.

This is why Skok’s thinking still holds up. If you can increase ACV without rebuilding your entire product from scratch, you improve the economics of the business. Higher-value contracts can justify more support, better onboarding, and more human touch. They can also improve net revenue retention when customers expand over time. That matters because strong SaaS companies are not built only on winning new logos. They are built on turning today’s customers into bigger customers next year.

The Big Insight: One Product, Multiple Value Stories

The smartest takeaway from the podcast is that SaaS founders should stop assuming every buyer should pay the same way. That idea sounds fair on paper and terrible in practice. Customers do not all consume value the same way, do not have the same willingness to pay, and definitely do not show up with the same list of needs.

A founder might think, “We sell one platform, so we should have one simple price.” Clean idea. Nice spreadsheet. Sadly, the market usually responds by throwing that spreadsheet into a volcano.

The reason is simple: the same product can deliver very different levels of value to different segments. A smaller customer may need the basics and care deeply about affordability. A larger customer may need integrations, admin controls, governance, premium support, and the confidence that your team will not disappear when procurement sends a 17-page security questionnaire at 4:52 p.m. on a Friday.

That is why the same software can support different ACVs. The code base may be similar, but the commercial package is not.

How to Gain Different ACVs From the Same Product

1. Choose a Value Metric That Grows With Customer Success

Skok makes a crucial point: strong SaaS products usually have at least one variable pricing axis. In other words, there should be a logical way for price to grow as customer value grows. This is where founders often make their first big pricing mistake. They charge for the easiest thing to count, not the thing customers actually value.

Seats are common, but seats are not always ideal. In some products, the number of users barely changes while the business value explodes. That is why SaaS companies often price using other metrics such as contacts, storage, transactions, usage volume, servers, or workflow capacity. The best value metric makes the price feel fair because it moves in step with customer outcomes.

Think about it this way: if your product helps customers process more transactions, automate more workflows, or manage more data, your pricing should have a way to rise with that success. Otherwise, you are doing the digital equivalent of running an all-you-can-eat buffet and charging by the number of napkins.

2. Build Packaging for Distinct Customer Segments

Different ACVs often come from packaging, not just price increases. This is a key distinction. Good packaging helps smaller customers enter easily while giving larger customers a reason to spend more. That can mean a classic Good-Better-Best structure, a usage-based model, a platform with add-ons, or a hybrid of all three.

For a startup buyer, the entry plan should reduce friction. It should be easy to understand, easy to buy, and easy to adopt. For mid-market buyers, the package might add collaboration, reporting, automation, or integrations. For enterprise buyers, the same core product can command a much higher ACV by including advanced permissions, security features, audit logs, dedicated onboarding, service levels, procurement support, and broader deployment rights.

The trick is to avoid making lower tiers feel broken. Your entry product should solve a real problem. Your upper-tier products should solve bigger, more complex, more operationally expensive versions of that problem.

3. Align Sales Motion With ACV

This is where many companies step on a rake. They create an enterprise plan, slap “Contact Sales” on it, and assume large ACVs will appear like magic. That is not a strategy. That is wishful thinking wearing a blazer.

Higher ACVs usually require a different go-to-market motion. Self-service works beautifully for smaller customers because the buying process is fast and the cost to acquire them must stay low. Mid-market customers may need inside sales. Enterprise customers often require a more hands-on motion with sales, solutions support, procurement coordination, and customer success involvement.

Skok’s broader SaaS framework is useful here: as sales complexity rises, customer acquisition cost rises too. That means you cannot just chase bigger deals because they look impressive in a board deck. You need higher ACVs that justify the increased sales and service cost. Bigger contracts are great. Bigger contracts with bad unit economics are just expensive theater.

4. Design for Expansion, Not Just the First Deal

One of the most valuable ideas connected to this topic is negative churn, or the ability to grow revenue from existing customers fast enough to offset revenue lost from churn. That is where multiple ACVs become especially powerful. The first contract does not need to be the final contract.

A customer might start small with limited seats, a lighter usage tier, or a basic bundle. As adoption spreads, the account can expand through more users, more usage, more departments, more integrations, more data, or premium capabilities. This is how the same product becomes a land-and-expand engine.

That expansion path should not feel like a trap. It should feel natural. Customers should not need a PhD in pricing tables to understand how to grow with you. If they are getting more value, spending more should feel logical, not punitive.

5. Use Customer Success to Protect and Increase ACV

Packaging and pricing may open the door, but customer success determines whether the account grows. If onboarding is weak, usage stalls. If adoption stalls, expansion stalls. And if expansion stalls, your fancy plan to support different ACVs becomes a very expensive slide in your next planning deck.

Skok emphasizes the importance of creating expansion revenue from the existing base. That means customer success is not just a support function. It is a growth function. The teams that win here are the ones that help customers activate the core value fast, then identify the next logical use case, the next team, the next workflow, or the next outcome worth paying for.

In practical terms, that means building playbooks around adoption milestones, product-qualified expansion opportunities, usage thresholds, and executive reviews that connect product usage to business value.

Real-World Patterns Behind Different ACVs

Historically, SaaS companies have used several patterns to create different ACVs from the same product:

Segment-Based Packaging

Basic, Professional, and Enterprise plans remain popular because they simplify choice and create a clean upsell path. Smaller customers can start with less friction, while larger buyers can pay for more sophisticated needs.

Usage-Based Expansion

When usage tracks customer value, a consumption or hybrid model can unlock higher ACVs without alienating smaller accounts. Light users stay comfortable. Heavy users scale into larger contracts because the product is delivering more value.

Feature Gates With Logic

Advanced analytics, governance, integrations, and compliance features often command higher ACVs because they matter more to larger organizations. The feature gate works when it reflects a real segment need, not when it feels like you removed the steering wheel and now want extra money to put it back.

Commercial Terms

Annual prepay, multi-year commitments, premium support, implementation packages, and service levels can all increase contract value without changing the core product. These do not replace product value, but they can absolutely raise ACV when matched to customer needs.

Mistakes Founders Make When Chasing Bigger ACVs

The first mistake is trying to move upmarket before product-market fit is solid. Skok is clear on this theme in his broader work: do not obsess over expansion mechanics too early. First make sure people truly want the product.

The second mistake is creating pricing chaos. Too many custom deals, too many one-off packages, and too many SKUs eventually turn your pricing model into spaghetti with revenue attached. Sales may love the flexibility for a while. Finance and operations will eventually stage an intervention.

The third mistake is choosing the wrong value metric. If the metric discourages usage, feels disconnected from outcomes, or punishes customers for growing in the wrong way, expansion becomes harder.

The fourth mistake is forgetting that bigger ACVs require better delivery. You cannot sell enterprise expectations on a startup support model and hope nobody notices. They will notice. Loudly.

Why This SaaStr Episode Still Matters

What makes this episode useful years later is that it reframes pricing as strategy, not decoration. The goal is not simply to charge more. The goal is to capture value fairly across segments while building a model that supports retention and expansion.

That is why different ACVs from the same product matter so much. They let you serve multiple customer types without forcing every buyer into the same box. They create a ladder customers can climb. They improve revenue quality. And they help you avoid the classic SaaS problem of building more value into the product while charging like it is still version 1.0.

In short, David Skok’s message is refreshingly practical: if your product works, your pricing should have a way to grow with that success. If it does not, you may still have a good product, but you are leaving revenue, retention, and scale on the table.

Operator Experiences: What This Looks Like in the Real World

In practice, the journey to different ACVs usually starts with a founder noticing something odd in the pipeline. Small customers close quickly. They love the product, pay on a card, and get moving. Larger prospects also love the product, but their questions are different. They ask about governance, procurement terms, implementation support, reporting depth, user management, integrations, and rollout planning. That is the first signal that the market is not asking for one price. It is asking for one product with multiple commercial shapes.

A common experience is that startups accidentally undercharge their best-fit larger customers because they built the original pricing for speed, not scale. Their self-serve plan worked brilliantly to get traction, but now a 500-person company is trying to buy through the same packaging designed for a five-person team. Everyone can feel the mismatch. The buyer wants reassurance and flexibility. The SaaS company wants a bigger contract. Neither side is fully wrong. The packaging just has not caught up to the market.

Another common lesson is that enterprise ACV rarely comes from “more features” alone. It often comes from reducing organizational risk. A larger customer pays more because the software must fit into a more complex environment. That includes identity management, permissions, compliance, approvals, support expectations, onboarding help, and confidence that the vendor can handle change management. Founders often learn this the hard way. They think the enterprise buyer is only paying for advanced functionality, when in reality that buyer is also paying for trust, process, and operational reliability.

Teams also discover that expansion is easiest when pricing follows real usage. When the value metric is intuitive, account growth feels natural. Customers do not need to be “sold” nearly as hard because the contract expands alongside adoption. But when the pricing metric is weak, sales has to keep inventing reasons for the account to pay more. That creates friction. Customers can smell artificial upsells from a mile away.

There is also a culture lesson here. Companies that successfully support multiple ACVs usually stop treating pricing as a one-time launch decision. They revisit packaging, watch where deals stall, study discount patterns, and learn which features truly matter to each segment. Product, sales, finance, and customer success all contribute. The result is not just higher contract values. It is cleaner positioning, better qualification, healthier expansion, and a much clearer sense of which customers the company is really built to serve.

And yes, there will still be spreadsheet drama. It is SaaS. There is always spreadsheet drama. But with the right pricing architecture, at least the drama starts generating better revenue.

Conclusion

SaaStr Podcast #073, Part 2 remains a sharp lesson in SaaS growth because it strips away the myth that bigger contracts require a completely different product. More often, they require a better commercial design. When founders understand value metrics, packaging, segmentation, customer success, and sales complexity, they can unlock different ACVs from the same product without turning the business into a discount circus.

That is the real takeaway: do not just build software people want. Build a pricing and packaging system that lets the right customers start, succeed, and grow. That is where the strongest SaaS businesses separate themselves from the merely busy ones.