Exhibit F

Professional Services Wrike Integrate Standard Package

1. WRIKE INTEGRATE

1.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 description outlined below address the steps related to the delivery and implementation of the Wrike Integrate Standard 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”).

1.2. DEFINITIONS

1. “Defect(s)” mean a material deviation from the Functional Requirements Document such that the expected functional outcome does not produce the intended output and does not mean nor apply to cosmetic defects such as aesthetic changes/look and feel or modifications or enhancements to the underlying Wrike product.
2. “Integration Flow” mean the steps of a given business process which execute together in one continuous sequence beginning at a single point in time (the “trigger”) and occurring in no more than two applications.
   1. For purposes of clarity and illustration, each of the following non-exhaustive hypothetical examples represent 1 (one) Integration Flow:
      1. When a Salesforce Opportunity reaches the “Closed-Won” stage, also create a Project in Wrike, choosing the appropriate blueprint based on the SFDC Opportunity type
      2. When a Project in Wrike reaches its start date, also send a Slack Bot message to all project owners notifying them of the Project details
      3. Send a weekly email to all members of the “Escalation Managers” Wrike User group, while also listing all outstanding escalation ticket tasks in Wrike and highlighting all SLA violations
      4. When a Project in Wrike reaches the “Ready to Bill” workflow state, also create an Invoice in Quickbooks including a line item for each task in the project
      5. When a Wrike Task is delayed at least 14 days past its scheduled end date, also add a comment to the task, @mentioning all Project owners with a notification message.
3. “Functional Requirements Document” means a jointly drafted document between Customer and Wrike that outlines (a) step by step Recipe with triggers and actions; (b) Data Mapping Table (optional); (c) authoritative data sources; and (d) defined User Acceptance Criteria for User Acceptance Testing.
4. “Recipe” means an automated workflow that connects applications (“apps”) to complete Tasks composed by Customer based on a combination of apps, triggers, and actions. Recipes are comprised by a trigger and one or more actions (in one or more apps) based on Customer’s use case. Recipes use actions to perform the logic of converting the input(s) of a trigger into the output(s) of the requirements.
5. “Task” means a usage metric that is counted every time Wrike Integrate requests a piece of data from another platform/software or performs an action. https://docs.workato.com/recipes/tasks.html#tasks
6. “Test Scripts” means Customer-developed test cases to validate the business functionality of the integration(s) developed under this Implementation, which Customer will use to perform User Acceptance Testing.
7. “Unit Testing” means Wrike’s execution of functional and/or technical tests (if applicable) to validate compliance of the configured Recipes with the Functional Requirements Document.
8. “User Acceptance Criteria” means the criteria against which Customer will test the integrations developed under this Implementation during Customer’s performance of User Acceptance Testing.
9. “User(s)” mean an individual who is authorized by Customer to use or access the Service and who has been supplied an identification and password by Customer or at Customer’s direction. Users can be a Regular User, External User, or Collaborator, which are further defined at https://help.wrike.com/hc/en-us/articles/209603989-Types-of-Licenses-in-Wrike, and may include Customer’s or Customer’s Affiliates’ employees, representatives, and agents.
10. “User Acceptance Testing” or “UAT” means Customers’ User testing its Test Scripts to confirm the defined outcomes materially comply with the outcomes in the Functional Requirements Document.

1.3. 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. Technical Lead(s): Customer’s representatives who will take ownership of Recipes developed as part of this Implementation post-Launch, and who will be consumers of technical training sessions. Technical Leads are not part of the Implementation Team.
   6. 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 the applicable package will be the Wrike Implementation/ Professional Services Consultant(s).

1.3. INTEGRATE PACKAGE DESCRIPTIONS

1. Wrike Integrate Standard

If purchased, the Wrike Integrate Standard Package includes:

1. In Scope: Through a series of 10 (ten) steps (detailed below), Wrike PS and Customer’s Implementation Team will cover the basic underlying functionality of Wrike Integrate as well as training related to Customer’s specific use-case. The scope of this integration covers only applications for which a pre-built connector exists, and for which the connector includes pre-built triggers and actions (a then-current and complete list can be found on the Wrike Integrate App Directory located at www.workato.com/integrations). The connector will be used to integrate between Wrike and Customer’s cloud or on-premise applications. Wrike PS will work with Customer’s Implementation Team to design an up to 1 (one) Integration Flow and develop up to 5 (five) Recipes for this Integration Flow using the triggers and actions available for the chosen connector.

*NOTE: Wrike will attempt to resolve Defects or implement a workaround prior to Use Case Training if the Defect(s) is identified prior to Launch. After Launch, Wrike Support should be contacted for newly identified Defects, and the Parties must execute a Change Order describing the added scope and price (if any).

1. Out of Scope:
   1. 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;
   2. Additional and/or incremental work not referenced above (including modifications or additions to Recipe(s), tasks, triggers, post-launch);
   3. Non-Wrike related bug fixes (including issues caused by third-party application updates, system changes or upgrades, etc.);
   4. Delivering any Workato training on Wrike Integrate (other than providing access to the self-paced training in Step 3 above);
   5. Any and all work in excess of 1 (one) Integration Flow as determined by the Implementation Consultant; and
   6. Any and all Integration Flows to SAP, NetSuite, or any in-house custom application or on-premise software not part of the standard package.
2. Additional Customer Responsibilities:
   In addition to the roles and responsibilities set forth in the table above, Customer is also responsible to provide the following resources (together, with the Customer Action Items above shall be defined as “Customer Responsibilities”):
   1. Provide business analysis support as needed for Wrike and “System”
   2. Provide a “System” subject-matter expert as needed
3. Functional Requirements Document Approval Process:
   Customer will provide the Wrike Implementation Consultant with written notice (email sufficient) of Customer’s approval of the Functional Requirements Document within 5 (five) business days of completion of the Use Case Analysis session(s) referenced in Step 3 above. If Customer requests any revision to the Wrike-provided portions of the Functional Requirements Document, Wrike will provide one update to address Customer’s concerns. If the Parties are still unable to reach agreement, the Wrike Implementation Consultant will schedule a meeting to discuss further, and the Implementation will be paused until such time as the Parties are in agreement to move forward.

1.4. ASSUMPTIONS

Customer understands Wrike’s performance is dependent upon Customer’s timely and complete performance of its Customer Responsibilities. In addition, Wrike’s performance is based on the following assumptions (“Assumptions”). Deviations from the Assumptions or failure of Customer to perform its roles and responsibilities may result in price, schedule, and/or scope adjustments, and Wrike will not be liable for its inability to provide Wrike PS that result from such a delay. Any such change will be made pursuant to the Professional Services Terms & Conditions unless otherwise agreed to and signed between Parties.

1. To the extent required to complete the Implementation, Wrike will be granted timely access Customer’s Wrike account. Access, if any, is limited in duration and scope and only for Wrike’s delivery of its obligations as it relates to this Implementation. If necessary, and for the duration of this Implementation, Wrike will provide additional licenses to assign to Wrike team member(s) for this Implementation at no additional charge to Customer.
2. Any determination of actual number of Integration Flows required for Customer’s identified need will be made solely at the discretion of the Wrike Implementation Consultant. Customer agrees that in the event that the Wrike Implementation Consultant determines that Customer’s desired functionality is in excess of 1 (one) Integration Flow, Customer agrees to either (a) accept a narrower scope of work for the Implementation equal to 1 (one) Integration Flow, or (b) execute a mutually agreed upon Change Order to add additional Integration Flow(s) to the scope and outline associated new Fees (as applicable).

2. WRIKE INTEGRATE LITE

2.1. WRIKE INTEGRATE LITE - ONBOARDING ASSISTANCE

Wrike Integrate Lite, the premium add-on that streamlines your workflow by seamlessly integrating popular CRMs (like Salesforce or HubSpot) with Wrike. Lite is a limited version of the Wrike Integrate automation platform that allows customers to create custom integrations between the Wrike platform and select cloud or on-premise applications. With Wrike Integrate Lite, your team can improve cross-departmental efficiency by syncing important deal information with Wrike tasks, freeing up valuable time and increasing productivity. Additionally, when a deal is closed in your CRM, Wrike automatically launches associated tasks, ensuring consistent project initiation and optimal outcomes. Wrike's powerful two-way sync with CRMs also increases real-time visibility, allowing relationship owners to better visualize project progress as it happens. With Wrike Integrate Lite, you have the ability to customize the pre-configured integration recipe with additional low-code logic to fit your specific needs.

The package description outlined below addresses the steps related to the delivery and implementation of the Wrike Integrate Lite Onboarding Assistance 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 and provide advisory on how to meet such requirements.

2.2. DEFINITIONS

1. “Connector” means the building blocks for recipes. Each connector includes a method of authentication, triggers, and actions for a specific app.
2. “Connector Package(s)” means a specific set of connectors that are available along with recipe templates.
3. “Integration Flow” means the steps of a given business process which execute together in one continuous sequence beginning at a single point in time (the “trigger”) and occurring in no more than two applications.
4. “Recipe” means an automated workflow that connects applications (“apps”) to complete Tasks composed by Customer based on a combination of apps, triggers, and actions. Recipes are comprised by a trigger and one or more actions (in one or more apps) based on Customer’s use case. Recipes use actions to perform the logic of converting the input(s) of a trigger into the output(s) of the requirements.
5. “Task” means a usage metric that is counted every time Wrike Integrate Lite requests a piece of data from another platform/software or performs an action. https://docs.workato.com/recipes/tasks.html#tasks
6. “User(s)” mean an individual who is authorized by Customer to use or access the Service and who has been supplied an identification and password by Customer or at Customer’s direction. Users can be a Regular User, External User, or Collaborator, which are further defined at https://help.wrike.com/hc/en-us/articles/209603989-Types-of-Licenses-in-Wrike, and may include Customer’s or Customer’s Affiliates’ employees, representatives, and agents.

2.3. ONBOARDING ROLES

To support Wrike’s collaborative Implementation, Wrike expects that Customer’s personnel are identified and made available to collaborate with their Wrike counterparts during the Onboarding phase. 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. 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.
4. Technical Lead(s): Customer’s representatives who will take ownership of Recipes developed as part of this Implementation post-Launch. Technical Leads are not part of the Implementation Team.
5. Implementation Team: Customer’s team participating in the Onboarding of Wrike Integrate Lite. Team members include the Champion(s), Implementation Lead(s), and any additional internal Users of Customer.
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. Professional Services Consultant: The primary designated point of contact during Wrike Integrate Lite Onboarding responsible for ensuring on-time execution of package and communicating changes (if any) to scope and timeline. The Wrike Attendee for the activities in the applicable package will be the Wrike Professional Services Consultant(s).

2.3. INTEGRATE LITE PACKAGE DESCRIPTIONS

1.    Wrike Integrate Lite Onboarding Assistance

If purchased, the Wrike Integrate Lite Onboarding Assistance Package includes:

Scope Overview:

In Scope:

The scope of this Wrike Integrate Lite Package is limited to the onboarding and enablement of identified Customer Personnel regarding the Wrike Integrate Lite add on feature. Wrike Personnel will partner with Customer Personnel to work through the following activities:

• Review of Wrike configuration and discussion of leveraging Wrike Integrate Lite functionality within that use case according to best practices;
• Assist the customer with its installation of the pre-built recipe templates that are included with the Wrike Integrate Lite Standard. Review provided documentation and instructions with customer personnel.

Out of Scope:

• Configuration and onboarding of use cases not directly related to Wrike Integrate Lite functionality; and
• Integrations and configurations with other systems and Customer’s third-party partners beyond what is included in Wrike Integrate Lite package,
• Modifying the pre-built recipes to customize to customer requirements.
• Additional and/or incremental work not referenced above (including modifications or additions to Recipe(s), tasks, triggers, post-launch);
• Non-Wrike related bug fixes (including issues caused by third-party application updates, system changes or upgrades, etc.);
• Delivering any Workato training on Wrike Integrate (other than providing access to the self-paced training )

1. Additional Customer Responsibilities:
   In addition to the roles and responsibilities set forth in the table above, Customer is also responsible to provide the following resources (together, with the Customer Action Items above shall be defined as “Customer Responsibilities”):
   1. Provide Wrike Consultant access to the environment and systems needed to perform their duties.
   2. Provide business analysis support as needed for Wrike and “System”
   3. Provide a “System” subject-matter expert as needed

2.4. ASSUMPTIONS

Customer understands Wrike’s performance is dependent upon Customer’s timely and complete performance of its Customer Responsibilities. In addition, Wrike’s performance is based on the following assumptions (“Assumptions”). Deviations from the Assumptions or failure of Customer to perform its roles and responsibilities may result in price, schedule, and/or scope adjustments, and Wrike will not be liable for its inability to provide Wrike PS that result from such a delay. Any such change will be made pursuant to the Professional Services Terms & Conditions unless otherwise agreed to and signed between Parties.

1. To the extent required to complete the Implementation, Wrike will be granted timely access Customer’s Wrike account. Access, if any, is limited in duration and scope and only for Wrike’s delivery of its obligations as it relates to this Implementation. If necessary, and for the duration of this Implementation, Wrike will provide additional licenses to assign to Wrike team member(s) for this Implementation at no additional charge to Customer.
2. Any determination of updates to recipes or additional integration flows required for Customer’s identified need will be made solely at the discretion of the Wrike Implementation Consultant. Customer agrees that in the event that the Wrike Implementation Consultant determines that Customer’s desired functionality is outside of the included recipe templates, Customer agrees to either (a) accept the included recipe templates as is or (b) execute a mutually agreed upon Change Order to add additional Integration Flow(s) to the scope and outline associated new Fees (as applicable).
3. Wrike Integrate Lite Onboarding Assistance shall be delivered within thirty (30) days of Customer requesting such assistance, provided Customer must request such assistance within two(2) weeks of purchasing Wrike Integrate Lite. Any request for assistance from Customer beyond thirty (30) days from the purchase of Wrike Integrate Lite shall be subject to a separate statement of work agreed by the Parties.

PROFESSIONAL SERVICES TERMS & CONDITIONS

Professional services terms & conditions can be found here.

For Professional Service Packages purchased prior to October 1, 2021, the terms and 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 UPDATED: FEBRUARY 1, 2022.