Book Image

NetSuite for Consultants

By : Peter Ries
Book Image

NetSuite for Consultants

By: Peter Ries

Overview of this book

NetSuite For Consultants takes a hands-on approach to help ERP and CRM consultants implement NetSuite quickly and efficiently, as well deepen their understanding of its implementation methodology. During the course of this book, you’ll get a clear picture of what NetSuite is, how it works, and how accounts, support, and updates work within its ecosystem. Understanding what a business needs is a critical first step toward completing any software product implementation, so you'll learn how to write business requirements by learning about the various departments, roles, and processes in the client's organization. Once you've developed a solid understanding of NetSuite and your client, you’ll be able to apply your knowledge to configure accounts and test everything with the users. You’ll also learn how to manage both functional and technical issues that arise post-implementation and handle them like a professional. By the end of this book, you'll have gained the necessary skills and knowledge to implement NetSuite for businesses and get things up and running in the shortest possible time.
Table of Contents (27 chapters)
1
Section 1: The NetSuite Ecosystem, including the Main Modules, Platform, and Related Features
5
Section 2: Understanding the Organization You Will Implement the Solution for
11
Section 3: Implementing an Organization in NetSuite
21
Section 4: Managing Gaps and Integrations
Appendix: My Answers to Self-Assessments

Gathering requirements and interviews

In any software project, understanding the users' requirements is a key step in the early process. However, for NetSuite implementations, we want to be careful about how we start to ask our questions and talk to users. You might think that the right approach is to start by asking the client how they do things now and then translate that into NetSuite terms and processes. But doing that can lead to a lot of unnecessary customizations if you're not careful, and that means delays and cost overruns.

Important note

When gathering requirements, it's always beneficial to put yourself in your client's shoes; try to anticipate how they will receive every question you ask and everything else you tell them. If you were them and you heard the question, how might you respond? If you realize your first idea for a question is too hard to answer, you need to ask the question differently.

For instance, How many expense accounts will...