Ask most CFOs what they hate most about their ERP contract and the answer isn’t the software. It’s the invoice every time someone gets hired.
Per-user licensing punishes growth. Add a warehouse shift, bring on a new AP clerk, give a project manager view-only access to check job costs from the field, and the bill goes up, whether or not that person touches the system for more than ten minutes a day. Over a three- or five-year contract, that adds up to real money nobody budgeted for, and it forces an ugly workaround: companies start rationing logins, sharing credentials, or keeping people out of the system who should have visibility into it.
That’s not a licensing detail. It’s an operating model problem, and it shows up directly in your total cost of ownership.
The math that breaks under per-seat pricing
Say your ERP is priced at $150 per user, per month. A 40-person company pays $6,000 a month for licenses alone. Add ten people over two years of growth (new hires, seasonal staff, a warehouse expansion) and that number climbs to $7,500 a month before you’ve changed a single workflow. Multiply that gap over a five-year term and you’re looking at tens of thousands of dollars that had nothing to do with the value the system delivered. It’s a tax on hiring.
Companies respond to this the way you’d expect: they under-license. The purchasing manager doesn’t get a seat, so purchase orders route through email instead of the system. The field technician doesn’t get mobile access, so job costs get entered a week late from a paper ticket. Every one of those workarounds is a visibility gap, and visibility gaps are exactly what shows up in a Business Optimization Assessment as “we have the data, we just can’t see it in time to act.”
How Acumatica prices it instead
Acumatica licenses by consumption: the resources and transaction volume your business actually uses, not by user count. Practically, that means unlimited users at no additional license cost. Pricing is set by the applications you need, your expected transaction volume, and your deployment choice, and you can adjust those levels as the business grows without renegotiating a per-seat contract.
The result: every employee who needs visibility gets it. Warehouse staff can log receipts directly instead of handing a clipboard to someone with a login. Field technicians can update job costs from a phone instead of a windshield-mounted notepad. Finance can pull real-time reports instead of waiting for someone with the “right” license to run them. Acumatica’s stated position is direct about this: businesses shouldn’t be penalized for growing, and adding users shouldn’t cost more just because the company got bigger.
What this means for your implementation cost, specifically
When you’re building a business case for ERP, per-user licensing has to be modeled over the full contract term, not just year one. A system that looks cheaper at 15 users can cost significantly more once you factor in the headcount growth you’re already planning for. Consumption-based licensing removes that variable from the math entirely: the cost scales with transaction volume and data, not with how many people need to log in.
That’s the number a CFO actually needs before signing: not “what does it cost today,” but “what does it cost at the headcount we’ll have in year three.”
What this looks like when a business is actually scaling
Premier 1 Supplies, a 40-year family agricultural retail business, needed to unify B2C e-commerce with B2B ERP operations on Sage MAS 500, a system that couldn’t handle the volume or the payment compliance requirements the business had grown into. Dairy Connection, a 12-person ingredient supplier, was manually re-entering website orders into QuickBooks and Fishbowl because the systems didn’t talk to each other. Neither company’s core problem was headcount. It was a system that made growth expensive and manual, one workaround at a time.
That’s the pattern per-user licensing quietly reinforces: businesses ration system access to control cost, which limits exactly the visibility they need while scaling. Consumption-based licensing removes that incentive. The question shifts from “can we afford to give this person a login” to “does this person need visibility to do their job,” which is the question it should have been all along.
Where Crestwood fits
Crestwood has scoped this exact licensing math for manufacturing, distribution, and construction clients for 27+ years and 5,000+ implementations, and every consultant doing that scoping is an in-house Crestwood employee: the same person who prices the deployment stays engaged through go-live and support. If you want the actual pricing tiers and deployment cost ranges for your business, our Acumatica deployment and pricing breakdown has the specifics.
FAQ (for FAQ schema)
Does Acumatica really allow unlimited users at no extra cost?
Yes. Acumatica licenses based on consumption: the applications, transaction volume, and resources your business uses, not the number of user logins. Adding employees doesn’t trigger additional per-seat fees.
How is Acumatica’s pricing actually structured, if not per user?
Pricing is tailored to three factors: the applications your business needs, your expected usage and transaction volume, and your deployment preference (SaaS or private cloud). You scale resource levels up as transaction volume grows.
Will my ERP cost go up if I hire more people?
Not under Acumatica’s licensing model. You may need to adjust resource tiers as transaction volume increases, but adding users specifically does not carry a per-seat penalty.
Get a clearer view of your real ERP cost before you sign anything visit crestwood.com/acumatica to talk to an expert who understands your business needs.



