Exhibit H

Remote Package – Flex-time Consulting

I. INTRODUCTION

This SOW outlines the activities related to Wrike’s Professional Services consulting hours that have been purchased through an applicable Order Form by the Customer. 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, unless otherwise stated herein.

II. TERM

The SOW shall commence on the effective date specified in the applicable Order Form between the Parties (the “SOW Effective Date”) and shall continue until (a) completion of the Capacity Hours purchased by the Customer in an applicable Order Form indicated below; or (b) the applicable days, as outlined below for the applicable Capacity Hours purchased, 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.

III. 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 for 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.

IV. 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 delivery – Wrike will prepare an agenda in addition to facilitating such training 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.
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 applicable Order Form.

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 applicable Order Form for this SOW.
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 applicable Order Form for this SOW.
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 IV(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 in advance of any such hours worked (email acceptable) and describe a list of the activities to be performed and estimated timing for completion.
2. Customer may request to use its Capacity Hours for any of the listed activities in Section IV(A) by creating a “Task” in the Service, assigning it to the Consultant, and describing the project request. Wrike shall notify the Customer of the estimated Capacity Hours it will consume to complete the Customer’s request and the Parties shall mutually agree to a project schedule in the applicable Task within the Service.
3. Upon completion of the Professional Services described in the project schedule, Wrike shall notify the Customer through the applicable task in the Service of its completion, the number of Capacity Hours consumed, and will request Customer’s acceptance. Customer shall provide its acceptance by documenting its approval in the Service within three (3) days of the notice of completion from Wrike (“Final Acceptance”). If Customer rejects its acceptance, it must do so in writing by providing sufficient detail of any material nonconformance to the project schedule within three (3) business days from being notified by Wrike of its completion. Notwithstanding anything to the contrary, Customer shall have been deemed to have provided its Final Acceptance if it does not reject the Professional Services in accordance with this Section IV(C)(3).
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 meetings 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 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. Ad hoc meetings of up to one (1) hour require forty-eight (48) hours advance written notice, meetings greater than two (2) hours require seventy-two (72) hours advance written notice, and a half or full day blocks must be booked ten (10) days in advance.

D. Approval and Acceptance

1. Approval and Acceptance Process for new Configurations. 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 IV(A)(9).
2. Task Creation. Prior to Service Configuration, Wrike will create a Task or Tasks in Customer's Service account to upload the requirements for Configuration (“Configuration Requirements”) and @mention the Customer Project Lead(s) and/or other team members responsible for reviewing it.
3. Configuration Requirements: After the  Parties’ review of the Customer’s current business processes and future-state design considerations), Wrike will provide Customer with any updates to the Configuration Requirements, and, within three (3) business days, upload the Configuration Requirements to the Service Task described above. Once Accepted (definition below), the Configuration Requirements will describe the specifications of Wrike’s Configuration build.
4. Customer Review and Feedback of the Configuration Requirements. Should Customer have any revisions to the Configuration Requirements, Customer's  assignees (those denoted as an Assignee in the Service Task) and, if applicable, designees of Customer's assignees, shall review the Configuration Requirements, compile internal Customer feedback, and provide written feedback to the Wrike submitter by uploading such feedback into the Service within three (3) business days of Wrike's submission of such of the Configuration Requirements ("Feedback Process"). Any feedback uploaded after three (3) business days from the time of submission may not be incorporated into the Configuration Requirements. Customer's failure to provide any written feedback within three (3) business days of Wrike's submission shall be deemed accepted and no further revisions will be made.
5. Wrike Response and Updates to the Configuration Requirements. If Customer submits its feedback requesting changes to the Configuration Requirements in accordance with the procedure set in Section IV(D)(4), Wrike will acknowledge the requested changes  within three (3) business days, and if applicable, update the Configuration Requirements. Revisions to the Configuration Requirements that require additional Capacity Hours for Wrike to complete the build will be subject to a Change Order. Wrike will detail its concerns with such Customer revisions that are not feasible (if any) in its response back to Customer. 
6. Final Acceptance Process.
   
   i. Wrike will request final acceptance by sending an email or Service Task to Customer requesting confirmation the Configuration materially conforms to the Configurations Requirements. Customer will provide final acceptance (“Final Acceptance”) by documenting its approval in Wrike. If Customer rejects the Configuration, it must do so in writing by providing sufficient detail of any material nonconformance to the Configuration Requirements within three (3) business days from completion. Notwithstanding anything to the contrary, Customer will have been deemed to have accepted the Configuration if Customer does not reject the Configuration in accordance with this Section (VI)(D)(6)(i). In the event Customer does provide timely and proper rejection in accordance with this Section (VI)(D)(6)(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.
   
   ii. Should Customer fail to reject its Final Acceptance within three (3) business days of receipt of the Final Acceptance request or any Wrike response with revisions to the original Final Acceptance request, Customer will have been deemed to have provided its Final Acceptance to the Configuration.

V. PROFESSIONAL SERVICES TERMS & CONDITIONS

This SOW is governed by the Professional Services Terms and Conditions found here.