Exhibit C.
Wrike Integrate Professional Services

1. WRIKE INTEGRATE PROFESSIONAL SERVICES

Wrike Integrate is an automation platform whereby the Parties 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 Order Form. The goal of this engagement is for Wrike Professional Services (“Wrike PS”) and Customer’s Implementation Team (defined in Section 1.1) 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”).

To support Wrike’s collaborative Implementation, Wrike expects that Customer’s personnel are identified and made available to collaborate with their Wrike counterparts. Below is a breakdown of the roles and responsibilities of each Party during the Implementation. Please note, the Wrike Attendee will be the Implementation/ Professional Services Consultant(s).

1.1. Customer Personnel

A. Sponsor - The 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.

B. Champion(s) - 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. Part of the Implementation Team.

C. 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. Part of the Implementation Team.

D. 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 the Implementation Team.

E. 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.

1.2. Wrike Personnel

A. Account Manager - The 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.

B. Implementation / Professional Services Consultant — The primary point of contact throughout Wrike Integrate Implementation responsible for ensuring on-time execution of package purchased and communicating changes to scope and timeline.

 

2. INTEGRATE PACKAGES

2.1. Small Implementation Package
A. Summary
Implementation Package Small
Mode of Delivery Remote
Maximum Number of Remote Sessions 8
Maximum Number of Recipes 1
Timeline for delivery Implementation must start within 30 days of Order Form Effective Date and shall expire within 60 days from Order Form Effective Date
B. Scope

The scope of this integration 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.

Steps Expected Effort¹ Activities Involved Customer Attendees² Customer Action Items
1. Kick Off Up to 30 Minutes
  • Define business outcomes
  • Determine dependencies
  • Grant access
  • Discuss Implementation steps
Sponsor, Implementation Lead, SME Post-Call:
  • Review Wrike’s Discover course before the next session
  • Grant Wrike Implementation Consultant access to systems
2. Training Up to 2 Hours
  • Introduction to Wrike Integrate
Implementation Team, SME Post-Call:
  • Customer shall decide on the use case before the next session
3. Use Case Analysis Up to 1 Hour
  • Define requirements and scope
  • Review existing processes and workspace setup
  • Create Functional Requirements Document, which shall include the following information:
    • Step by step Recipe with triggers and Actions
    • Data Mapping Table(optional)
    • Define User Acceptance criteria for User Acceptance Testing ("UAT”)
Champion, Implementation Lead, SME Post-Call:
  • Customer to obtain necessary internal approvals regarding the Functional Requirements Document
  • Customer to provide Wrike Implementation Consultant with written notice (e-mail sufficient) of functional requirements document approval
4. Integration Mapping Up to 1 Hour
  • Verify access and dependencies to Customer’s systems integrating with Wrike
  • Identify triggers, actions & functions in Wrike Integrate
  • Identify authoritative sources of Customer data
SME, Implementation Lead
  • None
5. Integration Configuration Up to 1 Hour
  • Wrike builds the Recipe for the defined use case
  • Wrike to perform unit testing
  • Parties review and fix any issues identified
SME Post-Call:
  • Customer to identify UAT resources (which will be the required attendees for Step 5)
6. Integration Validation Up to 1 Hour
  • Perform UAT
  • Address any identified issues from UAT
SME, Implementation Lead Post-Call:
  • Customer to compile and prioritize issues from UAT within three (3) business days after Step 5
7. Use Case Training Up to 2 Hours
  • 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”)
Implementation Team, SME, Implementation Lead Post-Call:
  • Customer to set launch date
5. Launch and Close Out Up to 1 Hour
  • Address remaining questions
  • Summarize Implementation outcomes and facilitate knowledge transfer with Wrike and Customer’s teams
Champion, Implementation Lead None


¹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.
²Wrike Attendees shall be Implementation Consultant.

C. Out of Scope
  1. 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.2. Medium Implementation Package
A. Summary
Implementation Package Medium
Mode of Delivery Remote
Maximum Number of Remote Sessions 10
Maximum Number of Recipes 2
Timeline for delivery Implementation must start within 30 days of Order Form Effective Date and shall expire within 90 days from Order Form Effective Date
B. Scope

The scope of this integration covers 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 two (2) 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.

Steps Expected Effort¹ Activities Involved Customer Attendees² Customer Action Items
1. Kick Off Up to 30 Minutes
  • Define business outcomes
  • Determine dependencies
  • Grant access
  • Discuss Implementation steps
Sponsor, Implementation Lead, SME Post-Call:
  • Review Wrike Discover course before the next session
  • Grant Wrike Implementation Consultant access to systems
2. Training Up to 2 Hours
  • Introduction to Wrike Integrate
Implementation Team, SME Post-Call:
  • Customer shall decide on the use case before the next session
3. Use Case Analysis Up to 2 Hours
  • Define requirements and scope
  • Review existing processes and workspace setup
  • Create Functional Requirements Document, which shall include the following information:
    • Step by step Recipe with triggers and Actions
    • Data Mapping Table(optional)
    • Define User Acceptance criteria for User Acceptance Testing ("UAT”)
Sponsor, Implementation Lead, SME Post-Call:
  • Customer to obtain necessary internal approvals regarding the Functional Requirements Document
  • Customer to provide Wrike Implementation Consultant with written notice (e-mail sufficient) of functional requirements document approval
4. Integration Mapping Up to 2 Hours
  • Verify access and dependencies to Customer’s systems integrating with Wrike
  • Identify triggers, actions & functions in Wrike Integrate
  • Identify authoritative sources of Customer data
SME, Implementation Lead
  • None
5. Integration Configuration Up to 2 Hours
  • Wrike builds the Recipe for the defined use case
  • Wrike to perform unit testing
  • Parties review and fix any issues identified
SME Post-Call:
  • Customer to identify UAT resources (which will be the required attendees for Step 5)
6. Integration Validation Up to 2 Hours
  • Perform UAT
  • Address any identified issues from UAT
SME, Implementation Lead Post-Call:
  • Customer to compile and prioritize issues from UAT within three (3) business days after Step 5
7. Use Case Training Up to 3 Hours
  • 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”)
Implementation Team, SME, Implementation Lead Post-Call:
  • Customer to set launch date
8. Launch Preparation Up to 1 Hour
  • Address remaining questions
  • Review next steps & objectives
Champion, Implementation Lead Post-Call:
  • Identify resources to support launch.
9. Launch Up to 1 Hour
  • Address remaining questions
Champion, Implementation Lead None
10. Post Launch Review Up to 2 Hours
  • 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
Champion, Implementation Lead None


¹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.
²Wrike Attendees shall be Implementation Consultant.

C. Out of Scope
  1. Building a custom connector (one not listed in the 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 Implementation Package
A. Summary
Implementation Package Large
Mode of Delivery Remote
Maximum Number of Remote Sessions 10
Maximum Number of Recipes Up to 3
Timeline for delivery Implementation must start within 30 days of Order Form Effective Date and shall expire within 120 days from Order Form Effective Date
B. Scope

The scope of this integration covers 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 three (3) 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.

Steps Expected Effort¹ Activities Involved Customer Attendees² Customer Action Items
1. Kick Off Up to 1 Hour
  • Define business outcomes
  • Determine dependencies
  • Grant access
  • Discuss Implementation steps
Sponsor, Implementation Lead, SME Post-Call:
  • Review Wrike Discover course before the next session
  • Grant Wrike Implementation Consultant access to systems
2. Training Up to 2 Hours
  • Introduction to Wrike Integrate
Implementation Team, SME Post-Call:
  • Customer shall decide on the use case before the next session
3. Use Case Analysis Up to 3 Hours
  • Define requirements and scope
  • Review existing processes and workspace setup
  • Create Functional Requirements Document, which shall include the following information:
    • Step by step Recipe with Triggers and Actions
    • Data Mapping Table(optional)
    • Define User Acceptance criteria for User Acceptance Testing("UAT”)
Champion, Implementation Lead, SME Post-Call:
  • Customer to obtain necessary internal approvals regarding the Functional Requirements Document
  • Customer to provide Wrike Implementation Consultant with written notice (e-mail sufficient) of functional requirements document approval
4. Integration Mapping Up to 4 Hours
  • Verify access and dependencies to Customer’s systems integrating with Wrike
  • Identify triggers, actions & functions in Wrike Integrate
  • Identify authoritative sources of Customer data
SME, Implementation Lead
  • None
5. Integration Configuration Up to 3 Hours
  • Wrike builds the Recipe for the defined use case
  • Wrike to perform unit testing
  • Parties review and fix any issues identified
SME Post-Call:
  • Customer to identify UAT resources (which will be the required attendees for Step 5)
6. Integration Validation Up to 3 Hours
  • Perform UAT
  • Address any identified issues from UAT
SME, Implementation Lead Post-Call:
  • Customer to compile and prioritize issues from UAT within three (3) business days after Step 5
7. Use Case Training Up to 5 Hours
  • 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”)
Implementation Lead, Implementation Team, SME Post-Call:
  • Customer to set launch date
8. Launch Preparation Up to 1 Hour
  • Address remaining questions
  • Review next steps & objectives
Champion, Implementation Lead, SME Post-Call:
  • Identify resources to support launch.
9. Launch Up to 1 Hour
  • Address remaining questions
Champion, Implementation Lead, Resources supporting the launch None
10. Post Launch and Close Out Up to 2 Hours
  • 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
Champion, Implementation Lead None


¹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.
²Wrike Attendees shall be Implementation Consultant.

C. Out of Scope
  1. Building a custom connector (one not listed in the 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.4. Small Integration Without Training Package
A. Summary
Implementation Package Small
Mode of Delivery Remote
Maximum Number of Remote Sessions 6
Maximum Number of Recipes 1
Number of Training Sessions 0
Timeline for delivery Implementation must start within 30 days of Order Form Effective Date and shall expire within 60 days from Order Form Effective Date
B. Scope

The scope of this integration covers leveraging 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. Both Parties acknowledge and agree that Customer has not purchased any training in this package.
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.

Steps Expected Effort¹ Activities Involved Customer Attendees² Customer Action Items
1. Kick Off Up to 30 Minutes
  • Define business outcomes
  • Determine dependencies
  • Grant access
  • Discuss Implementation steps
Sponsor, Implementation Lead, SME Post-Call:
  • Review Wrike Discover course before the next session
  • Grant Wrike Implementation Consultant access to systems
  • Customer shall decide on the use case before the next session
2. Use Case Analysis Up to 1 Hour
  • Define requirements and scope
  • Review existing processes and workspace setup
  • Create Functional Requirements Document, which shall include the following information:
    • Step by step Recipe with Triggers and Actions
    • Data Mapping Table(optional)
    • Define User Acceptance criteria for User Acceptance Testing("UAT”)
Champion, Implementation Lead, SME Post-Call:
  • Customer to obtain necessary internal approvals regarding the Functional Requirements Document
  • Customer to provide Wrike Implementation Consultant with written notice (e-mail sufficient) of functional requirements document approval
3. Integration Mapping Up to 1 Hour
  • Verify access and dependencies to Customer’s systems integrating with Wrike
  • Identify triggers, actions & functions in Wrike Integrate
  • Identify authoritative sources of Customer data
SME, Implementation Lead
  • None
4. Integration Configuration Up to 1 Hour
  • Wrike builds the Recipe for the defined use case
  • Wrike to perform unit testing
  • Parties review and fix any issues identified
SME Post-Call:
  • Customer to identify UAT resources (which will be the required attendees for Step 5)
5. Integration Validation Up to 1 Hour
  • Perform UAT
  • Address any identified issues from UAT
SME, Implementation Lead Post-Call:
  • Customer to compile and prioritize issues from UAT within three (3) business days after Step 5
  • Customer to set launch date
6. Launch and Close Out Up to 1 Hour
  • Address remaining questions
  • Summarize Implementation outcomes and facilitate knowledge transfer with Wrike and Customer’s teams
Champion, Implementation Lead None


¹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.
²Wrike Attendees shall be Implementation Consultant.

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

 

2.5. Wrike Integrate Training Only Package
A. Summary
Training Package Training Only
Mode of Delivery Remote
Maximum Number of Remote Sessions 3
Timeline for delivery Implementation must start within 30 days of Order Form Effective Date and shall expire within 60 days from Order Form Effective Date
B. Scope

Wrike PS will partner with Customer’s identified Implementation Team for basic training on Wrike Integrate functionality.

Steps Expected Effort¹ Activities Involved Customer Attendees²
1. Kick Off Up to 30 Minutes
  • Review the training plan
  • Ensure Customer can login to
    • Wrike
    • Wrike Integrate
Business Process Owners or SMEs, Implementation Team
2. Training 101 Up to 2 Hours (remote)
  • Wrike Integrate Platform Concepts and Capabilities training
  • Step-by-Step walkthrough of automation recipes
  • Wrike Integrate best practices
  • Hands-on working session
SME, Implementation Team
3. Training 201 Up to 2 Hours (remote) Understanding:
  • HTTP REST APIs
  • File processing
  • Databases
  • Wrike Integrate Enterprise Features
  • How to formulate a recipe
  • Working Session
SME, Implementation Team


¹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.
²Wrike Attendees shall be Implementation Consultant.

C. Out of Scope
  1. Building or coding Recipes or connectors;
  2. Additional sessions, 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.).

 

3. PROFESSIONAL SERVICES TERMS & CONDITIONS

This Professional Services Terms of Service (“PSTC”) is hereby incorporated and part of the Wrike Terms and Conditions and sets forth the additional terms and conditions under which Wrike will provide Professional Services pursuant to the applicable Order Form. Terms used herein without definition shall have meanings ascribed to such terms in the Wrike Terms and Conditions.

3.1. Performance of Professional Services
  1. Order of Interpretation. If there is a conflict between the terms set forth in the Wrike Terms and Conditions and those set forth herein, the terms set forth herein will control for Professional Services only.
  2. Delivery and Cooperation. Customer acknowledges that Customer’s cooperation is essential to the timely performance of Wrike’s services. Customer will, to the extent required in connection with the performance of Wrike’s Professional Services: (i) provide Wrike with any necessary Customer materials; (ii) provide Wrike with any necessary access to Customer’s personnel, facilities or data; (iii) cause the appropriate personnel to cooperate with Wrike as required for Wrike to provide Wrike’s services, including subject matter experts and decision makers that can provide timely critical project decisions; and (iv) make all payments when due. Customer’s delay or failure to do so may delay the estimated delivery of Service(s). If Customer fails to do any of the foregoing, both Parties will cooperate in good faith to draft a change order signed by both Parties with new pricing.
  3. Place of Performance. Unless agreed to between the Parties and indicated in the applicable Order Form, all Professional Services are to be provided remotely. When Professional Services will be provided on-site at Customer’s facilities, such on-site day(s) will be scheduled in advance by the Parties. On-site days will be consecutive within each trip and each day will be limited to regular eight-hour workdays (partial days are not permitted). Customer’s office resources, such as facility and internet access, will be made accessible to Wrike. Both Parties will use reasonable efforts to accommodate any requested change in the scheduled dates for on-site services, subject to the availability of appropriate personnel.
  4. Qualified Personnel. Wrike will provide all Professional Services in accordance with Wrike’s industry standards and practices using qualified personnel with the necessary skills, qualifications and experience to provide the Professional Services. Wrike will not allocate personnel prior to the signing of the applicable Order Form. Staffing decisions will be based on availability of Wrike personnel at the time of signature. Personnel providing Professional Services will be Wrike’s employees acting within the scope of their employment or will be Wrike subcontractors (see Section 4 below).
3.2. Payment Terms
  1. Fees. Customer will pay Wrike for all undisputed Professional Services provided in accordance with the Payment Terms in the applicable Order Form. Professional Services are billed upfront as a fixed fee.
  2. Expenses. If applicable, Customer agrees to remit payment to Wrike for such travel, lodging, and applicable out of pocket expenses reasonably incurred by Wrike in support of on-site Professional Services. Expenses shall be incurred in accordance with Wrike’s then-current corporate travel policies, unless reasonable Customer on-site guidelines have been agreed to and incorporated into the applicable Order Form, and will be billed at-cost with no mark-up in addition to the Professional Services Fees. At Customer’s request, Wrike will provide receipts or other reasonably satisfactory evidence of such expenses.
3.3. Changes to Professional Service(s) Scope

Any scope changes shall be documented in writing in a Change Order signed by both Parties. Wrike shall be responsible for drafting the Change Order and providing to Customer for review.

3.4. Subcontractors

A Subcontractor is a person, or an entity who may provide services or personnel to Wrike, with whom Wrike has contracted to provide some component of the Professional Services. The Parties agree Wrike shall have the right to utilize Subcontractors to fulfill its Professional Service obligations. Subcontractors shall be subject to the same material obligations and requirements of Wrike, as set forth in the Wrike Terms and Conditions, and except as may be specifically agreed to in writing by the Parties, Wrike shall remain fully liable for the acts or omissions of its Subcontractors. Wrike shall have sole discretion as to whether to use Subcontractors, subject to Wrike providing notice to Customer of any Subcontractor who, in the course of providing the subcontracted Services, will have access to any personally identifiable Customer Data.

 

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

Last update: February, 2020. Wrike, Inc.