Do you need to define a meter before you can bill for something?

Announcements
Read time: 3 min

Arnon Shimoni
✓ Expert opinion
Not anymore.
The latest Solvimon release adds dynamic meter creation. By simply setting a parameter to DYNAMIC, you can feed Solvimon with meters and events without figuring them out ahead of time.
For teams who want the old guardrail (rejects the event outright if the meter isn't there yet) - the previous mode remains the default.
Experiment first, monetize later
In 2026 when you deliver really really fast, it's very normal for you to figure out the pricing later.
The classic metering flow used to force you to predict anyway: you had to define a meter before a single event could be ingested, which meant deciding, in advance, whether a brand-new feature was billable at all.
For AI agents specifically, it matters even more because a single agent workflow throws off a lot of candidate events before anyone's sure which ones are worth billing. For example:
an AI SDR agent that drafts an email, books a meeting, or advances a deal could send out lots of different events.
A document agent that extracts a field, categorizes it, hands back a summary.
A support agent that resolves a ticket instead of escalating it
Every one of those is a moment someone might eventually pay for, and you find out which by watching, not by guessing on day one.
Dynamic metering lets the event show up first and the pricing decision happen whenever you're ready to commit. Some of it will stay as a signal you monitor, while others become a billable event the day someone attaches a price to it.
The big change is the event doesn't need to know in advance which one it's going to be, and neither do you.
We call this "organic monetization" - and it's becoming increasingly common. The metering catalog bends to what you're actually seeing in production instead of a pricing doc's best guess.
As a plug, it's also much easier to work with when onboarding because you no longer depends on a fully configured meter catalog existing first.
More of what Solvimon released in June 2026
A few other things shipped this cycle that are really in the same direction:
On-demand charging, end to end. One-off items, a setup fee, an add-on a customer wants right now, can be flagged as on-demand and charged on top of an existing subscription whenever you need to, with an optional preview first. It shipped in the API and in the customer portal, so a customer can trigger their own charge from a buy button without anyone opening Solvimon's Desk.
Pricing directly on a schedule. A schedule can now carry its own bespoke pricing (
pricing_categories, same shape as a plan version) instead of needing a pricing plan version or a rate card behind it. Built for the negotiated deal that's never going to repeat.Mid-term subscription upgrades. Upgrade a customer mid-cycle, choose how the old subscription gets credited prorata for the unused period, and the new one invoices in full. The quote view links both subscriptions directly, so the relationship stays traceable and auditable.
Lots more tools in our MCP. For analytics as well as creating new products and prices.
Also in this release are quote templates and a redesigned quote flow, conditional discounts on coupons, custom fields on price plans and product items, a reverse action for payments that figures out cancel-versus-refund on its own, and a Metronome integration, alongside a longer list of invoicing, reporting and Desk improvements.
Full changelog is at docs.solvimon.com/changelog, as always.
Ready for billing v2?
Solvimon is monetization infrastructure for companies that have outgrown billing v1. One system, entire lifecycle, built by the team that did this at Adyen.



