Exhibit C.
Wrike Integrate Professional Services

1. WRIKE INTEGRATE PROFESSIONAL SERVICES

Wrike Integrate is an automation platform whereby Customer and Wrike can create customized integrations between the Wrike platform and Customer’s cloud or on-premise applications.

The package descriptions outlined below address the steps related to the delivery and implementation of the Wrike Integrate Implementation package purchased in the applicable Order Form between Wrike and Customer. The goal of this engagement is for Wrike Professional Services (“Wrike PS”) and Customer’s Implementation Team (defined below) to identify Customer’s business requirements, build and deliver an integration that meets such requirements, and train Customer’s Implementation Team on how to utilize and maintain the integration (the “Implementation”).

2. IMPLEMENTATION ROLES

To support Wrike’s collaborative Implementation, Wrike expects that Customer’s personnel are identified and made available to collaborate with their Wrike counterparts throughout the Implementation. Below is a breakdown of the key roles and responsibilities of each Party during the Implementation.

  1. Customer Personnel
    1. Implementation Lead(s): Customer’s project leader and primary point of contact for communications with the Wrike Implementation Consultant, coordination and facilitation of Customer personnel, calls, meetings, and sign off on outcomes.
    2. Sponsor: Person(s) with authority to clarify why this project is being initiated, who is expected to participate, and the highest applicable chain in command to ensure all escalations are handled. Additionally, the Sponsor may be called upon to enforce Wrike usage internally.
    3. Champion: Key representative(s) from each user group with a broad view of the group’s objectives and acting as an internal driver of adoption and change.
    4. Subject Matter Experts (SMEs): Customer’s representatives who the Wrike team can consult to understand the system with which Wrike will be integrated and understand relevant processes at a detailed level. SMEs are not part of Customer’s Implementation Team.
    5. Implementation Team: Customer’s team participating in the Implementation of Wrike Integrate. Team members include the Champion(s), Implementation Lead(s), and any additional internal Users of Customer. The team may be comprised of both technical and non-technical personnel.
  2. Wrike Personnel
    1. Account Manager: A designated contact responsible for the business relationship between Wrike and Customer for the lifetime of Customer’s relationship with Wrike. All contractual and licensing questions will be addressed and resolved by the Account Manager.
    2. Implementation / Professional Services Consultant: The primary designated point of contact throughout Wrike Integrate Implementation responsible for ensuring on-time execution of package purchased and communicating changes to scope and timeline. The Wrike Attendee for the activities in each applicable package will be the Wrike Implementation/ Professional Services Consultant(s).

 

3. INTEGRATE PACKAGES

A. Small Integrate

If purchased, the Small Integrate Package includes:

 

Small Integrate Package
Mode of Delivery Remote
Maximum Number of Remote Sessions 8 (Eight)
Maximum Number of Recipes 1 (One)
Timeline for delivery Kickoff must start within 70 (seventy) days of Customer’s purchase if purchased at the same time as the main deployment in Exhibit B or separate Statement of Work (otherwise shall be started within thirty (30) days of purchase); Implementation activities will expire 60 (sixty) days later

 

    1. In Scope: The scope the Small Integrate Package leverages a pre-built connector from the Integrate App Directory to integrate between Wrike and Customer’s cloud or on-premise applications. Wrike PS will design and develop up to one (1) Recipe for this integration using triggers and actions. For purposes of clarity, a “Recipe” is an automated workflow that connects apps to complete tasks composed by Customer based on a combination of apps, triggers and actions.
Small Integrate Package
Steps Expected Effort* Customer Attendees Activities Involved Customer Action Items
1. Kick Off Up to 30 Minutes 1. Sponsor
2. Implementation Lead
3. SME
  • Define business outcomes
  • Determine dependencies
  • Grant access
  • Discuss Implementation steps
Post-Call:
  • Review Wrike’s Discover course before the next session
  • Grant Wrike Implementation Consultant access to systems
2. Training Up to 2 Hours 1. Implementation Team
2. SME
  • Introduction to Wrike Integrate
Post-Call:
  • Decide on the use case before the next session
3. Use Case Analysis Up to 1 Hour 1. Champion
2.Implementation Lead
3. SME
  • Define requirements and scope
  • Review existing processes and workspace setup
  • Create Functional Requirements Document, which shall include the following information:
    1. Step by step Recipe with triggers and Actions
    2. Data Mapping Table(optional)
    3. Define User Acceptance criteria for User Acceptance Testing ("UAT”)
Post-Call:
  • Obtain necessary internal approvals regarding the Functional Requirements Document
  • Provide Wrike Implementation Consultant with written notice (e-mail sufficient) of functional requirements document approval
4. Integration Mapping Up to 1 Hour 1. SME
2. Implementation Lead
  • Verify access and dependencies to Customer’s systems integrating with Wrike
  • Identify triggers, actions & functions in Wrike Integrate
  • Identify authoritative sources of Customer data
  • N/A
5. Integration Configuration Up to 1 Hour 1. SME
  • Wrike builds the Recipe for the defined use case
  • Wrike to perform unit testing
  • Parties review and fix any issues identified
Post-Call:
  • Customer to identify UAT resources (which will be the required attendees for Step 5)
6. Integration Validation Up to 1 Hour 1. SME
2. Implementation Lead
  • Perform UAT
  • Address any identified issues from UAT
Post-Call:
  • Compile and prioritize issues from UAT within three (3) business days after Step 5
7. Use Case Training Up to 2 Hours 1. Implementation Team
2. SME
3. Implementation Lead
  • Train on end-to-end integration process
  • Train on Use Case and relevant functions
  • Train on how to manage/maintain the Recipe(s) (“Integration Life Cycle Enablement”)
Post-Call:
  • Set launch date
8. Launch and Close Out Up to 1 Hour 1. Champion
2. Implementation Lead
  • Address remaining questions
  • Summarize Implementation outcomes and facilitate knowledge transfer with Wrike and Customer’s 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 Party.

  • Out of Scope:

 

  1. Building a custom connector (one not listed in the Wrike Integrate App Directory) or custom coding;
  2. Additional / incremental work, including modifications or additions to Recipe(s), tasks, triggers, post-launch; and
  3. Non-Wrike related bug fixes (including issues caused by third-party application updates, system changes or upgrades, etc.).

 

B. Medium Integrate Package

If purchased, the Medium Integrate Package includes:

Medium Integrate Package
Mode of Delivery Remote
Maximum Number of Remote Sessions 10 (Ten)
Maximum Number of Recipes 2 (Two)
Timeline for delivery Kickoff must start within 70 (seventy) days of Customer’s purchase if purchased at the same time as the main deployment in Exhibit B or separate Statement of Work (otherwise shall be started within thirty (30) days of purchase); Implementation activities will expire 90 (ninety) days later

 

    1. In Scope: The scope the Small Integrate Package leverages a pre-built connector from the Integrate App Directory to integrate between Wrike and Customer’s cloud or on-premise applications. Wrike PS will design and develop up to one (1) Recipe for this integration using triggers and actions. For purposes of clarity, a “Recipe” is an automated workflow that connects apps to complete tasks composed by Customer based on a combination of apps, triggers and actions.
Medium Integrate Package
Steps Expected Effort* Customer Attendees Activities Involved Customer Action Items
1. Kick Off Up to 30 Minutes 1. Sponsor
2. Implementation Lead
3. SME
  • Define business outcomes
  • Determine dependencies
  • Grant access
  • Discuss Implementation steps
Post-Call:
  • Review Wrike Discover course before the next session
  • Grant Wrike Implementation Consultant access to systems
2. Training Up to 2 Hours 1. Implementation Team
2. SME
  • Introduction to Wrike Integrate
Post-Call:
  • Decide on the use case before the next session
3. Use Case Analysis Up to 2 Hours 1. Sponsor
2. Implementation Lead
3. SME
  • Define requirements and scope
  • Review existing processes and workspace setup
  • Create Functional Requirements Document, which shall include the following information:
    1. Step by step Recipe with triggers and Actions
    2. Data Mapping Table(optional)
    3. Define User Acceptance criteria for User Acceptance Testing ("UAT”)
Post-Call:
  • Obtain necessary internal approvals regarding the Functional Requirements Document
  • Provide Wrike Implementation Consultant with written notice (e-mail sufficient) of functional requirements document approval
4. Integration Mapping Up to 2 Hours 1. SME
2. Implementation Lead
  • Verify access and dependencies to Customer’s systems integrating with Wrike
  • Identify triggers, actions & functions in Wrike Integrate
  • Identify authoritative sources of Customer data
  • N/A
5. Integration Configuration Up to 2 Hours 1. SME
  • Wrike builds the Recipe for the defined use case
  • Wrike to perform unit testing
  • Parties review and fix any issues identified
Post-Call:
  • Identify UAT resources (which will be the required attendees for Step 5)
6. Integration Validation Up to 2 Hours 1. SME
2. Implementation Lead
  • Perform UAT
  • Address any identified issues from UAT
Post-Call:
  • Compile and prioritize issues from UAT within three (3) business days after Step 5
7. Use Case Training Up to 3 Hours 1. Implementation Team
2. SME
3. Implementation Lead
  • Train on end-to-end integration process
  • Train on Use Case and relevant functions
  • Train on how to manage/maintain the Recipe(s) (“Integration Life Cycle Enablement”)
Post-Call:
  • Set launch date
8. Launch Preparation Up to 1 Hour 1. Champion
2. Implementation Lead
  • Address remaining questions
  • Review next steps & objectives
Post-Call:
  • Identify resources to support launch.
9. Launch Up to 1 Hour 1. Champion
2. Implementation Lead
  • Address remaining questions
N/A
10. Post Launch Review Up to 2 Hours 1. Champion
2. Implementation Lead
  • Discuss additional integration needs
  • Adjust roadmap and plan next steps (together with Account Team)
  • Summarize Implementation outcomes and facilitate knowledge transfer with Wrike and Customer’s teams
  • Hand off to Customer Success Team
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 Party.

  • Out of Scope:

 

  1. Building a custom connector (one not listed in the Wrike Integrate App Directory) or custom coding;
  2. Additional / incremental work, including modifications or additions to Recipe(s), tasks, triggers, post-launch; and
  3. Non-Wrike related bug fixes (including issues caused by third-party application updates, system changes or upgrades, etc.).

 

2.3. Large Integrate Package

If purchased, the Large Integrate Package includes:

Large Integrate Package
Mode of Delivery Remote
Maximum Number of Remote Sessions 10 (Ten)
Maximum Number of Recipes Up to 3 (Three)
Timeline for delivery Kickoff must start within 70 (seventy) days of Customer’s purchase if purchased at the same time as the main deployment in Exhibit B or separate Statement of Work (otherwise shall be started within thirty (30) days of purchase); Implementation activities will expire 120 (one hundred twenty) days later

 

    1. In Scope: The scope of the Large Integrate Package leverages a pre-built connector from the Integrate App Directory to integrate between Wrike and Customer’s cloud or on-premise applications. Wrike PS will design and develop up to 3 (three) Recipes for this integration using triggers and actions. For purposes of clarity, a “Recipe” is an automated workflow that connects apps to complete tasks composed by Customer based on a combination of apps, triggers and actions.
Large Integrate Package
Steps Expected Effort* Customer Attendees Activities Involved Customer Action Items
1. Kick Off Up to 1 Hour 1. Sponsor
2. Implementation Lead
3. SME
  • Define business outcomes
  • Determine dependencies
  • Grant access
  • Discuss Implementation steps
Post-Call:
  • Review Wrike Discover course before the next session
  • Grant Wrike Implementation Consultant access to systems
2. Training Up to 2 Hours 1. Implementation Team
2. SME
  • Introduction to Wrike Integrate
Post-Call:
  • Decide on the use case before the next session
3. Use Case Analysis Up to 3 Hours 1. Champion
2. Implementation Lead
3. SME
  • Define requirements and scope
  • Review existing processes and workspace setup
  • Create Functional Requirements Document, which shall include the following information:
    1. Step by step Recipe with Triggers and Actions
    2. Data Mapping Table(optional)
    3. Define User Acceptance criteria for User Acceptance Testing("UAT”)
Post-Call:
  • Obtain necessary internal approvals regarding the Functional Requirements Document
  • Provide Wrike Implementation Consultant with written notice (e-mail sufficient) of functional requirements document approval
4. Integration Mapping Up to 4 Hours 1. SME
2. Implementation Lead
  • Verify access and dependencies to Customer’s systems integrating with Wrike
  • Identify triggers, actions & functions in Wrike Integrate
  • Identify authoritative sources of Customer data
  • N/A
5. Integration Configuration Up to 3 Hours 1. SME
  • Wrike builds the Recipe for the defined use case
  • Wrike to perform unit testing
  • Parties review and fix any issues identified
Post-Call:
  • Customer to identify UAT resources (which will be the required attendees for Step 5)
6. Integration Validation Up to 3 Hours 1. SME
2. Implementation Lead
  • Perform UAT
  • Address any identified issues from UAT
Post-Call:
  • Compile and prioritize issues from UAT within three (3) business days after Step 5
7. Use Case Training Up to 5 Hours 1. Implementation Lead
2. Implementation Team
3. SME
  • Train on end-to-end integration process
  • Train on Use Case and relevant functions
  • Train on how to manage/maintain the Recipe(s) (“Integration Life Cycle Enablement”)
Post-Call:
  • Set launch date
8. Launch Preparation Up to 1 Hour 1. Champion
2. Implementation Lead
3. SME
  • Address remaining questions
  • Review next steps & objectives
Post-Call:
  • Identify resources to support launch.
9. Launch Up to 1 Hour 1. Champion
2. Implementation Lead
3. Resources supporting the launch
  • Address remaining questions
N/A
10. Post Launch and Close Out Up to 2 Hours 1. Champion
2. Implementation Lead
  • Discuss additional integration needs
  • Adjust roadmap and plan next steps (together with Account Team)
  • Summarize Implementation outcomes and facilitate knowledge transfer with Wrike and Customer’s teams
  • Hand off to Customer Success Team
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 Party.

  • Out of Scope:

 

  1. Building a custom connector (one not listed in the Wrike Integrate App Directory) or custom coding;
  2. Additional / incremental work, including modifications or additions to Recipe(s), tasks, triggers, post-launch; and
  3. Non-Wrike related bug fixes (including issues caused by third-party application updates, system changes or upgrades, etc.).
D. Wrike Integrate Training-Only Package

If purchased, Wrike Integrate Training-Only Package includes:

Wrike Integrate Training-Only Package
Mode of Delivery Remote
Maximum Number of Remote Sessions 3 (Three)
Timeline for delivery Kickoff must start within 70 (seventy) days of Customer’s purchase if purchased at the same time as the main deployment in Exhibit B</> or separate Statement of Work (otherwise shall be started within thirty (30) days of purchase); Implementation activities will expire 60 (sixty) days later

 

    1. In Scope: Wrike PS will partner with Customer’s identified Implementation Team for basic training on Wrike Integrate functionality.
Wrike Integrate Training-Only Package
Steps Expected Effort* Customer Attendees Activities Involved
1. Kick Off Up to 30 Minutes 1. SMEs
2. Implementation Team
3. Business Process Owners
  • Review the training plan
  • Ensure Customer can login to Wrike and Wrike Integrate
2. Training 101 Up to 2 Hours (remote) 1. SME
2. Implementation Team
  • Wrike Integrate Platform Concepts and Capabilities training
  • Step-by-Step walkthrough of automation recipes
  • Wrike Integrate best practices
  • Hands-on working session
3. Training 201 Up to 2 Hours (remote) 1. SME
2.Implementation Team
  • Understanding:
    • HTTP REST APIs
    • File processing
    • Databases
    • Wrike Integrate Enterprise Features
    • How to formulate a recipe
  • Working 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 Party.

  • Out of Scope:

 

  1. Building or coding Recipes or connectors;
  2. Additional / incremental work, including modifications or additions to Recipe(s), tasks, triggers created by Customer; and
  3. Non-Wrike related bug fixes (including issues caused by third-party application updates, system changes or upgrades, etc.).

 

4. PROFESSIONAL SERVICES TERMS & CONDITIONS

Professional services terms & conditions can be found here.

For Professional Service Packages purchased prior to July 1, 2021, the terms and conditions can be found here.

For Professional Service Packages purchased prior to February 15, 2020, the terms and conditions can be found here.

Last update: July 1, 2021.