Exhibit B
Professional Services Deployment Packages
LAST UPDATE: AUGUST 28, 2024. WRIKE, INC.
Table of contents:
3. DEPLOYMENT PACKAGE DESCRIPTIONS
A. Full Deployment—Remote Package - Business A
B. Full Deployment—Remote Package - Business B
C. Full Deployment—Remote Package - Business C
D. Full Deployment—Remote Package - Business D
E. Full Deployment—Remote Package - Enterprise A
F. Full Deployment—Remote Package - Enterprise B
G. Full Deployment—Remote Package - Enterprise C
H. Full Deployment—Remote Package - Enterprise D
I. Full Deployment—Remote Package - Pinnacle A
J. Full Deployment—Remote Package - Pinnacle B
K. Full Deployment—Remote Package - Pinnacle C
L. Full Deployment—Remote Package - Pinnacle D
4. PROFESSIONAL SERVICES TERMS & CONDITIONS
1. DEPLOYMENTS
Wrike Professional Services (“Wrike PS”) utilizes a coaching model to assist with the onboarding and deployment of the Wrike Service (“Deployment”). Through a series of steps (outlined below), Wrike will guide the Customer Deployment Team (defined below) through the onboarding process so Customer’s Deployment Team may learn to use and configure the Wrike Service and drive internal adoption.
Business A and Business B packages employ a combination of self-led online trainings along with sessions with a Wrike Professional Services Consultant. Full Deployment Packages (Professional A – B, Business C – D, Enterprise A – D, or Pinnacle A – D, whichever purchased) include process and change management sessions, best practice configuration, user training, and adoption guidance. The quantity and content of each session scales according to team size and complexity. The purchase of full deployment packages may be required for teams of a certain size.
2. DEPLOYMENT ROLES
To support Wrike’s collaborative Deployment, Wrike expects that Customer’s personnel are identified and made available to collaborate with their Wrike counterparts throughout the Deployment. Below is a breakdown of the key roles and responsibilities of each Party during the Deployment.
A. Customer Personnel
- Deployment Lead: Customer’s project leader and point of contact for communications with the Wrike team, coordination and facilitation of meetings, and deployment of the appropriate Customer’s personnel.
- Sponsor: Person(s) with authority to clarify project need, identify participants, and act as point of escalation, as needed.
- Subject Matter Experts (SMEs): Customer resources whom the Deployment Team can consult with to understand organizational structure and processes at a detailed level.
- Deployment Team: Consists of the Deployment Lead, Sponsor(s), Subject Matter Experts, and team leaders and department heads that have the proper authority and knowledge to define Customer’s workflow(s) and processes. The Deployment Team will work with the Professional Services Consultant to map and refine Customer’s processes and translate them into Wrike.
- User: An individual who is authorized to use or access the Service and who has been supplied an identification and password by Customer or at Customer’s direction.
B. Wrike Personnel
- Professional Services Consultant: Designated point of contact throughout the Deployment, responsible for delivering Wrike’s portion of the Deployment activities. The Wrike attendee for all applicable sessions shall be the Professional Services Consultant.
3. DEPLOYMENT PACKAGE DESCRIPTIONS
A. Full Deployment—Remote Package - Business A
If purchased, the Remote Deployment Package Business A includes:
- Quick Start online learning module outlined in the “Quick Start” package in Exhibit E.
- Consulting sessions include those depicted below.
Remote Package - Business A | |
Maximum Number of Remote Sessions | 5 (Five) Sessions |
Maximum Number of Teams or Processes | 1 (One) Team or Process |
Maximum Number of Users | Up to 35 (thirty-five) Users |
Timeline for Deployment | Deployment must start within 30 (thirty) days of Customer’s purchase; Deployment activities will expire 75 (seventy-five) days from Customer’s purchase |
Applicable Subscription Type | Wrike Business |
Remote Package Business A: Activities/Steps | ||||
Deployment Step | Mode of Delivery / Expected Effort* | Customer Attendees | Activities Involved | Customer Action Items |
1. Kickoff | Remote / Up to 30 minutes | 1. Deployment Lead(s) | • Introductions •Restatement of scope and purpose •Preparation for Kickoff call (ensure appropriate audience, schedule call/s) •Discussion of timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete Champion Training as defined in Exhibit E |
2. Champion Training | Self-led online training / 12-18 hours total | 1. Deployment Lead(s) 2. Additional Champions (if applicable) | The following activities are to be completed by Customer as part of the self-led portion of the Champion Training:
| Pre-Training: •Provide a list of Additional Champions to be enrolled into the Champion portion of the Training Post-Training: •Schedule remaining sessions with the Professional Services Consultant |
3. Consulting Sessions | Remote / Up to 4 Sessions of up to 1 hour each | 1. Deployment Team 2. Sponsor | These sessions can used for the following, based on agreement between the Consultant and Customer: •Review of homework completed by Customer •Discussion on opportunities for improvement •Discussion on additional Wrike functionality •Change Management best practice •Training sessions/office hours | Pre-Session: •Configure account based on self-led modules defined in Exhibit E Post-Session: •Complete action items discussed in preparation for next session |
*NOTE: “Expected Effort” refers to time spent in meetings or workshops between Wrike and Customer teams. It does not account for time spent on preparation or follow-up actions for either team.
B. Full Deployment—Remote Package - Business B
If purchased, the Remote Deployment Package Business B includes:
- Quick Start online learning module outlined in the “Quick Start” package in Exhibit E.
- Consulting sessions include those depicted below.
Remote Package - Business B | |
Maximum Number of Remote Sessions | 8 (Eight) Sessions |
Maximum Number of Teams or Processes | 1 (One) Team or Process |
Maximum Number of Users | Up to 65 (sixty-five) Users |
Timeline for Deployment | Deployment must start within 30 (thirty) days of Customer’s purchase; Deployment activities will expire 90 (ninety) days from Customer’s purchase |
Applicable Subscription Type | Wrike Business |
Remote Package Business B: Activities/Steps | ||||
Deployment Step | Mode of Delivery / Expected Effort* | Customer Attendees | Activities Involved | Customer Action Items |
1. Kickoff | Remote / Up to 60 minutes | 1. Deployment Lead(s) | • Introductions •Restatement of scope and purpose •Preparation for Kickoff call (ensure appropriate audience, schedule call/s) •Discussion of timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete Champion Training as defined in Exhibit E |
2. Champion Training | Self-led online training / 12-18 hours total. | 1. Deployment Lead(s) 2. Additional Champions (if applicable) | The following activities are to be completed by Customer as part of the self-led portion of the Champion Training:
| Pre-Training: •Provide a list of Additional Champions to be enrolled into the Champion portion of the Training Post-Training: •Schedule remaining sessions with the Professional Services Consultant |
3. Consulting sessions | Remote / Up to 7 Sessions of up to 1 hour each | 1. Deployment Team 2. Sponsor | These sessions can used for the following, based on agreement between the Consultant and Customer: •Review of homework completed by Customer •Discussion on opportunities for improvement •Discussion on additional Wrike functionality •Training sessions/office hours | Pre-Session: •Configure account based on self-led modules defined in Exhibit E Post-Session: •Complete action items discussed in preparation for next session |
*NOTE: “Expected Effort” refers to time spent in meetings or workshops between Wrike and Customer teams. It does not account for time spent on preparation or follow-up actions for either team.
C. Full Deployment—Remote Package - Business C
If purchased, the Remote Deployment Package Business C includes:
Remote Package - Business C | |
Maximum Number of Remote Sessions | 15 (Fifteen) Sessions |
Maximum Number of Teams or Processes | 1 (One) Team or Process |
Maximum Number of Users | Up to 100 (one hundred) Users |
Timeline for Deployment | Deployment must start within 30 (thirty) days of Customer’s purchase; Deployment activities will expire 90 (ninety) days from Customer’s purchase |
Applicable Subscription Type | Wrike Business |
Remote Package Business C: Activities/Steps | ||||
Deployment Step | Mode of Delivery / Expected Effort* | Customer Attendees | Activities Involved | Customer Action Items |
1. Pre-Kickoff | Remote / Up to 30 minutes | 1. Deployment Lead(s) | • Introductions •Restatement of scope and purpose •Preparation for Kickoff call (ensure appropriate audience, schedule call/s) •Discussion of timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
2. Kickoff | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introductions •Review team processes and collect background information •Agree on timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
3. Change Management | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introduction to Change Management concepts •Review of change readiness questionnaire •Identification of affected stakeholders and change management planning | Post-Session: •Develop Communications Plan and content •Determine process to be reviewed during next session and identify leads and SMEs for each process |
4. Discovery | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • In-depth review of current processes and future-state design considerations •Discussion on opportunities for improvement | Post-Session: •Communicate with affected stakeholders |
5. Process Configuration | Remote / Up to 2 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Identification of desired process refinements •Training and guidance on translating Customer business process into Wrike •Recommendations on Wrike usage proven practice(s) | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete process configuration tasks as defined during session(s) |
6. Workspace Configuration | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Creation of initial account structure •Recommendations on sharing and visibility | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete workspace configuration tasks as defined during session(s) |
7. Configuration Walk-through | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Validation of end-to-end process via a walkthrough from process initiation to completion | Post-Session: •Address any identified changes prior to team trainings |
8. Dashboards and Reporting | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Identification and initial build out of work monitoring needs (dashboards, reports, calendars) | Post-Session: •Continue to build out identified dashboards, reports and calendars |
9. Launch Planning | Remote / Up to 1 hour | 1. Deployment Team | • Discussion to identify potential roadblocks to adoption and usage •Preparation for training sessions | Post-Session: •Develop identified collateral and communications |
10. Training | Remote / Up to 4 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs 3. Other team members as identified by Deployment Team | • Training sessions can focus on account administration, end user capabilities, champions, specific functionality, open office hours, train-the-trainer, Space administrators | Pre-Session: •Watch required Wrike Discover courses in preparation for training •Coordinate attendees to ensure participation During Session: •Deployment Lead or Sponsor to assist in the delivery of agreed upon agenda content |
11. Deployment Closeout | Remote / Up to 30 minutes | 1. Deployment Lead 2. Sponsor | • Summary of outcomes and knowledge transfer with Wrike and Customer teams | • N/A |
*NOTE: “Expected Effort” refers to time spent in meetings or workshops between Wrike and Customer teams. It does not account for time spent on preparation or follow-up actions for either team.
D. Full Deployment—Remote Package - Business D
If purchased, the Remote Deployment Package Business D includes:
Remote Package - Business D | |
Maximum Number of Remote Sessions | 27 (Twenty-seven) Sessions |
Maximum Number of Teams or Processes | 2 (Two) Teams or Processes |
Maximum Number of Users | Up to 250 (two hundred fifty) Users |
Timeline for Deployment | Deployment must start within 30 (thirty) days of Customer’s purchase; Deployment activities will expire 120 (one hundred twenty) days from Customer’s purchase |
Applicable Subscription Type | Wrike Business |
Remote Package Business D: Activities/Steps | ||||
Deployment Step | Mode of Delivery / Expected Effort* | Customer Attendees | Activities Involved | Customer Action Items |
1. Pre-Kickoff | Remote / Up to 30 minutes | 1. Deployment Lead(s) | • Introductions •Restatement of scope and purpose •Preparation for Kickoff call (ensure appropriate audience, schedule call/s) •Discussion of timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
2. Kickoff | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introductions •Review team processes and collect background information •Agree on timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
3. Change Management | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introduction to Change Management concepts •Review of change readiness questionnaire •Identification of affected stakeholders and change management planning | Post-Session: •Develop Communications Plan and content •Determine process to be reviewed during next session and identify leads and SMEs for each process |
4. Discovery | Remote / Up to 2 Sessions of up to 1 hour each | 1. Deployment Team 2. Sponsor | • In-depth review of current processes and future-state design considerations •Discussion on opportunities for improvement | Post-Session: •Communicate with affected stakeholders |
5. Requirements Review | Remote / Up to 2 Sessions of up to 1 hour each | 1. Deployment Team 2. Sponsor | • Review design plans based on Discovery conversations | Post-Session: •Review final requirements document with affected stakeholders |
6. Process Configuration | Remote / Up to 4 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Identification of desired process refinements •Training and guidance on translating Customer business process into Wrike •Recommendations on Wrike usage proven practice(s) | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete process configuration tasks as defined during session(s) |
7. Workspace Configuration | Remote / Up to 2 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Creation of initial account structure •Recommendations on sharing and visibility | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete workspace configuration tasks as defined during session(s) |
8. Configuration Walk-through | Remote / Up to 2 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Validation of end-to-end process via a walkthrough from process initiation to completion | Post-Session: •Address any identified changes prior to team trainings |
9. Dashboards and Reporting | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Identification and initial build out of work monitoring needs (dashboards, reports, calendars) | Post-Session: •Continue to build out identified dashboards, reports and calendars |
10. Launch Planning | Remote / Up to 1 hour | 1. Deployment Team | • Discussion to identify potential roadblocks to adoption and usage •Preparation for training sessions | Post-Session: •Develop identified collateral and communications |
11. Training | Remote / Up to 8 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs 3. Other team members as identified by Deployment Team | • Training sessions can focus on account administration, end user capabilities, champions, specific functionality, open office hours, train-the-trainer, Space administrators | Pre-Session: •Watch required Wrike Discover courses in preparation for training •Coordinate attendees to ensure participation During Session: •Deployment Lead or Sponsor to assist in the delivery of agreed upon agenda content |
12. Adoption Monitoring | Remote / Up to 30 minutes held the week after the Champion Training | 1. Deployment Team 2. Sponsor | • Post training follow-up reviewing usage data and identifying risk areas | Post-Session: •Communicate with affected stakeholders |
13. Deployment Closeout | Remote / Up to 30 minutes | 1. Deployment Lead 2. Sponsor | • Summary of outcomes and knowledge transfer with Wrike and Customer teams | • N/A |
*NOTE: “Expected Effort” refers to time spent in meetings or workshops between Wrike and Customer teams. It does not account for time spent on preparation or follow-up actions for either team.
E. Full Deployment—Remote Package - Enterprise A
If purchased, the Remote Deployment Package Enterprise A includes:
Remote Package - Enterprise A | |
Maximum Number of Remote Sessions | 9 (Nine) Sessions |
Maximum Number of Teams or Processes | 1 (One) Team or Process |
Maximum Number of Users | Up to 35 (thirty-five) Users |
Timeline for Deployment | Deployment must start within 30 (thirty) days of Customer’s purchase; Deployment activities will expire 75 (seventy-five) days from Customer’s purchase |
Applicable Subscription Type | Wrike Enterprise |
Remote Package Enterprise A: Activities/Steps | ||||
Deployment Step | Mode of Delivery / Expected Effort* | Customer Attendees | Activities Involved | Customer Action Items |
1. Pre-Kickoff | Remote / Up to 30 minutes | 1. Deployment Lead(s) | • Introductions •Restatement of scope and purpose •Preparation for Kickoff call (ensure appropriate audience, schedule call/s) •Discussion of timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
2. Kickoff | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introductions •Review team processes and collect background information •Agree on timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
3. Process Configuration | Remote / Up to 2 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Identification of desired process refinements •Training and guidance on translating Customer business process into Wrike •Recommendations on Wrike usage proven practice(s) | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete process configuration tasks as defined during session(s) |
4. Workspace Configuration | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Creation of initial account structure •Recommendations on sharing and visibility | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete workspace configuration tasks as defined during session(s) |
5. Launch Planning | Remote / Up to 1 hour | 1. Deployment Team | • Discussion to identify potential roadblocks to adoption and usage •Preparation for training sessions | Post-Session: •Develop identified collateral and communications |
6. Training | Remote / Up to 2 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs 3. Other team members as identified by Deployment Team | • Training sessions can focus on account administration, end user capabilities, champions, specific functionality, open office hours, train-the-trainer, Space administrators | Pre-Session: •Watch required Wrike Discover courses in preparation for training •Coordinate attendees to ensure participation During Session: •Deployment Lead or Sponsor to assist in the delivery of agreed upon agenda content |
7. Deployment Closeout | Remote / Up to 30 minutes | 1. Deployment Lead 2. Sponsor | • Summary of outcomes and knowledge transfer with Wrike and Customer teams | • N/A |
*NOTE: “Expected Effort” refers to time spent in meetings or workshops between Wrike and Customer teams. It does not account for time spent on preparation or follow-up actions for either team.
F. Full Deployment—Remote Package - Enterprise B
If purchased, the Remote Deployment Package Enterprise B includes:
Remote Package - Enterprise B | |
Maximum Number of Remote Sessions | 16 (Sixteen) Sessions |
Maximum Number of Teams or Processes | 1 (One) Team or Process |
Maximum Number of Users | Up to 65 (sixty-five) Users |
Timeline for Deployment | Deployment must start within 30 (thirty) days of Customer’s purchase; Deployment activities will expire 90 (ninety) days from Customer’s purchase |
Applicable Subscription Type | Wrike Enterprise |
Remote Package Enterprise B: Activities/Steps | ||||
Deployment Step | Mode of Delivery / Expected Effort* | Customer Attendees | Activities Involved | Customer Action Items |
1. Pre-Kickoff | Remote / Up to 30 minutes | 1. Deployment Lead(s) | • Introductions •Restatement of scope and purpose •Preparation for Kickoff call (ensure appropriate audience, schedule call/s) •Discussion of timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
2. Kickoff | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introductions •Review team processes and collect background information •Agree on timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
3. Change Management | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introduction to Change Management concepts •Review of change readiness questionnaire •Identification of affected stakeholders and change management planning | Post-Session: •Develop Communications Plan and content •Determine process to be reviewed during next session and identify leads and SMEs for each process |
4. Discovery | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • In-depth review of current processes and future-state design considerations •Discussion on opportunities for improvement | Post-Session: •Communicate with affected stakeholders |
5. Requirements Review | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Review design plans based on Discovery conversations | Post-Session: •Review final requirements document with affected stakeholders |
6. Process Configuration | Remote / Up to 3 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Identification of desired process refinements •Training and guidance on translating Customer business process into Wrike •Recommendations on Wrike usage proven practice(s) | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete process configuration tasks as defined during session(s) |
7. Workspace Configuration | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Creation of initial account structure •Recommendations on sharing and visibility | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete workspace configuration tasks as defined during session(s) |
8. Configuration Walk-through | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Validation of end-to-end process via a walkthrough from process initiation to completion | Post-Session: •Address any identified changes prior to team trainings |
9. Dashboards and Reporting | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Identification and initial build out of work monitoring needs (dashboards, reports, calendars) | Post-Session: •Continue to build out identified dashboards, reports and calendars |
10. Launch Planning | Remote / Up to 1 hour | 1. Deployment Team | • Discussion to identify potential roadblocks to adoption and usage •Preparation for training sessions | Post-Session: •Develop identified collateral and communications |
11. Training | Remote / Up to 3 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs 3. Other team members as identified by Deployment Team | • Training sessions can focus on account administration, end user capabilities, champions, specific functionality, open office hours, train-the-trainer, Space administrators | Pre-Session: •Watch required Wrike Discover courses in preparation for training •Coordinate attendees to ensure participation During Session: •Deployment Lead or Sponsor to assist in the delivery of agreed upon agenda content |
12. Deployment Closeout | Remote / Up to 30 minutes | 1. Deployment Lead 2. Sponsor | • Summary of outcomes and knowledge transfer with Wrike and Customer teams | • N/A |
*NOTE: “Expected Effort” refers to time spent in meetings or workshops between Wrike and Customer teams. It does not account for time spent on preparation or follow-up actions for either team.
G. Full Deployment—Remote Package - Enterprise C
If purchased, the Remote Deployment Package Enterprise C includes:
Remote Package - Enterprise C | |
Maximum Number of Remote Sessions | 28 (Twenty-eight) Sessions |
Maximum Number of Teams or Processes | 2 (Two) Teams or Processes |
Maximum Number of Users | Up to 100 (one hundred) Users |
Timeline for Deployment | Deployment must start within 30 (thirty) days of Customer’s purchase; Deployment activities will expire 120 (one hundred twenty) days from Customer’s purchase |
Applicable Subscription Type | Wrike Enterprise |
Remote Package Enterprise C: Activities/Steps | ||||
Deployment Step | Mode of Delivery / Expected Effort* | Customer Attendees | Activities Involved | Customer Action Items |
1. Pre-Kickoff | Remote / Up to 30 minutes | 1. Deployment Lead(s) | • Introductions •Restatement of scope and purpose •Preparation for Kickoff call (ensure appropriate audience, schedule call/s) •Discussion of timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
2. Kickoff | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introductions •Review team processes and collect background information •Agree on timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
3. Change Management | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introduction to Change Management concepts •Review of change readiness questionnaire •Identification of affected stakeholders and change management planning | Post-Session: •Develop Communications Plan and content •Determine process to be reviewed during next session and identify leads and SMEs for each process |
4. Discovery | Remote / Up to 2 Sessions of up to 1 hour each | 1. Deployment Team 2. Sponsor | • In-depth review of current processes and future-state design considerations •Discussion on opportunities for improvement | Post-Session: •Communicate with affected stakeholders |
5. Requirements Review | Remote / Up to 2 Sessions of up to 1 hour each | 1. Deployment Team 2. Sponsor | • Review design plans based on Discovery conversations | Post-Session: •Review final requirements document with affected stakeholders |
6. Process Configuration | Remote / Up to 5 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Identification of desired process refinements •Training and guidance on translating Customer business process into Wrike •Recommendations on Wrike usage proven practice(s) | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete process configuration tasks as defined during session(s) |
7. Workspace Configuration | Remote / Up to 2 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Creation of initial account structure •Recommendations on sharing and visibility | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete workspace configuration tasks as defined during session(s) |
8. Configuration Walk-through | Remote / Up to 2 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Validation of end-to-end process via a walkthrough from process initiation to completion | Post-Session: •Address any identified changes prior to team trainings |
9. Dashboards and Reporting | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Identification and initial build out of work monitoring needs (dashboards, reports, calendars) | Post-Session: •Continue to build out identified dashboards, reports and calendars |
10. Launch Planning | Remote / Up to 1 hour | 1. Deployment Team | • Discussion to identify potential roadblocks to adoption and usage •Preparation for training sessions | Post-Session: •Develop identified collateral and communications |
11. Training | Remote / Up to 7 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs 3. Other team members as identified by Deployment Team | • Training sessions can focus on account administration, end user capabilities, champions, specific functionality, open office hours, train-the-trainer, Space administrators | Pre-Session: •Watch required Wrike Discover courses in preparation for training •Coordinate attendees to ensure participation During Session: •Deployment Lead or Sponsor to assist in the delivery of agreed upon agenda content |
12. Adoption Monitoring | Remote / Up to 2 Sessions of up to 30 minutes each held weekly starting the week after the Champion Training | 1. Deployment Team 2. Sponsor | • Post training follow-up reviewing usage data and identifying risk areas | Post-Session: •Communicate with affected stakeholders |
13. Deployment Closeout | Remote / Up to 30 minutes | 1. Deployment Lead 2. Sponsor | • Summary of outcomes and knowledge transfer with Wrike and Customer teams | • N/A |
*NOTE: “Expected Effort” refers to time spent in meetings or workshops between Wrike and Customer teams. It does not account for time spent on preparation or follow-up actions for either team.
H. Full Deployment—Remote Package - Enterprise D
If purchased, the Remote Deployment Package Enterprise D includes:
Remote Package - Enterprise D | |
Maximum Number of Remote Sessions | 40 (Forty) Sessions |
Maximum Number of Teams or Processes | 3 (Three) Teams or Processes |
Maximum Number of Users | Up to 250 (two hundred fifty) Users |
Timeline for Deployment | Deployment must start within 30 (thirty) days of Customer’s purchase; Deployment activities will expire 150 (one hundred fifty) days from Customer’s purchase |
Applicable Subscription Type | Wrike Enterprise |
Remote Package Enterprise D: Activities/Steps | ||||
Deployment Step | Mode of Delivery / Expected Effort* | Customer Attendees | Activities Involved | Customer Action Items |
1. Pre-Kickoff | Remote / Up to 30 minutes | 1. Deployment Lead(s) | • Introductions •Restatement of scope and purpose •Preparation for Kickoff call (ensure appropriate audience, schedule call/s) •Discussion of timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
2. Kickoff | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introductions •Review team processes and collect background information •Agree on timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
3. Change Management | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introduction to Change Management concepts •Review of change readiness questionnaire •Identification of affected stakeholders and change management planning | Post-Session: •Develop Communications Plan and content •Determine process to be reviewed during next session and identify leads and SMEs for each process |
4. Discovery | Remote / Up to 3 Sessions of up to 1 hour each | 1. Deployment Team 2. Sponsor | • In-depth review of current processes and future-state design considerations •Discussion on opportunities for improvement | Post-Session: •Communicate with affected stakeholders |
5. Requirements Review | Remote / Up to 3 Sessions of up to 1 hour each | 1. Deployment Team 2. Sponsor | • Review design plans based on Discovery conversations | Post-Session: •Review final requirements document with affected stakeholders |
6. Process Configuration | Remote / Up to 9 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Identification of desired process refinements •Training and guidance on translating Customer business process into Wrike •Recommendations on Wrike usage proven practice(s) | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete process configuration tasks as defined during session(s) |
7. Workspace Configuration | Remote / Up to 3 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Creation of initial account structure •Recommendations on sharing and visibility | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete workspace configuration tasks as defined during session(s) |
8. Configuration Walk-through | Remote / Up to 3 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Validation of end-to-end process via a walkthrough from process initiation to completion | Post-Session: •Address any identified changes prior to team trainings |
9. Dashboards and Reporting | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Identification and initial build out of work monitoring needs (dashboards, reports, calendars) | Post-Session: •Continue to build out identified dashboards, reports and calendars |
10. Launch Planning | Remote / Up to 1 hour | 1. Deployment Team | • Discussion to identify potential roadblocks to adoption and usage •Preparation for training sessions | Post-Session: •Develop identified collateral and communications |
11. Training | Remote / Up to 10 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs 3. Other team members as identified by Deployment Team | • Training sessions can focus on account administration, end user capabilities, champions, specific functionality, open office hours, train-the-trainer, Space administrators | Pre-Session: •Watch required Wrike Discover courses in preparation for training •Coordinate attendees to ensure participation During Session: •Deployment Lead or Sponsor to assist in the delivery of agreed upon agenda content |
12. Adoption Monitoring | Remote / Up to 2 Sessions of up to 30 minutes each held weekly starting the week after the Champion Training | 1. Deployment Team 2. Sponsor | • Post training follow-up reviewing usage data and identifying risk areas | Post-Session: •Communicate with affected stakeholders |
13. Executive Briefing | Remote / Up to 1 hour | 1. Deployment Lead 2. Sponsor 3. Executive Sponsor | • Summary of accomplishments and process improvements •Identification of areas for growth •Introduction of Customer Success model | • N/A |
14. Deployment Closeout | Remote / Up to 30 minutes | 1. Deployment Lead 2. Sponsor | • Summary of outcomes and knowledge transfer with Wrike and Customer teams | • N/A |
*NOTE: “Expected Effort” refers to time spent in meetings or workshops between Wrike and Customer teams. It does not account for time spent on preparation or follow-up actions for either team.
I. Full Deployment—Remote Package - Pinnacle A
If purchased, the Remote Deployment Package Pinnacle A includes:
- Access for 1 (one) User to complete the self-paced Report Mastery Silver Certification on Wrike Discover;
- Deployment sessions include those depicted below.
Remote Package - Pinnacle A | |
Maximum Number of Remote Sessions | 13 (Thirteen) Sessions |
Maximum Number of Teams or Processes | 1 (One) Team or Process |
Maximum Number of Users | Up to 35 (thirty-five) Users |
Timeline for Deployment | Deployment must start within 30 (thirty) days of Customer’s purchase; Deployment activities will expire 120 (one hundred twenty) days from Customer’s purchase |
Applicable Subscription Type | Wrike Pinnacle |
Remote Package Pinnacle A: Activities/Steps | ||||
Deployment Step | Mode of Delivery / Expected Effort* | Customer Attendees | Activities Involved | Customer Action Items |
1. Pre-Kickoff | Remote / Up to 30 minutes | 1. Deployment Lead(s) | • Introductions •Restatement of scope and purpose •Preparation for Kickoff call (ensure appropriate audience, schedule call/s) •Discussion of timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
2. Kickoff | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introductions •Review team processes and collect background information •Agree on timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
3. Discovery | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • In-depth review of current processes and future-state design considerations •Discussion on opportunities for improvement | Post-Session: •Communicate with affected stakeholders |
4. Process Configuration | Remote / Up to 3 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Identification of desired process refinements •Training and guidance on translating Customer business process into Wrike •Recommendations on Wrike usage proven practice(s) | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete process configuration tasks as defined during session(s) |
5. Workspace Configuration | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Creation of initial account structure •Recommendations on sharing and visibility | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete workspace configuration tasks as defined during session(s) |
6. Configuration Walk-through | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Validation of end-to-end process via a walkthrough from process initiation to completion | Post-Session: •Address any identified changes prior to team trainings |
7. Dashboards and Reporting | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Identification and initial build out of work monitoring needs (dashboards, reports, calendars) | Post-Session: •Continue to build out identified dashboards, reports and calendars |
8. Launch Planning | Remote / Up to 1 hour | 1. Deployment Team | • Discussion to identify potential roadblocks to adoption and usage •Preparation for training sessions | Post-Session: •Develop identified collateral and communications |
9. Training | Remote / Up to 2 sessions with a maximum of 90 mins for a single session; not to exceed 150 mins (2.5 hours) total for 2 sessions | 1. Deployment Team 2. Process SMEs 3. Other team members as identified by Deployment Team | • Training sessions can focus on account administration, end user capabilities, champions, specific functionality, open office hours, train-the-trainer, Space administrators | Pre-Session: •Watch required Wrike Discover courses in preparation for training •Coordinate attendees to ensure participation During Session: •Deployment Lead or Sponsor to assist in the delivery of agreed upon agenda content |
10. Deployment Closeout | Remote / Up to 30 minutes | 1. Deployment Lead 2. Sponsor | • Summary of outcomes and knowledge transfer with Wrike and Customer teams | • N/A |
*NOTE: “Expected Effort” refers to time spent in meetings or workshops between Wrike and Customer teams. It does not account for time spent on preparation or follow-up actions for either team.
J. Full Deployment—Remote Package - Pinnacle B
If purchased, the Remote Deployment Package Pinnacle B includes:
- Access for 1 (one) User to complete the self-paced Report Mastery Silver Certification on Wrike Discover;
- Deployment sessions include those depicted below.
Remote Package - Pinnacle B | |
Maximum Number of Remote Sessions | 18 (Eighteen) Sessions |
Maximum Number of Teams or Processes | 1 (One) Team or Process |
Maximum Number of Users | Up to 65 (sixty-five) Users |
Timeline for Deployment | Deployment must start within 30 (thirty) days of Customer’s purchase; Deployment activities will expire 120 (one hundred twenty) days from Customer’s purchase |
Applicable Subscription Type | Wrike Pinnacle |
Remote Package Pinnacle B: Activities/Steps | ||||
Deployment Step | Mode of Delivery / Expected Effort* | Customer Attendees | Activities Involved | Customer Action Items |
1. Pre-Kickoff | Remote / Up to 30 minutes | 1. Deployment Lead(s) | • Introductions •Restatement of scope and purpose •Preparation for Kickoff call (ensure appropriate audience, schedule call/s) •Discussion of timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
2. Kickoff | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introductions •Review team processes and collect background information •Agree on timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
3. Change Management | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introduction to Change Management concepts •Review of change readiness questionnaire •Identification of affected stakeholders and change management planning | Post-Session: •Develop Communications Plan and content •Determine process to be reviewed during next session and identify leads and SMEs for each process |
4. Discovery | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • In-depth review of current processes and future-state design considerations •Discussion on opportunities for improvement | Post-Session: •Communicate with affected stakeholders |
5. Requirements Review | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Review design plans based on Discovery conversations | Post-Session: •Review final requirements document with affected stakeholders |
6. Process Configuration | Remote / Up to 4 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Identification of desired process refinements •Training and guidance on translating Customer business process into Wrike •Recommendations on Wrike usage proven practice(s) | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete process configuration tasks as defined during session(s) |
7. Workspace Configuration | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Creation of initial account structure •Recommendations on sharing and visibility | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete workspace configuration tasks as defined during session(s) |
8. Configuration Walk-through | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Validation of end-to-end process via a walkthrough from process initiation to completion | Post-Session: •Address any identified changes prior to team trainings |
9. Dashboards and Reporting | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Identification and initial build out of work monitoring needs (dashboards, reports, calendars) | Post-Session: •Continue to build out identified dashboards, reports and calendars |
10. Launch Planning | Remote / Up to 1 hour | 1. Deployment Team | • Discussion to identify potential roadblocks to adoption and usage •Preparation for training sessions | Post-Session: •Develop identified collateral and communications |
11. Training | Remote / Up to 4 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs 3. Other team members as identified by Deployment Team | • Training sessions can focus on account administration, end user capabilities, champions, specific functionality, open office hours, train-the-trainer, Space administrators | Pre-Session: •Watch required Wrike Discover courses in preparation for training •Coordinate attendees to ensure participation During Session: •Deployment Lead or Sponsor to assist in the delivery of agreed upon agenda content |
12. Deployment Closeout | Remote / Up to 30 minutes | 1. Deployment Lead 2. Sponsor | • Summary of outcomes and knowledge transfer with Wrike and Customer teams | • N/A |
*NOTE: “Expected Effort” refers to time spent in meetings or workshops between Wrike and Customer teams. It does not account for time spent on preparation or follow-up actions for either team.
K. Full Deployment—Remote Package - Pinnacle C
If purchased, the Remote Deployment Package Pinnacle C includes:
- Analyze sessions as outlined in the “Analyze Standard” package in Exhibit D.
- Deployment sessions include those depicted below.
Remote Package - Pinnacle C | |
Maximum Number of Remote Sessions | 31 (Thirty-one) Sessions |
Maximum Number of Teams or Processes | 2 (Two) Teams or Processes |
Maximum Number of Users | Up to 100 (one hundred) Users |
Timeline for Deployment | Deployment must start within 30 (thirty) days of Customer’s purchase; Deployment activities will expire 120 (one hundred twenty) days from Customer’s purchase |
Applicable Subscription Type | Wrike Pinnacle |
Remote Package Pinnacle C: Activities/Steps | ||||
Deployment Step | Mode of Delivery / Expected Effort* | Customer Attendees | Activities Involved | Customer Action Items |
1. Pre-Kickoff | Remote / Up to 30 minutes | 1. Deployment Lead(s) | • Introductions •Restatement of scope and purpose •Preparation for Kickoff call (ensure appropriate audience, schedule call/s) •Discussion of timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
2. Kickoff | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introductions •Review team processes and collect background information •Agree on timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
3. Change Management | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introduction to Change Management concepts •Review of change readiness questionnaire •Identification of affected stakeholders and change management planning | Post-Session: •Develop Communications Plan and content •Determine process to be reviewed during next session and identify leads and SMEs for each process |
4. Discovery | Remote / Up to 2 Sessions of up to 1 hour each | 1. Deployment Team 2. Sponsor | • In-depth review of current processes and future-state design considerations •Discussion on opportunities for improvement | Post-Session: •Communicate with affected stakeholders |
5. Requirements Review | Remote / Up to 2 Sessions of up to 1 hour each | 1. Deployment Team 2. Sponsor | • Review design plans based on Discovery conversations | Post-Session: •Review final requirements document with affected stakeholders |
6. Process Configuration | Remote / Up to 7 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Identification of desired process refinements •Training and guidance on translating Customer business process into Wrike •Recommendations on Wrike usage proven practice(s) | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete process configuration tasks as defined during session(s) |
7. Workspace Configuration | Remote / Up to 2 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Creation of initial account structure •Recommendations on sharing and visibility | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete workspace configuration tasks as defined during session(s) |
8. Configuration Walk-through | Remote / Up to 2 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Validation of end-to-end process via a walkthrough from process initiation to completion | Post-Session: •Address any identified changes prior to team trainings |
9. Dashboards and Reporting | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Identification and initial build out of work monitoring needs (dashboards, reports, calendars) | Post-Session: •Continue to build out identified dashboards, reports and calendars |
10. Launch Planning | Remote / Up to 1 hour | 1. Deployment Team | • Discussion to identify potential roadblocks to adoption and usage •Preparation for training sessions | Post-Session: •Develop identified collateral and communications |
11. Training | Remote / Up to 8 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs 3. Other team members as identified by Deployment Team | • Training sessions can focus on account administration, end user capabilities, champions, specific functionality, open office hours, train-the-trainer, Space administrators | Pre-Session: •Watch required Wrike Discover courses in preparation for training •Coordinate attendees to ensure participation During Session: •Deployment Lead or Sponsor to assist in the delivery of agreed upon agenda content |
12. Adoption Monitoring | Remote / Up to 2 Sessions of up to 30 minutes each held weekly starting the week after the Champion Training | 1. Deployment Team 2. Sponsor | • Post training follow-up reviewing usage data and identifying risk areas | Post-Session: •Communicate with affected stakeholders |
13. Deployment Closeout | Remote / Up to 30 minutes | 1. Deployment Lead 2. Sponsor | • Summary of outcomes and knowledge transfer with Wrike and Customer teams | • N/A |
*NOTE: “Expected Effort” refers to time spent in meetings or workshops between Wrike and Customer teams. It does not account for time spent on preparation or follow-up actions for either team.
L. Full Deployment—Remote Package - Pinnacle D
If purchased, the Remote Deployment Package Pinnacle D includes:
- Analyze sessions as outlined in the “Analyze Standard” package in Exhibit D.
- Deployment sessions include those depicted below.
Remote Package - Pinnacle D | |
Maximum Number of Remote Sessions | 42 (Forty-two) Sessions |
Maximum Number of Teams or Processes | 3 (Three) Teams or Processes |
Maximum Number of Users | Up to 250 (two hundred fifty) Users |
Timeline for Deployment | Deployment must start within 30 (thirty) days of Customer’s purchase; Deployment activities will expire 150 (one hundred fifty) days from Customer’s purchase |
Applicable Subscription Type | Enterprise Pinnacle |
Remote Package Pinnacle D: Activities/Steps | ||||
Deployment Step | Mode of Delivery / Expected Effort* | Customer Attendees | Activities Involved | Customer Action Items |
1. Pre-Kickoff | Remote / Up to 30 minutes | 1. Deployment Lead(s) | • Introductions •Restatement of scope and purpose •Preparation for Kickoff call (ensure appropriate audience, schedule call/s) •Discussion of timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
2. Kickoff | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introductions •Review team processes and collect background information •Agree on timelines, training approach and team roles | Pre-Session: •Provide any supporting documentation to Wrike PS prior to session Post-Session: •Complete action items discussed in preparation for next session |
3. Change Management | Remote / Up to 1 hour | 1. Deployment Team 2. Sponsor | • Introduction to Change Management concepts •Review of change readiness questionnaire •Identification of affected stakeholders and change management planning | Post-Session: •Develop Communications Plan and content •Determine process to be reviewed during next session and identify leads and SMEs for each process |
4. Discovery | Remote / Up to 3 Sessions of up to 1 hour each | 1. Deployment Team 2. Sponsor | • In-depth review of current processes and future-state design considerations •Discussion on opportunities for improvement | Post-Session: •Communicate with affected stakeholders |
5. Requirements Review | Remote / Up to 3 Sessions of up to 1 hour each | 1. Deployment Team 2. Sponsor | • Review design plans based on Discovery conversations | Post-Session: •Review final requirements document with affected stakeholders |
6. Process Configuration | Remote / Up to 9 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Identification of desired process refinements •Training and guidance on translating Customer business process into Wrike •Recommendations on Wrike usage proven practice(s) | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete process configuration tasks as defined during session(s) |
7. Workspace Configuration | Remote / Up to 3 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Creation of initial account structure •Recommendations on sharing and visibility | Pre-Session: •Watch required Wrike Discover courses Post-Session: •Complete workspace configuration tasks as defined during session(s) |
8. Configuration Walk-through | Remote / Up to 3 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs | • Validation of end-to-end process via a walkthrough from process initiation to completion | Post-Session: •Address any identified changes prior to team trainings |
9. Dashboards and Reporting | Remote / Up to 1 hour | 1. Deployment Team 2. Process SMEs | • Identification and initial build out of work monitoring needs (dashboards, reports, calendars) | Post-Session: •Continue to build out identified dashboards, reports and calendars |
10. Launch Planning | Remote / Up to 1 hour | 1. Deployment Team | • Discussion to identify potential roadblocks to adoption and usage •Preparation for training sessions | Post-Session: •Develop identified collateral and communications |
11. Training | Remote / Up to 12 Sessions of up to 1 hour each | 1. Deployment Team 2. Process SMEs 3. Other team members as identified by Deployment Team | • Training sessions can focus on account administration, end user capabilities, champions, specific functionality, open office hours, train-the-trainer, Space administrators | Pre-Session: •Watch required Wrike Discover courses in preparation for training •Coordinate attendees to ensure participation During Session: •Deployment Lead or Sponsor to assist in the delivery of agreed upon agenda content |
12. Adoption Monitoring | Remote / Up to 2 Sessions of up to 30 minutes each held weekly starting the week after the Champion Training | 1. Deployment Team 2. Sponsor | • Post training follow-up reviewing usage data and identifying risk areas | Post-Session: •Communicate with affected stakeholders |
13. Executive Briefing | Remote / Up to 1 hour | 1. Deployment Lead 2. Sponsor 3. Executive Sponsor | • Summary of accomplishments and process improvements •Identification of areas for growth •Introduction of Customer Success model | • N/A |
14. Deployment Closeout | Remote / Up to 30 minutes | 1. Deployment Lead 2. Sponsor | • Summary of outcomes and knowledge transfer with Wrike and Customer teams | • N/A |
*NOTE: “Expected Effort” refers to time spent in meetings or workshops between Wrike and Customer teams. It does not account for time spent on preparation or follow-up actions for either team.
4. PROFESSIONAL SERVICES TERMS & CONDITIONSProfessional services terms & conditions can be found here.
For Professional Service Packages purchased prior to November 15, 2022, the terms and conditions for those packages can be found here.