Over the years, we have heard a variety of terms that characterize a set of documented CRM requirements. Terms include: request for proposal, high-level requirements, blueprint, functional specification, specification plan, agile requirements and more. Labels aside, there are several levels of depth of CRM requirements. The deeper your team goes into defining requirements before selecting a CRM system, the more successful your CRM implementation will be.

1. 5 Levels of CRM Requirements

2. The deeper your team digs into
requirements before selecting a CRM
system...

3. ...the more successful your CRM
implementation will be.

4. "Please enlighten me as to why we spent all that
money on CRM."
Here's the conversation you want to avoid

5. Requirements are multi-dimensional
Let's look at the different levels

6. 1. Feature
Requirements A high level list of
items that's often
associated with an
RFP that's generated
by a purchasing
department

7. 2. Business
Requirements
An analysis of current
pain points and
potential business-level
solutions

8. 3. Non-
Functional
Requirements Criteria that can be
used to judge the
operational aspects of
a system

9. 4. Functional
Requirements Functional
requirements are
expressed in the form,
"the system must allow
for doing this specific
thing"

10. 5. System
Design The plan for
implementing
functional requirements
is detailed in the system
design

11. Read the full blog post