What started as a focused banking integration engagement with Pyramid Pharma Services eventually grew into a broader NetSuite optimization effort across finance, approvals, reporting, inventory visibility, and operational controls.
Pyramid Pharma Services is a Costa Mesa-based CDMO specializing in sterile drug manufacturing. Like many established companies operating in a highly regulated environment, Pyramid’s NetSuite instance had grown alongside the business. Over time, that growth created opportunities to better align the system with how the company operates today.
The original request was specific: help diagnose and stabilize a Fispan and JP Morgan banking integration supporting AP workflows.
But once our team was inside the environment, the engagement began to surface a wider set of opportunities. Not major breakdowns. Not a system in crisis. More like the kind of accumulated operational friction that appears naturally as companies grow, teams evolve, and processes become more complex.
That is often where the most valuable NetSuite work begins.
Aligning approvals with the way the business works today
One of the first areas we supported was Pyramid’s approval workflow structure.
As companies grow, approval paths that once made sense can become harder to maintain. Roles change. Teams expand. Escalation paths need to become clearer. Access controls need periodic review. For businesses operating in regulated industries, approval workflows are not just an internal convenience. They are part of the operational foundation.
Our team helped rebuild and document approval workflows across key areas including AP, journal entries, and purchase order controls. The goal was to make the approval structure easier to follow, easier to audit, and better aligned with Pyramid’s current operating model.
That work included mapping approval hierarchies, refining escalation paths, reviewing user access, and strengthening the documentation behind the workflow structure.
Supporting a smoother close process
As the engagement continued, our work expanded into financial process support.
Period-end close is one of the places where small system dependencies become very visible. Revenue arrangements, scripts, automation, and reporting all need to work together cleanly. When one piece requires adjustment, the impact can show up quickly during close.
Because our team was already familiar with Pyramid’s environment, we were able to help identify and resolve process issues quickly, then support improvements that made the revenue run process more repeatable going forward.
The value here was not only in resolving a specific issue. It was in reducing reliance on manual intervention and helping the close process become more consistent.
For growing companies, that kind of reliability matters. A smoother close gives finance teams more time to review, analyze, and make decisions instead of chasing system dependencies.
Building visibility where teams needed it most
Some of the most useful improvements in a NetSuite engagement are not always the most dramatic.
For Pyramid, reporting and saved search work became a major part of the project. The company had reporting in place, but there were opportunities to improve visibility in areas that mattered to daily operations, finance, audit preparation, and warehouse workflows.
Our team supported saved searches and reporting views for areas such as pending AP approvals, vendor bill aging, warehouse bin visibility, SOC 1 preparation, and FP&A reporting needs.
These are the kinds of improvements that often have an outsized impact. A better saved search can replace a spreadsheet. A daily alert can prevent a bottleneck. A clearer aging view can help finance teams act sooner. Better warehouse visibility can reduce the back-and-forth between operations and accounting.
NetSuite becomes more valuable when teams can trust the system to show them what they need before they have to go looking for it.
Strengthening inventory and traceability workflows
For a CDMO, inventory visibility and traceability are especially important.
Pyramid’s environment included inventory processes that needed careful handling as the company continued modernizing its NetSuite setup. Our team supported work around lot-level visibility and inventory traceability, helping ensure that item records and related workflows were handled in a controlled, well-documented way.
This type of work requires patience. Inventory data touches operations, compliance, accounting, and warehouse execution. Moving too quickly can create confusion downstream. The priority was to support better visibility while preserving data integrity and keeping the process aligned with the realities of a regulated manufacturing environment.
What the engagement became
Over seven months, the work expanded well beyond the initial banking integration request.
Our team supported Fispan and JP Morgan plugin management, approval workflow updates, user access review, sales order automation, revenue process improvements, reporting infrastructure, SOC 1-related searches, FP&A visibility, inventory traceability support, and ongoing managed services response.
That range of work is common when a company is not simply trying to “fix NetSuite,” but trying to make the system better reflect the business it has become.
Pyramid was not a company starting from zero. It was an established CDMO with decades of operating history, moving through a deliberate modernization effort. The opportunity was to help NetSuite keep pace with that direction.
The larger lesson is simple: when a growing company has a list of NetSuite processes that are almost right, that list rarely gets shorter on its own. The better path is to address those issues systematically, improve visibility, and build a system that supports the business instead of slowing it down.
For Pyramid, a banking integration request became the starting point for a broader operational improvement effort.
And that is often where the most meaningful NetSuite work happens.
