How Many Contractors a NetSuite Go-Live Actually Needs: Sizing the Crew for Cutover and the 60 Days After

Last updated: October 22, 2026

By Colin Boothe, CIO at Foretopia

A NetSuite go-live needs a customer-side contract crew from cutover week through the second month-end close, built from an ERP admin, a business analyst, a project manager, and floor support, and sized by your subsidiaries, integrations, and warehouses. KORE1-placed ERP consultants bill $73 to $123 an hour, median $91, which is about $47,200 per seat for three months (KORE1 Contract Rate Index 2026-Q4). Price the seats by the week, because most of them roll off long before the quarter ends.

Picture day three after go-live. The AP clerk can’t find a vendor bill she keyed in yesterday. Gone. The warehouse lead is printing pick tickets from a saved search somebody built on Friday, nobody remembers who, and it quietly skips every order that ships from the second dock. The controller wants to know whether the opening balances tie. Before lunch.

Your implementation partner is on a call about phase two. Nobody on your side has the hours to chase any of this. Nobody.

That gap is what this post prices. The partner builds NetSuite. You run it. And “you” usually means the same handful of people who were already doing two other jobs before the project started, which is why the first week after cutover feels like a second full-time job that nobody was hired to do. So here’s the crew I’d put around a mid-market go-live, week by week, priced from the KORE1 Contract Rate Index. Write the crew into one hourly SOW with the SOW template for a go-live crew.

Disclosure, since you’ll wonder. My consulting group is the partner in that picture. We build. KORE1, whose site you’re reading, places the contract people for your side through its ERP consultant staffing and ERP program team staffing practices, and we each get paid if you act on any of this. Fair warning. I tried to make the arithmetic work in your favor anyway, including the parts where it tells you to book fewer seats.

Video chapters

• 0:00 — Intro
• 0:34 — Who Is on the Go-Live Crew
• 1:20 — How Company Shape Changes the Crew
• 1:50 — When Each Seat Rolls Off
• 2:14 — What Breaks If Support Ends Early
• 2:43 — How Fast Seats Start and What the Quote Leaves Out

Who Does the Go-Live Crew on the Customer Side Include?

A customer-side go-live crew is the group of contract seats on your side of the table, the people who retest fixes, reconcile balances, answer user questions, and run the checklist while your implementation partner finishes the build. The partner configures NetSuite. The crew makes your company able to use it on Monday morning.

Six seats. Not every company needs all six. I’ll say which ones to cut. Weeks count from cutover, and I’m assuming a go-live on the first of a month, so the first close lands in weeks five and six and the second close in weeks nine and ten.

Source: KORE1 Contract Rate Index 2026-Q4, effective October 16, 2026. “Observed” cells come from KORE1 W2 contract placements started 2023 to 2026, with the placement count (n) shown. The tester cell is modeled from BLS Occupational Employment and Wage Statistics (May 2025) wages, a 24% employer burden, and the bill bands KORE1 observes. Bill rates include payroll taxes, insurance, and benefits. Three-month cost assumes 520 hours. Method: how the index is built. “Full” is 40 hours a week and “Half” is 20. Next refresh: January 2027.

Read the labels before you quote any of those. The ERP cell covers ERP, NetSuite, and Salesforce consultants of every level, 15 placements across several states, so it is not 15 NetSuite admins and I won’t pretend it is. The business systems analyst cell has six placements behind it, which is enough to publish and not enough to bet your budget on a one-dollar gap. The tester row is modeled. Not observed. Different animal.

Now the part the index doesn’t print. Take each median, multiply by 40 hours, then by the weeks that seat is on. Here’s the crew.

The whole crew lands near $154,160 at the median. Book those same six seats full time for three months, straight from the index’s own three-month figures, and the bill is $288,000. Big gap. That gap is the whole argument for rolling seats off on evidence, and it’s a number your partner’s quote will never show you, because your side of the table isn’t in the partner’s quote to begin with.

Want it priced against your own go-live date? Price your go-live crew with KORE1’s recruiting team. Send the seats you need, the go-live date, how many weeks you want covered through the second close, your metro or remote, and which modules go live.

How Does Company Shape Change the Crew?

That grid describes a single-entity company with a couple of integrations and one warehouse. Real companies are weirder. Four things move the crew. They don’t move it equally.

Take three subsidiaries, two warehouses, and four integrations. I’d add a second business systems analyst for weeks five through ten and a second floor-support seat for the extra warehouse in weeks one through four. Six analyst weeks at the $99 median come to $23,760, and four floor-support weeks at $49 come to $7,840. Add them up. About $31,600 on top of the base crew.

Notice what isn’t in that table. Revenue. A $40 million company with five subsidiaries needs a bigger close crew than a $90 million company with one, and buyers still size the whole thing off the revenue line. Entities and warehouses are what make a close hard.

Who Sits in the War Room During Cutover Week?

Start with the people who are not contract seats. Your controller, because she decides what “tied out” means. An executive who can say stop. And the partner’s build lead, who knows why the configuration looks the way it does and, more usefully, which parts of it somebody built at 11 p.m. the night before. Everyone else in the room is one of the six.

The project manager runs the checklist and keeps the decision log. Boring, until the third time somebody asks who approved the workaround for tax codes, and then it’s the most valuable document in the building. The ERP admin owns roles, scripts, and the status of every integration. The business analyst takes each complaint and drops it in one of three bins. Bug. Training gap. Process nobody agreed on. Those bins have different owners, and mixing them up is how a training problem turns into a two-week change request.

The tester retests every fix in the sandbox before it moves to production. Every one, including the “tiny” ones. Floor support walks the AP desk and the dock with a notebook. Nice. Low-tech. It finds more than the ticket queue does.

The business systems analyst is on half time in these weeks for one reason, the opening balances. Oracle’s own CSV import FAQ says to enter opening balances as journal entries on go-live and not to include account balances in the chart of accounts import. Fine. Somebody on your side then has to tie those journal entries back to the legacy trial balance, line by line, in the first 48 hours, while the same person is also getting asked why the AR aging doesn’t match what the old system printed on Friday. That’s a finance-literate person’s job with a controller sign-off. A project manager can’t do it.

If you’re staffing from a standing start, our ERP go-live and hypercare staffing page covers the service side, and the NetSuite implementation consultant staffing page covers the build-side consultants you’d hire separately.

Who Stays Through the First and Second Month-End Close, and When Does Each Seat Roll Off?

Roll seats off on evidence, not on a date, because the date is a guess you made before you saw how clean the data load was, how many users actually showed up to training, and whether the first close would take three days or nine. The calendar in the grid is a budget. Not a promise.

The ERP admin is the odd one. Everybody else on the crew works themselves out of a job by design. The admin is the person you were going to need anyway. A full-time seat reaches 1,040 hours in week 26, and KORE1 contractors who complete 1,040 hours can convert to your payroll with no additional fee from KORE1. A ten-week seat won’t get there on its own. Conversion is a separate decision, and the NetSuite managed services cost breakdown prices the part-time and retainer options for what comes after.

For context, the median KORE1 contract assignment runs 116 days across 1,887 placements, and 37.5% of 552 contract-to-hire placements converted. Those are firm-wide numbers, not NetSuite-only. This crew is shorter than that median. One more reason to buy it by the week.

What Breaks If Go-Live Support Ends Before the Second Close?

The first close is run with the builders in the room. The second one is the first close your own people run alone. That’s where the bill arrives.

Here’s a detail about NetSuite that surprises people. On the period close checklist, the intercompany adjustments task and the foreign currency revaluation task can be marked complete after you merely review the page, and Oracle says it is “strongly recommended” that you complete them before closing. Which means a rushed team can close a period without doing either, and NetSuite will let them. Nice feature. Terrible default. The consolidated exchange rates task is stricter. Once you mark it complete, the rates for that period can’t be changed. And after you close the period, no further actions can be completed in it, so fixing a mistake means reopening it.

See the problem? In close one, somebody senior is watching those tasks. In close two, there is a clerk, a deadline, and a checklist that says you can skip it. Guess which one wins.

Other things I’d expect to break when the crew leaves early, based on how these projects tend to go.

• Scheduled jobs and recurring entries that only fire at month end. Nobody sees them in week two.
• An integration that drifted after a vendor update, where the first sign is a total that’s off by a few hundred orders and nobody can say which day the drift began.
• Trust. The sales manager notices the open-orders total in NetSuite disagrees with the one in her morning email, picks a side, and quietly builds her own spreadsheet. Sucks, and nobody else will ever see it happen.

One correction to my own title, while I’m here. The “60 days” is shorthand. With a go-live on the first of the month, the second close wraps up closer to day 70, and a go-live on the 20th compresses the first close into two weeks. If you can pick the date, pick the day after a close.

For the adoption side of those same ninety days, see my piece on driving ERP adoption after go-live.

How Fast Can Contract Seats Start?

Fast, usually. KORE1 contract placements start a median of 3 days after the offer is accepted, across 1,997 placements, and that clock starts at the accepted offer, so sourcing and interviews come before it and your own access provisioning comes after. That second piece is the one people forget. Single sign-on, a license seat, a building badge, and a sandbox role that someone has to approve.

Devin Hornick, one of KORE1’s partners, described the appeal on an internal call this way: “The contract allows that company… you can get them quick… flexible… to scale up, to scale down as needed.” For a go-live that’s the whole pitch. The crew has a shape that changes every two weeks, and a permanent hire doesn’t.

If your go-live is thirty days out, floor support, a tester, and a business analyst are realistic to place in that window. Name the ERP admin and the project manager first, though, and get both of them into the sandbox before user acceptance testing starts, because a person who has never seen your configuration is slow in week one and expensive in week two. How fast a contractor can start breaks the curve down. Seat-level rates for the roles in the grid are in the business analyst and business systems analyst bill rates and the project manager bill rates posts.

What Does the Partner Quote Leave Out?

Your side of the table. Every time.

On a project I scoped this summer for a mid-market pharma manufacturer, the release phase ran about four weeks, three of them hypercare. That’s right for a validated environment where the customer’s quality group owns the approvals. It is wrong for an operating company with two closes ahead of it. And a quote that says “hypercare included” with no number of weeks is not a plan. Ask how many.

The same proposals assume your reviewers turn documents around in ten business days. If nobody on your side has the hours to review, the schedule slips, and that slip is sitting on the calendar long before it shows up on an invoice. I also write change orders so that waiting earns schedule relief only, and cost follows rework. Ask whether your partner does, and notice how long the pause on that call lasts.

A materially cheaper quote is usually cheaper by exclusion, not by efficiency. Before you compare totals, compare what each quote leaves to you.

• How many weeks of hypercare, and does it reach the second close?
• Who retests fixes? Who signs off?
• Data cleanup before cutover. Whose job, and whose hours?
• Training. Is it in the statement of work, or did someone assume your super-users would handle it in their spare time between their real jobs?
• Who answers the floor in week one. If the answer is “the ticket queue,” read the quote again.

None of this makes a partner a bad partner. The job is the build, and the build is the only part the partner can price. The rest is yours. The crew above is what it looks like when you staff it on purpose. For a longer look at the split, read about an ERP implementation partner versus a staffing agency.

Questions Controllers Ask Before the Cutover Weekend

So how many contractors does a NetSuite go-live actually need?

Four to six seats for a single-entity mid-market company, and eight or more once subsidiaries, warehouses, and integrations pile on.

The six in the grid are an ERP admin, a business analyst, a project manager, a business systems analyst, floor support, and a tester. The count is my judgment from projects. Not an index figure. What the index supplies is the price of each seat.

What does a contract ERP or NetSuite consultant cost per hour?

As of October 16, 2026, KORE1 contract placements for ERP consultants (n=15, 2023 to 2026, multi-state) billed $73 to $123 an hour, median $91.

Three months full time at the median is about $47,200 and six months is about $94,400. Bill rates include payroll taxes, insurance, and benefits. Source: KORE1 Contract Rate Index 2026-Q4.

Business analyst for a go-live, what’s the bill rate?

$90 to $120 an hour, median $116, for KORE1-placed business analysts (n=10, primarily Southern California, KORE1 Contract Rate Index 2026-Q4).

That is about $60,400 for three months. In this crew the analyst is on for six weeks, not thirteen, which is $27,840 at the median.

Is a help desk tech enough for floor support, or do I need someone senior?

Help desk is the right seat, and KORE1 placements billed $41 to $55 an hour, median $49 (n=39, primarily Southern California).

Three months is about $25,500, and the grid books only four weeks, $7,840. Cheap seat, short stay. Don’t staff a senior consultant to answer “where did my button go.” Do keep the ERP admin one message away for everything the floor can’t answer.

When can we let the crew go?

Seat by seat, on evidence, not on a date.

Floor support and the tester go first, once the topic log and the fix queue are quiet. The business analyst follows when two straight weeks pass without new process gaps. The project manager and the business systems analyst stay until the second close ties out without anyone reaching for a manual plug or writing an apologetic email to the auditors. The admin is the last to go, and often converts.

Book the Seats by the Week

Count your entities. Count your warehouses. Count your integrations. Open the grid, strike the seats you don’t need, add the ones the shape table says you do, and then put the five questions from the partner section in front of whoever is quoting you before anybody signs anything.

For seat-level numbers across more roles, grab the 2026 Contract Rate Card. To model a full team instead of one crew, try the ERP contract team calculator. Already know what you need? Send KORE1’s recruiting team the seats and the go-live date, and use that quote as your yardstick.

Not sure which of these your company needs? Hit me up on LinkedIn and I’ll tell you what I’d cut.

The partner gets you live. The crew gets you to a second close nobody has to apologize for. Simple.