5. Where are you now?
When considering the development of a CRM programme in your institution, a critical first step is to make an honest assessment of your current position.
Three different stages of maturity in CRM practice in HEIs have been identified (The KSA Partnership, 2007, p.6).
-
Peripheral - isolated incidences of CRM usage, mainly to manage contacts, with no integration with other institutional systems
-
Tactical - multiple incidences of CRM usage to inform service delivery and improvement, with some integration with other institutional systems
-
Strategic – institution-wide use of CRM across all business units to inform strategic management of relationships, fully integrated with other institutional systems; cross-institutional BCE partner relationship management with other institutions at the same stage.
Business and community engagement (BCE)
BCE is the strategic management, by higher and further education institutions of relationships with external partners and clients and of the associated knowledge exchange and workforce development services. It is about solving problems and creating opportunities through external engagement and strategic management of the resulting interactions, partnerships and transactions. It includes both research-based and education-based services. The scope of engagement includes the commercial sector, the public sector, the cultural landscape and the social and civic arena. The objective is to deliver benefits to the economy and society and enrich the institutions themselves, resulting in a more highly skilled workforce, a more efficient, dynamic and sustainable economy and a more cohesive, knowledge-enabled society (JISC, 2008)
In fact, the different stages can be viewed as a continuum as shown by the diagram below.
| |
CRM defined narrowly and tactically
|
|
|
|
CRM defined broadly and strategically
|
|
 |
 |
 |
| |

|
|

|
|

|
|
| |
CRM is about the implementation of a specific technology solution project |
|
CRM is the implementation of an integrated series of customer-oriented technology solutions |
|
CRM is a holistic approach to managing customer relationships in order to create shareholder value |
|
The CRM continuum (Payne, 2006) |
Where are you now?
The diagram below can be used to assess the present position of your institution with respect to the development of CRM
Uptake across institution's business units |
 |
All business units across the institution (academic schools, BCE unit and other relevant support services) use the CRM system on a routine basis |
|
|
Strategic |
| |
BCE unit and some business units across the university (acadenuc schools and other relevant support services) use the CRM system on a routine basis |
|
Tactical |
|
 |
BCE unit and/or central team uses the CRM system on a routine basis
|
Peripheral |
|
|
| |
|
|
BCE relationships managed; no/little integration with other institutional systems; multiple instance/record of customer data |
BCE relationships managed; integration with some other institutional systems; movement towards a single incidence of customer data |
BCE relationships managed; full integration with relevant institutional systems; single instance/record of customer data |

|
|

|
Functions / functional integration |
The horizontal axis represents the breadth of the functions or BCE services/activities managed by the CRM system.
The vertical axis represents the level of uptake of the CRM system across the institution’s business units.
Where are you now?
-
To help you assess more accurately where you are at present,the following descriptors might help.
-
The left hand descriptors are typical of an institution in the early stages of development of a CRM. The right hand descriptors are typical of a more mature development.
-
Look at each descriptor. Where do you think you are now?
Covers a limited range of BCE services |
 |
Covers full range of BCE services |
Narrow range of transaction types supported |
 |
Wide range of transaction types supported |
Multiple instances of customer |
 |
Single instance/record of customer |
Supports interaction with a narrow range of customer types |
 |
Supports interactions with a wide range of customer types |
Single business unit uses the system on a routine basis |
 |
Multiple business unit uses the system on a routine basis |
Limited/no integration with other HEI function |
 |
Full integration with other HEI functions |
Limited/no integration with other relevant institutional systems |
 |
Full integration with other relevant institutional systems |
Provides basic customer needs to support operational activity |
 |
Provides client intelligence to inform strategic decision making/planning |
HEI-centric |
 |
Customer-centric |
Read a description of an HEI moving from peripheral to tactical
 |
This HEI is increasingly focusing on BCE but there is no enterprise-wide CRM system to support this strategy. Whilst there is a dedicated website, email addresses and telephone number for businesses, community and organisations to contact the HEI for research and business engagement, the majority of activities are done pro-actively by the Research Development Office and Schools / Academics with their existing contacts. Moreover, whilst there are some contact management systems in operation within the Alumni Office (Razors Edge) and some centralising of information via existing finance systems (Agresso), different schools, individual academics and staff appear to be holding their own contact databases, either in their own notebooks, simple Excel spreadsheets or in other database systems. Hence, there are duplicated contact details being held by different departments, schools or academics.
At the moment, the interoperability and sharing of data between these systems in this HEI is limited and in most cases, data collection and analysis are done manually among these independent databases. In addition to this, certain staff are also accessing external databases - such as the UK Research Councils, local authorities and companies. It would be impossible to have a general view of the past and on-going projects unless data are pulled and gathered from different systems manually. There is no central control system, which could enable different departments, schools and academics to share information at different stages of BCE.
This HEI recognised that more was needed to be done to provide an enterprise-wide approach to CRM. They considered that the following would help move them towards a more tactical focus:
-
Working towards more centralised CRM systems by sharing contact information between at least 2 or 3 departments units
-
Well communicated policies regarding information sharing across departments with the aim of ensuring clarity and institutional ‘buy in’
-
Harnessing existing contacts (within existing databases) rather than trying to foster new contacts (and databases)
-
Clear processes in terms of updating and sharing contact information
|
| |
Read a description of an HEI moving from tactical to strategic
 |
This HEI has a well worked up CRM supported process for dealing with BCE enquiries. This institution has a well documented vision for engaging with businesses and is moving towards an enterprise-wide approach to CRM usage.
The Business Partnership Office (BPO) usually acts as the first contact for business enquiries to the University, which can come from a variety of sources. Enquiries fall into six types corresponding to the main business propositions on the University’s 'Services to Business' web pages and brochures: person, expertise, training, facilities, specific programmes and others. The clients are required to mention the type of enquiry when making their request. Next, the BPO will assess the company or person who made the request, looking to see if there are any records of previous business or issues relating to this client; in case of previous records of a client not paying for previous services - or any other problems - the request may be refused. Otherwise, a new record is made for the new request or, for a client who has made previous enquiries, the record is updated. The current CRM system cannot, however, track multiple concurrent enquiries from the same client. The contacts are recorded using a customised CRM system built around Microsoft Outlook and Exchange. The CRM system is used within the BPO, by ‘Sector Partnership Champions’ (SPCs) and by Business Development Coordinators in other units. The graduate employability unit also uses the system. Next, the BPO will identify the relevant academic/department who can deal with the enquiry. If such expertise does not exist within the University the request is usually referred either to Exemplas or to the region’s other HEIs via Ask i10. The enquirer’s permission is asked first. The request is also routed to Sector Partnership Champions (SPCs) and/or faculty Business Development Coordinators. The BPO has agreed with the Heads of School to create a ‘tree’ of representatives and champions who have knowledge of the expertise of the people and research within academic departments and will record, manage and store the clients and tasks. They communicate periodically with the BPO.
There are other ways in which this University is contacted for business purposes either via KT or Graduates Services or directly to the faculties or relevant academics. The faculties have Faculty Client Service teams which include Business Development Coordinators, marketing executives, employability advisors, finance advisors and HR specialists. The SPC will contact the relevant person concerning the task. If the person can deal with the problem alone then the process is completed and the task accomplished. If there are agreements or contracts to be made, the Intellectual Property Rights and Contracts department is contacted which will draft the agreement or contract and agree with the client. There are several ways in which this HEI might move towards a more strategic phase.
-
Using a single CRM system adopted by all departments / schools and integrated with other corporate information systems such as finance, business development offices, graduate services and marketing and communications;
-
Ensuring that institutional policies and senior management instructions around BCE and information sharing were actually put into practice;
-
That the right amount of money is invested into the people, process and technology areas needed to ensure successful CRM development.
|
Where would you like to be?
The diagram below can be used to plan where you would like to move to in terms of being more tactical or strategic in your approach to CRM.
Remember: The horizontal axis represents the breadth of functions managed by the CRM system. The vertical axis represents the extent of uptake across the institution.
The arrows show the possible routes an institution might take to move from peripheral to tactical to strategic deployment of the CRM system.

What approach to implementation will you take?
There are four main implementation approaches:
The appropriateness of each model will depend on the circumstances of your institution. You do not have to move from peripheral straight to strategic. Many developers/consultancies advise on a phased approach so that the organization can get accustomed to the changes and any difficulties can be resolved without huge consequences to the entire organization.
More detail on each of the models can be found in JISC infoNet System Implementation www.jiscinfonet.ac.uk/InfoKits/system-implementation/planning/implementation-models
Key points to remember about planning a CRM implementation
 |
Three stages of maturity in CRM practice have been identified – peripheral, tactical and strategic |
 |
Use the case studies and descriptors to determine your present position |
 |
Plan where you want to move to |
 |
Be realistic in your aims. You do not have to move straight form Peripheral to strategic |
 |
Choose an implementation model that suits your institution |
 |
Use value maps to assess whether or not your institution is creating value for customers |
|
Jump to another section
require 'jump.inc'?>
|