Exhibit C
Statement of Work

Last update: February, 2019. Wrike, Inc.

1. Executive Summary

This documentation outlines how Wrike Professional Services (“Wrike PS”) will initiate services as it pertains to the PS package outlined in the applicable signed Order Form between Wrike and Customer identified on said Order Form (“Customer”). For purposes of clarity, this document outlines the details of the various packages outlined with Wrike Integrate only—there are three options.

1.1 Option 1: Wrike Integrate Single Connection No Training

Configuration of Wrike Integrate with one other solution using one of the standard out of the box Wrike Integrate connectors . This does not include training of Customer users and Wrike strongly urges Customer to purchase training or additional Services in the near future to ensure an optimal deployment of Wrike Integrate as well as allow Customer to further automate and innovate within in their organisation.

1.2 Option 2: Wrike Integrate Small, Medium and Large Package

Configuration of Wrike Integrate with particular attention to use case(s) or recipe(s) based on Customers need  and concurrently onboard Customer Wrike champions. Wrike PS will run a training session focused on the basic underlying functionality of Wrike Integrate as well as training related to the specific use-case(s).

1.3 Option 3: Wrike Integrate Training Only

Wrike PS will run a training session focused on the basic underlying functionality of Wrike Integrate with specific individuals within Customer organisation with a view to equipping them with the skills to successfully use Wrike Integrate and configure basic Wrike Integrate Connectors. It is assumed that there is an existing level of Wrike administration competence within the targeted training individual(s) and that they also possess subject matter expertise of the system with which Wrike is to be integrated.

There are two extra options that can be purchased with the Training, the first being to have the training performed on site at Customer location and the second is to have an additional 5 hours of remote support.

2. Scope of Work

2.1 Option 1: Wrike Integrate Single Connection No Training

Wrike will partner with Customer’s identified deployment team to identify and configure the one Wrike Integrate use-case.

The scope includes

  • Configuring one Wrike Integrate Recipe with one other solution using one of the standard out of the box Wrike Integrate connectors.
  • Two hours of post integration support which can be used for adjustments to the integration, fixing recipe bugs ****

The scope does not include

  • Training on Wrike Integrate
  • Training on Wrike or Wrike API
2.1.2 Work Packages

During this Wrike Integrate engagement there are 8 steps which Wrike PS will manage jointly with Customer Deployment Lead.

The Integration will be between Wrike and one other system using native Wrike Integrate Connectors and no custom coding or custom connectors. Wrike PS will design and create up to two recipes for that integration

In order to achieve a successful deployment we will be following the steps outlined below. Customer resources must be made available as advised by the Wrike PS team.

Steps Expected Effort Activities Involved
1. Kickoff Up to 1 hour (remote)
  • Define Business Outcomes
  • Determine dependencies
  • Grant needed Access
  • Define requirements and scope
2. Use Case analysis Up to 1 hours (remote)
  • Review existing processes and workspace setup
  • Verify access and dependencies
  • Create Functional Requirements Document
  • Define Test Cases
3. Integration Mapping Up to 1 hour (remote)
  • Create the Technical Specification Document
  • Identify Triggers, Actions & Functions
  • Identify authoritative sources of data
  • Identify authorizations
4. Integration Configuration Up to 1 hours (remote)
  • Build the Recipe for the defined use case
  • Perform ongoing testing
  • Review and fix any issues client and agree on changes to requirements if needed
5. Integration Validation Up to 1 hours (remote)
  • Verify automation is setup per client requirements
  • Perform User Acceptance Testing (UAT)
  • Address any identified issues from UAT
6. Post Launch Support Up to 2 hours (remote)
  • Identify adjustments needed to process
  • Discuss additional integration needs
  • Product questions
  • Help with use case specific issues
  • Help with usability
  • Wrike API specific questions
  • Up to 2 x 1 hour sessions (Remote)

Note: Should Customer require onsite presence, Wrike PS will perform steps 3, 4, 5 onsite at Customer Location, spanning a total of maximum 1 calendar day. Customer will be required to pay for Travel and Expenses as outlined in Section 5.3.

2.2 Option 2: Wrike Integrate Small, Medium and Large Package

Wrike’s Professional Services engagement utilizes a coaching model to deploy your teams. Wrike will partner with Customer’s identified deployment team to identify and configure the relevant Wrike Integrate use-case(s). Through participation during the engagement, members of Customer’s team will become the internal Wrike Integrate users so Customer has the skills to support long-term success as their organization grows, changes and expands.

Each of these Wrike Integrate packages consist of 8 steps which Wrike PS will manage jointly with Customer Deployment Lead.

In order to achieve a successful deployment we will be following the steps outlined below. Customer resources must be made available as advised by the Wrike PS team.

2.2.1 Wrike Integrate Small Package – Work Packages

The Integration will be between Wrike and one other system using native Wrike Integrate Connectors and no custom coding or custom connectors. Wrike PS will design and create up to two recipes for that integration

Steps Expected Effort Activities Involved
1. Training & Kickoff Up to 3 hours (remote)
  • Wrike Integrate Training 101
  • Define Business Outcomes
  • Determine dependencies
  • Grant Access
  • Define requirements and scope
2. Use Case analysis Up to 1 hours (remote)
  • Review existing processes and workspace setup
  • Verify access and dependencies
  • Create Functional Requirements Document
  • Define Test Cases
3. Integration Mapping Up to 1 hours (remote)
  • Create the Technical Specification Document
  • Identify Triggers, Actions & Functions
  • Identify authoritative sources of data
  • Identify authorizations
4. Integration Configuration Up to 1 hours (remote)
  • Build the Recipe for the defined use case
  • Perform ongoing testing
  • Review and fix any issues client and agree on changes to requirements if needed
5. Integration Validation Up to 1 hours (remote)
  • Verify automation is setup per client requirements
  • Perform User Acceptance Testing (UAT)
  • Address any identified issues from UAT
6. Use Case Training Up to 2 hours (remote)
  • Train on end-to-end integration process
  • Train on Use Case and relevant functions
  • Integration Life Cycle Enablement
7. Launch Preparation Up to 1 hours (remote)
  • Address lingering questions
  • Review next steps & objectives
  • Note: Only for Advanced and Enterprise packages
8. Post Launch Review Up to 1 hours (remote)
  • Identify adjustments needed to process
  • Discuss additional integration needs
  • Adjust roadmap and plan next steps (together with Account Team)

Note: Should Customer require onsite presence, Wrike PS will perform steps 4, 5, 6 onsite at Customer Location, spanning a total of approx 1.5 consecutive days. Customer will be required to pay for Travel and Expenses as outlined in Section 5.3.

2.2.2 Wrike Integrate Medium Package – Work Packages

The Integration will be between Wrike and one other system using native Wrike Integrate Connectors and no custom coding or custom connectors. Wrike PS will design and create up to two recipes for that integration.

Steps Expected Effort Activities Involved
1. Training & Kickoff Up to 3 hours (remote)
  • Wrike Integrate Training 101
  • Define Business Outcomes
  • Determine dependencies
  • Grant Access
  • Define requirements and scope
2. Use Case analysis Up to 2 hours (remote)
  • Review existing processes and workspace setup
  • Verify access and dependencies
  • Create Functional Requirements Document
  • Define Test Cases
3. Integration Mapping Up to 2 hours (remote)
  • Create the Technical Specification Document
  • Identify Triggers, Actions & Functions
  • Identify authoritative sources of data
  • Identify authorizations
4. Integration Configuration Up to 2 hours (remote)
  • Build the Recipe for the defined use case
  • Perform ongoing testing
  • Review and fix any issues client and agree on changes to requirements if needed
5. Integration Validation Up to 2 hours (remote)
  • Verify automation is setup per client requirements
  • Perform User Acceptance Testing (UAT)
  • Address any identified issues from UAT
6. Use Case Training Up to 3 hours (remote)
  • Train on end-to-end integration process
  • Train on Use Case and relevant functions
  • Integration Life Cycle Enablement
7. Launch Preparation Up to 1 hours (remote)
  • Address lingering questions
  • Review next steps & objectives
  • Note: Only for Advanced and Enterprise packages
8. Post Launch Review Up to 2 hours (remote)
  • Identify adjustments needed to process
  • Discuss additional integration needs
  • Adjust roadmap and plan next steps (together with Account Team)

Note: Should Customer require onsite presence, Wrike PS will perform steps 4, 5, 6 onsite at Customer Location, spanning a total of approx 1.5 consecutive days. Customer will be required to pay for Travel and Expenses as outlined in Section 5.3.

2.2.3 Wrike Integrate Large Package – Work Packages

The Integration will be between Wrike and up to 5 other system using native Wrike Integrate Connectors and no custom coding or custom connectors. Wrike PS will design create up to three recipes for each integration

Steps Expected EffortMedium Package1 Activities Involved
1. Training & Kickoff Up to 3 hours (remote)
  • Wrike Integrate Training 101
  • Define Business Outcomes
  • Determine dependencies
  • Grant Access
  • Define requirements and scope
2. Use Case analysis Up to 3 hours (remote)
  • Review existing processes and workspace setup
  • Verify access and dependencies
  • Create Functional Requirements Document
  • Define Test Cases
3. Integration Mapping Up to 4 hours (remote)
  • Create the Technical Specification Document
  • Identify Triggers, Actions & Functions
  • Identify authoritative sources of data
  • Identify authorizations
4. Integration Configuration Up to 3 hours (remote)
  • Build the Recipe for the defined use case
  • Perform ongoing testing
  • Review and fix any issues client and agree on changes to requirements if needed
5. Integration Validation Up to 3 hours (remote)
  • Verify automation is setup per client requirements
  • Perform User Acceptance Testing (UAT)
  • Address any identified issues from UAT
6. Use Case Training Up to 5 hours (remote)
  • Train on end-to-end integration process
  • Train on Use Case and relevant functions
  • Integration Life Cycle Enablement
7. Launch Preparation Up to 1 hours (remote)
  • Address lingering questions
  • Review next steps & objectives
  • Note: Only for Advanced and Enterprise packages
8. Post Launch Review Up to 2 hours (remote)
  • Identify adjustments needed to process
  • Discuss additional integration needs
  • Adjust roadmap and plan next steps (together with Account Team)

Note: Should Customer require onsite presence, Wrike PS will perform steps 4, 5, 6 onsite at Customer Location, spanning a total of approx 1.5 consecutive days. Customer will be required to pay for Travel and Expenses as outlined in Section 5.3.

2.3 Option 3: Wrike Integrate Training Only

Wrike’s Professional Services engagement utilizes a coaching model to deploy your teams. Wrike will partner with Customer’s identified team and train them on the relevant Wrike Integrate functionality. Members of Customer’s team will become the internal Wrike Integrate users so Customer has the skills to support long-term success as their organization grows, changes and expands.

2.3.1 Work Packages

During this “Wrike Integrate Training Only Package” engagement there are 5 steps which Wrike PS will manage jointly with Customer Deployment Lead.

The training focuses on the basic functionality and a pre prepared Wrike Integrate scenario, and not on any specific scenario of Customer in Question.

In order to achieve a successful deployment we will be following the steps outlined below. Customer resources must be made available as advised by the Wrike PS team.

Steps Expected Effort Activities Involved
1. Audience & Preparation

 Communication and material sharing only
  • Business Process Owners or SMEs
  • IT Staff
  • Required skills:
    • Understanding APIs,
    • Data Types and modelling
    • Conceptual understanding of data processing
2. Pre-Training Check Communication and material sharing only
  • Pre Training Materials Reviewed / Completed.
  • Create Slack account
  • Create Salesforce Developer account
  • Ensure customer can login to
    • Wrike
    • Wrike Integrate
3. Training Objective Part 1 Up to 3 hours (remote)
  • Understand Wrike Integrate Platform Concepts and Capabilities
  • Step-by-Step Walkthrough of automation recipes
  • Wrike Integrate Best Practices
  • Working Session
4. Training Objective Part 2 Up to 3 hours (remote)
  • Understanding:
    • HTTP REST APIs
    • File processing
    • Databases
  • Wrike Integrate Enterprise Features
  • How to formulate a recipe
  • Working Session
5. Post Training Q&A Session Up to 1 hour (remote)
  • Product questions
  • Help with use case specific issues
  • Help with usability
  • Wrike API specific questions
6. Optional: 5 Hours extra Services Support1 Up to 3 hours (remote)
  • As per Step 5. Post Training Q&A Session”
  • 5 additional sessions of up to 1 hour each
  • All sessions remotely delivered

Note: Should Customer require onsite presence, Wrike PS will perform steps 3, 4, onsite at Customer Location, on a single day. Customer will be required to pay for Travel and Expenses as outlined in Section 5.3.

3. Governance

3.1 Roles and Responsibilities

Specifically for the Wrike Integrate Training Only package, Wrike PS are present to ensure your team is successfully onboarded with sufficient skills to use the basic functionality and out of the box integrations of Wrike Integrate, assuming Customer has the relevant skills for both Wrike Integrate and the targeted system{s).

For all other Wrike Integrate packages, Wrike PS are present to ensure your team is successfully onboarded sufficiently to use Wrike Integrate for the specific focus on the identified Integration use cases.

To support Wrike’s collaborative deployment process, we expect that Customer’s personnel are identified and made available to collaborate with their Wrike counterparts as needed. Below is a breakdown of the key roles and responsibilities during the scoping and deployment process.

3.1.1 Wrike Role Descriptions
  • Deployment Consultant - Is the primary point of contact throughout Deployment. Responsible for ensuring on-time execution of SOW deliverables and communicating changes to scope and timeline.

  • Account Manager - Is 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.

3.1.2 Customer Role Descriptions
  • Sponsor - The person(s) with authority to clarify  why this project is being executed, 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 initially.

  • Deployment Lead - Customer’s project leader and point of contact for communications with the Wrike team, coordination and facilitation of calls/meetings, sign off on outcomes, and deploying the appropriate Customer’s personnel. This individual will be a part of the Deployment Team.

  • Champions - Key representatives from each user group that can help define the process, integrations, responsible for maintaining folder and project structures, and acting as change agents within teams to encourage adoption and usage. These individuals are a part of the Deployment Team.

  • Subject Matter Experts (SMEs) - Customer’s representatives who the Wrike team can consult to understand the system with which Wrike will be integrated, relevant processes at a detailed level.

  • Deployment Team - The team at Customer who will do the actual deployment of Wrike within the organization. Team members always include the Deployment Lead and can include some or all of the Champions.

3.1.3 Responsibility by Role

The following table lists the roles and responsibilities tentatively foreseen by Wrike for the deployment in general terms

Customer Role Responsibility
Deployment Lead


  • Plan how the deployment will be structured and managed
  • Start the individual deployment components and coordinate activities
  • Ensure a smooth and safe closure of the deployment.
  • Distribution of documents for review
  • Creation and execution of the communication plan
Sponsor
  • Executive level presence and ensure that there is buy-in from all levels.
Subject Matter Experts (SME’s)
  • Provide the deployment with knowhow and knowledge of the current way-of-working and tools, with a technical process and organizational perspective, including knowledge of system identified for integration
Deployment Team
  • Participate in all configuration and setup discovery and activities
  • Be internal advocates to support onboarding adoption
  • Act as knowledge center for all team members with regards to process and Wrike functionality
Wrike Role Responsibility
Deployment Consultant
  • Support execution of quality assurance
  • Manages scope: avoids scope creep and raises change requests when appropriate
  • Keep team on task: support that tasks are executed on the estimated time and closed as expected

Support the validation quality

Specifically for Wrike Integrate Training Only Package:

  • Supports the preparation of the Wrike Integrate Training as outlined in Steps 1 and 2 of “2.1 Work Packages.
  • Performs the User training.

For all Other Packages:

  • Supports the definition of the integration mapping and, facilitate the setup and configuration of the Wrike integration recipes
  • Performs the Champion and End User training.
Account Manager
  • Supports the deployment on any commercial or license questions
  • After deployment primary contact for any commercials

3.2 Change Control Process

A Change Order Request Form (appendix A) must be completed for all changes requested by either Wrike or Customer that impact or deviate from the scope of the SOW. The Wrike Deployment Consultant will be responsible for managing all change order requests submitted on the project in accordance with the following process:

  1. Review of request to confirm complete requirements are identified.
  2. Completion of Change Order Request Form (attached as Attachment A). The form must include a detailed description of the change request, the reason for the change, and the overall time and price impact of this change.
  3. Review/Sign Off the Change Order Request Form by Customer’s Executive Sponsor.
  4. Define new work package to be completed

3.3 Issue Management and Escalation Process

Timely resolution of issues is critical to maintaining control of the pilot. The purpose of the escalation process is to help ensure that issues are identified and resolved quickly.

Either Wrike or Customer personnel may escalate a project issue as follows:

  • Raise the issue initially to the Wrike Deployment Consultant and Customer Deployment Lead.
  • If not resolved at this level within 2 weeks, an issue report will be generated and the issue will be escalated to the Wrike Engagement Manager and Wrike Sponsor.
3.4 Acceptance Process
3.4.1 Option 1: Wrike Integrate Training Only Package
3.4.1.1 Audience and Prep, Pre-Training Check
  • The training sessions will only be scheduled with Customer has confirmed by email to the Wrike Deployment Consultant that the preparation checklist has been completed. This will deem Steps 1 and 2 complete.
3.4.1.2 Training Objectives Part 1, Part 2
  • Training Objective Sessions Part 1 and Part 2 will be deemed accepted by Customer on delivery (either remote or onsite) on the same day of delivery, by a confirmation email from the Wrike Deployment Consultant to Customers Deployment Lead and or Customer Sponsor.
3.4.1.3 Post Training Q&A
  • This Step will be deemed accepted by Customer on delivery (either remote or onsite) on the same day of delivery, by a confirmation email from the Wrike Deployment Consultant to Customers Deployment Lead and or Customer Sponsor.
  • Should this session not be delivered within 1 month of the confirmation of acceptance as described in 3.4.2 Training Objectives Part 1, Part 2, it will be deemed accepted by Customer.
3.4.1.4 Optional Extra: 5 Hours Services Support
  • This Step will be deemed accepted by Customer on delivery of the 5 extra sessions of up to 1 hour each (either remote or onsite) on the same day of delivery of the final 1 hour session by a confirmation email from the Wrike Deployment Consultant to Customers Deployment Lead and or Customer Sponsor.
  • Should these sessions not be delivered within 3 months of the confirmation of acceptance as described in 3.4.2 Training Objectives Part 1, Part 2, it will be deemed accepted by Customer.
3.4.2 Option 2 or 3: All Other Wrike Integrate Packages
3.4.2.1 Non-Document Deliverables Acceptance Process

Wrike will notify Customer when the non-document Deliverable is ready for acceptance. Upon such notification, Customer shall make available all personnel and systems necessary to perform the testing in a timely manner. Should this be done onsite, Customer must ensure that the relevant personnel and systems are available.

  • If the acceptance tests demonstrate that the non-document Deliverable meets the acceptance criteria, then Customer shall provide written notification to Wrike that Customer accepts the non-document Deliverable within 5 working days and acceptance is thereby achieved.
  • If the acceptance tests demonstrate that the non-document Deliverable fails to meet the acceptance criteria then Customer shall notify Wrike in writing, within 5 working days (or such other time period as otherwise agreed by the parties in writing in respect to a particular non-document Deliverable) after the acceptance tests have been completed, of the details of how the non-document Deliverable failed to meet the acceptance criteria.
  • Wrike shall, within a reasonable time period after receipt of Customers notification, correct any such non-conformance so that the non-document Deliverable (as modified) meets the acceptance criteria and resubmit the non-document Deliverable (as modified) for a repetition of the acceptance tests. If such repeat tests meet the acceptance criteria then Customer shall provide written notification to Wrike that Customer accepts the non-document Deliverable and acceptance is thereby achieved.
    • Items such as changing the data defined in the initial user case, do not count as grounds not to accept.

Where the non-document Deliverable (as modified) does not pass the acceptance tests, Customer may elect to:

  • Agree on a new date to conduct an additional acceptance tests for the affected non-document Deliverable. If the non-document Deliverable fails such additional tests, then Customer shall be entitled to:
    • Accept the non-document Deliverable on an “as-is” basis, subject to a reasonable price adjustment to be agreed by the parties, or
  • Return the affected non-document Deliverable and associated documentation to Wrike and receive a refund of the amounts paid to Wrike for such non-conforming non-document Deliverable.

Acceptance of the non-document Deliverable shall be deemed to have occurred on whichever is the earliest of:

  • Customer  provides written confirmation the non-document Deliverable is accepted or
  • Expiry of five (5) working days after the completion of the relevant acceptance tests, and Customer does not notify Wrike in that time of any objectively verifiable non-compliance with the relevant acceptance criteria, or
  • Use of the non-document Deliverable by Customer, in any manner, including putting the non-document Deliverable into production.
3.4.2.2 Document Acceptance Process

If Wrike provides a document Deliverable as part of the Services described in this SOW, each document outcome will initially be created in draft form. The Wrike Technical Project Manager or Deployment Consultant and Customer Deployment Lead may schedule working sessions, inclusive of Wrike and/or Customer personnel, to refine the draft document as it is written.

When the draft document is complete, the Wrike Technical Project Manager or Deployment Consultant will submit the initial draft document for release to Customer Deployment Lead for review. Customers Deployment Lead will be responsible for distributing copies of the released initial draft document for internal review.

Customer Deployment Lead will have three (3) working days to review and to return the consolidated comments to the Wrike Technical Project Manager or Deployment

Consultant, unless otherwise agreed to by the parties. If no revisions are received within three (3) working days, the document will be deemed accepted.

Wrike will review and evaluate Customers comments and respond in writing within three (3) working days. Customers comments and Wrikes recommendations will be discussed and integrated within three (3) working days into a final version and delivered to Customers Deployment Lead.

Delivery of the final version of a document will constitute Customers acceptance of the document.

4. Assumptions

  • Wrike PS team member(s) will be granted timely User access to Customer’s Wrike account. If necessary, Wrike will provide license overdraft allowance up to the number of User licenses given to Wrike team member(s).
  • Customer must provide the Deployment team with all necessary access rights to the targeted system prior to the Integration configuration taking place.
  • Wrike may choose to use more than one deployment consultant.
  • Relevant Customer’s personnel are available on an immediate basis.
  • Customer will prior to engagement start identify and make available a Deployment Lead and other key personnel (Champions, Sponsors, and SMEs).
  • The Wrike staffing/scheduling for this deployment will only occur upon signing of office Quote.
  • If Customer or Wrike requires a change in any of the specifications, requirements, or scope, a written change order will be defined and mutually agreed upon before new work is initiated.
  • If Customer has additional requirements that are not included in this SOW, Wrike will provide a separate SOW, or request a change, and provide a scoped price for the additional services.
  • The deployment will be conducted in English unless otherwise indicated in this Agreement
  • All Wrike deliverables in Section 2 will be assumed accepted by Customer upon execution

Specific to the following packages, the project shall be deemed delivered on earlier date of either:

Wrike Integrate Single Connection No Training

  • Completed delivery of scope outlined in Section 2 of this SOW
  • 45 days past contract Effective Date.

Wrike Integrate Small Package

  • Completed delivery of scope outlined in Section 2 of this SOW
  • 45 days past contract Effective Date.

Wrike Integrate Medium Package

  • Completed delivery of scope outlined in Section 2 of this SOW
  • 60 days past contract Effective Date.

Wrike Integrate Large Package

  • Completed delivery of scope outlined in Section 2 of this SOW
  • 90 days past contract Effective Date.

Wrike Integrate Training Only

  • Completed delivery of scope outlined in Section 2 of this SOW, with acceptance criteria outlined in Section 3 of this SOW.
  • 45 days past contract Effective Date.

5. Pricing

5.1 Pricing
5.1.1 Integration Pricing

The price for the Professional Services scope and deliverables outlined in this SOW is listed in the official Quote sent to Customer. For reference, the list prices of the Wrike Integrate Packages is outlined in Attachment B - Wrike Integrate Packages & Price.

Specifically for Wrike Integrate Training Only, should Customer request the Training steps to be delivered onsite, Wrike will charge Customer an additional fee of $500 plus actual in costs as outlined in Section 5.3 Travel & Expenses, below.

5.1.2 Additional Professional Services and Rate Card

Additionally, Wrike’s Professional Services team is available throughout your relationship with Wrike, as needed, for consulting and service engagements with specific scope, deliverables and pricing. We will partner with your team to determine needs, deliverables/outcomes and necessary personnel required for the project. Once scoped, a new project SOW, or Change Order, will be priced according to our standard services rate card. Note that Wrike may change these rates without notification.

SENIOR DEPLOYMENT CONSULTANT $350/hour
DEPLOYMENT CONSULTANT $300/hour

5.2 Payment Terms

Payment is due up front and in advance in accordance with the applicable Order Form.

5.3 Travel & Expenses

Reasonable travel and living expenses required in connection with delivering onsite professional services will be incurred in accordance with Wrike’s internal travel and expense policy, unless otherwise agreed upon by the parties, and billed to Licensee as actual charges in addition to the professional services fees.

6. Acknowledgment and Agreement

By signing an Order Form referencing the package as outlined in this Exhibit, Customer agrees to its terms referenced herein.

7. Attachment A – Change Order Request Form

General Information
Customer Name: Account ID/Wrike ID:
Customer Deployment Lead: Wrike Deployment Consultant:

Description of Change
Change Reason:

— Change in Scope
— Change in Delivery Time Frame (New Delivery Deadline:____________________)
— Other: ______________________________________________
Description of Change (Please include full narrative of change):
Cost Impact of Change (in US Dollars):

Terms and Conditions

Except as set forth herein, the Terms and Conditions of the underlying Agreement and/or Statement of Work remain in full force and effect.

Signatures

The parties have signed this Change Order as of the Effective Date.

LICENSEE

Do not sign—Form template only

_____________________________________ Authorized Signature

_____________________________________ Print Name

_____________________________________ Title

_____________________________________ Date

WRIKE, INC.

Do not sign—Form template only

_____________________________________ Authorized Signature

_____________________________________ Print Name

_____________________________________ Title

_____________________________________ Date

7. Attachment B – Packages & Pricing