There is no meter.
Genwright does not charge per action, per record, per API call or per token. The platform fee is set by the size of the operation on the platform, and it is the same fee whether you build one application or nine.
Per-user pricing quietly breaks the thing you bought the system for
Charge per user and an operation does the rational thing: it limits who gets an account. The driver shares a login. The night shift uses the supervisor's tablet. The contractor is entered by someone else the next morning.
Every one of those decisions destroys attribution. And attribution is the entire value of an operational record — who did it, when, and can you prove it. A per-seat model that produces a cheaper invoice and a worthless audit trail is a bad trade, and it is a trade the customer usually does not realize they are making until an auditor asks.
So field users do not carry a per-seat charge. It costs Genwright some revenue on paper and it is the reason the records hold up.
The greater of deployed users or units under management
Operations come in two shapes, and one measure cannot price both fairly.
People-heavy operations
A 3PL with four hundred warehouse and driver personnel and comparatively few tracked assets. Deployed users is the measure that reflects the load and the value.
Asset-heavy operations
An upstream operator with nine hundred wells and thirty people, or a leasing company with a large fleet and a small back office. Units under management is the measure that reflects it.
Adding the two would double-count an operation where each person manages assets, which is most of them. Taking the greater prices to whichever dimension is actually driving the size of the deployment.
Footprint questions
What counts as a unit under management?
Whatever the operation tracks as the thing being managed: vehicles, trailers, vessels, wells, tanks, plant assets. It is agreed during scoping and written into the agreement rather than reinterpreted at renewal.
What happens when we grow into the next band?
The fee moves to the next band. How and when that is assessed — and any notice you get before it applies — is set out in your agreement. Ask about it during scoping; a band model with a surprise reassessment is a bad model.
Does adding a second application change the fee?
No. Applications are added within the same deployment. The footprint measures the operation, not the number of workflows you have automated, which is deliberate — a pricing model that penalizes adopting the platform more widely works against both sides.
Are there usage charges we should expect?
There is no per-action, per-record or per-call metering in the platform fee. Model usage sits outside it entirely and is billed to you by Anthropic. Expert hours and builder subscriptions are the other separately listed items.
Tell us the two numbers and we will tell you the band.
Roughly how many people will touch it, and roughly how many units you manage. That is enough for an indicative fee before you invest any more time.