/
.webp)
September 2008.
Lehman Brothers has just filed for the largest bankruptcy in American history. Bear Stearns has already been sold for pennies on the dollar. The Dow is dropping by the hundreds of points, day after day. Companies everywhere are freezing budgets, laying off staff, and quietly shelving anything that looks like a long-term bet.
John Howell and Mike Shchelkonogov are choosing this exact moment to start a company.
Not just any company. An enterprise software company. One that will build cloud ERP for small and midsize businesses at a time when most CFOs in America are calling their banks to figure out if they still have money.
The timing looks insane on paper. No venture capital firm wants to back a new software company in a collapsing economy. The companies they want to sell to are cutting IT budgets, not expanding them. And the technology they're betting on — "cloud" software delivered over the internet — is not yet the obvious future. In 2008, "cloud" is still a sales pitch that takes three slides to explain.
But Howell and Shchelkonogov have something that makes them willing to move anyway: they know the incumbent software world from the inside. They know its weaknesses. And they've made a calculation that the crisis that's scaring everyone else will, eventually, make their bet look smart.
They just have to survive long enough for the world to catch up.
The World They Came From
To understand why Acumatica exists, you have to understand the world that Howell and Shchelkonogov worked in before it.
The mid-market ERP space in the early 2000s was ruled by a handful of entrenched players — SAP, Oracle, Sage, and Microsoft's Dynamics lineup, which had been built largely through acquisition. Microsoft bought Great Plains in 2001 and Solomon Software around the same time. The Dynamics family grew into a sprawling suite: GP, SL, NAV, AX. Each product had its own architecture, its own partner ecosystem, its own legacy codebase stitched together over decades.
The economics of that world were built around a specific model: software installed on-premise, sold through a network of resellers called Value Added Resellers (VARs), with implementation costs often equaling or exceeding the software cost itself. A mid-market company putting in a new ERP could expect to spend anywhere from $100,000 to $500,000, wait 12 to 18 months for deployment, and then spend years managing customizations that made upgrades nearly impossible.
The per-user license fee was the heartbeat of it all. More users meant more money — for the software vendor, for the VAR, for everyone in the channel. It was a beautiful business if you were the vendor. For the customer, adding five new users mid-year meant a phone call to the reseller, a contract amendment, a purchase order, and a line item in the budget that wasn't there before.
Howell had lived inside this ecosystem. He understood the margins, the partner dynamics, and — critically — the frustrations that customers quietly accumulated. The software worked, mostly. But it was expensive, slow to deploy, and anchored to a pricing model that treated the customer's growth as the vendor's revenue event.
Shchelkonogov brought the technical depth. He would become Acumatica's CTO, leading an engineering team — based initially in Russia — with the skills and vision to rebuild ERP from the ground up, not as a client-server application ported awkwardly to the web, but as a true cloud-native platform designed for the browser from day one.
That distinction would matter enormously.
The Russian Engineering Foundation
Shchelkonogov's Slavic name is not incidental to the Acumatica story. The original engineering team was built in Russia — a deliberate decision that gave the company access to world-class software talent at a fraction of what comparable engineers cost in Seattle or San Francisco.
In the late 2000s, before US-Russia tech relations deteriorated, Russian software development shops were widely regarded as some of the most technically sophisticated in the world. The mathematical and computer science traditions of Russian universities produced engineers who thought differently — more rigorous, more comfortable with complex systems architecture, less prone to the shortcuts that accumulated into technical debt.
For a bootstrapped startup trying to build a genuinely new ERP architecture while keeping burn low, a strong Russian engineering team was a strategic asset. Acumatica could do more with less. They could afford to build it right.
That engineering culture shaped Acumatica's DNA in ways that would outlast the Russian team's direct involvement. The platform's architecture — modular, API-first, built to extend — reflects the kind of careful, systems-level thinking that tends to come from engineers who learned to build things that last.
2008–2012: The Years Nobody Was Watching
Acumatica's early years were not a growth story. They were a construction project.
Howell and Shchelkonogov were not racing to hit a hockey-stick revenue curve. They were building a foundation — an ERP platform that could eventually displace the on-premise systems they'd spent their careers watching customers struggle with. That meant making architectural decisions in 2008 and 2009 that would only pay off years later.
The core technical bet was building what they called the xRP platform — a cloud framework designed not just to deliver Acumatica's own ERP applications, but to serve as a foundation that partners and independent software vendors could build on top of. It was a platform strategy disguised as a product company. At a time when every other ERP vendor was treating customization as an afterthought (something your VAR would handle for a fee), Acumatica was building extensibility into the architecture itself.
They chose .NET and C# as their development stack — the same tools that Acumatica's VAR partners were already using in the Microsoft ecosystem. This was not an accident. It meant that the thousands of developers who already lived in that world could extend Acumatica without learning a new stack. The barrier to building on top of Acumatica was deliberately kept low.
The VAR Channel Decision
One of the most consequential decisions Acumatica made in its early years was to build no direct sales force. At all.
Every customer acquisition would flow through VARs — the same independent resellers who had built careers selling and implementing Dynamics, Sage, and similar products. Acumatica positioned itself as their next-generation option: a cloud-native platform with better architecture, better pricing economics, and better margins for the resellers themselves.
This was a calculated choice that cut both ways. On the downside, Acumatica would never own the customer relationship directly. They would always be one step removed, dependent on partners to represent them well. On the upside, they could scale distribution without building a massive internal sales organization — which they couldn't afford anyway. And they could tap into a ready-made network of partners who already had the customer relationships, the industry expertise, and the implementation capacity.
By going 100% channel, Acumatica was, in a sense, betting that their product could sell itself once a motivated partner got it in front of the right prospect. The partner economics had to be compelling enough to make those partners choose Acumatica over incumbents.
Acumatica made a promise that became a differentiator in its own right: the most generous margins and terms in the industry. When your entire go-to-market depends on other people's enthusiasm, you pay for that enthusiasm.
The Long Ramp
The years from 2008 to 2012 were not glamorous. Acumatica was not raising Series B rounds to put on TechCrunch. It was quietly building product, slowly recruiting partners, and watching the cloud transition in enterprise software unfold at exactly the pace Howell and Shchelkonogov had predicted — which is to say, much more slowly than the tech press wanted to believe.
Salesforce was proving the cloud CRM thesis. NetSuite was proving cloud ERP could work for small businesses. But mid-market ERP — the $500M to $2B revenue companies with real manufacturing, distribution, and financial complexity — was still deeply on-premise. Those companies had too much invested in existing systems to move quickly. Their VARs had too much revenue tied up in support contracts to push migration.
Acumatica was planting seeds in soil that wouldn't yield crops for years.
The Per-Seat Tax
In enterprise software, there is a tax on growth. It's called per-user licensing.
Every major ERP vendor — SAP, Oracle, Microsoft Dynamics, NetSuite — built their revenue models on the same foundation: you pay per seat. Add a user, pay more. Grow your company from 50 people to 200, your ERP bill quadruples. It's presented as a feature (you only pay for what you use), but it functions as a penalty on the thing your vendor is supposed to be helping you do.
The per-seat model also creates perverse behavior inside companies. Finance people guard user licenses the way they guard headcount. Employees who need occasional access to financial data get locked out because nobody wants to pay for another seat. Customers, auditors, temporary workers — anyone who would benefit from system access gets excluded because access has a price tag. Data silos form, not because the technology can't connect people, but because the pricing model makes connection expensive.
Acumatica looked at this and decided to do something different.
Resource-Based Pricing
Acumatica doesn't charge by the user. It charges by computational resources consumed — roughly, by the volume of transactions, data storage, and processing activity the business generates. You can have one user or a thousand users; the cost doesn't change based on headcount.
The practical implications of this are profound and, in some cases, invisible to companies that have lived so long under per-seat pricing that they've stopped noticing the constraints it creates.
Under Acumatica's model, a company with 50 employees can give access to all 200 people in its supply chain — suppliers, contractors, customers checking on order status, temporary warehouse staff during peak season. Not because it's cost-free, but because the cost structure is based on how hard the system is working, not on how many people are touching it.
This shifts the conversation from "who gets a license?" to "what do we actually do with this system?" It's a subtle but powerful reframe. Companies that move to Acumatica frequently describe giving their ERP access to people who were previously excluded — and discovering that access itself creates value they weren't capturing before.
The model also changes the competitive conversation dramatically. When a manufacturer is comparing Acumatica to NetSuite and running the math on a 150-person company that might grow to 400 over five years, the per-seat model starts to look terrifying. One Acumatica customer — a pharmaceutical services company called ProPharma — reported saving $120,000 annually compared to what per-seat licensing would have cost them at their scale.
That number spreads through the industry like a story. Every VAR who sells Acumatica into a competitive evaluation has a version of that story ready.
The Platform Beneath the Product
The pricing model gets the attention, but the xRP platform is the structural bet underneath it. Acumatica was not just building ERP. It was building a cloud application framework that could be used to create ERP — and specifically, to let partners and ISVs create industry-specific extensions that live natively within the system.
This matters because no horizontal ERP vendor can be all things to all industries. SAP tries, and the result is a product so complex that implementation partners have become a multi-billion-dollar professional services industry just to absorb the complexity. Acumatica's answer was different: give the platform to the ecosystem and let specialized builders go deep in their verticals.
The construction edition. The manufacturing edition. Distribution. Field service. Each one not built solely by Acumatica, but extended by a community of ISVs who know those industries better than any ERP vendor ever will. The platform becomes more valuable as the ecosystem grows. The ecosystem grows because the platform is genuinely extensible. It's a flywheel that Acumatica set in motion slowly, years before anyone was paying attention.
The EQT Acquisition (2019)
By 2019, Acumatica had reached the kind of scale that attracts serious money. The cloud ERP market was no longer a concept in need of explanation. The mid-market transition off on-premise systems was real and accelerating.
In June 2019, EQT Partners — a Swedish private equity firm with deep roots in enterprise software — acquired Acumatica and simultaneously merged it with IFS, a Swedish industrial software company. The combined entity operated under EQT's ownership, with Acumatica maintaining its independent brand and go-to-market while gaining access to EQT's capital and IFS's global enterprise relationships.
The deal was, in retrospect, a validation of everything Howell and Shchelkonogov had built in the years when nobody was watching. The $430 million valuation attached to the transaction (widely cited in industry coverage at the time) was the market's formal acknowledgment that the 2008 bet had been right.
Under EQT's ownership, Acumatica accelerated. The company invested heavily in the manufacturing and construction verticals — industries where the operational complexity is high, the data is messy, and the gap between what legacy systems could do and what modern businesses need is widest. These were not the glamorous markets of fintech or SaaS. They were industries full of companies that had been sold bad software for decades and had the maintenance bills to prove it.
CEO John Case, who joined Acumatica after the EQT acquisition, brought a steady operational hand. The company grew from a few hundred employees to over 800 in six years, crossing 10,000 customers worldwide. The VAR network expanded to over 350 active partners and more than 500 ISVs in the marketplace.
The Vista Equity Acquisition (2025)
In May 2025, Acumatica entered its next ownership chapter. Vista Equity Partners — a firm that specializes in enterprise software and has a long track record of operational improvement in tech companies — signed a definitive agreement to acquire Acumatica from EQT.
Vista Equity brought a different thesis than EQT. Where EQT was the European PE firm hunting for cloud ERP assets to combine, Vista is the enterprise software specialist who believes it can run software businesses better than most founders can. The acquisition was not about combining Acumatica with another company. It was a vote of confidence in what Acumatica already was — and a bet on what operational discipline could unlock.
The move into AI, signaled loudly at Acumatica Summit 2026, was the product vision sharpening in parallel with the corporate transition. The company launched "AI Studio" — a set of native AI capabilities embedded into the ERP, not bolted on — and positioned the platform as moving from a system of record to a system of intelligence. Jon Pollock, the new CPO who replaced Ali Jani after Jani's 15-year tenure, articulated the next horizon: ERP that doesn't just store data, but predicts, recommends, and acts.
The Numbers That Tell the Story
Seven global offices. 800+ employees. 10,000+ customers. 74% of company resources dedicated to R&D. No direct sales force — every customer acquired through a partner.
These numbers describe a company that looks almost nothing like the software giants it competes against. SAP has 100,000 employees and a direct enterprise sales army. Oracle has 160,000 people. Microsoft has teams of account executives who have spent careers selling Dynamics. Acumatica has fewer people than some of its competitors have in a single division — and it has grown faster than any of them in its market segment for a decade running.
That efficiency is not an accident. It is a design principle.
1. The company was built by people who had made the incumbent's bed — and decided to unmake it.
The founding team didn't come from Silicon Valley. They came from the Microsoft Dynamics partner ecosystem — the world of Great Plains resellers, mid-market ERP implementations, and the channel economics of selling business software to $50M-$500M companies. They had seen that world from the inside: the per-user tax, the bloated implementation projects, the partner margins that created perverse incentives. When they built Acumatica, they weren't guessing at what mid-market customers were frustrated by. They were building the antidote to a system they'd personally operated within.
2. The engineering team that built the original platform was in Russia.
Mike Shchelkonogov's name is the tell. The initial Acumatica engineering team was developed in Russia, at a time when Russian software talent represented one of the world's great undervalued resources — deeply trained in mathematics and systems thinking, accessible at costs that would have been impossible to replicate in the US. That team built the xRP platform — the architectural foundation that still underlies Acumatica today. The platform's quality and extensibility are, in part, the product of an engineering culture that valued getting systems architecture right over moving fast and fixing it later. The geopolitical complications that later made US-Russia tech collaboration difficult came well after the foundational decisions were already made in code.
3. The per-resource pricing model doesn't just save money — it fundamentally changes organizational behavior.
Companies moving from per-user ERP to Acumatica consistently report a behavioral shift that they didn't anticipate: they start giving the system to people they previously excluded. Suppliers get access to check inventory availability. Customers get access to check order status. Seasonal workers get access during peak periods. Temporary contractors can see what they need to see without someone manually exporting a spreadsheet. The system stops being a resource to be rationed and starts being infrastructure everyone uses. That behavior change — invisible on a pricing comparison sheet — is often what produces the biggest ROI for customers who switch.
4. Acumatica has no direct sales team, and this is a deliberate strategic choice, not a limitation.
In a world where SaaS companies typically celebrate their enterprise sales organizations as the engine of growth, Acumatica's 100% channel model looks like an anachronism. But it's actually a calculated bet on leverage. Every VAR and implementation partner who sells Acumatica brings with them years of industry relationships, vertical expertise, and customer trust that no direct sales hire could replicate. The channel pays for itself by delivering customers that a direct sales motion would take ten times longer to reach. The tradeoff is control — Acumatica never owns the customer relationship. But for a mid-market ERP vendor serving manufacturing, construction, and distribution, where the partner often knows more about the customer's business than the customer's own leadership team, that tradeoff has proven to be worth it.
5. Acumatica was born the same year the financial crisis destroyed the companies it was being built to replace.
The 2008 financial crisis didn't kill ERP. But it exposed the fragility of the model Acumatica was disrupting. Companies that had spent years locked into expensive on-premise systems, with upgrade cycles measured in years and IT costs measured in millions, suddenly faced a world where cash was scarce and flexibility was existential. Acumatica launched into that environment not as a disruption, but as an alternative that would only look better as the crisis prolonged. The companies that survived 2008 and 2009 and came out lean were exactly the kind of customers Acumatica was built for: businesses that needed enterprise-grade software at a cost structure that didn't assume unlimited IT budgets. The founding timing that looked insane in September 2008 looked prescient by 2011, and looked like genius by 2015.
Acumatica is headquartered in Bellevue, Washington. As of 2025, it is owned by Vista Equity Partners. Its platform serves 10,000+ customers across manufacturing, construction, distribution, retail, and professional services, delivered exclusively through a network of more than 350 Value Added Resellers and 500+ ISV partners worldwide.
