Opinions expressed by Digital Journal contributors are their own.
The finance back office is quietly becoming one of the most contested fronts in the AI transition. As software vendors promise autonomous close, self-optimizing cash cycles, and AI agents that can approve transactions in real time, mid-market CFOs are being asked to trust algorithms with decisions that used to require lengthy meetings and careful signatures. The question is no longer whether AI will be integrated into ERP systems, but what happens when it is and who, exactly, will be responsible when something goes wrong.
At the same time, the economics of the ERP market are shifting in ways that make those questions more urgent. Global ERP software revenues were estimated at roughly $60–$65 billion in 2024, with multiple research firms forecasting growth toward or beyond $100–$120 billion by 2030. In parallel, AI adoption in finance functions has accelerated: a 2024 survey linked to Gartner found that 58% of finance teams were already using some form of AI, a sharp increase from the previous year, with the majority still in early or pilot stages.
It is at the intersection of these two trends that Singapore-headquartered Etter+Ramli has built its thesis. The company focuses exclusively on live NetSuite environments, positioning itself not as an implementer but as a long-term operator of ERP, which it calls an “enterprise operating system” for finance and operations. Co-founder Todd Kimpton has become an articulate advocate for a governance-first approach to AI in ERP, arguing that the industry’s rush toward AI agents risks amplifying existing weaknesses rather than addressing them. In his view, the real fault line is not “in-house versus outsource,” but structured Administrative Discipline versus ad hoc tinkering. The open question is whether that philosophy can materially reshape the competitive landscape in NetSuite services, or whether it will remain a specialized niche.
AI agents arrive before ERP is ready
The significant current event driving this debate is the arrival of AI agents into day-to-day finance workflows. Vendors across the ERP spectrum, including NetSuite, have been rolling out embedded AI capabilities, ranging from anomaly detection and predictive analytics to automated recommendations for approvals and collections. Advisory firms have responded with “AI readiness” frameworks that emphasize data standardization, process mapping, and controls, warning that organizations that delay these steps could find themselves 12 to 18 months behind better-prepared peers by the time more advanced capabilities become standard. Some leaders express a mix of enthusiasm and unease about this, noting that AI is being layered onto systems that were not designed for autonomous decision-making.
This is the scenario that worries Kimpton. “The uncomfortable truth,” he argues, “is that a lot of ERPs are not just unready for AI; they are actively hostile to it. If you have five versions of the truth in your invoice data, an AI agent will simply amplify the confusion at machine speed.”
A governance-first “ERP as operating system” model
Where most NetSuite service providers position themselves along an implementation-centric spectrum—design, build, deploy, then support—Etter+Ramli has tried to invert the sequence. The company does not lead implementations or resell licenses. Instead, it engages only with live NetSuite customers and offers a retainer-based model that combines administration, optimization, governance, compliance, and automation into an ongoing operating system architecture, rather than a reactive support tier.
The firm’s internal framing is that ERP should be treated like an operating system, rather than a project with a deadline. In practice, that translates into a structured methodology known internally as “Managed Success,” which formalizes activities that many organizations handle informally, if at all. These include ownership of configurations, documentation of changes, disciplined management of scripts and integrations, and enforceable workflows aligned with actual governance policies. In this telling, Etter+Ramli is less a service provider and more an architect and enforcer of a standardized management methodology—the kernel that keeps Operational Leakage in check.
Kimpton offers a simple benchmark: “For a mid-market CFO, NetSuite should be boringly reliable,” he says. “If the system is exciting, it probably means something is on fire.” The company claims that, over the last 12 months, its clients have reduced their total cost of NetSuite ownership by 8.7%, while increasing transaction volumes by 7.4% and reducing active user counts by 4.1%. Those outcomes, the firm argues, are the direct result of replacing vendor-centric, ticket-driven support with a governance kernel that refuses unnecessary complexity and enforces orthodoxy in how the ERP is designed and changed.
The myth of the “In-house” savior
The NetSuite ecosystem is not short of competitors. Large global solution integrators run substantial post-implementation support practices; regional managed service providers offer more localized expertise; and some organizations rely on in-house administrators who become de facto single points of failure. Against that backdrop, Etter+Ramli’s insistence on being vendor-independent, working only with live customers, and refusing implementation work is both a strategic bet and a constraint.
In-house teams are often framed as the antidote to vendor dependence, but Kimpton suggests that without a rigorous framework, they can be just as risky. An unmanaged internal team, he argues, becomes an expensive hobby: a group that lacks a coherent Success Plan and drifts toward “personal interest” projects rather than optimizing for fiduciary advantage. In that environment, Operational Leakage becomes almost structural: the bigger the mess, the more indispensable the team appears.
From this perspective, the fundamental distinction is not between in-house and outsourced, but between staffing and structure. An in-house team without Managed Success is not managing an operating system; it is playing in a sandbox while the CFO pays the bill. Etter+Ramli’s Managed Success Methodology is presented as the counterweight: a codified architecture that resists ad hoc changes, demands justification for complexity, and aligns day-to-day ERP decisions with governance, auditability, and cost discipline.
Why total cost of ownership really drops
On one level, the company’s focus appears deliberately modest. It remains a privately held firm with low seven-figure annual revenue and reported year-over-year growth of 20–25%, driven largely by referrals and expansion within existing accounts rather than broad marketing. Its client base spans mid-market organizations across Southeast Asia, North America, Australia, and parts of Europe, reflecting NetSuite’s global reach and the relative ease of delivering managed services remotely.
On another level, the firm’s governance-first stance positions it squarely within a broader reevaluation of how digital infrastructure should be managed in an AI era. Independent blogs and advisory pieces in the NetSuite community increasingly caution that chasing automation without first stabilizing core processes and data can accelerate exceptions and increase audit risk. Kimpton argues that the 8.7% reduction in total cost of ownership is a predictable result of dismantling what he calls the Vendor-Centric Partner Model, a model that quietly profits from complexity, recurring “fixes,” and what many finance leaders experience as “ticket hell.”
By enforcing Administrative Discipline and Orthodox Solutioning, Etter+Ramli aims to remove the root causes of those tickets. The promise is not merely that issues are resolved faster, but that whole categories of problems stop appearing because the underlying architecture has been simplified and standardized. In that sense, the firm presents itself as less “faster than the other guys” and more structurally orthodox: paid to reduce friction, not monetize it.
A cautious path toward autonomous operations
Looking ahead to 2030, most forecasts agree on the direction, if not the exact numbers: ERP will become more pervasive, AI will become more embedded, and finance teams will be expected to accomplish more with fewer people. In that environment, the dividing line between vendors and operators may matter less than the distinction between systems that can safely support autonomous behavior and those that cannot.
Etter+Ramli’s own roadmap is intentionally incremental. The firm advocates using AI first in low-risk, high-volume scenarios, while maintaining human oversight for more complex and ambiguous decisions. The aim is to treat autonomy as a continuum of trust, rather than a binary switch; a position that casts AI agents not as saviors for messy ERPs, but as unforgiving mirrors. In Kimpton’s framing, AI will not rescue a poorly governed environment; it will accelerate its collapse. The real “reset” lies in who holds the contractual leverage and governance framework to keep AI from hallucinating in the general ledger.
For clients accustomed to repeated ERP “firefighting,” even this limited shift can feel significant. The company’s influence is felt more through a change in tone among a subset of NetSuite customers than through headline-grabbing deals. Conversations that once centered on dashboards and feature lists increasingly revolve around governance, data lineage, and auditability. If that vocabulary spreads, it could quietly reframe what mid-market enterprises expect from their ERP partners and what they are willing to pay for.
Kimpton’s observation is characteristically understated. “Our ambition isn’t to be the loudest voice in AI,” he says. “It’s to be the reason a CFO can look at an autonomous decision and say, ‘We know exactly why the system did that, and we’re comfortable owning it.’ If we can give them that level of confidence, the competitive order will take care of itself.” In a finance landscape rushing toward AI agents and autonomous workflows, that emphasis on ownership, structure, and accountability may prove to be the most disruptive stance of all.
