ERP Implementation Statement of Work Template

Count everything. A deliverable a client cannot count is a deliverable a client can expand.

1. 2.1Configuration of NetSuite for 2 subsidiaries with the modules listed in Schedule A: general ledger, accounts payable, accounts receivable, fixed assets and inventory.
2. 2.2A signed solution design document at the end of the design phase.
3. 2.3Up to 12 custom saved searches and 8 custom reports listed in Schedule B.
4. 2.4Up to 6 SuiteScript customizations and 10 workflows listed in Schedule C.
5. 2.5Integrations with Shopify and a 3PL using prebuilt connectors as listed in Schedule D.
6. 2.6Migration of open balances, vendors, customers, items and open transactions as of cutover date.
7. 2.7Train-the-trainer sessions for 8 key users, user acceptance testing support and 30 days of post go-live support.

Name what the engagement does not include. These are the lines your PMs will cite most often.

1. 3.1Additional subsidiaries, currencies or modules not listed, including manufacturing, payroll and advanced revenue recognition.
2. 3.2Migration of closed historical transactions.
3. 3.3End-user training beyond the train-the-trainer sessions.
4. 3.4Data cleansing in legacy systems.
5. 3.5Software licenses and connector subscriptions.
6. 3.6Business process redesign beyond configuring the processes agreed in the solution design document.

The solution design document includes two review rounds. After sign-off, requirement changes follow Change Control. Configuration adjustments discovered during user acceptance testing that are within the signed design are included.

Acceptance needs a measurable test and a window. Without both, delivery never formally ends.

1. 5.1Each phase closes with a signed gate review.
2. 5.2User acceptance testing passes the test scripts in Schedule E with no open severity 1 or 2 defects.
3. 5.3Trial balance and open balances reconcile to the legacy system at cutover.

Tie each dependency to a date so a late input has a known effect on the schedule.

1. 6.1The client appoints a project sponsor and one process owner per module with decision authority.
2. 6.2Legacy data is extracted by the client into the agreed templates.
3. 6.3Key users are available for at least 25% of their time during design and testing.

Any change to the signed solution design, including new reports, scripts, workflows, integrations, entities or data objects, is a change. The integrator logs it, assesses effort and timeline impact within three business days, and presents a change order to the steering committee. Approved changes are added to the plan with a revised phase budget.