MHI Talent Solutions | Senior Manager, Business Systems

Job Responsibilities What You'll Do Here

Start by Listening: the fastest way to level this system up is to have the conversations a compressed go-live didn't leave room for. In your first weeksyou'll sit with purchasing, fulfillment, sales support, and finance to learn howthe work actually happens — then publish a clear-eyed assessment of where

NetSuite fits the business, where it doesn't, and the order you propose fixing things in. We want a plan the whole company recognizes as accurate, not abacklog of complaints.

Take Ownership of the Configuration: get to the bottom of what's actually inthere — Suite Scripts, Suite Flow workflows, custom records and fields, saved searches, roles and permissions — and document it as you go. On a system this young that's weeks of work rather than quarters, and it's the foundation for everything after. Then tell us honestly what's solid, what needs reshaping,and what should be retired.

Establish Change Management, Technical and Human: we launched fast,which meant changes went to production without much process behind them.

You'll build real sandbox-to-production discipline — testing, release process,the ability to roll back. Then you'll own the harder half: getting changes adopted. A Net Suite change that lands badly here doesn't produce a bugreport, it produces a workaround, and the people most affected are on forklift sand delivery trucks rather than reading release notes. You'll communicate changes before they land, train people in a format they'll actually absorb, andgo back afterward to confirm the new way is the way — not the clipboard someone quietly returned to.

Own the Integration Layer:you'll be accountable for how our systems talk toeach other — the connections to freight, banking, EDI, and our partner network, plus the Net Suite side of the Hub Spot handoff, where a closed deal becomes a sales order, a fulfillment, and an invoice. Revenue Operations configures Hub Spot; you make sure what lands in Net Suite is correct,monitored, and never fails silently.

Coordinate with Engineering:some of our customer-facing products readfrom the ERP, which makes Net Suite a production dependency rather than apurely internal tool. Engineering owns the product side and the code that talksto us; you own the ERP side of that contract — which means knowing which fields have downstream consumers and talking to Engineering before youchange them. It also means your work reaches customers.

Most business systems people never touch anything outside the building; here, the quality ofour operational data is visible in the product.

Serve Sales and Fulfillment: these are your power users, and their problems are physical. You'll spend real time in our facilities understanding how material actually moves before proposing how the system should model it — then buildthe operational reporting they depend on for inventory, purchasing, order status, and fulfillment, and fix the data quality problems that keep people in parallel spreadsheets. Funnel, pipeline, and revenue reporting belong to Revenue Operations;

your job is making sure both sets of numbers reconcile.

Own How We Absorb Acquisitions: we've completed four and expect more.

Each arrives with its own data, processes, and habits. You'll own the ERPstandard — how the operational data model should look, what gets mapped where, what documentation we require — while contractors do the migration labor and Revenue Operations handles the GTM side. Our most recent acquisition is being onboarded to Net Suite right now, so depending on yourstart date you'll either inherit the tail end of it or arrive just behind it.

Then Build. Once the foundation is right, the work ahead is substantive: better fulfillment across owned and partner locations, a smoother…