This article is relevant if you are a business executive trying to sort out what AI-generated software means for your NetSuite investment.
TL;DR Summary
A recent Fortune article by Zach Lloyd is worth paying attention to because he has real authority to speak on this subject. He is the founder and CEO of Warp, and before that he spent years at Google helping engineer Google Sheets into a product used by hundreds of millions of people. So when he says AI coding agents are collapsing the time and cost required to build useful applications, we should listen.
But for NetSuite leaders, the lesson is bigger than cheap app building. As interfaces and processing logic become easier to create, the durable value shifts to what sits underneath: the data model, the business rules, the permissions, the transaction integrity, and the accounting truth. That is why NetSuite still matters. In fact, it matters more. It gives us a serious platform with built-in gates and guardrails. Then our job is to add the next layer of explicit gates & guardrails so planning commitments drive operational practices for fulfillment, and accounting measures what actually happened. That is the path to trustworthy scale. That is also the path to meaningful AI automation.
Background
I want to start with Zach Lloyd because his credibility matters. He is not a casual observer making fashionable comments about AI. Fortune presents him as the founder and CEO of Warp, and it highlights his earlier work at Google where he helped build Google Sheets from a small project into a globally used platform. That is not a lightweight experience. He understands software construction at scale and what it means when the cost curve for building applications suddenly starts to fall rapidly.
His article lands because it explains a phenomenon many of us can already feel: software is becoming cheaper to create. That matters, but it should not push us into shallow thinking. It should push us to think more deeply.
I have already argued in my recent article, Rethinking Make vs. Buy for High Performance NetSuite Applications in the AI Era, that the old economics of application design are changing. This new discussion strengthens that point. We need to look again at what we should buy, what we should shape, and where the real value lives.
How Authoritative Software Leaders See the Direction of Change
Let’s reflect on Zach’s points and consider what it means to those working with NetSuite:
AI coding agents are compressing app-building time
Lloyd’s first major point is straightforward. AI coding agents are compressing the time required to build useful software. He points to his team’s production of a working Google Sheets clone in a matter of days.
That is a stunning statement! But let’s be careful with what it means. He is not saying they rebuilt the full Google Sheets product. He is saying that the cost and time required to produce something useful, something app-like, something functional enough to matter, have dropped dramatically.
This sits right on top of the make-versus-buy issue I have been talking about. For years, organizations tolerated standard application experiences because the cost of shaping them was simply too high. That assumption has now cracked. We do not have to wait for NetSuite Next or a future release cycle to get the logic we need that fits how management wants the business to work. The economics are changing before our eyes.
Standalone apps lose value when custom interfaces become cheap
Lloyd’s next point is that standalone applications lose value when custom interfaces become cheap to build. This is an important observation. If a useful interface can be generated in days rather than years, the interface itself becomes less defensible.
That is exactly right, and it is exactly why NetSuite leaders should rethink what they look at when evaluating software. We have spent too much time acting like the screen is the product. It is not. The screen is one expression of a model. It is one way to expose process. It is one way to prompt behavior.
More serious thinkers go deeper. The real question about the user interface should be, does it support the adoption we need to drive the business outcomes we demand? This matters because every user interface makes assumptions about how someone wants to work. Those assumptions may be good, bad, or merely generic. The breakthrough now is that we can stop treating the default interface as sacred. The platform’s interface is the default. It is not destiny. We now have more freedom to shape usability so people actually work the way the business needs them to.
Many SaaS products risk becoming glorified databases
Lloyd argues that many SaaS products may end up looking like glorified databases. He gives the example of using a recruiting platform primarily through its API while building a custom front end that better fits internal workflow.
That is a good point, but I want to drive it deeper. The real issue is not merely that the front end can be detached. The real issue is what the platform underneath actually represents.
In the world we are moving toward, the first question is the database and how it is modeled. The second question is the business rules around it. We want a platform that more closely models the business we are trying to produce so it can reliably drive the practices and actions we actually care about.
This is why NetSuite still deserves serious respect. If we strip off the native interface for a moment, what do we see? We see a set of business assumptions, transaction relationships, permissions, and accounting consequences that are generally sound. We see logic that protects us from making big mistakes. We see a structure that helps the business hold together.
That is not trivial. That is the point.
The “meta-app” becomes the new interface
Lloyd’s fourth point is that the “meta-app” becomes the new interface. In other words, a person states what they want, and an AI-driven layer generates the working interface or workflow on demand.
That is a big idea! It suggests individualized user experiences created on the fly (have you tried it yet with Claude.ai?). It suggests interfaces that can adapt to the role, the need, the moment, and even the person.
But let’s not get hypnotized by the novelty. We only care about this if it drives deeper user adoption. And we only care about deeper user adoption because it reflects a more serious commitment to the operating practices that support the organization’s mission.
This is why I keep coming back to the same idea: the user experience matters because it shapes behavior, but the deeper question is: what behavior are we trying to produce?
This is also why I see opportunity in areas where people dismiss NetSuite too quickly, especially CRM. If the objection is mostly about user interface fit, then AI reduces the cost of overcoming it. The native screen setup has blinded too many to the richness of the underlying model.
APIs and integrations are transitional, not the end state
Lloyd suggests that APIs and integrations are transitional artifacts of a world where data remains scattered across legacy systems.
I would frame that more carefully. Integration has always come with a tax. There is latency. There are data misalignments. There are governance challenges. There is the constant burden of staying in control.
So rather than saying integration simply goes away, I would say this: the value of centralizing the model remains very real. NetSuite’s single-platform premise still matters because centralized models are easier to understand, easier to govern, easier to trust, and easier to connect without unnecessary friction.
This is not ideology. This is practical systems thinking. Fragmentation has a cost. Always has. Still does.
Companies should structure data for agents
Lloyd argues that companies should organize their data in ways that make it easier for agents to work with.
That point is right, and it fits well with his prior one. We do have to store business information somewhere. But just because NetSuite is SaaS does not mean we are trapped or limited. That is too simplistic.
The real issue is whether the information is modeled clearly, related coherently, and governed well enough that both humans and agents can act on it safely. If the system is modeled well, NetSuite is not a prison. It is a platform. In fact, it can be exactly the kind of platform we need.
Not every app category is equally exposed
Lloyd does not claim that every software category disappears. He is careful about that, and that is to his credit. He notes that categories with complex business logic, unique data, trust, compliance, or transaction infrastructure remain more defensible.
This fits very well with ERP. The change in ERP should be slower, and for good reason. ERP is not a toy. It is part of what constitutes the business. It supports our deepest commitments around planning, operational execution, and accounting truth.
If we change these systems carelessly, we do not just create inconvenience. We create distrust. We create operational confusion. We create accounting risk. We create chaos that becomes expensive to unwind. We risk breaking real trust with customers with real business implications.
Enterprise platforms will matter more in this new reality. It is a reason to understand them more deeply.
NetSuite and the Planning, Operations, Accounting chain
This is where I want to bring forward the chain of thinking that matters most to business leaders wondering about this new world:
Planning commitments lead to operational practices for fulfillment, which lead to accounting measuring what happened.
That is the fundamental management lesson that may be lost in the hype. Planning expresses intention. It says what we mean to do. Operations turn that intention into action, or fail to. Accounting measures what actually happened and confirms whether the performance met the intended standard.
If those three are disconnected, then no amount of AI will save us. We will simply automate confusion, move it faster, and scale the disorder. Yet, if those three are connected, then the business has a real foundation. Then technology becomes a multiplier. Then AI has a chance to be useful.
This is why I keep insisting that the real value of NetSuite lies in unlocking it. It is that it can serve as a serious system of record, tying planning, operations, and accounting together in a disciplined way.
NetSuite gives us built-in gates and guardrails
This point needs to be emphasized because it is easy to overlook.
By simply accepting NetSuite as the core operational engine, we get a foundational set of gates and guardrails.
Debits equal credits. That must never break.
The accrual accounting perspective matters. All serious enterprises need to understand economic performance, not just cash movement. Accrual practices represent mature management considerations.
Inventory subledgers matter. Purchase orders, receipts, work orders, assemblies, bills of materials, transfer orders, shipments, and related transactions can be tied together coherently so that operational truth remains connected to financial truth.
These are not cosmetic features. These are not minor conveniences. These are platform-level protections. They help preserve trust. They help prevent significant errors. They help the business stay grounded in reality.
In a world where attractive interfaces and software logic are getting cheaper to manufacture, these kinds of built-in structural guardrails become more valuable, not less.
We still need our own Gates & Guardrails
But let’s be clear. NetSuite’s native protections are only the base layer.
The next layer is to define our own Gates & Guardrails that represent the business practices required for scalable operations. This has been a major part of my thinking for more than a decade, and I laid out a version of it in my 2017 article, Learn how to Manage any NetSuite Record by Exception.
This is the pattern our clients care about because it works.
- It says we should define what must be true before a record can move forward.
- It says we should make exceptions visible.
- It says we should identify where the human-in-the-loop needs to act.
- It says we should manage by exception, not by heroic manual chasing.
That is why this framework is so important right now. It is the missing control layer in much of the AI conversation. Everyone wants the new automation. Sure. But automation without control is just accelerated chaos.
This is where we are good. We do not just automate activity. We help management define the commitments that matter and then translate them into operating structures that can scale.
Getting ready for AI agent-driven tasks
Once a Gates & Guardrails framework is in place, we now have something useful to work with.
- Now, reasoning agents can inspect exceptions.
- Now they can summarize likely causes.
- Now they can suggest next actions.
- Now they can support the human-in-the-loop in ways that actually reduce friction without compromising control.
And over time, if recurring exceptions are cataloged and understood, those solutions can be fed back into the model so the process keeps improving.
But here is the hard truth: it is a fantasy to think reasoning agents can safely run important work when the process itself has not been disciplined around exception management first. If we cannot get the process to work by exception, then AI agents will absolutely wander into places we do not want. They will amplify the very chaos we are supposed to be taming.
Modeling is still the leadership discipline
This is why my 2025 article, Modeling: The Leadership Discipline Behind NetSuite Excellence, matters even more now than when I wrote it.
We need leaders who can be explicit about the commitments they want the business to make. Then we need those leaders to translate those commitments into scalable operations and insightful accounting.
That is the work. Shortcuts do not help. Tool enthusiasm does not help.
If the model is unclear, then more powerful tools simply make the resulting confusion happen faster and on a greater scale.
We must tame the default condition of chaos into an ordered world in accordance with vision and intention. That takes leadership. It takes the ability to see what matters, to specify it clearly, and to build structures so that both humans and agents can reliably act within them.
Why This Matters to Clients and to Serious Builders
The good news is that we are in the right space. The lesson from Lloyd’s article is not that enterprise systems are going away. The lesson is that weak workflow shells are increasingly vulnerable, while serious systems of record with meaningful business logic become even more important. That is encouraging for NetSuite thinking, but only if we do the work.
The tool alone does not deliver value. The value comes when management designs planning practices that translate into operational practices, which then allow accounting to measure and confirm whether intentions are met.
That is where the return lives. That is where trustworthy automation lives. We believe this is where the best firms will distinguish themselves.
At Prolecto, this is the kind of work we care about. We help clients exploit NetSuite’s foundational strengths while designing the additional Gates & Guardrails needed to scale responsibly. We bring methods, algorithms, practical patterns, and real implementation discipline because we care about getting the model right. We care about listening well. We care about execution. And in the world we are moving toward, that is exactly the kind of leadership that will be in short supply.
If you found this article relevant, feel free to sign up for notifications to new articles as I post them. If you are ready to shape your NetSuite environment so planning commitments drive operational fulfillment and accounting confirms performance inside a well-governed AI-ready framework, let’s have a conversation.
