Exhibit H

Remote Package – Flex-time Consulting

I. GOVERNING TERMS

These Professional Services activities outlined below are governed by the Professional Services Terms and Conditions found here.

II. INTRODUCTION

This Statement of Work “SOW” outlines the activities related to Wrike’s Professional Services consulting hours that have been purchased through an applicable Order Form between Customer and Wrike. Capitalized terms used but not defined herein shall have the meanings ascribed to them in the Agreement between the Parties. All activities performed by the Consultant (defined below) shall be done remotely.

III. TERM

The SOW shall commence on the effective date specified in the relevant Order Form between the Parties (the “SOW Effective Date”) and shall continue until (a) completion of the Capacity Hours purchased by the Customer set forth in the relevant Order Form between the Parties; or (b) the applicable days, as outlined below for the applicable Capacity Hours purchased in the relevant Order Form between the Parties, has expired, whichever comes first (the “SOW Term”). Both Parties acknowledge and agree that SOW commencement must be within thirty (30) days from the SOW Effective Date. Notwithstanding anything to the contrary, the SOW Term may not be extended for any reason.

IV. ROLES

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

A. Customer Personnel:

1. Project Lead(s): Customer’s primary point of contact for communications with the Consultant. The Project Lead is also responsible for coordination and facilitation of Customer personnel, calls, and meetings as necessary for completion of the activities further described below.

B. Wrike Personnel:

1. Account Manager: The contact responsible for the general business relationship between Wrike and Customer during the SOW Term. The Account Manager acts as a point of escalation to resolve issues the Consultant raises and provide general guidance to the Consultant as needed. The Account Manager’s hours spent performing this role will not count against Customer’s Capacity Hours allotment.
2. Professional Services Consultant (the “Consultant”): The designated point of contact for this SOW responsible for delivering Wrike’s portion of the activities associated with this SOW.

V. SCOPE OF WORK

A. In Scope – the following is a list of activities Wrike may perform at Customer’s request during the SOW Term:

1. Analysis of Customer’s current business processes to map against Wrike’s configuration such that Customer can complete its workspace configuration within the Service. Wrike may provide guidance on efficient ways for Customer to implement their existing processes as workflows in the Service and/or suggest enhancements to existing processes;
2. Provide guidance to Customer’s administrators on their design and build of the workspace within the Service;
3. Provide guidance to Customer on its design of Customer’s request form(s) for the work intake process in the Service;
4. Host informational sessions with Customer Personnel to provide guidance on Wrike-proven practices and ways to work efficiently within the Service;
5. Provide guidance to Customer on Customer’s cleanup and reorganization of its project(s), task(s), custom field(s), intake forms, and/or other elements within the Service as requested by Customer;
6. Provide guidance to Customer on its creation of dashboards, calendars, and reports;
7. Training – Wrike will prepare an agenda in addition to facilitating trainings mutually agreed by the Parties for Customer attendees;
8. Technical consulting services related to Wrike Integrate (consisting of Recipe definition only), usage of the Wrike API (limited to the methods documented in the API Documentation and API Reference located in the Wrike Developers portal (https://developers.wrike.com/), and Wrike Analyze. For clarity, “Recipes” are automated workflows that connect applications to complete jobs. Recipes are generally comprised by a trigger and one or more actions in one or more applications and use actions to perform logic of converting the input(s) of a trigger into the output(s) of the requirements used to build the Recipe; and
9. Perform workspace Configurations (defined below) of Customer’s Service account, including, but not limited to, workflows, blueprints, reports, dashboards, Wrike Analyze (within the scope of existing functionality), integrations, and any other feature or functionality mutually agreed to by the Parties in accordance with this SOW.

The activities outlined above are not an exhaustive list and may be supplemented based on mutual agreement by Parties. Notwithstanding the foregoing, any supplemental activities shall not include activities listed below as “Out of Scope,” and all activities must directly pertain to Customer’s licenses for the Wrike Account ID described in the relevant Order Form between the Parties.

B. Out of Scope - the following activities are out of scope for this SOW:

1. Activities for Wrike Account IDs other than the Wrike Account ID specified on the relevant Order Form between the Parties.
2. Technical configuration with third-party applications.
3. Configuration of Wrike add-ons, features, or functionality not included in Customer’s Subscription(s) for the Wrike Account ID listed on the relevant Order Form between the Parties.
4. Data migrations from third party applications.
5. Building a custom connector (one not listed in the Wrike Integrate App Directory) or custom coding or any functionality not achievable through Workato using then-current published and supported API methods.
6. Anything not expressly stated in Section V(A).

C. Capacity Hours Allocation

Wrike shall provide the consulting hours as described herein, up to the maximum hours purchased (“Capacity Hours”).

If Customer fails to use all its Capacity Hours within the SOW Term, any unused Capacity Hours shall be forfeited, and no refunds or credits shall be issued as a result. Customer may allocate its Capacity Hours to the activities described above at its discretion, subject to the following:

1. The Consultant will be available during Customer’s standard business hours (8am-5pm Monday through Friday, excluding Wrike holidays) based on the time zone where the Project Lead is primarily located at SOW commencement. If Customer requires the Consultant to be available during non-standard business hours, the Parties shall mutually agree in writing (email acceptable) in advance on the activities to be performed and estimated consumption of Capacity Hours needed to complete the request.
2. Customer may request to use its Capacity Hours for any of the listed activities in Section V(A) by submitting its project request to Wrike via email describing the requested Professional Services (the “Project”). Wrike shall notify (email) the Customer of the estimated Capacity Hours it will consume to complete the requested Project and the Parties shall mutually agree to a “Project Plan” for the Project. The “Project Plan” shall mean the steps associated with completing the Project, where such steps will be made available to Customer through Wrike’s internal service account.
3. Upon completion of the Project, Wrike shall notify (email) the Customer of Project completion, the number of Capacity Hours consumed, and will request Customer’s acceptance of the Project. Customer shall provide written (email) acceptance (“Project Acceptance”) within three (3) days of the notice of Project completion from Wrike (“Project Review Period”). If Customer rejects the Project, it must do so in writing (email) by providing sufficient detail of any material nonconformance to the Project Plan within the Project Review Period. In the event Customer does provide timely and proper rejection in accordance with this Section V(C)(3), then at no additional cost to Customer and as Customer’s sole and exclusive remedy for any material non-conformances to the Project Plan, Wrike will use commercially reasonable efforts to correct any such nonconformity. Customer's failure to provide written Project Acceptance or rejection of the Project within the Project Review Period in accordance with this Section V(C)(3) shall constitute Customer’s acceptance of the Project.
4. All scheduled meetings between Wrike and the Customer shall at a minimum be thirty (30) minutes in length. The duration of the scheduled meeting will be charged against the Customer's Capacity Hour balance. Wrike will charge against the Customer’s Capacity Hours in increments of thirty (30) minutes for all meetings between Wrike and the Customer that exceed the scheduled time.
5. Preparation for meetings, calls, presentations, and hosting or attending sessions, including follow-up action items or communications, shall be a consumption of Customer’s Capacity Hours.
6. Scheduled meeting(s) canceled by Customer with less than 24 hours’ notice or “no shows” by Customer shall be recognized as completed delivery of that activity and any Capacity Hours used to prepare for or attend any such meeting(s) shall be allocated against Customer’s total Capacity Hours. Unless agreed by the Consultant in writing, all request from Customer to reschedule a meeting must be made no later than 48 hours before the set meeting or the meeting will be considered canceled and subject to the cancelation terms described in the preceding sentence.
7. The Consultant is responsible for tracking the Capacity Hours consumed by the Customer and shall provide the remaining number of Capacity Hours to the Customer upon request.
8. The Parties will use commercially reasonable efforts to schedule meetings for one (1) hour at least two (2) business days in advance, meetings for two (2) hours at least three (3) business days in advance, meetings for three (3) hours or more, at least ten (10) business days in advance, and for on-site meetings at least three (3) business weeks in advance.

D. Approval and Acceptance Processes - This Section shall apply solely to activities related to Wrike’s customized build-out of elements of Customer’s Service account (“Configuration”) for additional end-to-end processes as described in Section V(A)(9).

1. Configuration Requirements Approval

1. Initial Configuration Requirements Submission: Prior to Service Configuration, but after the Parties’ review of the Customer’s current business processes and future-state design considerations), Wrike will upload and make available to Customer the requirements for Configuration (“Configuration Requirements’) in Wrike’s internal service account for Customer approval. The Project Lead, or other Customer designee responsible for the approval of the Configuration, shall review the Configuration Requirements and provide written (email) acceptance within three (3) business days of Wrike’s submission of the Configuration Requirements (“Acceptance”).
2. Configuration Requirements Review. Should the Customer request revisions to the Configuration Requirements, the Project Lead, or other Customer designee responsible for the approval of the Configuration, shall provide written (email) feedback to Wrike requesting such changes to the Configuration Requirements (“Requested Revision(s)”) within three (3) business days of Wrike's submission of the Configuration Requirements (“Initial Review Period”). Any Requested Revisions submitted after the Initial Review Period may not be incorporated into the Configuration Requirements. Customer's failure to provide written Acceptance or any Requested Revision(s) to the Configurations Requirements within the Initial Review Period shall be deemed accepted.
3. Response to Requested Revision(s). If Customer submits Requested Revision(s) to the Configuration Requirements within the Initial Review Period, Wrike will review such Requested Revision(s) within three (3) business days of receiving such Requested Revision(s), and as applicable, update the Configuration Requirements or reasonably reject such Requested Revision(s). Requested Revisions(s) to the Configuration Requirements that require additional Capacity Hours for Wrike to complete the build will be subject to a Change Order. Wrike will provide a written explanation for any rejected Requested Revision(s) in its response back to the Customer.

2. Final Acceptance of Configuration

1. Upon completion of the Configuration, Wrike will notify (email) the Customer and request final acceptance of the Configuration. The Project Lead, or other Customer designee responsible for the approval of the Configuration, shall review the Configuration and provide written (email) acceptance (“Final Acceptance”) or rejection of the Configuration within three (3) business days of Wrike’s written notice of Configuration completion (“Final Review Period”). If Customer rejects the Configuration, it must do so in writing by providing sufficient detail of any material nonconformance to the Configuration Requirements within the Final Review Period. In the event Customer does provide timely and proper rejection in accordance with this Section V(D)(2)(i), then at no additional cost to Customer and as Customer’s sole and exclusive remedy for any material non-conformances to the Configuration Requirements, Wrike will use commercially reasonable efforts to correct any such nonconformity. This limited warranty shall be void if the nonconformity is caused by modifications to the Configuration that were not made by Wrike or Wrike’s authorized representatives. Customer's failure to provide written Final Acceptance or rejection of the Configuration within the Final Review Period in accordance with this Section V(D)(2)(i) shall constitute Customer’s acceptance of the Configuration.