Home / Points of View #1
Prolecto Points of View · No. 1

Model the business, then fit NetSuite.

Think about the business you want to build, the experience you want to give your customers, and what it will take to make both happen. Get that right first. Then make NetSuite work for your business, one step at a time.

Uncovering the Prolecto Roadmap · documentary
Read the documentary transcript

At some point, probably a half hour into it, his mood shifted. About an hour into the conversation, he would pause and say, "I really love these questions."

Welcome to our first point of view: the Prolecto Roadmap, led by our Architecture Practice. Growth creates complexity. The systems and habits that built the business start to limit what comes next.

This is often a time for planning, and planning is what makes the difference in getting the outcomes we all know are possible on the platform. Clients often come to us because what they ended up with was an installation of NetSuite, not a well-planned implementation of NetSuite.

One of the most important things is to understand where you're going. Ambitious clients always have a storyline about a capacity they are trying to unlock in their business. Usually it is about reaching new customers, through an extension or new product lines. There is some story about getting more through their business.

So we model the business at the leadership layer first. Then we shape NetSuite to fit it. It's always the business first, then how the leadership team sees things going, and then we naturally shape the business system, NetSuite, to fit. We've got a platform that can be shaped. That's why I like to call it Play-Doh. How do we get it to fit powerfully into the organization? That means understanding where the business is trying to go, and the constraining factors that are reducing its capacity to get there.

That happens in the roadmap workshop: three to five days in the room with the whole leadership team. When you're building a really good roadmap, you're painting a vision of a potential future, and it's wonderful to see it all connected up. The workshop pulls leaders out of the day-to-day. Everyone sits down together and works through what we're going to build. We listen to the issues the team is facing and guide the conversation toward a path everyone can get behind.

Once you understand that, you ask where you are in relation to your capacity to do it with these tools. That story of where they're trying to go, and where they are now, lets us develop a bridge: what configuration we will need, what adaptation we will need, and how we will help people get up to speed to reach those new capacities.

Leadership leaves with something they can act on: four deliverables and a phased plan to get there. The biggest output is a solution design, an architecture for how the business should work and how NetSuite fits it. That plan belongs to the client. They can build it with Prolecto or take it and do it on their own. Either way, they leave with a clear path forward.

We ended up producing a three-phase plan. Phase one is everything they have to do immediately. Phase two is where we get the scalability and the operations. And they appreciated that I wasn't trying to throw away an existing business system they were using.

Here's how that worked for Totus, a gift card platform built for brands. Daniel Hawtof, Chief Product Officer at Totus: "It became pretty clear pretty early that Prolecto was the best choice for a unique business like us. We did a roadmap process where we brought our finance, ops, sales, implementation and technology teams together with the Prolecto team to do a deep dive on how we operated and how we financially managed the business. It's interesting when you get the opportunity to take several days and really listen, in great detail, to each other. It also allowed us to ask: we do certain things today, but is that the right way to do it? We started doing that three years ago, but now that we know more, should we re-engineer some of it to operate better? Prolecto has really helped us align our vision, process and technology into a clear path. We did not have that before. I don't think we could have accomplished it alone."

The objective isn't a roadmap. It's a business that scales predictably on one platform. Every engagement starts with architecture. Talk to an expert at prolecto.com.

How to Unlock NetSuite's Full Potential

It starts with the business: three things made explicit before anyone touches a field. Prolecto calls it the commitment chain.

Modeling the business first means the leadership team defines how the company should run at scale before anyone configures NetSuite: what it promises customers, how operations keep those promises, and how accounting measures the result. NetSuite is then shaped to fit that model and built in phases, so each phase adds to the last instead of undoing it.

The Benefits

What Changes When the Business Comes First

Better decisionsNumbers leadership can trust, from one version of the truth instead of reconciled spreadsheets.
Leadership alignedExecutives agree on what the company promises, and how it keeps those promises, before anything is built.
Lower cost, less reworkNo reimplementation and fewer add-ons. Each phase builds on the last instead of undoing it.
A system designed to fitNetSuite shaped to how the business should run, not to the workarounds it grew up with.
A more effective teamPeople work in the system instead of around it, and manage by exception instead of heroics.
AI that worksClean records, clear rules and permissions give AI something reliable to act on.

Client Stories: What Getting the Business Right First Looked Like

Case study · Totus
“It's interesting when you get the opportunity to take several days and really listen, in great detail, to each other. You learn more about the core challenges, and you test whether your assumptions were valid.”
Read the interview transcript

I'm Daniel Hawtof. I'm Chief Product Officer at Totus, a relatively new gift card platform built for brands.

It became pretty clear pretty early that Prolecto was the best choice for a unique business like us.

One of the first steps we went through with Prolecto: we had some virtual conversations to prepare, and then we did a roadmap process where we brought our finance, ops, sales, implementation and technology teams together with the Prolecto team to do a deep dive on how Totus operated and how we financially managed the business.

The roadmap process was interesting for all of us because, as a young company, we're very heads down. We do our best to share information and understand the different functions of our company, their challenges and how we can overcome them. I run product, so it's my job not only to achieve what we need for our brands, but also to help our own functional teams succeed.

It's interesting when you get the opportunity to take several days and really listen, in great detail, to each other. You learn more about the core challenges and the issues. Maybe you made some assumptions, and you got a chance to test whether they were valid. It also allowed us to ask: we do certain things today, but is that the right way to do it? We started doing that three years ago, but now that we know more, should we re-engineer some of it to operate better?

Prolecto has really helped us align our vision, process and technology into a clear path. We did not have that before. I don't think we could have accomplished it alone. NetSuite along with Prolecto is a clear strategic partner for us to continue the outstanding growth Totus has had so far, and to grow in a very controlled manner.

Daniel Hawtof
Daniel HawtofChief Product Officer, Totus · interview, 3:20
Client story · Syringa Networks
“Prolecto met us where we were, cut through the noise, and helped us stand up a NetSuite-centric operating model that actually scales.”
Michael Leonhardt
Michael LeonhardtCTO, Syringa Networks, LLC

What are your growth ambitions? What's holding you back?

About an hour into a recent roadmapping workshop, a CEO who had walked in guarded paused and said, “I really love these questions.” The Prolecto team had not shown him a single NetSuite screen. They had asked how his business operates, what it promises its customers, and where it needs to be in three years.

His company had already implemented NetSuite once. A merger, new private equity money and a three-year growth target meant the system now had to scale, and the first implementation had not given him what he expected. His caution made sense. The questions were what changed the room.

For more than fifteen years, Prolecto has written weekly about NetSuite and worked with more than 500 clients. Across all of it, one pattern separates the companies that scale on NetSuite from the ones that reimplement: whether leadership decides how the business should work before anyone configures the system.

Why it works

A business is a chain of commitments.

This sounds abstract. In practice it means writing down three things before anyone touches a field: what the company promises, how the work keeps those promises, and how that activity becomes economic truth.

Prolecto calls this the commitment chain. Planning informs operations, and operations drive accounting. Once the chain is explicit, NetSuite can act as the nervous system of the company. It carries the signals between sales, operations and finance, enforces the standards management chose, and lets people manage by exception instead of by heroics.

NetSuite is built to take the shape of your business.

QuickBooks and industry packages hand you a process and ask the business to conform. That works for a while. NetSuite takes the opposite approach. It is a general-purpose platform with a strong financial core, designed to be shaped, and it asks leadership to define the shape.

When nobody designs the business and its systems first, the implementation configures feature by feature and will likely mirror how the company already works, workarounds included. The system then amplifies whatever confusion or weaknesses in process were there. The symptoms are familiar: shadow spreadsheets, reports nobody trusts, users who route around the system. Many companies incorrectly conclude they bought the wrong software, when the issue is deeper and they have more agency. Usually they had the right software and the wrong implementation.

Leadership mindset unlocks the platform.

The firms that thrive on NetSuite are rarely the best funded. Their leaders look for patterns instead of features, and they use the system to express accountability instead of delegating it to software. Prolecto sees three mentalities: leaders who want a stronger feature set, leaders who want their operations to harmonize, and leaders who treat NetSuite as strategic infrastructure. Only the third realizes the platform's potential.

Break-fix thinking keeps companies small. Solution thinking composes proven patterns into an architecture. Skipping this design work does not save time. It shows up later as technical debt.

What you gain

Clean accounting starts upstream.

Many clients first call Prolecto about finance. The period close takes too long. Inventory valuation is suspect. Product margin is unclear. Journal entries get reclassified every month-end.

These sound like accounting problems, but accounting only records what it can with the inputs available. When operational records are incomplete, finance ends up reconstructing the story after the fact, often with estimates. To fix accounting, fix operations. To optimize operations, strengthen planning. Margin you can trust is designed into the transaction architecture. It should not be rebuilt in a spreadsheet after the fact.

Fit NetSuite to your complexity.

“Can NetSuite work in our business?” is one of the questions executives ask Prolecto most. The honest answer is that complexity nobody has mapped will keep NetSuite’s potential locked away. Start with the products and services the business seeks to offer customers. Consider the best practices for delivery, and contemplate the accounting while respecting the coordination required to produce recurring customer satisfaction. Visualize the reporting and data insights managers need to drive scalable business flows.

Unlocking NetSuite’s potential always starts with a clear picture of how the business should run. The configuration comes second.

One platform at the center keeps one truth.

The second question usually follows: “Do we need another tool for that?” Sometimes the answer is yes. Once Prolecto maps the business requirements, the team often finds that NetSuite’s native structures need adapting for a better fit. Prolecto has built configurable quoting without a CPQ subscription, portfolio project management on NetSuite, and entity deduplication without another product add-on.

While Prolecto favors hub-and-spoke designs with NetSuite at the center of the universe, there are times when other system architectures make sense. For example, for a rental-based business, the client leadership appreciated that Prolecto fully embraced their existing business system and proposed integrating it with NetSuite. The key is to make good assessments about the trade-offs between pragmatic and ideal realities.

Clear business rules make AI pay off.

AI is making screens, scripts and small applications cheap to build. That shifts the durable value to what sits underneath: the data model, the business rules, the permissions, transaction integrity and accounting truth. NetSuite matters more in that world, not less.

NetSuite itself is making the same point. At SuiteWorld 2026, founder Evan Goldberg described an AI-first NetSuite and said the AI has to be grounded in how the business actually works.

“Reasoning without context is just guessing with confidence.”Evan Goldberg, Founder and EVP, Oracle NetSuite, SuiteWorld 2026 keynote · Computer Weekly

For a NetSuite customer, that context is how the business is designed to work. It matters even more now that people can work with NetSuite from outside it. Through MCP, someone can ask an AI tool such as Claude or ChatGPT to read and act on NetSuite data without opening a NetSuite screen.

Inside NetSuite
A person
NetSuite screensForms, saved searches, workflows and approvals guide the work
Outside, through MCP
A person in Claude or ChatGPT
AI agent, via MCPNo screens. The agent sees only the records, rules and permissions
Your business, as designed in NetSuiteRecords, rules, permissions and the commitment chain
Both paths land on the same records and rules. Inside NetSuite, the screens guide people. Outside, the records and rules are all the AI has to go on.

A sound design makes NetSuite safe and useful from anywhere. An unclear one leaves the AI guessing.

Consider an AI agent that reads a customer complaint and ships a free replacement. No employee approved that shipment, yet inventory is consumed and margin is spent. Someone committed in advance to letting the agent act within those boundaries. The human commitment did not disappear. It moved upstream into the design of the system, which is exactly where the design work happens.

Where to start

Define the optimal state, then phase it.

The practical step is simple and often skipped. Before configuring anything, ask how the business should work. Which practices exist only because an old system required them? Where could you serve customers, fulfill commitments, earn revenue and measure success better? Define that optimal state, with the relationships, rules and exceptions that matter, and write it down. Then let it decide how NetSuite supports the organization, and phase the work so phase one handles what cannot wait and phase two builds scale. That is how companies avoid a reimplementation.

This is what Prolecto’s Roadmapping engagement does. Senior Prolecto leaders spend three to five days with your leadership team, and leadership leaves with four deliverables it can act on:

Transaction & entity architectureA blueprint of how value flows through the business
Governance modelAlignment and control at scale
Phased implementation planA realistic path to incremental value
Investment & risk insightsClarity on investment, risks and expected outcomes
“Prolecto has really helped us align our vision, process and technology into a clear path. We did not have that before.”Daniel Hawtof, Chief Product Officer, Totus

Turn this thinking into your roadmap.

In three to five days, Prolecto’s senior leaders and yours define how the business should work and leave with a phased plan you own.

70+

This point of view is supported by over 70 articles.

Frequently Asked Questions

Planning a new implementation

  • What does it mean to model the business first?

    Modeling the business first means the leadership team defines how the company should run at scale before anyone configures NetSuite: what it promises customers, how operations keep those promises, and how accounting measures the result. Prolecto calls this the commitment chain. NetSuite is then shaped to fit that model and built in phases, so each phase adds to the last instead of undoing it. In Prolecto's Roadmapping engagement, this takes three to five days with the leadership team.

  • What leads to a successful NetSuite implementation?

    A successful implementation is one where NetSuite runs the business the way leadership intends: one set of numbers everyone trusts, teams working in the system instead of around it, and no reimplementation a few years later. What leads there is the work done before anything is configured: a clear picture of what the company promises customers, how operations keep those promises and how accounting measures them. Implementations that fall short usually had the right software and the wrong starting point, with NetSuite configured to match today's habits. Prolecto's roadmapping engagement is that pre-implementation step: three to five days with your leadership team to define the optimal state of the business, then decide how NetSuite should support it. Leadership leaves with four deliverables: the transaction and entity architecture, a governance model, a phased implementation plan, and investment and risk insights. The plan belongs to you, so you can build it with Prolecto or run it on your own.

  • Should we phase our NetSuite implementation, or get everything done at once?

    Phase it, but design the whole business first. You need that picture before anything is configured: what the company promises, how operations keep those promises, and how accounting measures them. Then phase the build by business priority, so each phase delivers value and builds toward the same design. Without it, phases become a feature list and later phases undo earlier ones. Prolecto's roadmapping engagement does this in three to five days with your leadership team. Leadership leaves with four deliverables: the transaction and entity architecture, a governance model, a phased implementation plan, and investment and risk insights. The plan belongs to you, so you can build it with Prolecto or run it on your own.

  • What should be in scope for phase 1 versus phase 2 of a NetSuite implementation?

    Decide the full design of the business first, so both phases build toward the same design. Phase one handles what cannot wait. Phase two builds scale. Without that design, phases become a list of features, and the company risks a reimplementation later. With it, each phase delivers value and nothing has to be undone.

  • Can NetSuite handle our complex customer pricing, quotes and commissions, or will we need customizations during implementation?

    Often it can, once the requirements are mapped. Start with the products and services you offer, how you price and quote them, and how the accounting should follow. That picture shows where NetSuite's native structures fit and where they need to be adapted. Prolecto has built configurable quoting on NetSuite without a CPQ subscription. Complexity nobody has mapped is what keeps NetSuite's potential locked away.

  • Our warehouse, ecommerce and accounting systems don't talk to each other. Is moving to NetSuite the right way to fix that?

    Often, yes, as long as the move starts with a design. Keeping NetSuite at the center, with other systems as spokes, keeps one version of the truth instead of a separate version of the business in each system. Not everything has to move. Sometimes an existing system is the right choice and is best integrated with NetSuite. Decide how the business should work first, then decide what belongs at the center.

  • Should we pay for a separate discovery and design phase before committing to a full NetSuite implementation?

    Yes, if the design phase produces a model of the business and not just a list of requirements. A discovery phase pays for itself when leadership agrees on what the company promises, how operations keep those promises and how accounting measures them before configuration starts. That agreement is what prevents rework and reimplementation later. Prolecto's Roadmapping engagement is this phase: three to five days with your leadership team, ending in a solution design and a phased plan that belongs to you, whether you build it with Prolecto or on your own.

Fixing a NetSuite account you already have

  • What does a NetSuite health check or optimization roadmap include, and what does it cost?

    For a company already on NetSuite, a health check compares how the account works today with how the business should work. Senior Prolecto leaders spend three to five days with your leadership team and review the account: the transaction and entity design, custom scripts and workflows, integrations, and the reports finance relies on. You see where the configuration fits and should be kept, where it mirrors old workarounds and should be redesigned, and where technical debt is building up. Leadership leaves with a phased roadmap, with effort and investment estimates for each phase, a governance model to keep it on track, and the risks to watch. The cost depends on the size of the account, such as the number of subsidiaries, users and integrations, so talk to an expert for a quote.

  • Our auditors flagged too many manual journal entries in NetSuite. What does that usually say about how the account was configured?

    It usually means the problem sits upstream of accounting. Accounting records what it can with the inputs available, so when operational records are incomplete, finance reconstructs the story after the fact, often with estimates and manual entries. To fix accounting, fix operations, and to optimize operations, strengthen planning. Margin you can trust is designed into the transaction architecture, not rebuilt in a spreadsheet.

  • Our team has stopped using NetSuite and is back on spreadsheets. How do we tell if the system or the implementation is at fault?

    Shadow spreadsheets, reports nobody trusts and users who route around the system are the classic signs of an implementation configured feature by feature, without designing the business first. NetSuite is designed to be shaped, so it takes on whatever design it was given. If the configuration copied how the company already worked, workarounds included, the implementation is at fault, not the system.

  • Should we re-implement NetSuite or fix the current setup? How do we make that call?

    Start with the business, not a decision about software. Define the optimal state of the business: what it should be at scale, what it promises customers, and how operations keep those promises. Then compare the current account with that picture. Where the configuration fits, keep it and improve it in phases. Where it mirrors old workarounds, redesign those areas. Most companies had the right software and the wrong implementation, so a full re-implementation is rarely the only answer.

  • Our business has changed a lot since we implemented NetSuite, but the setup hasn't. Is it time for a redesign?

    Usually yes, but redesign the model of the business before you redesign the system. When a company outgrows its NetSuite setup, the signs are workarounds, spreadsheets beside the system and numbers leadership questions. Start by writing down how the business should run now, including new entities, channels and revenue models, and how they connect. Then compare that picture with how NetSuite is configured and phase the changes. Often the account can be reshaped in place rather than reimplemented, and the model tells you which areas need it.

  • How do we keep our NetSuite customizations from becoming a mess as the company grows?

    Tie every customization to a written model of the business, not to the request in front of you. Customizations become a mess when they are built one at a time to solve the problem of the day. When leadership has defined how the business should run, each change can be checked against that model: does it fit, does it duplicate something that exists, and will it scale. Keep one owner for the overall design, document what each customization does and why, and use configuration instead of code wherever NetSuite already supports the need.

AI and NetSuite

  • My board is asking what our AI strategy is for finance. Where should a NetSuite company start?

    Start with how your business is set up in NetSuite. AI now works inside NetSuite and outside it, through MCP in tools such as Claude or ChatGPT, and both paths run on the same records, rules and permissions. AI makes screens and scripts cheap, so the lasting value is in the data model, business rules and accounting truth underneath. A sound design makes AI safe and useful. An unclear one leaves it guessing.

  • We tried ChatGPT on our financial data and it made up numbers. Is AI ready for NetSuite finance work?

    AI is ready for NetSuite finance work when it reads from clean records and clear business rules, not from raw spreadsheet exports. General chat tools make up numbers when they have no reliable source of truth to check against. Inside a well-modeled NetSuite account, with defined permissions and a governed connection, AI can read the actual records and follow the rules the business has set. The prerequisite is the same as for trustworthy reporting: one platform, one version of the truth, and business rules that are written down.

Turn this thinking into your roadmap.

The Architecture Practice starts every engagement with your business. See how a three to five day roadmapping session works.