Revver Software as a Service Agreement

1. Purpose

This Statement of Work (“SOW”) outlines the standard implementation services Revver (“Provider”) will deliver to the Customer (“Client”) as part of their Revver subscription. This SOW applies to small-scale engagements where no custom development or advanced integrations are required.

2. Scope of Services

Revver will provide a standard implementation package that includes guided sessions and defined deliverables to ensure successful onboarding and adoption of the Revver platform.

Implementation Sessions

Revver will deliver the following four remote onboarding sessions:

1. Kickoff & Planning Session
   • • Confirm goals, success metrics, and key contacts
     • Review implementation schedule and access requirements
2. System Configuration & Setup
   • • Guided setup of core Revver modules (document management, user roles, workflows)
     • Assistance with initial data import and user provisioning
3. Training & Enablement
   • • End-user training for standard functionality
     • Administrator training for ongoing management
4. Go-Live Support
   • • Support for launch-day readiness
     • Q&A and issue resolution assistance

Deliverables

At the conclusion of onboarding, Revver will provide:

• • Configured Revver environment aligned to Client’s defined structure
  • User and admin documentation (standard templates)
  • Summary of sessions completed and recommended next steps

3. Responsibilities

Revver

• • Provide assigned Implementation Specialist
  • Deliver sessions and guidance according to the defined scope
  • Provide access to standard documentation and training resources

Client

• • Assign a primary point of contact
  • Ensure timely scheduling and participation in sessions
  • Provide necessary system access and configuration inputs

4. Assumptions & Exclusions

• • Engagement assumes standard configuration only; no custom integrations or feature modifications are included.
  • Data migration support is limited to template-based import guidance.
  • User Acceptance Testing (UAT) is informal and Client-driven.
  • Implementation support is delivered remotely unless otherwise agreed.

5. Timeline

• • Standard implementation duration: 4–6 weeks from kickoff, contingent on Client participation and data readiness.

6. Completion Criteria

Implementation is considered complete upon delivery of the Go-Live Support session and provision of final documentation.

7. Acceptance

This SOW is effective upon delivery to the Client and does not require a signature. Engagement begins upon scheduling of the Kickoff session.

Prepared by: Revver Implementation Team