Acumatica Consultant Staffing for Unlimited Users and a Metered API
Functional, developer and integration consultants who build around what your Acumatica license actually counts.
Acumatica consultant staffing is how companies running Acumatica Cloud ERP hire functional consultants, xRP developers and integration specialists of their own, on contract or direct hire, instead of waiting behind their reseller’s project work. KORE1 has recruited technology talent since 2005.
Last updated: September 16, 2026
Every Acumatica license is sold through a partner. The company calls itself 100% channel-driven on its about page and counts more than 350 value-added resellers. Sensible way to sell software. It also puts most of the people who know the product well on somebody else’s payroll.
The license is the other odd part. Acumatica doesn’t charge per user, and its customer bill of rights promises unlimited user access. So headcount tells you almost nothing about the job. Load does.
We recruit for Acumatica through the same ERP recruiters desk that handles ERP consultant staffing across every major platform at KORE1. Still choosing a system? Read the NetSuite versus Acumatica hiring comparison before this page. What follows is for teams already live, or about to be.
What Acumatica Counts When It Stops Counting Users
Take the user count away and something else has to set the ceiling. On Acumatica, several things do. Job descriptions almost never mention them.
- People who log in
- Not counted. Packers, field techs and approvers can all have their own accounts.
- API users
- Counted. Each license caps how many integration sessions can be signed in at once.
- Requests at once
- Counted. Anything past the cap waits in an internal queue.
- Requests per minute
- Counted. Halfway to the limit, Acumatica starts adding delay.
- AI Assistant use
- Counted in AI Units. The 2026 R1 program gave participants 5,000 a month, about 100 prompts.
The API limits all show on one form, the License Monitoring Console, screen SM604000. Ask a candidate when they last opened it. The good ones don’t have to think. Nobody else asks.
The hard part moved. Adding a fortieth warehouse login costs nothing, while an EDI provider, a shipping platform and a nightly reporting extract that each sign in through the web services API quietly spend headroom nobody on the finance side can see, right up until an order sync starts failing on a busy Monday. Nobody budgets for that.
Fifty Requests Arrive in the Same Second
Acumatica’s help documentation walks through this exact case. Fifty outside applications each send one request to the same server, every request takes a second to process, and the license allows 16 concurrent requests.
Web services API · 50 requests · 1 second each · 16 allowed at once
Processed now
One request per API processing core. These start right away.
Waiting in the queue
The queue holds 20. A request left waiting more than 10 minutes is declined too.
Declined
Turned away. Not counted as processed, either. Unless the integration catches that and sends them again, those records never land.
The Per-Minute Limit Brakes at Half
A second rule runs on top of the first. It’s quieter. Once the requests processed in the past minute reach 50% of the license limit, each new request gets held back a little, and Acumatica’s documentation even shows the math.
- License limit per minute
- 50
- Processed in the past minute
- 25
- Seconds left in that minute
- 20
- Delay on the next request
- 0.8 s
Twenty seconds split across 25 remaining requests. Small number, one request. It adds up. Multiply it across a catalog sync that fires every few minutes and the order backlog is suddenly somebody’s problem.
One more line on that page is worth circling. An application that never signs out keeps its API session open, and that can stop other applications from signing in at all. Every limit above is set by the license and spelled out in Acumatica’s License Restrictions for API Users documentation, which is why we screen integration candidates on arithmetic before architecture.
Configure, Extend, Connect or Own?
All four get posted as “Acumatica consultant.” They come from different places. Pay differs too.
Functional consultant
Sets up financials, distribution, manufacturing or construction to match how your business really runs.
Often paired with · manufacturing ERP staffingxRP developer
Writes C# graph and DAC extensions, keeps customization projects compiling, and owns what breaks at upgrade.
Adjacent pool · .NET developer staffingIntegration specialist
Builds against the contract-based REST API with OAuth 2.0, sizing every sync to your license limits.
Adjacent pool · integration engineer staffingSystem administrator
Runs roles, generic inquiries, patches and preview sandboxes after go-live, so the reseller stops being your help desk.
Often paired with · post-go-live support staffingSmall teams often fold two of these into one requisition. That can work. Price it for the rarer half, which is nearly always the developer or the integration skill, and compare it with published ERP consultant rates for 2026 before anybody sets the band.
Acumatica Consultant Staffing for Two Upgrades a Year
Acumatica ships two major versions a year, R1 and R2. 2026 R1 became available in March. Nobody gets to skip that.
Small updates changed too. Starting with 2025 R1, Acumatica replaced its monthly update releases with patches every two to four weeks, applied automatically for every SaaS customer, plus one optional service pack three to four months after each major version. Can a SaaS customer skip a patch? The company’s own FAQ opens its answer with the word no.
Customizations are where upgrades bite. Last September a team moving a customer from 2024 R1 to 2025 R1 watched its customization package fail validation, because the new version had renamed the PX.Concurrency namespace to PX.Async and two graph files still used the old one. A one-line change fixed each file. Finding it was the job.
Private cloud subscription customers decide when updates are applied. More time. Same work, moved onto your calendar.
So we ask developer candidates something a badge can’t answer. Which customization did you retire at your last major upgrade, and who signed off on losing it? People who have owned an instance through a few R1 and R2 cycles answer fast. They remember.
More questions in that shape sit in the ERP consultant interview question bank.
An Acumatica Edition Is Its Own Specialty
Acumatica is one platform sold in editions. General Business, Distribution, Manufacturing, Retail, Construction and Professional Services each license a different set of applications, per the product editions table, and a consultant who is excellent in one can be a beginner in the next.
- Construction
- Retainage, cost codes, compliance tracking, and the Procore and ProEst integrations.
- Manufacturing
- Bills of material and routing, MRP, advanced planning and scheduling, engineering change control.
- Distribution
- Sales and purchase orders, lot and serial inventory, warehouse management with barcoding.
- Retail
- Point of sale plus the Shopify, BigCommerce and Amazon connectors.
A construction controller will spot a consultant who has never billed retainage inside ten minutes. Distributors find out later. Usually at physical inventory.
Expect resumes from the Dynamics GP world too. Microsoft ends GP product support on December 31, 2029, with security updates running to April 30, 2031, according to its Dynamics GP lifecycle page, and Acumatica markets to legacy Microsoft Dynamics customers by name. GP finance knowledge carries over. The customization model doesn’t.
Rent the Upgrade, Own the System
Most Acumatica gaps come in three shapes. Length decides.
Contract
A defined job with an end date. An R1 or R2 upgrade, a customization cleanup before one, or an integration rebuilt to live inside the license limits. Scope it to one release cycle and it prices cleanly through contract staffing. Then it ends.
Contract-to-hire
Go-live just happened and nobody knows whether the support load justifies a permanent seat. Contract-to-hire gives you a quarter of real evidence first. Decide later.
Direct hire
Acumatica runs your billing, inventory or job cost every single day. Keep the person who knows why each customization exists on staff through direct hire. That memory is the asset.
Keeping the reseller is normal. An internal owner mostly changes what gets sent to them and how estimates get reviewed, and our implementation partner versus staffing agency guide covers when all of it should stay with the VAR. A whole crew for a migration or a second entity runs as project staffing, often next to ERP data migration staffing, and extra seats on an in-house ERP team come through ERP staff augmentation.
An Acumatica Consultant Search, From Edition Check to Start Date
What happens between the first call and a start date.
-
01
Name the edition and version
We confirm your edition, your current release, and whether you run SaaS or a private cloud subscription.
-
02
Read the license limits
Your administrator pulls API users, concurrent requests and requests per minute from the License Monitoring Console.
-
03
List what signs in
Every integration that calls the API gets named, along with its owner and how often it syncs.
-
04
Screen on your own case
Finalists walk through one of your real customizations or integrations instead of a textbook scenario.
-
05
Start or hire
You pick contract, contract-to-hire or a permanent offer, and we stay in touch through the first quarter.
Common Questions
What does an Acumatica consultant do day to day?
An Acumatica consultant configures the system around how the business runs and keeps it working as Acumatica changes underneath it. Mornings go to user problems, like a posting rule or a generic inquiry that stopped matching the books. Afternoons go to projects. Upgrade weeks swallow both.
How much does an Acumatica consultant cost?
$105,850 is the May 2025 BLS median for computer systems analysts, the federal category closest to ERP consultants, and experienced Acumatica specialists usually price above it. The middle half of that category earns $82,860 to $134,110. Contract rates for developers and integration leads run higher, and construction or manufacturing edition depth narrows the pool further.
Can we hire our own Acumatica consultant if a reseller already supports us?
Yes. The reseller sells and supports the license, and your own consultant or administrator works alongside them. Settle two things early. Who holds the customization project source, and who opens support cases with Acumatica.
Do Acumatica API limits really affect our integrations?
They do once several integrations share one license, because Acumatica caps API sessions, concurrent requests and requests per minute, and it starts delaying requests at half the per-minute limit. Past the concurrency cap, requests wait in a queue of 20. Anything waiting longer than 10 minutes gets declined.
What happens to our customizations at each R1 or R2 release?
Nothing, until somebody publishes them against the new version. That is when a package referencing a renamed class or namespace fails validation, the way customization code that still called PX.Concurrency failed when it was published to 2025 R1 last September. SaaS customers get a free preview sandbox to catch it before the real upgrade.
Should we hire a functional consultant or a developer first?
Functional, most of the time. Hire the developer first only when you already own customization projects or integrations that nobody on staff can maintain, because that code has to survive two major releases every year.
How long does KORE1 take to fill an Acumatica role?
Plan on roughly three weeks for a well-scoped Acumatica search, since the typical KORE1 IT search closes in 17 days. Asking for construction or manufacturing edition experience plus C# in one person takes longer. We’ll say so upfront.
What Does Your License Count Today?
Your edition, your release, and the integrations that sign in. That’s enough for a straight answer on which seat you’re short and what it pays.
Talk Through Your Instance →