Elevate2's unique implementation methodology. Transforming your vision into a working solution.


We believe that the requirements phase is the single most important phase in any project. A successful requirements phase, where all key requirements are discussed and all process pain points worked through, invariably leads to a successful project.

Tasklite© therefore prioritises requirements capture, with the intent of having a crystal-clear understanding of a project’s demands before proceeding to the design. It is crucial at the requirements stage of the project that clients continually focus on the following key questions:

1) What would I like my target operating model and end-to-end business processes to be?

and 2) What are the top current process pain points or inefficiencies I would like to resolve as part of my NetSuite implementation?

Addressing these questions at the requirements stage goes a long way to ensuring that a fit-for-purpose NetSuite solution is delivered in every project.


A key component of Tasklite© is ensuring that clients are left with documentation describing their NetSuite setup and configuration. In the requirements stage, our professional services team work collaboratively with clients to understand their key process pain paints and inefficiencies.

Using extensive implementation experience the professional services team describe how NetSuite best fits into the client’s target operating model and desired end-to-end business processes. NetSuite is highly configurable and if the “out of the box” processes do not satisfy requirements then these can often be adjusted through configuration, customisation, scripts and/or automation tools. Prior to build commencing, a detailed Business Design Document (BDD) is produced, syndicated and signed off by the client.


The Tasklite© Proof of Concept (POC) stage allows clients to choose the functional areas they would like to see go through an early build cycle or a POC. This process allows clients to gain confidence in their platform by better visualising the NetSuite end product early on in the project lifecycle.

At Elevate2 we believe in transparency, collaboration and a no surprises approach to project delivery. We endeavour to communicate frequently, openly and honestly with our clients, with the expectation of building a trusting long lasting relationship. We recognise that most projects will encounter a few bumps in the road. Where these arise, our preference is to deal with them efficiently and effectively through positive and pragmatic dialogue. To support this approach, we operate a comprehensive governance model, with weekly project status meetings and weekly project reports covering achievements, next steps, budget vs actuals, risks & issues and overall delivery status. For larger projects we also operate a fortnightly / monthly steering committee with the project sponsor. This ensures timely and clear communication throughout the project lifecycle.


1 Sales


The Sales stage captures valuable business objectives and includes a NetSuite feasibility check and high-level capability to requirements mapping. This allows high-level solutioning and project estimates to be provided to clients in the form of a Statement of Work (SOW), alongside a provisional project plan.

2 Initiate


Following SOW signature, the project is resourced and mobilised, with the assigned consultants familiarising themselves with the clients requirements via a Sales team handover.

A project kick-off meeting is held to allow the Elevate2 project team and the client team to introduce themselves. This meeting is used to review the Tasklite© Methodology and walk through the provisional project plan. Any client feedback on the plan is always welcomed and the team work collaboratively with the client to develop a plan that meets all parties’ expectations.

The Business Process Questionnaire (BPQ) is issued for completion at this stage. The BPQ contains a comprehensive list of questions, which enable the delivery team to understand the client’s configuration requirements, business processes and key pain points.

3 Requirements


In the Requirements stage, Business Process Mapping (BPM) workshops are held using the information collected from the Business Process Questionnaire (BPQ) documentation.

The purpose of the BPM workshops is to understand fully all business requirements, key pain points & limitations, desired target operating model and end-to-end business processes. This allows a fit for purpose NetSuite solution to be designed. It is crucial that the relevant Subject Matter Experts (SMEs) are actively involved in the BPM workshops.

The output of the BPM workshops is the Business Design Document (BDD). The BDD captures client requirements and the corresponding NetSuite solution on a requirement by requirement basis. Where standard NetSuite cannot deliver a business requirement, this is listed as a Gap and a custom solution suggested.

The BDD is signed off by the client before proceeding to the Proof of Concept (PoC) stage.

4 Proof of Concept


The PoC allows for the build and demonstration of selected standard NetSuite functionalities using sample data provided by the client. The PoC provides a high-level understanding of how NetSuite works and the general look and feel of the product, which allows for early insight into the final NetSuite solution.

5 Build


The NetSuite solution is built based on the approved scope of work, which is documented in the BDD and approved by the client. The project team remain in regular contact with the client throughout the build process. After the build is complete, a Solution Walkthrough (SWT) is scheduled for the client to review the solution and provide feedback. The SWT also allows the client to get familiar with the system ahead of the User Acceptance Testing (UAT).

6 Data Migration


The Data migration phase encompasses the migration of historical legacy system data to the NetSuite platform. This can be a very significant undertaking and we advise clients to only migrate the most critical data. Clients identify the in-scope master and transactional data and will perform all data cleansing tasks before performing data migration to NetSuite. Our consulting team provide guidance and assistance, while the client performs the data extraction, cleansing, transformation, manipulation, and the actual migration.

7 Test


The propose of the User Acceptance Testing (UAT) is for the client to test the solution and ensure it functions in line with their requirements described in the BDD.

Test script templates are provided to help clients create test scripts based on their business scenarios and expected results. The project team review these test scripts and provides client feedback ahead of the actual testing.

To further assist, a training session on how to perform User Acceptance Testing (UAT), how to review the UAT results and carry out any remedial actions, is also provided.

8 Delivery


During the delivery stage, following key activities will be performed.


Train-The-Trainer (TTT) training is provided to client super-users. This training is designed to put the super-users in a position to be able to deliver training to their wider team(s).

Go / No Go

A Go / No Go meeting it held where the client decides whether to deploy to production or not.

Migration to Production

The production environment is prepared for go-live and the signed-off application deployed to the production environment.

Final Data Migration

The client migrates all the reconciled and signed-off data into the production environment.


Understand how NetSuite can help transform your business with a bespoke demonstration.


Understand how NetSuite can help transform your business with a bespoke demonstration.


Join the many companies we’ve helped and get in touch today.


Join the many companies we’ve helped and get in touch today.


There are various ways to implement projects and various ways to successfully govern them. Classic project management principles, such as Prince2, are a good foundation for rigorous project and programme management.

However, in reality their practical implementation can be rigid and prescriptive. There is often very little room to deviate from the plan, even when circumstances change during the project – and they do not take into consideration the natural differences between companies with varied cultures and from different industries

Login to TaskLite©