logo conga
  • Products

    Advantage Platform

    Conga’s unified, extensible platform to help you accelerate your end-to-end revenue lifecycle and gain a Revenue Advantage

    Learn more
    • Document Automation
      • Composer

        Create streamlined and professional-looking documents that align with your brand

      • Sign

        Unlock powerful affordable enterprise-grade eSignature for a better way to sign across your business

    • Contract Lifecycle Management
      • CLM

        Automate contract processes for increased visibility and a better customer experience

      • CLM AI

        Get accurate answers quickly to accelerate decision-making and time to revenue with ethical AI

    • Revenue & Commerce
      • CPQ

        Deliver accurate quotes, faster for bigger deals, better margins, and a higher win rate

      • Digital Commerce

        Provide unified buyer and seller experiences with a modern digital commerce platform

      • Billing

        Improve margins through customized automated billing for any business model

    • Integrations

      Merge data from any CRM, ERP, or platform of your choice

      Contact sales
  • Solutions

    Revenue Lifecycle Management

    Your complete suite of solutions to Propose and Quote, Negotiate and Execute, Manage and Fulfill, and Renew and Expand

    Learn more
    • BY DEPARTMENT
      • Business operations
      • Finance
      • IT
      • Legal
      • Procurement
      • Sales
    • BY INDUSTRY
      • Technology
      • Financial services
      • Healthcare
      • Life sciences
    • BY PROCESS
      • Propose and quote
      • Negotiate and execute
      • Manage and fulfill
      • Renew and expand
  • Resources
    G2 2025 Grid® Report
    G2 Grid Leader badge

    Conga named #1 leader in document automation

    Read the report
    • LEARN
      • Blogs
      • Customer stories
      • On demand webinars
      • Guides
      • Training
    • DISCOVER
      • Partners
      • Community
      • Live events and webinars
    • SUPPORT
      • Professional services
      • Customer success
      • Support
    • Resource Center

      A Revenue Advantage starts here! Access support, guides, training, on-demand webinars, and more to optimize your experience and get the most out of your Conga solutions.

  • The Conga Way
  • Pricing
  • Contact sales
    • English
    • Deutsch
    • Français
Book a demo
  • Products

    Advantage Platform

    Conga’s unified, extensible platform to help you accelerate your end-to-end revenue lifecycle and gain a Revenue Advantage

    Learn more
    • Document Automation
      • Composer

        Create streamlined and professional-looking documents that align with your brand

      • Sign

        Unlock powerful affordable enterprise-grade eSignature for a better way to sign across your business

    • Contract Lifecycle Management
      • CLM

        Automate contract processes for increased visibility and a better customer experience

      • CLM AI

        Get accurate answers quickly to accelerate decision-making and time to revenue with ethical AI

    • Revenue & Commerce
      • CPQ

        Deliver accurate quotes, faster for bigger deals, better margins, and a higher win rate

      • Digital Commerce

        Provide unified buyer and seller experiences with a modern digital commerce platform

      • Billing

        Improve margins through customized automated billing for any business model

    • Integrations

      Merge data from any CRM, ERP, or platform of your choice

      Contact sales
  • Solutions

    Revenue Lifecycle Management

    Your complete suite of solutions to Propose and Quote, Negotiate and Execute, Manage and Fulfill, and Renew and Expand

    Learn more
    • BY DEPARTMENT
      • Business operations
      • Finance
      • IT
      • Legal
      • Procurement
      • Sales
    • BY INDUSTRY
      • Technology
      • Financial services
      • Healthcare
      • Life sciences
    • BY PROCESS
      • Propose and quote
      • Negotiate and execute
      • Manage and fulfill
      • Renew and expand
  • Resources
    G2 2025 Grid® Report
    G2 Grid Leader badge

    Conga named #1 leader in document automation

    Read the report
    • LEARN
      • Blogs
      • Customer stories
      • On demand webinars
      • Guides
      • Training
    • DISCOVER
      • Partners
      • Community
      • Live events and webinars
    • SUPPORT
      • Professional services
      • Customer success
      • Support
    • Resource Center

      A Revenue Advantage starts here! Access support, guides, training, on-demand webinars, and more to optimize your experience and get the most out of your Conga solutions.

  • The Conga Way
  • Pricing
  • Contact sales
Book a demo
Access the Legal Center

Conga Sign Essentials/Essentials Plus Accelerator Services SOW

Version
Effective
Download

This Conga Sign Essentials/Essentials Plus Accelerator Services Statement of Work (“SOW”) for  Professional Services, including any applicable addenda, annexes, exhibits, or other similar  agreements, constitutes a legal agreement between you, your employer, or other entity on whose  behalf you enter into this SOW (the “Customer”), and Apttus Corporation (“Conga” or Apttus”), and is  issued pursuant to the Professional Services Terms, or similar professional services agreement  (collectively, “PS Terms”), attached to the Master Subscription Services Agreement, or similar  subscription agreement (collectively, “MSSA”), by and between the parties. In the absence of existing  PS Terms between the parties, this SOW shall be governed by the Professional Services Terms located  at: /legal-center/professional-services-terms. 

YOU MUST READ AND AGREE TO THIS SOW PRIOR TO RECEIVING THE PROFESSIONAL SERVICES.  BY CLICKING ON THE “ACCEPT” BUTTON, SIGNING AN ASSOCIATED ORDER OR ORDER FORM, OR  RECEIVING THE PROFESSIONAL SERVICES, YOU ARE AGREEING TO BE BOUND BY THE TERMS ON  BEHALF OF CUSTOMER. 

IF YOU ARE ENTERING INTO THIS SOW ON BEHALF OF YOUR EMPLOYER OR ANOTHER LEGAL  ENTITY, THEN YOU REPRESENT AND WARRANT THAT YOU HAVE THE AUTHORITY TO BIND THAT  ENTITY AS THE CUSTOMER. 

Conga may amend this SOW from time to time by posting an amended version at its website and  sending Customer notice thereof (an email to Customer’s Project sponsor or designated contact shall  be deemed sufficient in this case). Such amendment will be deemed accepted and become effective  thirty (30) days after such notice (the “Proposed Amendment Date”), unless Customer first gives  Conga written notice of rejection of the amendment. In the event of such rejection, this SOW will  continue in its existing form, and the amendment will become effective at the start of Customer’s  next purchase of Professional Services meant to be governed by this SOW following the Proposed  Amendment Date. Customer’s continued use of the Professional Services hereunder following the  Proposed Amendment Date will confirm Customer’s consent thereto. This Agreement may not be  amended in any other way except through a written agreement by authorized representatives of each  party. 

Whereas, Customer wishes to have Conga provide certain Professional Services pursuant to this SOW, 

For good and valuable consideration, the receipt and sufficiency of which is hereby acknowledged,  the parties agree as follows: 

Definitions: 

“Project” refers to the scope of services, including performance of all work, activities, and Deliverables,  set forth in this SOW, including any and all appendices. Notwithstanding any other provision of these  terms, timelines and hours in this SOW are estimates only. 

“Services” and “Professional Services” as used herein means Professional Services work rendered by  Conga in relation to this SOW. It is distinguished from the meaning of “Subscription Services” as used  in the MSSA.

 

1. UNDERSTANDING OF OBJECTIVES

Our understanding of Customer objectives and desired outcome is the following:

  • Implementation of Conga Sign solution within the constraints of the scope detailed below

2. SCOPE OF WORK

This section defines the scope of Professional Services to be delivered by Conga, with support from  Customer resources, under this SOW. Detailed scope and objectives will be confirmed during the define  and design phases. If changes or expanded scope are necessary, a new SOW will be needed.

2.1 Organizational Scope

The efforts assume one configuration across the organization, and no effort or time is allocated to design  or configure variations. All countries, divisions, and user roles will leverage the same data structures,  processes, and approval workflows.

2.2 Product Scope

The following Conga solutions will be configured as part of this SOW:

  • Conga Sign

2.3 Functional Use Case Scope:

The following Use Cases are in scope:

Conga Sign E Signature Functionality 

Conga Sign Essentials Accelerator Offering Configuration Scope

Conga Sign Essentials Plus Accelerator Offering Configuration  Scope

Conga Sign Installation

Conga Sign installed in Development, UAT  and Production environments

Conga Sign installed in Development, UAT and Production environments

Conga Sign added to page Layout

Three (3) page layout updates 

Three (3) page layout updates

eSignature Status on Agreement

Included 

Included

Signature tags on contract templates

Three (3) Contract Templates: 3 Signature  Tags each

Three (3) Contract Templates: 3 Signature Tags each

Write-back Conga Sign Tags

None 

Six (6) Write-back Conga Sign Tags  (Field Updates) 

Conga Sign Custom Tags will write  back to parent objects directly related to the object that Conga Sign  is launching from

Auto population of recipients

None 

Three (3) Auto-populate Recipients

Environment MigrationsMigrations from Development to UAT to ProductionMigrations from Development to UAT to Production

2.4 Out of Scope 

Professional Services and/or scope not included and/or not itemized as “Scope” in this SOW are out of scope, including: 

  • Non-Conga program management

  • Data migration & legacy contracts migration

  • Data archiving

  • Development of training materials

  • Additional Languages (apart from English) and Currencies

  • Interfaces/Integrations

  • Third-Party support and related activities

  • Any scope item not explicitly listed in section ‘Use Case Scope’

  • Additional documentation that are not specified in section ‘Project Methodology and  Delivery Assurance’

  • Change Management including, but not limited to, stakeholders management; change  readiness; communications plan and execution; training plan and execution including  development of training materials; adoption tracking

  • Creation/Definition of business requirements document

  • UI Enhancement/Guidance

  • Data extraction from any source systems or hard-copy papers

  • Management and migration of Customer’s CRM records (e.g. Accounts, Contacts)

  • Automation testing

  • Performance testing

  • Automated QA Testing or automated test scripts

  • Deployment strategy, plan, and execution for non-Conga systems

  • Translation services of Conga standard and non-standard fields in different languages

  • Type of other currencies

  • Any third-party support related activities

  • Other Conga Services such as Education Services and Application Management Services (AMS)

  • Refactoring the standard Conga user flow, e.g. splitting standard pages into multiple pages,  rerouting transitions amongst standard pages, development of custom pages, development  of custom widgets.

  • Services for the migration of legacy Data (e.g. legacy Quotes, in-flight Quotes, legacy  Agreements, in-flight Agreements, and Assets) data migration, data quality, said  performance of data loads to and from the Conga solution(s) and the readiness and  configuration of the standard CRM objects/entities for which the intended solution is dependent upon.

  • Specification of eSignature software data input tags (Defining the type of “tag” and location  of the “tag”) unless otherwise defined in functional use case scope.

  • Advanced security capabilities e.g. data sharing, role/hierarchy driven sharing, permission set  driven sharing

  • Training and enablement for CRM system and platform capabilities, including creation or  delivery of user training

  • Production of Customer’s CRM reports

3. DELIVERABLES AND ACCEPTANCE CRITERIA

3.1 Deliverables 

The anticipated Deliverables provided by Conga for the scope of this SOW will be:

  • Project plan 

  • Standard getting started guide

  • Standard test scripts

  • Deployment tracker/workbook

  • Installed and configured Conga Sign solution per defined scope 

3.2 Acceptance of Conga Deliverables 

Deliverables will be produced in accordance with the Project Plan. Conga will provide early drafts when feasible to facilitate prompt review and approval. 

Customer shall have two (2) business days from the date of receipt of a Deliverable to provide final  acceptance or rejection of the Deliverable in writing. 

If Customer rejects a Deliverable, it will specify in reasonable detail each deficiency and / or  nonconformance serving as the basis of rejection in writing. Upon receipt of such Deliverable rejection  notification, Conga will promptly correct such deficiencies and / or nonconformities and re-deliver the  Deliverable for Customer’s review. Upon re-delivery of the Deliverable, Customer shall provide  notification of final acceptance or rejection in writing as soon as reasonably possible, but no later than  two (2) business days from the date of receipt. 

If Customer does not provide notice of final acceptance or rejection within two (2) business days in  writing of a Deliverable or re-delivery of a rejected Deliverable, the Deliverable will be deemed  accepted.

4. PROJECT METHODOLOGY & DELIVERY ASSURANCE

4.1 Methodology 

The following Implementation Methodology will be used for this Project. The Project methodology  includes three phases. Conga provides delivery assurance throughout the Project lifecycle as part of the  methodology.

conga-sign-essentials-essentials-plus-accelerator-methodology

Note that the Conga Sign Essentials Accelerator Package has a 1 week Define/Design, Configure, Testing  phase. 

The phases are outlined below: 

Plan and Prep - A Project kickoff readiness review is conducted. The predefined Project plan is shared, and  kickoff is held where clear Project objectives are established. Refer to section 6.4 for the list of prerequisite deliverables from Customer prior to starting the Plan Phase. These deliverables will be reviewed as part of  the kickoff readiness review. Environment readiness and access is provided  

Define/Design, Configure & Testing– This phase uses agile methodology to configure the defined scope.  Requirements and Design are defined and confirmed. Conga Sign is installed and basic setup is  completed. Template and Record Page layouts are configured. Other features are configured per scope.  User Acceptance test scripts are created. Customer to test that the system is configured according to  agreed requirements and design, and deployment plan is developed.  

Launch/Hypercare – Deployment of the solution to production and one week of Hypercare. 

Conga will utilize one or more of the following tools to support the implementation efforts. The tools are  templatized for fast and consistent implementation results. The client Project team may be granted access  for the duration of the Project. The tools that may be utilized during the Project are Microsoft Project,  Confluence, JIRA, Zephyr, Bitbucket.

5. PROJECT PLAN

Project kick-off will be planned on a mutually agreed date, based on Conga and Customer resource availability and completion of the Customer Pre-requisite Deliverables defined below.  

As of the Effective Date, the known requirements, estimates effort, and scope the following Project Plan (“Project Plan”) is anticipated for Conga solution delivery. The Project Plan will be confirmed after  the design phase. Any adjustments to the Project Plan (e.g. change in agreement type; scope  changes) may require a new SOW. 

Maximum Project Plan duration:  

  • Essentials: 2 Weeks (Customer Prep plus 1 week Define/Design/Configure to Launch plus 1  week of Hypercare).

  • Essentials Plus: 3 Weeks (Customer Prep plus 2 weeks Define/Design/Configure to Launch plus  1 week of Hypercare). 

Any extension beyond the allocated Project Plan will require a new SOW. For the avoidance of doubt, a  day is eight (8) hours, Monday through Friday, on Conga’s standard business days, excluding holidays. 

5.1 Kickoff 

Conga will contact Customer within three (3) weeks of SOW Effective Date to establish a Project start  date. The Project start date will be mutually agreed to in writing by the parties (email sufficient). 

5.2 Go-Live 

“Go-Live” refers to the on-boarding of users to the Conga Sign solution in the Production environment.

  • A single go-live event is in scope. Additional go-lives are not in scope and any functionality that  is mutually agreed to be deferred from the single go-live is no longer part of the scope of this  SOW.

  • Go-Live occurs after migration of the Conga solution to the Production environment.

  • Customer will be responsible for Go-live planning with guidance from Conga as outlined in this  SOW.

  • Conga assumes Customer’s information technology policies that govern the deployment of Conga solution to the Production environment and the go-live of new information technology,  will not extend the Project Plan described herein via a delay in the deployment or Go-Live of the Conga solution.

5.3 Hypercare Period

“Hypercare Period” refers to the period and services following the Go-Live of the Conga solution.

  • For a release of the Conga solution, the Hypercare Period begins at Go-Live and concludes after five (5) business days, i.e. one (1) week.

  • For clarity, issues identified after the Hypercare Period will be addressed per the terms set forth in Customer’s applicable subscription agreement with Conga (i.e. Customer’s purchased level of  Technical Support in the MSSA and applicable Order or Order Form). Upon completion of the  Hypercare Period, Conga will send Customer a notice (email sufficient) acknowledging SOW  Project completion.

6. RESOURCING, ROLES AND RESPONSIBILITIES

6.1 Resourcing 

Conga and Customer resources share responsibility for Project execution, as outlined in this SOW. Assigned resources are required to attend the Project kickoff, and to perform agreed activities  throughout the Project lifecycle. 

6.2 Customer Roles and Responsibilities 

Customer Roles 

Customer Responsibilities

Steering

Committee 

Representative

  • Provide Project oversight and high-level direction

  • Guide the Project’s alignment to key objectives

  • Highest level of escalation, decision making and issue resolution

Project Manager 

  • Act as primary point of contact for Conga Project Manager

  • Coordinate all Project activities and required Customer resources

Subject Matter Expert (Business and Technical)

  • Provide business and technical expertise to the Project related to  Customer’s desired solution processes; resources that are familiar with  Customer business processes, documents, approval processes, etc.

QA Testers 

  • Develop UAT test strategy, test scenarios, and test plans

  • Execute test cases and report findings to the Project managers

System

Administrators

  • Administer sandbox environment(s)

  • Manage all CRM activities required by and related to the Project

6.3 Conga Resourcing and Resource Allocations 

The following Conga roles, sometimes also referred to as “Resources”, will be allocated to the Project.  This is subject to change based on further analysis and discovery through the Project stages.

Conga Staffing/Resource Roles 

Conga Responsibilities

Project/Engagement Manager

  • Helps monitor and advise

  • Performs functional and Project management activities, including management of Conga consulting team

  • Issues status reports, manages risk and issue tracking and  manages budget and schedules

Consultant 

  • Facilitates requirements session

  • Installs Conga Sign in 2 Sandboxes and Production  environments

  • Performs technical configurations

  • Provide best practices and guidance on future state process

  • Performs SIT

  • Prepares User Acceptance Test scripts

  • Provides launch and post go-live support

6.4 Pre-Requisite Deliverables 

Prior to Project start, Customer will provide Conga with Pre-Requisite Deliverables (collectively, “Pre Requisite Deliverables”): 

  • Environments are ready and test users are set up in Salesforce Dev and UAT Test Sandbox Orgs.

  • Provide system administrator access to Conga resource has system administrator access to  Development, UAT Test and Production environments.

  • Salesforce “Files” must be configured in all environments and the Files related list must be on  each Agreement/Proposal page layout

  • Test recipients are setup as Salesforce Leads or Contacts; Company test signers are identified, and email addresses provided.

  • Gather the Templates in scope, and mark-up/highlight for Signature Blocks and Writeback fields 

6.5 Project Work Products and Activities* 

The following Work Product and Activities are minimally required for the Project:

  • Work Product: outputs to support Project delivery that do not require Customer approval

  • Activity: methodology component that is a task that does not require Customer approval

  • *Note: The below Work Product and/or Activities may result in the output of a Deliverable as  identified in Section 3.1.  

To complete the Work Products and Activities each parties’ Roles and Responsibilities are defined as  follows: 

  • R = Responsible: Conga or Customer performs the work to complete the Activity and /or Work  Product

  • A = Accountable: Conga or Customer responsible for justifying actions or decisions made to  complete the Activity and / or Work Product

  • C = Consulted -Conga or Customer whose opinions are sought by the person responsible for  the Activity and / or Work Product

  • I = Informed - Conga or Customer that should be kept up to date on progress of the Activity  and / or Work Product 

Conga and Customer are each responsible for completing their assignments, as indicated in the  following table:

Stage/Category

Activity or Work Product Description

Owner 

Type
Conga Customer
Plan

Project kick-off 

CRActivity

Project Plan 

R 

A

Work Product

Training Plan 

C 

R

Work Product

Resource management 

R 

R 

Activity

Facilitate regular Project meetings 

C 

R 

Activity

Weekly status reports 

R 

R

Work Product

Define/Configuration/SIT

Conduct requirements workshop 

R 

A, C, R 

Activity

Define functional requirements 

A, R 

C 

Activity

Configure Conga solution 

R 

C 

Activity 

Develop deployment plan 

R, C 

R 

Activity

Develop UAT Test plan/cases 

C 

R 

Activity

UAT

Migrate solution from Development Environment to UAT Environment 

R, C 

R, C 

Activity

System Navigation and walkthrough  Session 

R 

A 

Activity 

    

Conduct UAT Testing 

C 

R 

Activity 

Manage UAT Fixes 

R 

R 

Activity

Launch

UAT Sign-off 

C 

R 

Activity

Develop Hypercare Plan 

C 

R

Work Product

Go/no-go decision 

C 

R, A 

Activity

Migrate solution from UAT
Environment to Production
Environment

R, C 

R, C 

Activity

Hypercare

Develop support transition Project overview 

R 

R 

Activity 

Validate Status and availability of key  Deliverables 

R 

R 

Activity

Information sharing sessions to Tech  Support 

R 

A 

Activity

Disposition cases opened during  Project 

R 

C 

Activity

 

 

6.6 Customer Project Deliverables* 

During the Project, Customer is responsible for ensuring completing the following Customer  Deliverables are completed (collectively, “Customer Deliverables”) according to the Project Plan:

  • Functional Requirements

  • UAT Test Plan

  • UAT Test Cases

  • UAT Testing

  • Deployment Plan

  • Training Plan

  • Hypercare period Plan

  • Signoff on Testing

For clarity, the acceptance criteria set forth in this SOW does not apply to Customer Deliverables.

7. TRAVEL AND EXPENSES

7.1 Travel and Expenses 

No travel is anticipated for this SOW. In the event travel is required, Customer will be invoiced  separately for travel expenses incurred on a monthly basis pursuant to Conga’s Travel & Expense  policy, located At /legal-center/travel-expense-policy. Invoices shall be issued and  payment shall be due pursuant to the MSA terms.

8. PROJECT GOVERNANCE

During the Plan stage for the Project, the Customer and Conga will establish appropriate governance  to support effective and appropriate decision making, sign off, and escalation procedures. Governance may include the following:  

  • Project Status Meetings: Regularly scheduled with required participation from both Conga and Customer participants.

  • Project Status Reports: Regularly provided by Conga to Customer’s Project management  team, no more than weekly. 

The first level of escalation within the Project governance structure is the Customer and Conga Project managers. Any issues which cannot be resolved at this level will be escalated to the  representatives below: 

Conga Representation 

  1. Vice President, Conga Professional Services

  2. Director, Conga Professional Services 

Customer Representation 

  1. Senior Representative, To be determined by the parties (email being sufficient)

  2. Senior Representative, To be determined by the parties (email being sufficient)

Appendix B. Salesforce Platform Assumptions 

Salesforce Lightning Platform Assumptions (referred to as “Platform”) 

Language  

The user interface can only support the languages that are supported by the Platform. 

Platform Limitations 

Apttus is 100% native to the Platform. The Apttus solutions are subject to the constraints, limitations,  features and capability provided by the Platform, e.g. the limitation of uploaded files to twenty-five  (25) megabytes, 

Advanced Configuration 

“Advanced Configurations” refer to Apttus Solution components composed of the Salesforce and  software development technologies listed here: salesforce Apex, salesforce Visualforce, salesforce  triggers and JavaScript, Apttus callbacks and APIs. Apttus will make all commercially reasonable  efforts to minimize the design, development and testing of Advanced Configurations. Customer will  be responsible for the maintenance of all Advanced Configurations following Go-Live, unless  appropriate Apttus Managed services are procured. Apttus Services will achieve a code coverage of  eighty (80) percent for Apttus code exclusively. The Services included herein will not require the  modification of third-party code in Customer’s salesforce environments.  

Customer Salesforce Procured Lightning Platform Org Assumptions:  

For clarity, the assumptions below apply only in situations where Customer has procured Salesforce  Lightning Platform Org Licenses independent of Apttus for the purposes of Apttus to deliver its  product and services. If Apttus has procured the Org Licenses, then the below does not apply.  

Platform Dependencies 

As the Apttus Solution is 100% native to the Platform, the execution of this SOW is dependent on the  Customer’s configuration and management of Customer Salesforce instances in so far as the  readiness of these instances support the following standard Salesforce features, practices and  policies. 

Cumulative Code Coverage 

Cumulative code coverage in Customer's Salesforce environment cannot be guaranteed by Apttus. In  the event that Customer’s code coverage impacts the deployment of the Apttus Solution, Customer  will remediate code coverage in a timely manner. 

Customer Procured Third-party Apps and Configured Objects 

Apttus will not be responsible for servicing any third-party App running on the Salesforce platform  and servicing any Customer configured Objects, unless specified in the SOW.  

Salesforce Environments 

Customer must provide all necessary Platform environments, including sandboxes, to enable the  performance of the Project as described herein. Customer is required to license all required Platform  environments, including sandboxes, directly from Salesforce. Failure to do so will alter the expected  duration and cost of the Project implementation and require a Change Order. 

The Project is dependent upon Customer’s applicable Platform environments. Customer and Apttus  will conduct all Solution configuration, testing and deployment activities in the following three (3)  salesforce environments, as licensed from Salesforce by Customer and managed by Customer, unless  specified otherwise in the SOW:

  • Build – one (1) Salesforce sandbox environment (Developer Pro)

  • Test – one (1) Salesforce sandbox environment (bare minimum Partial Sandbox, ideal would  be the full sandbox) 

  • Production – one (1) Salesforce production environment 

While lesser varieties of salesforce sandbox environments are available, the storage capacity of a full copy sandbox is required for the Apttus Solution. Please consult salesforce materials at  help.salesforce.com for additional sandbox details.

This Conga Sign Essentials/Essentials Plus Accelerator Services Statement of Work (“SOW”) for  Professional Services, including any applicable addenda, annexes, exhibits, or other similar  agreements, constitutes a legal agreement between you, your employer, or other entity on whose  behalf you enter into this SOW (the “Customer”), and Apttus Corporation (“Conga” or Apttus”), and is  issued pursuant to the Professional Services Terms, or similar professional services agreement  (collectively, “PS Terms”), attached to the Master Subscription Services Agreement, or similar  subscription agreement (collectively, “MSSA”), by and between the parties. In the absence of existing  PS Terms between the parties, this SOW shall be governed by the Professional Services Terms located  at: /legal-center/professional-services-terms.

YOU MUST READ AND AGREE TO THIS SOW PRIOR TO RECEIVING THE PROFESSIONAL SERVICES.  BY CLICKING ON THE “ACCEPT” BUTTON, SIGNING AN ASSOCIATED ORDER OR ORDER FORM, OR  RECEIVING THE PROFESSIONAL SERVICES, YOU ARE AGREEING TO BE BOUND BY THE TERMS ON  BEHALF OF CUSTOMER. 

IF YOU ARE ENTERING INTO THIS SOW ON BEHALF OF YOUR EMPLOYER OR ANOTHER LEGAL  ENTITY, THEN YOU REPRESENT AND WARRANT THAT YOU HAVE THE AUTHORITY TO BIND THAT  ENTITY AS THE CUSTOMER. 

Conga may amend this SOW from time to time by posting an amended version at its website and  sending Customer notice thereof (an email to Customer’s Project sponsor or designated contact shall  be deemed sufficient in this case). Such amendment will be deemed accepted and become effective  thirty (30) days after such notice (the “Proposed Amendment Date”), unless Customer first gives  Conga written notice of rejection of the amendment. In the event of such rejection, this SOW will  continue in its existing form, and the amendment will become effective at the start of Customer’s  next purchase of Professional Services meant to be governed by this SOW following the Proposed  Amendment Date. Customer’s continued use of the Professional Services hereunder following the  Proposed Amendment Date will confirm Customer’s consent thereto. This Agreement may not be  amended in any other way except through a written agreement by authorized representatives of each  party. 

Whereas, Customer wishes to have Conga provide certain Professional Services pursuant to this SOW, 

For good and valuable consideration, the receipt and sufficiency of which is hereby acknowledged,  the parties agree as follows: 

Definitions: 

“Project” refers to the scope of services, including performance of all work, activities, and Deliverables,  set forth in this SOW, including any and all appendices. Notwithstanding any other provision of these  terms, timelines and hours in this SOW are estimates only. 

“Services” and “Professional Services” as used herein means Professional Services work rendered by  Conga in relation to this SOW. It is distinguished from the meaning of “Subscription Services” as used  in the MSSA.

 

1. UNDERSTANDING OF OBJECTIVES

Our understanding of Customer objectives and desired outcome is the following:

  • Implementation of Conga Sign solution within the constraints of the scope detailed below

2. SCOPE OF WORK

This section defines the scope of Professional Services to be delivered by Conga, with support from  Customer resources, under this SOW. Detailed scope and objectives will be confirmed during the define  and design phases. If changes or expanded scope are necessary, a new SOW will be needed.

2.1 Organizational Scope

The efforts assume one configuration across the organization, and no effort or time is allocated to design  or configure variations. All countries, divisions, and user roles will leverage the same data structures,  processes, and approval workflows.

2.2 Product Scope

The following Conga solutions will be configured as part of this SOW:

  • Conga Sign

2.3 Functional Use Case Scope:

The following Use Cases are in scope:

Conga Sign E Signature Functionality 

Conga Sign Essentials Accelerator Offering Configuration Scope

Conga Sign Essentials Plus Accelerator Offering Configuration  Scope

Conga Sign Installation

Conga Sign installed in Development, UAT and Production environments

Conga Sign installed in Development, UAT and Production environments

Conga Sign added to page Layout

Three (3) page layout updates 

Three (3) page layout updates

eSignature Status on Agreement

Included 

Included

Signature tags on contract templates

Three (3) Contract Templates: 3 Signature  Tags each

Three (3) Contract Templates: 3 Signature Tags each

Write-back Conga Sign Tags

None 

Six (6) Write-back Conga Sign Tags  (Field Updates) 

Conga Sign Custom Tags will write  back to parent objects directly related to the object that Conga Sign  is launching from

Auto population of recipients

None 

Three (3) Auto-populate Recipients

Environment MigrationsMigrations from Development to UAT to ProductionMigrations from Development to UAT to Production

2.4 Out of Scope 

Professional Services and/or scope not included and/or not itemized as “Scope” in this SOW are out of scope, including: 

  • Non-Conga program management

  • Data migration & legacy contracts migration

  • Data archiving

  • Development of training materials

  • Additional Languages (apart from English) and Currencies

  • Interfaces/Integrations

  • Third-Party support and related activities

  • Any scope item not explicitly listed in section ‘Use Case Scope’

  • Additional documentation that are not specified in section ‘Project Methodology and  Delivery Assurance’

  • Change Management including, but not limited to, stakeholders management; change  readiness; communications plan and execution; training plan and execution including  development of training materials; adoption tracking

  • Creation/Definition of business requirements document

  • UI Enhancement/Guidance

  • Data extraction from any source systems or hard-copy papers

  • Management and migration of Customer’s CRM records (e.g. Accounts, Contacts)

  • Automation testing

  • Performance testing

  • Automated QA Testing or automated test scripts

  • Deployment strategy, plan, and execution for non-Conga systems

  • Translation services of Conga standard and non-standard fields in different languages

  • Type of other currencies

  • Any third-party support related activities

  • Other Conga Services such as Education Services and Application Management Services (AMS)

  • Refactoring the standard Conga user flow, e.g. splitting standard pages into multiple pages,  rerouting transitions amongst standard pages, development of custom pages, development  of custom widgets.

  • Services for the migration of legacy Data (e.g. legacy Quotes, in-flight Quotes, legacy  Agreements, in-flight Agreements, and Assets) data migration, data quality, said  performance of data loads to and from the Conga solution(s) and the readiness and  configuration of the standard CRM objects/entities for which the intended solution is dependent upon.

  • Specification of eSignature software data input tags (Defining the type of “tag” and location  of the “tag”) unless otherwise defined in functional use case scope.

  • Advanced security capabilities e.g. data sharing, role/hierarchy driven sharing, permission set  driven sharing

  • Training and enablement for CRM system and platform capabilities, including creation or  delivery of user training

  • Production of Customer’s CRM reports

3. DELIVERABLES AND ACCEPTANCE CRITERIA

3.1 Deliverables 

The anticipated Deliverables provided by Conga for the scope of this SOW will be:

  • Project plan 

  • Standard getting started guide

  • Standard test scripts

  • Deployment tracker/workbook

  • Installed and configured Conga Sign solution per defined scope 

3.2 Acceptance of Conga Deliverables 

Deliverables will be produced in accordance with the Project Plan. Conga will provide early drafts when feasible to facilitate prompt review and approval. 

Customer shall have two (2) business days from the date of receipt of a Deliverable to provide final  acceptance or rejection of the Deliverable in writing. 

If Customer rejects a Deliverable, it will specify in reasonable detail each deficiency and / or  nonconformance serving as the basis of rejection in writing. Upon receipt of such Deliverable rejection  notification, Conga will promptly correct such deficiencies and / or nonconformities and re-deliver the  Deliverable for Customer’s review. Upon re-delivery of the Deliverable, Customer shall provide  notification of final acceptance or rejection in writing as soon as reasonably possible, but no later than  two (2) business days from the date of receipt. 

If Customer does not provide notice of final acceptance or rejection within two (2) business days in  writing of a Deliverable or re-delivery of a rejected Deliverable, the Deliverable will be deemed  accepted.

4. PROJECT METHODOLOGY & DELIVERY ASSURANCE

4.1 Methodology 

The following Implementation Methodology will be used for this Project. The Project methodology  includes three phases. Conga provides delivery assurance throughout the Project lifecycle as part of the  methodology.

conga-sign-essentials-essentials-plus-accelerator-methodology

Note that the Conga Sign Essentials Accelerator Package has a 1 week Define/Design, Configure, Testing  phase. 

The phases are outlined below: 

Plan and Prep - A Project kickoff readiness review is conducted. The predefined Project plan is shared, and  kickoff is held where clear Project objectives are established. Refer to section 6.4 for the list of prerequisite deliverables from Customer prior to starting the Plan Phase. These deliverables will be reviewed as part of  the kickoff readiness review. Environment readiness and access is provided  

Define/Design, Configure & Testing– This phase uses agile methodology to configure the defined scope.  Requirements and Design are defined and confirmed. Conga Sign is installed and basic setup is  completed. Template and Record Page layouts are configured. Other features are configured per scope.  User Acceptance test scripts are created. Customer to test that the system is configured according to  agreed requirements and design, and deployment plan is developed.  

Launch/Hypercare – Deployment of the solution to production and one week of Hypercare. 

Conga will utilize one or more of the following tools to support the implementation efforts. The tools are  templatized for fast and consistent implementation results. The client Project team may be granted access  for the duration of the Project. The tools that may be utilized during the Project are Microsoft Project,  Confluence, JIRA, Zephyr, Bitbucket.

5. PROJECT PLAN

Project kick-off will be planned on a mutually agreed date, based on Conga and Customer resource availability and completion of the Customer Pre-requisite Deliverables defined below.  

As of the Effective Date, the known requirements, estimates effort, and scope the following Project Plan (“Project Plan”) is anticipated for Conga solution delivery. The Project Plan will be confirmed after  the design phase. Any adjustments to the Project Plan (e.g. change in agreement type; scope  changes) may require a new SOW. 

Maximum Project Plan duration:  

  • Essentials: 2 Weeks (Customer Prep plus 1 week Define/Design/Configure to Launch plus 1  week of Hypercare).

  • Essentials Plus: 3 Weeks (Customer Prep plus 2 weeks Define/Design/Configure to Launch plus  1 week of Hypercare). 

Any extension beyond the allocated Project Plan will require a new SOW. For the avoidance of doubt, a  day is eight (8) hours, Monday through Friday, on Conga’s standard business days, excluding holidays. 

5.1 Kickoff 

Conga will contact Customer within three (3) weeks of SOW Effective Date to establish a Project start  date. The Project start date will be mutually agreed to in writing by the parties (email sufficient). 

5.2 Go-Live 

“Go-Live” refers to the on-boarding of users to the Conga Sign solution in the Production environment.

  • A single go-live event is in scope. Additional go-lives are not in scope and any functionality that  is mutually agreed to be deferred from the single go-live is no longer part of the scope of this  SOW.

  • Go-Live occurs after migration of the Conga solution to the Production environment.

  • Customer will be responsible for Go-live planning with guidance from Conga as outlined in this  SOW.

  • Conga assumes Customer’s information technology policies that govern the deployment of Conga solution to the Production environment and the go-live of new information technology,  will not extend the Project Plan described herein via a delay in the deployment or Go-Live of the Conga solution.

5.3 Hypercare Period

“Hypercare Period” refers to the period and services following the Go-Live of the Conga solution.

  • For a release of the Conga solution, the Hypercare Period begins at Go-Live and concludes after five (5) business days, i.e. one (1) week.

  • For clarity, issues identified after the Hypercare Period will be addressed per the terms set forth in Customer’s applicable subscription agreement with Conga (i.e. Customer’s purchased level of  Technical Support in the MSSA and applicable Order or Order Form). Upon completion of the  Hypercare Period, Conga will send Customer a notice (email sufficient) acknowledging SOW  Project completion.

6. RESOURCING, ROLES AND RESPONSIBILITIES

6.1 Resourcing 

Conga and Customer resources share responsibility for Project execution, as outlined in this SOW. Assigned resources are required to attend the Project kickoff, and to perform agreed activities  throughout the Project lifecycle. 

6.2 Customer Roles and Responsibilities 

Customer Roles 

Customer Responsibilities

Steering Committee Representative

  • Provide Project oversight and high-level direction

  • Guide the Project’s alignment to key objectives

  • Highest level of escalation, decision making and issue resolution

Project Manager 

  • Act as primary point of contact for Conga Project Manager

  • Coordinate all Project activities and required Customer resources

Subject Matter Expert (Business and Technical)

  • Provide business and technical expertise to the Project related to  Customer’s desired solution processes; resources that are familiar with  Customer business processes, documents, approval processes, etc.

QA Testers 

  • Develop UAT test strategy, test scenarios, and test plans

  • Execute test cases and report findings to the Project managers

System Administrators

  • Administer sandbox environment(s)

  • Manage all CRM activities required by and related to the Project

6.3 Conga Resourcing and Resource Allocations 

The following Conga roles, sometimes also referred to as “Resources”, will be allocated to the Project. This is subject to change based on further analysis and discovery through the Project stages.

Conga Staffing/Resource Roles 

Conga Responsibilities

Project/Engagement Manager

  • Helps monitor and advise

  • Performs functional and Project management activities, including management of Conga consulting team

  • Issues status reports, manages risk and issue tracking and  manages budget and schedules

Consultant 

  • Facilitates requirements session

  • Installs Conga Sign in 2 Sandboxes and Production  environments

  • Performs technical configurations

  • Provide best practices and guidance on future state process

  • Performs SIT

  • Prepares User Acceptance Test scripts

  • Provides launch and post go-live support

6.4 Pre-Requisite Deliverables 

Prior to Project start, Customer will provide Conga with Pre-Requisite Deliverables (collectively, “Pre Requisite Deliverables”): 

  • Environments are ready and test users are set up in Salesforce Dev and UAT Test Sandbox Orgs.

  • Provide system administrator access to Conga resource has system administrator access to  Development, UAT Test and Production environments.

  • Salesforce “Files” must be configured in all environments and the Files related list must be on  each Agreement/Proposal page layout

  • Test recipients are setup as Salesforce Leads or Contacts; Company test signers are identified, and email addresses provided.

  • Gather the Templates in scope, and mark-up/highlight for Signature Blocks and Writeback  fields 

6.5 Project Work Products and Activities* 

The following Work Product and Activities are minimally required for the Project:

  • Work Product: outputs to support Project delivery that do not require Customer approval

  • Activity: methodology component that is a task that does not require Customer approval

  • *Note: The below Work Product and/or Activities may result in the output of a Deliverable as  identified in Section 3.1.  

To complete the Work Products and Activities each parties’ Roles and Responsibilities are defined as  follows: 

  • R = Responsible: Conga or Customer performs the work to complete the Activity and /or Work  Product

  • A = Accountable: Conga or Customer responsible for justifying actions or decisions made to  complete the Activity and / or Work Product

  • C = Consulted -Conga or Customer whose opinions are sought by the person responsible for  the Activity and / or Work Product

  • I = Informed - Conga or Customer that should be kept up to date on progress of the Activity  and / or Work Product 

Conga and Customer are each responsible for completing their assignments, as indicated in the  following table:

Stage/Category

Activity or Work Product Description

Owner 

Type
Conga Customer
Plan

Project kick-off 

CRActivity

Project Plan 

R 

A

Work Product

Training Plan 

C 

R

Work Product

Resource management 

R 

R 

Activity

Facilitate regular Project meetings 

C 

R 

Activity

Weekly status reports 

R 

R

Work Product

Define/Configuration/SIT

Conduct requirements workshop 

R 

A, C, R 

Activity

Define functional requirements 

A, R 

C 

Activity

Configure Conga solution 

R 

C 

Activity 

Develop deployment plan 

R, C 

R 

Activity

Develop UAT Test plan/cases 

C 

R 

Activity

UAT

Migrate solution from Development Environment to UAT Environment 

R, C 

R, C 

Activity

System Navigation and walkthrough  Session 

R 

A 

Activity 

    

Conduct UAT Testing 

C 

R 

Activity 

Manage UAT Fixes 

R 

R 

Activity

Launch

UAT Sign-off 

C 

R 

Activity

Develop Hypercare Plan 

C 

R

Work Product

Go/no-go decision 

C 

R, A 

Activity

Migrate solution from UAT Environment to Production Environment

R, C 

R, C 

Activity

Hypercare

Develop support transition Project overview 

R 

R 

Activity 

Validate Status and availability of key  Deliverables 

R 

R 

Activity

Information sharing sessions to Tech  Support 

R 

A 

Activity

Disposition cases opened during  Project 

R 

C 

Activity

 

 

6.6 Customer Project Deliverables* 

During the Project, Customer is responsible for ensuring completing the following Customer  Deliverables are completed (collectively, “Customer Deliverables”) according to the Project Plan:

  • Functional Requirements

  • UAT Test Plan

  • UAT Test Cases

  • UAT Testing

  • Deployment Plan

  • Training Plan

  • Hypercare period Plan

  • Signoff on Testing

For clarity, the acceptance criteria set forth in this SOW does not apply to Customer Deliverables.

7. TRAVEL AND EXPENSES

7.1 Travel and Expenses 

No travel is anticipated for this SOW. In the event travel is required, Customer will be invoiced separately for travel expenses incurred. Payment is due net thirty (30) days from invoice. Invoices may be sent to the Customer via electronic mail. For clarity, travel and expenses are not included in the fees.

8. PROJECT GOVERNANCE

During the Plan stage for the Project, the Customer and Conga will establish appropriate governance  to support effective and appropriate decision making, sign off, and escalation procedures. Governance may include the following:  

  • Project Status Meetings: Regularly scheduled with required participation from both Conga and Customer participants.

  • Project Status Reports: Regularly provided by Conga to Customer’s Project management  team, no more than weekly. 

The first level of escalation within the Project governance structure is the Customer and Conga Project managers. Any issues which cannot be resolved at this level will be escalated to the  representatives below: 

Conga Representation 

  1. Vice President, Conga Professional Services

  2. Director, Conga Professional Services 

Customer Representation 

  1. Senior Representative, To be determined by the parties (email being sufficient)

  2. Senior Representative, To be determined by the parties (email being sufficient)

Appendix B. Salesforce Platform Assumptions 

Salesforce Lightning Platform Assumptions (referred to as “Platform”) 

Language  

The user interface can only support the languages that are supported by the Platform. 

Platform Limitations 

Apttus is 100% native to the Platform. The Apttus solutions are subject to the constraints, limitations, features and capability provided by the Platform, e.g. the limitation of uploaded files to twenty-five (25) megabytes, 

Advanced Configuration 

“Advanced Configurations” refer to Apttus Solution components composed of the Salesforce and  software development technologies listed here: salesforce Apex, salesforce Visualforce, salesforce  triggers and JavaScript, Apttus callbacks and APIs. Apttus will make all commercially reasonable  efforts to minimize the design, development and testing of Advanced Configurations. Customer will  be responsible for the maintenance of all Advanced Configurations following Go-Live, unless  appropriate Apttus Managed services are procured. Apttus Services will achieve a code coverage of eighty (80) percent for Apttus code exclusively. The Services included herein will not require the  modification of third-party code in Customer’s salesforce environments.  

Customer Salesforce Procured Lightning Platform Org Assumptions:  

For clarity, the assumptions below apply only in situations where Customer has procured Salesforce  Lightning Platform Org Licenses independent of Apttus for the purposes of Apttus to deliver its  product and services. If Apttus has procured the Org Licenses, then the below does not apply.  

Platform Dependencies 

As the Apttus Solution is 100% native to the Platform, the execution of this SOW is dependent on the  Customer’s configuration and management of Customer Salesforce instances in so far as the  readiness of these instances support the following standard Salesforce features, practices and  policies. 

Cumulative Code Coverage 

Cumulative code coverage in Customer's Salesforce environment cannot be guaranteed by Apttus. In  the event that Customer’s code coverage impacts the deployment of the Apttus Solution, Customer  will remediate code coverage in a timely manner. 

Customer Procured Third-party Apps and Configured Objects 

Apttus will not be responsible for servicing any third-party App running on the Salesforce platform  and servicing any Customer configured Objects, unless specified in the SOW.  

Salesforce Environments 

Customer must provide all necessary Platform environments, including sandboxes, to enable the  performance of the Project as described herein. Customer is required to license all required Platform  environments, including sandboxes, directly from Salesforce. Failure to do so will alter the expected  duration and cost of the Project implementation and require a Change Order. 

The Project is dependent upon Customer’s applicable Platform environments. Customer and Apttus  will conduct all Solution configuration, testing and deployment activities in the following three (3)  salesforce environments, as licensed from Salesforce by Customer and managed by Customer, unless  specified otherwise in the SOW:

  • Build – one (1) Salesforce sandbox environment (Developer Pro)

  • Test – one (1) Salesforce sandbox environment (bare minimum Partial Sandbox, ideal would  be the full sandbox) 

  • Production – one (1) Salesforce production environment 

While lesser varieties of salesforce sandbox environments are available, the storage capacity of a full copy sandbox is required for the Apttus Solution. Please consult salesforce materials at  help.salesforce.com for additional sandbox details.

  • LinkedIn
  • Twitter
  • Facebook
  • Instagram
  • Youtube
    • Platform
    • Advantage Platform
    • Document Automation
    • Contract Lifecycle Management
    • Revenue & Commerce
    • RLM solution
    • Propose and quote
    • Negotiate and execute
    • Manage and fulfill
    • Renew and expand
    • Conga and Salesforce
    • Integrations
    • Pricing
    • Resources
    • Blogs
    • Customer stories
    • On-demand webinars
    • Guides
    • All resources
    • Training
    • Professional services
    • Product documentation
    • Developer hub
    • Support
    • Community
    • Customer Community
    • Customer advocacy
    • Partner program
    • Become a partner
    • Partner directory
    • Partner Community
    • Events & live webinars
    • Company
    • About
    • The Conga Way
    • Careers
    • Newsroom
    • Contact us
  • English
    • Deutsch
    • Français

© 2025 All Rights Reserved

Footer Utility

  • Legal
  • Privacy
  • System Status