2. Pre-EDUCAUSE Objectives
Determine preferred Enterprise CRM
naming approach
Define desired Enterprise CRM suite
and platform name
Align on additional approvers,
approval/validation process required
before legal review
Note: We should align on which approach we will use in
naming the student success, continuing ed/workforce
development, and advancement solutions, but we do not
need to finalize solution names prior to EDUCAUSE.
April 5, 2016
2
3. Naming Considerations Assumptions
Naming Architecture: Ellucian’s naming architecture will continue to use descriptive rather
than fanciful solution names to ensure clarity about Ellucian offerings and what they do.
Use of “CRM” Term: It is preferable to use the “CRM” term in the suite name because “CRM”
is the accurate category name for this solution set. Using the CRM term will help the market
clearly identify how this solution set fits, what it does and where it competes.
Use of “Student Success” Term: The “Student Success” term should be reserved for Ellucian
to use at the category level, rather than in any specific product name. Because we will continue
to offer multiple solutions to address the broad set of needs around student success, it is
unwise for any single solution to carry the “student success” name.
Use of the “Suite” Term: Ellucian recently removed the term “Suite” from formal product
descriptions and a decision was made to not consider it in the naming considerations here in
alignment with the overall company branding and naming approaches.
Platform Name: As noted above, the platform is a component of the solution set, but not a
heavily featured component. For this reason, we should consider giving the platform the same
name as the suite itself, but designating it as the “platform” or “foundation” component of the
suite.
Legal Review: The name concepts below made it through a basic Google search to weed out
clear, direct conflicts in the CRM and educational software areas. However, these names have
not been through a legal review. Any favorite names will need to go through legal review to
ensure Ellucian’s legal team is comfortable with the naming approach.
April 5, 2016
3
4. Enterprise CRM Suite Approaches
April 5, 2016
Naming should be considered as
part of the greater whole – naming
should lend coherence and
alignment across the suite
Approach 1: Simple, descriptive
names across the board
Approach 2: More evocative solution
names across the board
4
7. A Side by Side Comparison (Example Only)
Ellucian CRM for
Education
Ellucian Recruiter
Ellucian Student
Engagement
Ellucian Advancement
Ellucian CRM Foundation
Ellucian Engage CRM
--
Ellucian Recruiter
Ellucian Mentor - -
-
Ellucian Ally
Ellucian Engage Platform
7April 5, 2016
8. Pre-EDUCAUSE Objectives
Determine preferred Enterprise CRM
naming approach
Define desired Enterprise CRM suite
and platform name
Align on additional approvers,
approval/validation process required
before legal review
Note: We should align on which approach we will use in
naming the student success, continuing ed/workforce
development, and advancement solutions, but we do not
need to finalize solution names prior to EDUCAUSE.
April 5, 2016
8