Software Packaging & Pricing as Configuration, Not Code
Packaging as configuration means managing plans, tiers, usage caps, and add-ons through a settings layer outside the application itself - so a pricing change is a data update, not a software release.
However, the unfortunate reality for many Software and SaaS companies is quite different...
You don't change an aircraft engine mid-flight. You land, you swap the engine, and then you take off again - and every minute on the ground costs money.
That's what changing pricing and packaging feels like inside most software and SaaS companies today: a strategic decision everyone agrees on, followed by an engineering sprint, then a re-code, then another re-code, while the market moves on without you. The plane doesn't crash. It just never gets back in the air fast enough to matter.
Until recently, that was tolerable. Pricing and packaging changed once a year, maybe. A slow ground crew was survivable when you only landed once a year. Now everyone's landing every few weeks - and the ground crew is still working at the old pace.
The Challenge You're Now Facing
If you're a product or go-to-market leader right now, there's a decent chance you don't actually know what your pricing should look like in six months. Not because you haven't thought about it - because the ground is moving so fast.
AI companies are revising their own pricing every couple of weeks, because usage is the only unit that makes sense when a single request can cost wildly different amounts depending on the model behind it. Every software company now building AI features into their product inherits that same problem, whether they wanted it or not - the AI giants are changing what it costs to serve a feature, so the company selling that feature has to keep changing what it charges for it.
Some have already shipped the AI functionality and just quietly absorbed the cost, hoping margin holds until someone works out how to charge for it. Others are still staring at the roadmap, aware something has to change, unsure what or when. Both groups are asking the same question underneath: if pricing has to move this fast now, how do we make that not terrifying?
It's the same pressure behind the rise of AI hybrid licensing models that blend subscription and usage-based pricing - and behind the broader shift toward value-based, tiered pricing strategies for AI-powered SaaS products.
Why Code Was Always the Wrong Place for This
Packaging a product into tiers - versions with increasing features and usage limits that customers can actually buy - sounds like a product decision. It behaves like an engineering one the moment it's implemented in application code, because every tier boundary, every cap, every add-on becomes a conditional statement somewhere in the codebase.
That's fine when packaging barely changes. It stops being fine when the market wants pricing to move every quarter, or every month, or - for usage-based AI features - every few weeks. Re-coding pricing logic means a sprint, then QA, then a release. Engineering time is incredibly expensive, and it's being spent re-litigating a commercial decision that product and go-to-market already made weeks ago.
The industry has been through this shift once before. SaaS itself was the force that pushed all software toward subscriptions. AI is now the equivalent force pushing all software toward usage-based pricing - and usage-based pricing changes far more often than a subscription tier ever did. The old approach to packaging wasn't built for that cadence, no matter how good the engineering team is.
Configuration, Not Code
The fix isn't a faster engineering team. It's removing pricing and packaging from the codebase entirely.
When the business logic for plans, tiers, caps, allowances, and add-ons sits in a configuration layer separate from the application, changing what a customer can buy stops being a release. Every aspect of feature usage gets tracked in a way that's already monetizable - so introducing a new cap, raising an allowance, or bundling in an add-on is a configuration change, not a redeploy. Plans that used to take a sprint to ship can go live in hours.
This only works if usage tracking and entitlement enforcement live in the same place as the configuration itself. A pricing platform that sits off to the side, disconnected from what the product actually enforces at runtime, just moves the bottleneck instead of removing it.
Three Timelines That Never Stop Moving
The reason this feels so hard isn't any single change - it's that packaging has to satisfy three independent timelines at once, permanently, on an in-production product.
The Product Timeline
New features ship on their own schedule, and each one needs to be slotted into whichever tiers it belongs in - sometimes several tiers at once, sometimes as a paid add-on, sometimes gated behind a usage threshold.
The Customer Timeline
Existing customers are mid-cycle, mid-consumption, already relying on what they bought. New features need to reach the plans they've already purchased, and usage limits need to adjust to new thresholds relative to wherever a customer sits in their current monthly or annual consumption - without breaking what they're already running.
The Go-to-Market Timeline
Competitors reposition, the market shifts, and product and commercial teams need to re-package and re-price to stay competitive - without waiting for whichever timeline engineering happens to be free to work on.
None of these timelines wait for the others. A configuration-first platform is what lets all three move independently without any of them getting stuck behind an engineering backlog.
Getting This Right
If you're still working out what your packaging should look like in a world where usage-based and AI pricing keep shifting under you, you're not behind - most of the market is having the same conversation right now. The companies getting ahead of it aren't the ones with the perfect pricing model. They're the ones who've made changing it fast and low-risk.
That's what Zenmeter and the Nalpeiron Growth Platform are built for - metering usage, enforcing entitlements, and managing plans, tiers, caps, and add-ons as configuration, so packaging can change in hours instead of sprints. Zenmeter doesn't replace your billing platform; it sits alongside Stripe, Chargebee, Zuora, or NetSuite, tracking usage and enforcing entitlements in real time so your billing system always has accurate data to invoice against.
If you're comparing options, see how Zenmeter stacks up in our comparison of the best metering and usage-based billing solutions for 2026.
→Are you wrestling with these kinds of problems?
If you're wrestling with what your next packaging move should be, or just want a second opinion on whether your current setup can keep up, talk to us about what you're thinking.
These are exactly the kinds of problems we help companies put a real process around.
Frequently Asked Questions
What does it mean to treat software packaging as configuration instead of code?
It means the business logic for plans, tiers, usage caps, allowances, and add-ons lives in a settings layer separate from the application, rather than as conditional statements in the codebase. Changing what a customer can buy becomes a configuration change instead of an engineering release.
Why is pricing and packaging changing so much faster now than it used to?
AI is pushing software toward usage-based pricing the same way SaaS once pushed it toward subscriptions - and usage-based pricing has to move more often, sometimes every couple of weeks, because the underlying cost of serving an AI feature keeps changing.
What's the risk of hard-coding pricing tiers into application code?
Every tier boundary, cap, and add-on becomes a conditional statement in the codebase, so any packaging change requires an engineering sprint, QA, and a release. That's tolerable when packaging changes once a year, but it can't keep pace with usage-based or AI pricing that needs to change every few weeks.
How does Zenmeter support configuration-based packaging?
Zenmeter meters usage and enforces entitlements in real time, with plans, tiers, caps, and add-ons managed as configuration rather than code. It doesn't replace a billing platform - it sits alongside tools like Stripe, Chargebee, Zuora, or NetSuite, feeding them accurate usage data to invoice against.
About the Author
Jon Gillespie-Brown is the Founder and CEO of Nalpeiron, a leader in cloud-based software licensing, entitlement management, software monetization, and analytics. With over 20 years of expertise, he works with enterprise B2B SaaS and IoT companies to optimize revenue models, accelerate go-to-market strategies, and scale with confidence. Jon is recognized as an authority in software licensing, software monetization, and software analytics, holds two issued U.S. patents, and is the author of five books. He also serves as a strategic guide to customers, helping them navigate and capitalize on the once-in-a-generation shift driven by AI, redefining how software is built, delivered, and monetized. For over 20 years, Jon has been a Professor at University of Colorado Boulder, a lecturer at University of California, Berkeley and Stanford University, and an Entrepreneur in Residence at London Business School.
Nalpeiron: A Long-Term Partner for the AI Era
At Nalpeiron, we go beyond technology — we act as a strategic partner in licensing, monetization, and growth. For over twenty years, enterprise and IoT companies have trusted us to guide and evolve their business models.
As AI shifts software from seats to usage, outcomes, and agent-driven activity, legacy approaches fall short. Nalpeiron enables this transition through entitlements as the control plane — a centralized system of record across SaaS, on-prem, IoT, and offline environments.
From strategy to execution, we help companies adapt faster, launch new models, and stay in control — making Nalpeiron a partner for the AI-driven future of software monetization.
Ready to Optimize Your Strategy?
See how Nalpeiron helps companies implement flexible monetization strategies that support both product-led and sales-led growth motions.
Book a Demo