# Activation and Success Plan > The Revomo Activation and Success Plan, the companion to the Order Form. Deployment scope, Standard Delivery, who does what on both sides, which systems, by when, and the number the deployment is measured against. Fill it in and export a Word document. Source: https://revomo.ai/commercial-transparency/activation-and-success-plan/ --- [Commercial transparency](https://revomo.ai/commercial-transparency/) › Activation and Success Plan Companion document · Series 2026 ## Activation and Success Plan The first ninety days, on the record: what is deployed, who does what on both sides, which systems, by when, and the number the deployment is measured against. Versioned, not signed. Nothing you type leaves this browser. Activation & Success Plan **Series 2026** Tasks done **0 / 0** Phase **Connect** [Order Form →](https://revomo.ai/commercial-transparency/subscription-agreement/order-form/) Contents Reset Print / PDF Download .docx **Prefilled from the Order Form draft in this browser:** subscriber, order date, sponsor, applications, start date and term. Change those on the [Order Form](https://revomo.ai/commercial-transparency/subscription-agreement/order-form/), not here. #### Plan identification Subscriber | | Order Form Date | | Plan version | a new version at each milestone; the change log in Section 13 says what moved | Plan date | | Status | Draft Active Closed | This Activation and Success Plan is the working record of how the order identified above is deployed, delivered and adopted. It is kept by Licensor and Subscriber together, versioned as the deployment progresses, and not signed. It does not modify the [Order Form](https://revomo.ai/commercial-transparency/subscription-agreement/order-form/) or the Agreement; nothing recorded here amends a Fee, a licence or an obligation under them. #### Owners Role | Side | Name and title | Email | Executive sponsor | Subscriber | | | Implementation lead | Subscriber | | | Delivery lead | Revomo | | | Customer Success Manager | Revomo | | | ### 1 Overview #### 1.1 The goal The outcome in Subscriber’s words. One or two sentences: the number, the time, the decision it changes. #### 1.2 Success criteria Three at most, each with a number and a date. These are what Section 8 measures. Criterion | Baseline | Target | By | | | | | | | | | | | | | | | | | #### 1.3 Key dates Kickoff | | Data connected | | First application live | | Production deployment | | End of hypercare | | First value review | | Target dates assume timely satisfaction of the Subscriber responsibilities in Section 3.3 and the Subscriber tasks in Section 5. Delays attributable to Subscriber or to third-party systems move the dates here, not the Fees. ### 2 Deployment Scope This Section identifies what Subscriber is implementing first. Standard Delivery under Section 3 is scoped to what is recorded here. #### 2.1 Subscription, from the Order Form Subscribed applications | | Service Start Date | | Initial Term | months | The [Order Form](https://revomo.ai/commercial-transparency/subscription-agreement/order-form/) grants the licence and sets the fees; this plan sets what is implemented first and how. #### 2.2 Deployment details Business unit(s) | | Geographies | | Standard integrations included | itemised in Section 7.1 | Data residency | United States Other | Standard Integration **Standard Integration** means an integration using a generally supported Revomo integration pattern, connector, API, database extract or file-based exchange, without material customer-specific software development. Bespoke integrations, customer-specific middleware, custom ERP extensions and substantial transformation logic are outside Standard Delivery and are addressed under Section 3.4. International transfers of Personal Data, where any are expected, are governed by Exhibit C and are not recorded here. #### 2.3 Initial use cases Margin Leakage & Price Realization Cost Recovery & Repricing Price Management Pricing Optimization Commercial Planning Quote & Deal Management Rebates / SPAs / Chargebacks Contract Pricing Licence rights and implementation scope Initial use cases define the initial Standard Delivery scope and do not restrict Subscriber’s licensed use of the subscribed applications after deployment. The Order Form grants the licence; this Section sets what is implemented first. ### 3 Standard Delivery #### 3.1 Included scope Standard Delivery Standard Delivery is included in the Subscription Fees under the Order Form and consists solely of the implementation services expressly described in the Standard Delivery Scope below, performed for the deployment scope identified in Section 2. #### 3.2 Standard Delivery Scope Standard Delivery | Included | Initial use cases | Those selected in Section 2.3 | Business units | Those listed in Section 2.2 | Source systems | Those itemised in Section 7.1 | Standard integrations | Those itemised in Section 7.1, within the count in Section 2.2 | Application configuration | The subscribed applications in Section 2.1 | Environment setup | Standard environment setup | Commercial Data & Context | Standard configuration | Initial data load | Standard data mapping and initial load | Workflows, roles and permissions | Standard workflows for the selected use cases | Business validation | Standard validation of the selected use cases | Enablement | Administrator and end-user enablement | Production deployment | Standard production deployment | Hypercare | weeks from production deployment | #### 3.3 Subscriber Responsibilities Subscriber will timely provide, at no cost to Licensor: - Required source data in a form reasonably usable by Licensor. - System credentials and access for the source systems identified in Section 7. - Technical contacts with authority over the relevant systems. - Business subject matter experts for the initial use cases. - Mapping and business-rule decisions. - Validation feedback within the agreed review windows. - Required approvals and sign-offs. - Access to relevant third-party systems, including any consents required from third-party vendors. Effect on dates Target implementation dates in this plan assume timely satisfaction of Subscriber dependencies. Delays attributable to Subscriber or to third-party systems may result in corresponding adjustments to implementation dates without adjustment to Fees. #### 3.4 Outside Standard Delivery Requires an SOW or amendment The following are not included and require a mutually executed statement of work or an Order Form amendment: custom development; bespoke integrations, customer-specific middleware, custom ERP extensions and substantial transformation logic; material data remediation; custom machine-learning or model development; custom optimization development; modifications to Subscriber systems; additional training sessions, custom training curriculum, on-site enablement and change-management programs; and any other services outside the Standard Delivery Scope. Optional Professional Services are planned in Section 11. ### 4 Progress Derived from the task status in Section 5. A phase is done when every task in it is done, and blocked when any task is. Phase | Aim | Tasks done | Status | Target date | Connect | Sources bound, data loaded, staging cleared | 0 / 7 | Not started | | Configure | Use cases become workflows, roles, models and presets | 0 / 4 | Not started | | Validate | Each use case proven against the current process | 0 / 4 | Not started | | Launch | Production, enablement, hypercare | 0 / 5 | Not started | | Prove | Realized against modeled, on the record | 0 / 5 | Not started | | ### 5 Plan Every task has an owner on one side or both, a due date and a status. The Subscriber tasks are the responsibilities in Section 3.3, dated; the Revomo tasks are the Standard Delivery scope in Section 3.2, dated. Add tasks as the deployment needs them. #### 5.1 Connect Sources bound, data loaded, staging cleared Task | Owner | Due | Status | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | Add a task #### 5.2 Configure Use cases become workflows, roles, models and presets Task | Owner | Due | Status | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | Add a task #### 5.3 Validate Each use case proven against the current process Task | Owner | Due | Status | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | Add a task #### 5.4 Launch Production, enablement, hypercare Task | Owner | Due | Status | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | Add a task #### 5.5 Prove Realized against modeled, on the record Task | Owner | Due | Status | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | Add a task ### 6 Team Both sides by role, including the contacts that do not belong in a signed order because they change: the technical lead, support administrators, data protection and security incident contacts. The billing and notices contacts stay on the Order Form. Role | Side | Name and title | Email | Phone | Executive sponsor | Subscriber | | | | Implementation lead | Subscriber | | | | Technical lead | Subscriber | | | | Support administrator | Subscriber | | | | Support administrator | Subscriber | | | | Data protection contact | Subscriber | | | | Security incident contact | Subscriber | | | | Business subject matter expert | Subscriber | | | | Delivery lead | Revomo | | | | Customer Success Manager | Revomo | | | | Support escalation | Revomo | | | | | Subscriber Revomo | | | | Add a person ### 7 Systems and Data #### 7.1 Source systems and integrations Each system with its direction and integration method, within the count in Section 2.2. Standard Integration is defined in Section 2.2; anything bespoke is outside Standard Delivery and needs a statement of work. System | Direction | Integration method | Owner | Status | | | | Revomo Subscriber Both | Not started In progress Done Blocked | | | | Revomo Subscriber Both | Not started In progress Done Blocked | | | | Revomo Subscriber Both | Not started In progress Done Blocked | | | | Revomo Subscriber Both | Not started In progress Done Blocked | Add a system #### 7.2 Environment Hosted at | | Identity provider and single sign-on | | Organization and workspaces | | Data residency is recorded in Section 2.2. Personal Data and international transfers are governed by Exhibit C, not recorded here. #### 7.3 Initial data load Source | Scope | History depth | Refresh cadence | Owner | | | | | Revomo Subscriber Both | | | | | Revomo Subscriber Both | | | | | Revomo Subscriber Both | Add a source Rows that fail to load land in staging and are cleared in the Connect phase, not silently dropped. Material data remediation is outside Standard Delivery (Section 3.4). ### 8 Success Measures The baseline is captured before go-live and the target is the one in Section 1.2. The week-twelve review compares what each price action realized on the invoice with what was modeled; it is the first entry in the record this deployment is judged by. Measure | Baseline | Target | Review date | | | | | | | | | | | | | | | | | | | | | | | | | Add a measure Week 4 review | | Week 8 review | | Week 12 value review | realized against modeled, per price action | ### 9 Enablement Session | Audience and roles | Date | Status | | | | Not started In progress Done Blocked | | | | Not started In progress Done Blocked | | | | Not started In progress Done Blocked | | | | Not started In progress Done Blocked | Add a session Administrator and end-user enablement are included in Standard Delivery. Additional sessions, a custom curriculum and on-site enablement are separately scoped (Section 3.4). The [field guides](https://revomo.ai/field-guides/) are the reference material. ### 10 Support and Reviews Designated administrators | Authorized to submit support requests and receive incident communications under Exhibit B, Section 10. | Support channel | As designated under Exhibit B, Section 6. Standard Support is included; Priority Support applies only if elected in Order Form Section 3.2. | Escalation path | | Named success contact | | Business review cadence | Quarterly Semiannual As agreed | ### 11 Optional Professional Services Services planned here are provided at additional cost and are separate from Standard Delivery and from the Subscription Fees. They are contracted by a mutually executed statement of work or an Order Form amendment, and invoiced on the basis agreed there; this table records what is planned, by whom, and when. Service | Scope / reference | Fee (USD) | Billing basis | Status | | | | | Not started In progress Done Blocked | | | | | Not started In progress Done Blocked | Total planned Professional Services | $0 | | | | | | Not started In progress Done Blocked | Add a line Suggested: Business consulting, Technology consulting, Value consulting, Data services, Additional enablement. ### 12 Risks and Dependencies Risk or dependency | Owner | Mitigation | Status | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | | Revomo Subscriber Both | | Not started In progress Done Blocked | Add a risk ### 13 Change Log Version | Date | Who | What changed | | | | | | | | | | | | | | | | | Add an entry #### Companion documents - [Order Form](https://revomo.ai/commercial-transparency/subscription-agreement/order-form/), Exhibit A: the applications, fees, term and capacity this plan delivers against. - [Service Level Agreement](https://revomo.ai/commercial-transparency/subscription-agreement/service-level-agreement/), Exhibit B: support tiers, severity levels and incident communications. - [Data Processing Addendum](https://revomo.ai/commercial-transparency/subscription-agreement/data-processing-addendum/), Exhibit C: Personal Data, security measures and transfers. - [Standard Capacity Schedule](https://revomo.ai/commercial-transparency/standard-capacity/): the operating allowances the subscription includes. Contents