# Implementation: How a Revomo Activation Runs

> How a Revomo activation is scoped, run and judged: the Planning & Design Workshop, gated phases, the five Activation Criteria, what each side provides, and the plan behind it.

Source: https://revomo.ai/implementation/

---

Implementation

## Scoped at a workshop. Done when the criteria are met.

Every activation runs on an Activation and Success Plan, Schedule 1 to the Order Form: the objective, the modules and workspaces in scope, the criteria that say when a module is activated, what each side provides, and how success continues afterwards. It supports activation alignment and amends no agreement.
[Request the plan template](https://revomo.ai/contact/?source=implementation&plan=Document%20request%3A%20Activation%20and%20Success%20Plan%20template)[Evaluation guide](https://revomo.ai/evaluate/)

- Approach
- Scope
- Criteria
- Who does what
- Boundaries
- Questions

Template

Activation & Success Plan

Schedule 1 to the Order Form. Supports activation alignment only.
- 01 Activation Objective
- 02 Activation Approach Planning & Design Workshop → design alignment → activation window per module
- 03 Deployment Scope
Seq. | Module | Initial use case | Systems | Users |
1 | | | | |
2 | | | | |

Documented by Revomo at the workshop, confirmed by the Subscriber. Does not amend the Order Form, Subscription Agreement, SLA or DPA.

- Included **No separate implementation fee** Standard Activation for the use cases in the Deployment Scope is included in the subscription, bounded per module and workspace.
- Gated **A module is activated when five criteria are met** Data available, use case configured, outputs validated, users enabled, production path active. Each phase before that ends at a gate you can see.
- Alignment **A plan, not an amendment** Workshop outputs documented by Revomo and confirmed by you. Nothing in it changes the Order Form or the agreements.

01 · Approach

### A workshop first. Then one gate at a time.

Activation begins with a Planning & Design Workshop, run jointly, that confirms use case priority, sequencing, workspaces, data sources and readiness, the activation approach and an activation window for each module. Its outputs are the design alignment. Modules may be activated sequentially or in parallel.

You

Both

Revomo

Gate

01 **Scope agreed** Data & Context Studio

- Executive sponsor and core team: pricing, finance, IT or ERP owner
- List of source systems: ERP, CRM, CPQ, pricing spreadsheets
- Reported net sales and margin for a recent period
- The pricing decision you most want help with

- Kickoff: success criteria and meeting cadence
- Data inventory: what lives where, keys, owners, refresh

- Organization and workspace set up, users invited

Gate **Finance tie-out number agreed**

02 **Data trusted** Data & Context Studio

- Extracts or connector access for each source
- Field definitions, or someone who knows the tables
- Finance time to review the tie-out

- Staging cleared, profiling reviewed
- Connectors or a refresh schedule set up and run once end to end

- Datasets loaded, typed and tagged

Gate **Totals tie to the finance number**

03 **Waterfall agreed** Data & Context Studio

- The waterfall elements you recognize: discounts, rebates, freight, terms
- Discount and rebate policies, thresholds and matrices
- How freight is charged and costed
- Who signs off the definitions

- Definitions and exclusions agreed in writing

- Datamart view from list price to pocket margin
- Discount policy held as rulesets

Gate **You sign off the definitions**

04 **Module phases** One per module in scope. Analytics & Insights shown

- Time with the pricing lead to review findings
- Someone who can approve a pricing action
- Owner and date for the action

- One actionable insight picked and sized

- Starter analyses on your own data

Gate **Action approved by you**

05 **Transition** Your team runs and changes Revomo without us

- Named administrators
- Time for training sessions
- A configuration change made without our help

·

- Administrators trained on datasets, views, models and rulesets
- Team trained on the support process
- Handover to the Customer Success cadence

Gate **A configuration change made unaided**

Every activation runs the three Data & Context Studio phases, then one phase per module in scope, then transition. A phase closes at its gate, stated as an outcome you can check; the next starts when the gate is met. Lanes are who brings what, not time.

#### Each module has its own gate

The module phase repeats for each module in the Deployment Scope. Its gate is the first real outcome in that module, not a deliverable from us.

- Analytics & Insights **A sized action approved by you**
- Planning & Forecasting **The plan ties to the finance budget**
- Predictive Modeling **The model holds up on your past data**
- Decision Optimization **Optimization guidance actioned**
- Price Management **The first live price change**
- Quoting & Deal Pricing **The first quote approved in Revomo**
- Contract Pricing & Renewals **The first renewal issued from Revomo**
- Rebates & Incentives **Accruals validated by finance**

02 · Scope

### What is in scope, recorded as a table.

Section 03 of the plan lists each module in sequence with its initial use case, business segment, key related systems and initial users, and names the production workspaces it is activated in. Standard Activation is bounded to what is recorded here.

Illustrative row Sequence | Module | Initial use case | Business segment | Key related systems | Initial users |
1 | Analytics & Insights | Price and margin leakage by customer and product | Fittings, North America | ERP, CRM, pricing spreadsheets | Pricing and finance |
| | | | | |

#### Workspaces in scope

The modules are activated in the production workspaces named in the plan: the three included in the subscription, plus any ordered under the Order Form. Further workspaces are named at design alignment or later in the term, each with a short design alignment of its own. One sandbox copy of each production workspace is available at any time and is not counted.

#### Scope principle

The Deployment Scope defines the initial activation priority and the activation services Revomo provides. It does not limit your licensed use of Revomo: you may self-configure additional use cases, users, business units and configurations with standard capabilities at any time, supported through the Customer Success Process.

03 · Criteria

### A module is activated when five things are true.

The criteria apply per module, per workspace. They are outcomes you can check, not milestones on our side.

- **Data available** The agreed data required for the initial use case is available in Revomo.
- **Use case configured** The initial priority use case is configured using standard Revomo capabilities.
- **Outputs validated** Representative outputs and workflows have been reviewed and validated.
- **Users enabled** Intended users, roles and permissions are enabled.
- **Production path active** The agreed production workflow, output or publishing path is active.

If you neither confirm activation nor identify a material gap in writing within the agreed review window after Revomo notifies that the criteria are met, or if you begin production use of the module, the module is considered activated.
Standard Activation

The configuration and enablement of the initial use cases listed in the Deployment Scope, in the workspaces named there, using no-code Revomo capabilities and Subscriber-provided data, up to the point each module meets the Activation Criteria.

04 · Who does what

### You provide data, access, decisions and a lead. Revomo configures, loads and proves the tie-out.

#### You Activation timing depends on your side providing, in good time

Data and access
Extracts, connections or credentials for the systems in the Deployment Scope, in the agreed format and cadence.

A named activation lead
A single point of contact with authority to coordinate internal resources and make day-to-day decisions.

Subject-matter input
Pricing, product, finance and IT stakeholders in the Planning & Design Workshop and the review and validation sessions.

Decisions and approvals
Business rules, thresholds and configuration choices confirmed within the agreed review window.

Validation
Review of representative outputs and workflows, with written confirmation or identified gaps within the review window.

Environment readiness
User accounts, single sign-on, and any internal security or IT approvals your users need to access Revomo.

Source system stability
Notice of planned changes to source systems, data structures or requirements during activation.

#### Revomo Revomo, within Standard Activation

- Runs the Planning & Design Workshop with you and documents its outputs
- Sets up the organization and workspaces and invites your users
- Loads, profiles, types and tags the data and ties the totals to your finance number
- Configures the initial use cases with standard capabilities, on your data
- Enables users, roles, permissions and the production path, and tells you when the criteria are met
- After activation, guidance and best practice through the Customer Success Process

Finance owns the tie-out number the data is checked against. IT or the ERP owner provides the extracts or connections and the single sign-on setup.

05 · Boundaries

### Where Standard Activation ends, and what continues after it.

Outside Standard Activation
- Customer-owned system development, for example changes to your ERP
- Bespoke Revomo product development
- Major data cleansing or remediation performed on your behalf
- Third-party services or licences
- Re-work from changes to your source systems, data structures or requirements after design alignment
- Activation by Revomo of a workspace beyond those named, which is agreed separately as Workspace Activation

Standard Activation is a bounded, one-time engagement per module in each workspace named in the Deployment Scope. Once a module is activated there, further configuration work by Revomo comes through the Customer Success Process or a separate agreement. If your dependencies are not met and activation extends well beyond the agreed window, the parties re-plan, and additional Revomo effort may be agreed separately.

#### Ongoing success

- **Customer Success Process** Periodic guidance, enablement and best-practice recommendations through the term, in addition to product support. Advisory by nature: it does not include Revomo building new use cases or integrations on your behalf unless agreed in writing.
- **Business reviews** Adoption, realized outcomes and next opportunities reviewed on a cadence you agree, monthly or quarterly.
- **Expansion** Additional modules, teams, business units or geographies as value is demonstrated. A new business unit or acquired company comes in as a workspace. Material Revomo effort is agreed through a statement of work.

FAQ

### Common questions

How long does an activation take?

It depends on the modules in scope, how ready the data and access are, and how quickly decisions come back. The Planning & Design Workshop confirms scope, sequencing, data readiness and an activation window for each module, and that window, with the dependencies beside it, is recorded in the Activation and Success Plan for your deployment.
Who owns the plan?

Both sides. The workshop outputs are documented by Revomo and confirmed by you, and that is the design alignment the plan refers to. The plan supports activation alignment only: it does not amend the Order Form, the Subscription Agreement, the SLA or the DPA. An optional acknowledgment records that it reflects the current working alignment.
What if our data is not clean?

Rows that cannot be parsed land in staging with their original values, where they are reviewed and resolved, fixed at source or handled in an agreed, documented way. The data phase does not close until the totals in Revomo tie to the finance number you agreed. Major data cleansing or remediation performed on your behalf is outside Standard Activation and is agreed separately if the data needs it.

[Data & Context Studio →](https://revomo.ai/product/data-context-studio/)
Do we need developers on our side?

Not for Standard Activation, which uses no-code Revomo capabilities and the data you provide. Your IT or ERP owner provides extracts, connections or credentials for the systems in the Deployment Scope, plus user accounts, single sign-on and any internal approvals. Customer-owned system development, for example changes to your ERP, is outside Standard Activation.
What does activation cost?

Standard Activation for the use cases in the Deployment Scope is included in the subscription with no separate implementation fee. It is a bounded, one-time engagement per module in each workspace named there. Activation of a workspace beyond those named is agreed separately as Workspace Activation; expansion that needs material Revomo effort is agreed through a statement of work.

[Pricing →](https://revomo.ai/pricing/)
Can we add use cases ourselves after activation?

Yes. The Deployment Scope sets the initial activation priority and the activation services Revomo provides; it does not limit your licensed use. You may self-configure additional use cases, users, business units and configurations with standard capabilities at any time, with guidance through the Customer Success Process, or agree Revomo-delivered expansion separately.

### See the plan before you commit to it.

The template is provided on request. Your own plan is drafted at the Planning & Design Workshop and confirmed by you before activation starts.
[Request the plan template](https://revomo.ai/contact/?source=implementation&plan=Document%20request%3A%20Activation%20and%20Success%20Plan%20template)[Pricing](https://revomo.ai/pricing/)
