.png)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Why Do B2B SaaS Companies Like LaunchDarkly Knack and RevenueCat Add Enterprise Pricing
A familiar pattern plays out in product-led B2B SaaS. A company starts with a clean price card, lets a developer or small team buy without talking to sales, and scales on the strength of that simplicity. Then larger customers arrive. They ask for SAML, SCIM, audit history, private infrastructure, custom SLAs, volume discounts, security reviews, procurement terms and a named person who will answer the phone when something breaks.
At first glance, adding an Enterprise tier can look like ordinary price discrimination: find the companies with larger budgets and charge them more. The evidence from LaunchDarkly, Knack and RevenueCat points to a more important explanation. As of August 2026, all three retain relatively simple ways for smaller customers to buy, while their Enterprise offers address requirements that emerge only when the software becomes important enough to carry operational, security or financial risk.
Monetizely's position is that Enterprise pricing should appear when the customer's buying problem changes, not simply when the vendor wants a larger ACV. The primary meter should continue to track how the customer uses or benefits from the product; Enterprise should add the contractual, security and operating commitments required to support that usage at scale.
Enterprise pricing appears when scale changes the buyer rather than merely enlarging the account
Monetizely's 5-Step Pricing Framework helps separate a legitimate Enterprise motion from an arbitrary "contact sales" tier. The framework begins with Goals and Segmentation, defining whom the company wants to serve and what those customers value. Packaging decides which capabilities belong together. Pricing Metric determines the unit that makes the bill grow with customer value. Rate Setting establishes what the customer pays for each unit or package. Operationalisation covers the systems and commercial processes needed to quote, meter, invoice, manage entitlements and renew the offer. Developed further in the 2026 book Monetizing Agentic AI, the framework matters here because Enterprise pricing can look sensible at the packaging step while failing at the metric or operationalisation step.
For a small customer, one person can often be buyer, administrator and daily user. A large organisation separates those roles. Engineering may want the product, security must approve it, procurement negotiates it, finance wants predictable spend, and IT wants access controls that survive employee turnover. LaunchDarkly's current Enterprise offer, for example, adds custom roles and teams, workflows and approvals, SCIM provisioning, contracted usage and longer data retention; Knack adds private-server options, HIPAA or GovCloud choices and enhanced support; RevenueCat offers custom SLAs, dedicated support and volume economics for high-transaction customers. All three price cards were current when accessed on 13 August 2026.
The pattern becomes easier to see when we separate the triggers.
| Enterprise trigger | What changes for the customer | Evidence from the three vendors | Why a normal self-service tier becomes strained |
|---|---|---|---|
| Operational scale | Usage can become large enough that standard rates produce poor economics or unpredictable bills | RevenueCat offers volume discounts; LaunchDarkly offers contracted usage, true-ups and volume discounts; Knack moves beyond 2.5 million database records into Enterprise arrangements as of 13 August 2026. | Standard list rates are designed for low-friction purchase, not negotiated commitments worth much larger ACVs |
| Security and access control | More employees, systems and privileged roles must be governed | LaunchDarkly adds custom roles, teams and SCIM; Knack adds Enterprise security and private-server options as of 13 August 2026. | The customer is buying control over organisational risk as well as product access |
| Reliability | Failure affects revenue, production systems or mission-critical workflows | LaunchDarkly lists Enterprise SLA treatment and contracted true-up; RevenueCat offers custom SLAs for high-volume apps; Knack describes Enterprise for mission-critical applications as of 13 August 2026. | A credit-card subscription cannot easily express negotiated service commitments |
| Procurement complexity | Legal, finance and technical reviews enter the purchase | LaunchDarkly's custom-pricing process explicitly includes architecture mapping and security/compliance review as of August 2026. | The sales process becomes part of the product required to close the account |
The table changes the meaning of "Enterprise". Large customers are not merely buying more units. They are buying the right to depend on the vendor.
LaunchDarkly's move away from seats shows why the Enterprise tier eventually does a different job
LaunchDarkly offers the clearest pricing evolution of the three. Its vendor-maintained legacy archive shows a Starter plan at $8.33 per seat per month when billed annually and Pro at $16.67, while Enterprise already moved to a sales conversation around usage-based subscriptions and carried a 25-seat minimum.
By the company's April 2025 archived price card, seats had effectively stopped being the commercial centre. Developer and Foundation both offered unlimited seats. Foundation charged $12 per month per service connection or per 1,000 client-side monthly active users, with experimentation usage separately priced at $3 per 1,000 MAU; Enterprise remained custom.
By 13 August 2026, the shift was more explicit. LaunchDarkly said there were "No per-seat pricing" charges and that pricing was based on usage. Foundation listed $10 per service connection per month, $8.33 per 1,000 client-side MAU per month and $5 per 1,000 AI runs beyond the included 5,000, while Enterprise used custom contracts, volume discounts and true-ups.
The sequence matters more than any individual price.
| Pricing era | Entry and growth offer | Enterprise treatment | What changed |
|---|---|---|---|
| Legacy archive, superseded before the April 2025 archive | Starter $8.33 per seat/month annually; Pro $16.67 per seat/month annually | Usage-based subscription through sales; 25-seat minimum | Enterprise had already begun separating from the seat model used lower in the ladder. |
| April 2025 archived pricing | Developer free with unlimited seats; Foundation $12 per service connection or 1,000 client-side MAU; experimentation MAU $3 per 1,000 | Custom price; advanced targeting, workflows, SAML/SCIM and custom roles | Usage replaced seats as the core scaling logic across the product. |
| 13 August 2026 | Developer free; Foundation $10 per service connection, $8.33 per 1,000 client-side MAU and $5 per 1,000 AI runs beyond the included amount | Custom contracts, volume discounts and contracted true-up; longer retention and tighter SLA treatment | Enterprise became a negotiated usage contract wrapped in organisational controls. |
LaunchDarkly therefore did something more consequential than add Enterprise pricing. It gradually removed headcount from the core revenue equation.
A feature-management platform can create more value when more developers collaborate, so charging every added user can penalise the behaviour the vendor wants to encourage. LaunchDarkly's August 2026 price page explicitly lets customers invite the whole team while charging against service connections, MAU and AI activity instead.
Against the three steps most relevant to this teardown, our score is strong but not perfect.
| 5-Step Pricing Framework step | Grade | Monetizely's rationale |
|---|---|---|
| Packaging | B+ | Developer, Foundation and Enterprise form a clear maturity ladder, while Guardian has been separated as a paid safety add-on. Enterprise, however, still mixes product capability, organisational control and commercial treatment in one opaque sales package as of August 2026. |
| Pricing Metric | A- | Moving away from seats towards service connections, client-side MAU and workload activity better reflects use of the platform. Multiple meters and architecture-specific exceptions still make the bill harder to forecast than a single usage unit. |
| Operationalisation | B+ | Contracted true-ups, volume discounts, tailored rates for architectures such as serverless environments and Enterprise SLAs show mature commercial plumbing. The customer still cannot see enough of the Enterprise rate logic before entering sales. |
What LaunchDarkly gets right is the direction of the meter. What it gets wrong is allowing the Enterprise price to become less intelligible precisely when the spend gets larger.
Knack and RevenueCat show that Enterprise works best when it solves a distinct commercial problem
LaunchDarkly is not an isolated case. Knack and RevenueCat reach Enterprise from very different products and end up in much the same place.
Knack is especially useful because seats cannot explain its Enterprise tier. As of 13 August 2026, Knack included unlimited app users on every listed plan. Starter began at $59 per month before a promotional discount, Pro at $130 per month, and Corporate at $300 per month on monthly billing, with Corporate's final cost determined by usage requirements. Enterprise was "Contact for Pricing".
What does Enterprise add when additional users are already free? Dedicated account management, HIPAA or GovCloud options, private-server environments, enhanced support, longer audit history and capacity beyond 2.5 million database records. Knack is charging around scale, infrastructure choice and risk, not human access.
RevenueCat goes further. Its August 2026 standard offer included all features and charged nothing up to $2,500 in monthly tracked revenue, then 1% of tracked revenue. Enterprise did not unlock a large hidden feature bundle. It targeted apps with high transaction volume, complex business models or unusual operating requirements, adding volume discounts, flexible tracking configurations, dedicated support and custom SLAs.
The three businesses therefore expose three variants of the same underlying transition.
| Vendor, 13 August 2026 | Core commercial logic | What Enterprise mainly adds | Monetizely's reading |
|---|---|---|---|
| LaunchDarkly | Usage through service connections, client-side MAU and workload activity | Contracted usage, controls, workflows, provisioning, SLA treatment and longer retention. | Enterprise is becoming the way large customers buy production infrastructure, not a larger team licence |
| Knack | Subscription level plus database scale; unlimited app users | Private environment options, regulated-sector deployment choices, support and much larger data scale. | Enterprise monetises requirements created by mission-critical use rather than user count |
| RevenueCat | 1% of monthly tracked revenue after the free threshold | Volume economics, flexible tracking, dedicated support and custom SLA. | Closest to the cleanest design: retain the underlying value meter and change the contract around it |
RevenueCat is the most revealing benchmark. An Enterprise tier does not require withholding ordinary functionality from smaller customers. All features can remain available while the commercial agreement changes as the customer's scale and risk change.
That distinction protects product-led growth. A startup can discover the product without negotiating for SSO-like table stakes or wondering which useful feature has been held hostage to an Enterprise contract. Sales enters when the account needs a negotiated economic and operating relationship.
Large-account economics explain why SaaS companies keep building an Enterprise motion
Public SaaS disclosures show why private vendors eventually make the investment. Large accounts can become a disproportionate part of revenue, and the capabilities required to win them are materially different from those needed to close a $100-a-month self-service account.
Atlassian offers perhaps the clearest practitioner description. In October 2025, CEO Mike Cannon-Brookes said customers were choosing Atlassian in part for "enterprise security, governance, and permissioning". In fiscal 2025, Atlassian also signed a record number of deals above $1 million in annual contract value, more than 1.5 times the prior year's total.
Cloudflare CEO Matthew Prince reported in February 2025, "We saw record growth in our largest customers". Cloudflare ended 2024 with 173 customers spending more than $1 million annually, up 47% year on year.
GitLab provides an even stronger revenue mix signal. For the year ended 31 January 2026, more than 70% of ARR came from enterprise and public-sector customers; customers above $1 million in ARR rose from 123 to 155.
Snowflake demonstrates the same effect under consumption pricing. At 31 January 2026 it had 733 customers producing more than $1 million in trailing twelve-month product revenue, up from 576 a year earlier. That cohort represented about 68% of product revenue.
| Public SaaS evidence | Large-account signal | Pricing lesson |
|---|---|---|
| Atlassian, FY2025 | Record number of >$1m ACV deals, more than 1.5x the prior year. | Serving the enterprise can become a material growth vector even for a company with strong self-service roots |
| Cloudflare, FY2024 | 173 customers spending >$1m a year, up 47% year on year. | The upper tail of the customer base can compound faster than the rest |
| GitLab, FY2026 | >70% of ARR from enterprise/public sector; 155 customers above $1m ARR versus 123 a year earlier. | Enterprise stops being a side channel once it drives most recurring revenue |
| Snowflake, FY2026 | 733 customers above $1m trailing product revenue; that group accounted for roughly 68% of product revenue. | Usage pricing and enterprise selling are complements, not alternatives |
The table also dispels a common misconception. "Enterprise" does not mean "per-seat". Snowflake's economics are built largely around consumption, while large customers account for most product revenue. LaunchDarkly is now pursuing a smaller-scale version of the same principle: keep usage as the meter and use contracts to handle large-account economics.
Two other practitioner comments sharpen the point. In November 2025, HubSpot CEO Yamini Rangan said customers were using the platform to "consolidate tech stacks, and reduce their total cost of ownership." GitLab co-founder Sid Sijbrandij described customer value in September 2024 as "aligning to business goals, providing measurable benefits, and improving security."
Enterprise buyers, in other words, are not just asking how many users they can licence. They are asking whether the vendor can become a dependable part of a broader operating system.
LaunchDarkly should make committed usage the Enterprise anchor and reduce the mystery around the quote
LaunchDarkly's next pricing reset should not bring seats back. Monetizely's position is the opposite: usage should remain the primary meter, while Enterprise becomes a clearer annual committed-usage contract using the same units customers already understand below Enterprise.
The company's present architecture contains most of the right pieces. Foundation exposes service connections and client-side MAU for CodeControl and workload activity for AgentControl. Enterprise already supports contracted true-ups and volume discounts. Guardian is separately priced, which is sensible because automated monitoring, guardrails and rollback constitute an additional capability rather than merely a procurement requirement.
Where the design loses clarity is the jump from visible Foundation rates to "Custom pricing". A sophisticated buyer can understand why the unit rate should fall at higher commitments. It is harder to understand why the relationship between price and usage needs to disappear altogether.
The division we would recommend is straightforward.
| Pricing element | LaunchDarkly today, August 2026 | Monetizely's position for the next reset |
|---|---|---|
| Seats | Unlimited; no per-seat pricing. | Keep at zero. More collaborators should not mechanically increase the bill. |
| Core usage | Foundation publishes service-connection and MAU rates; Enterprise negotiates. | Keep usage as the primary meter and carry the same units into Enterprise. |
| Large-account economics | Contracted true-up and volume discounts. | Make the annual commitment, discount logic and true-up rules visible before sales engagement, even if exact negotiated rates remain confidential. |
| Governance and identity | Custom roles, teams, workflows and SCIM concentrated in Enterprise. | Package them as Enterprise controls, but do not create new per-seat charges for them. |
| Release protection | Guardian is a separate paid add-on with monitoring and automated rollback. | Keep it separate. It adds a distinct job and therefore deserves its own monetisation path. |
The synthesis is important: Enterprise should change the commitment and service terms more than it changes the underlying pricing logic.
RevenueCat already demonstrates the clean version. Its standard price is 1% of tracked revenue; Enterprise offers discounts and operating accommodations to customers for whom that same economic relationship becomes very large. LaunchDarkly has more heterogeneous workloads, so it cannot be equally simple, but the principle survives.
Published Enterprise discount bands are not essential. Published mechanics are. A buyer should know whether signing a larger annual commitment lowers the rate, what usage is counted, when true-ups occur and which service guarantees come with the agreement.
That transparency also disciplines the vendor. Sales cannot quietly turn every large quote into a new pricing model, and finance can analyse gross margin and expansion using consistent units.
Operators should add Enterprise only after the customer has already outgrown self-service
The lesson from LaunchDarkly, Knack and RevenueCat is not "every SaaS company needs an Enterprise tier". The lesson is more demanding: an Enterprise tier should represent a real segment with a different buying process and different cost to serve.
Four decisions follow for operators considering the move.
Prove that a second buyer has appeared before building the tier. Look for security, finance, procurement and platform teams joining deals that previously involved only the end user. Repeated requests from those functions are stronger evidence than a salesperson asking for a higher-priced package.
Measure the economics of the largest customers as a separate cohort. Track expansion, sales cost, support burden, infrastructure cost and gross margin for accounts above a meaningful spend threshold. Snowflake, GitLab, Atlassian and Cloudflare show why the upper tail can eventually matter disproportionately to the business.
Protect the product-led entry point while moving upmarket. RevenueCat can give smaller customers its full feature set because Enterprise monetises scale and service commitments instead. Knack can offer unlimited app users because database scale, deployment requirements and support create the enterprise boundary.
Choose one commercial principle that survives from the smallest customer to the largest. For LaunchDarkly, that principle should be usage. The contract can become larger, longer and more negotiated as the customer matures without changing the basic answer to the question, "What makes our bill go up?"
The companies that get Enterprise pricing right are not abandoning self-service. They are recognising that success has created a second business inside the first one: the product is still software, but the largest customers now need a vendor they can safely depend on.
Assumptions
Pricing reflects official pages available on 13 August 2026; historical LaunchDarkly pricing uses LaunchDarkly's own legacy and April 2025 archived price pages. No issuer 10-K or public earnings-call transcript was identified for LaunchDarkly, Knack or RevenueCat in the Tier A source review, so no such document is implied; SEC filings from public SaaS companies are used only as comparable evidence for large-account economics. No modelled Enterprise price points or undisclosed discounts are assumed.
Footnotes
https://www.amazon.com/Monetizing-Agentic-AI-Handbook-Transformation/dp/B0H7Z13VKJ/
https://launchdarkly.com/pricing/archive/
https://launchdarkly.com/pricing/archive-apr2025/
https://launchdarkly.com/pricing/
https://launchdarkly.com/get-pricing/
https://www.knack.com/pricing/
https://www.revenuecat.com/pricing
https://www.sec.gov/Archives/edgar/data/1650372/000165037225000064/ex991q1fy26.htm
https://www.sec.gov/Archives/edgar/data/1650372/000165037225000058/team-20251014.htm
https://www.sec.gov/Archives/edgar/data/1477333/000147733325000017/q424exhibit991.htm
https://www.sec.gov/Archives/edgar/data/1653482/000162828026018731/gtlb-20260131.htm
https://www.sec.gov/Archives/edgar/data/1653482/000162828024039118/gitlab-ex99120240731fy25.htm
https://www.sec.gov/Archives/edgar/data/1640147/000164014726000008/snow-20260131.htm
https://www.sec.gov/Archives/edgar/data/1404655/000119312525267023/hubs-ex99_1.htm