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

Self-assessment

Here are some things you can think about on your own, related to this chapter's contents:

  1. What would your projects look like if you didn't start with a methodology in mind? Do you have a better idea for a project method you will follow?
  2. Since a waterfall project starts from a defined list of deliverables, how will you talk to your clients about changes they request in the middle of the project?
  3. With my proposed hybrid waterfall/agile approach, when is the right time to explain the approach to a client? Upfront, as part of selling your service to them? Or only when they start to ask for changes during the implementation?
  4. How does your business currently handle adapting to changes the client asks for? Are you in the strict the-contract-is-all-you-get camp or are you one of the all-you-can-eat type of service providers? Which is the best approach, in your opinion?