Evaluation guide

The questions your evaluation will ask. Answered in order, with sources.

For the IT, security, data and finance people who review Revomo: what connects, what data it needs, how it is protected, what it asks of your team, and how a deployment runs. Each answer names the page or document it comes from.

Evaluation guideHow this page works
01 · Systems integration

Which integration patterns are supported?

Three: supported connectors (today Databricks, Salesforce and Google Drive), the Revomo API, and file exchange in CSV or Excel. Connected sources sync on demand or on a schedule, from hourly to monthly. Other systems are reached through the API or files. The method for each of your systems is confirmed at the Planning & Design Workshop and recorded with the Deployment Scope of the Activation and Success Plan.

Source: Governance & Security FAQ; Data & Context Studio, Connect; Activation and Success Plan, sections 02 and 03Recorded in your plan
All answers in this area
02 · Data requirements

What data does a first activation need?

The sources behind the modules and use cases in scope, listed with each module in the Deployment Scope; extracts, connections or credentials then follow in the agreed format and cadence. For margin and pricing work that starts with transaction lines and the product, customer, cost and price records behind them. A margin assessment runs on extracts alone, with no integration.

Source: Plan sections 03 and 05; /margin-assessment/Recorded in your plan
All answers in this area
03 · Security and compliance

Where is Revomo hosted, and where is our data processed?

On Amazon Web Services in the United States, in a multi-availability-zone configuration, with production separated from development and staging. The application database is MongoDB Atlas, hosted in AWS. Subprocessors, what each does and where each is located are listed in Annex 3 of the Data Processing Addendum. Contact us to review residency or deployment requirements.

Source: DPA Annex 2 §4 to 5, Annex 3; Governance & Security FAQ
All answers in this area
04 · Your team

What does Revomo do?

Standard Activation: Revomo 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 and the production path; and tells you when the Activation Criteria are met. Afterwards, guidance through the Customer Success Process. No separate implementation fee.

Source: Plan sections 02, 04 and 06; activation phases 01 to 03
All answers in this area
05 · Timeline

What are the phases?

Three for the foundation, which every activation runs: scope agreed, closing when the finance tie-out number is agreed; data trusted, closing when totals in Revomo tie to that number; waterfall agreed, closing when you sign off the definitions. Then one phase per module in scope, each with its own gate, for example the first live price change for Price Management. Then transition: your team makes a configuration change unaided.

Source: Activation phases; Plan section 04
All answers in this area
  • SourcedEach answer names its sourceA page on this site, the Activation and Success Plan, or an agreement your reviewers can request.
  • Per deploymentSome answers are settled in your planWhich modules, systems, workspaces and activation windows apply to you are recorded in the Activation and Success Plan at the Planning & Design Workshop, not promised here.
  • DocumentsAgreements on requestThe Trust Center is public. The agreements and the SOC 2 report are provided on request; the documents section says how.
01 · Systems integration

What connects, in which direction, and how.

Revomo reads from the systems that run the business and publishes approved results back to them. It does not replace an ERP, CRM, CPQ or planning system. The figure shows the patterns; the plan records which one each of your systems uses.

  1. 01Systems integration5
  2. 02Data requirements6
  3. 03Security and compliance10
  4. 04Your team6
  5. 05Timeline5
Connectors named are the ones available today. Other systems connect through the API or files; the method is agreed per system.

How Revomo connects: the three inbound patterns, the approval gate, and the outbound push, export and publish. Categories on the left are kinds of system, not connector claims.

  1. Which integration patterns are supported?

    Three: supported connectors (today Databricks, Salesforce and Google Drive), the Revomo API, and file exchange in CSV or Excel. Connected sources sync on demand or on a schedule, from hourly to monthly. Other systems are reached through the API or files. The method for each of your systems is confirmed at the Planning & Design Workshop and recorded with the Deployment Scope of the Activation and Success Plan.

    Source: Governance & Security FAQ; Data & Context Studio, Connect; Activation and Success Plan, sections 02 and 03Recorded in your plan
  2. How do approved prices get back into our systems?

    Through the same patterns. An approved price list can be pushed to Salesforce price book entries or a Databricks table, exported as CSV, or published as a formatted document or a shareable link. Nothing is pushed, exported or published until the price list is approved, and each push reports how many records were written and rejected.

    Source: Governance & Security, Integrations & operations; evidence row 12
  3. Our ERP has no connector. What then?

    Standard Activation uses no-code Revomo capabilities and the data you provide. For an ERP without a connector that is a scheduled extract to a file location or a data platform Revomo connects to, in the format and cadence agreed at the workshop. Customer-owned system development and bespoke Revomo development are outside Standard Activation and are agreed separately.

    Source: Activation and Success Plan, sections 05 and 06Recorded in your plan
  4. Does it sync in real time?

    No. Syncs run on a schedule or on demand; Salesforce syncs incrementally and the other connectors refresh in full. Approved changes are published back through configured workflows, not streamed. If a step in your process needs a shorter cycle than a scheduled sync, raise it in review so the plan records how it is met.

    Source: Data & Context Studio, Connect; docs/faq-standard.md, "Integrations"
  5. How do we authenticate to the API?

    As an authenticated user of your organization, with that user's permissions. SFTP endpoints and standalone API keys are not part of the supported patterns; if your standard requires one, raise it in review so it is recorded in the plan rather than assumed.

    Source: Governance & Security evidence, row 12
02 · Data requirements

What data it needs, how it loads, and what happens to rows that fail.

Revomo works from the records your commercial decisions already use: transaction lines, product and customer masters, costs, price lists and agreements. Which sources the first solution needs, from which system and how far back, is recorded in the plan before work starts.

  1. 01Systems integration5
  2. 02Data requirements6
  3. 03Security and compliance10
  4. 04Your team6
  5. 05Timeline5

The Staging tab, illustrative data: three rows held with their issue, the failing value marked, and a bulk fix ready to apply. Nothing in staging has reached the dataset.

  1. What data does a first activation need?

    The sources behind the modules and use cases in scope, listed with each module in the Deployment Scope; extracts, connections or credentials then follow in the agreed format and cadence. For margin and pricing work that starts with transaction lines and the product, customer, cost and price records behind them. A margin assessment runs on extracts alone, with no integration.

    Source: Plan sections 03 and 05; /margin-assessment/Recorded in your plan
  2. How does data get in, and how is it checked?

    By connector, by file or through the API. Files are CSV or TSV; for an Excel workbook you choose the sheets in File Manager and each becomes a file ready to import. On import the columns are mapped and reviewed: names, types, tags and the key, with types suggested from the data.

    Source: Data & Context Studio, Connect
  3. What happens to rows that fail?

    They are not dropped silently. Each column parses strictly or leniently: a strict column sends failing values to staging, where they are reviewed, fixed and promoted; a lenient column leaves the value empty. An import with rows in staging is a partial load, and the count says so. Staging is cleared before the data phase closes, and that phase closes only when the totals in Revomo tie to the finance number you agreed.

    Source: Data & Context Studio, Connect; activation phases 01 and 02
  4. Who prepares the data?

    You provide extracts, connections or credentials in the agreed format and cadence, field definitions or someone who knows the tables, and the decisions on rules and thresholds. Revomo loads, profiles, types and tags the data and ties the totals to your finance number. Major data cleansing or remediation on your behalf is outside Standard Activation and is agreed separately.

    Source: Plan sections 05 and 06; activation phase 02Recorded in your plan
  5. How much data can it hold?

    The Standard Capacity Schedule sets the allowances a subscription includes, in four categories: data and processing, integrations and APIs, modeling and optimization, and AI and agents. There is no automatic or retroactive overage charge; sustained use above an allowance is reviewed with you and additional capacity agreed by Order Form amendment.

    Source: /pricing/ FAQ; Standard Capacity Schedule
  6. Does Revomo keep a history of changes?

    Where you turn it on. Row history is enabled per dataset or price list and kept for the period set there. Separately, each price list carries a lifecycle timeline (who did what, from which state to which), and lineage shows what every column and price list depends on.

    Source: Governance & Security evidence, row 6
03 · Security and compliance

How the data is protected, who can act, and what you can verify.

The Governance & Security page carries the full account with its evidence. These are the answers a security questionnaire asks for first; each names the page or the agreement that states it.

  1. 01Systems integration5
  2. 02Data requirements6
  3. 03Security and compliance10
  4. 04Your team6
  5. 05Timeline5
OrganizationNorthline
Pricing managerNorth AmericaExample configuration
Pricing manager in the North America workspace: permissions by resource
Resourceviewcreateupdatedeleteexport
Price ListsAllowedAllowedAllowedNot allowedAllowed
Pricing ModelsAllowedNot allowedNot allowedNot allowedNot allowed
DatasetsAllowedNot allowedNot allowedNot allowedNot allowed
ViewsAllowedAllowedAllowedNot allowedNot allowed
Rule EngineAllowedNot allowedNot allowedNot allowedNot allowed

Lifecycle authorityCan Submit. Approve is assigned to Finance.

Pricing analystEuropeExample configuration
Pricing analyst in the Europe workspace: permissions by resource
Resourceviewcreateupdatedeleteexport
Price ListsAllowedAllowedAllowedNot allowedNot allowed
Pricing ModelsAllowedNot allowedNot allowedNot allowedNot allowed
DatasetsAllowedNot allowedNot allowedNot allowedNot allowed
ViewsAllowedAllowedAllowedNot allowedNot allowed
Rule EngineAllowedNot allowedNot allowedNot allowedNot allowed

Lifecycle authorityCan Submit. No lifecycle approvals.

Finance reviewerFinanceExample configuration
Finance reviewer in the Finance workspace: permissions by resource
Resourceviewcreateupdatedeleteexport
Price ListsAllowedNot allowedNot allowedNot allowedAllowed
Pricing ModelsAllowedNot allowedNot allowedNot allowedNot allowed
DatasetsAllowedNot allowedNot allowedNot allowedNot allowed
ViewsAllowedNot allowedNot allowedNot allowedNot allowed
Rule EngineAllowedNot allowedNot allowedNot allowedNot allowed

Lifecycle authorityNamed on Approve and Reject for this pricing model.

Illustrative organization, workspaces and roles. Labels are the product's; your administrators define the roles.

Access scope, example configuration: one organization, three workspaces, and the role a user holds in each with the operations it grants. Roles are yours to define; two administrator roles ship.

  1. Where is Revomo hosted, and where is our data processed?

    On Amazon Web Services in the United States, in a multi-availability-zone configuration, with production separated from development and staging. The application database is MongoDB Atlas, hosted in AWS. Subprocessors, what each does and where each is located are listed in Annex 3 of the Data Processing Addendum. Contact us to review residency or deployment requirements.

    Source: DPA Annex 2 §4 to 5, Annex 3; Governance & Security FAQ
  2. How is our data encrypted and kept apart from other customers'?

    TLS 1.2 or higher in transit and AES-256 or equivalent at rest, with keys in a dedicated key management service with restricted access. Your organization keeps its data apart from other customers'; workspaces partition it inside your organization, for example by region or business unit, and a user works in one workspace at a time.

    Source: DPA Annex 2 §3; Governance & Security evidence, rows 2 and 4
  3. How do users sign in, and is single sign-on supported?

    With a password or a passkey, or through single sign-on over SAML or OpenID Connect, which can map identity-provider groups to workspace roles. Users can add an authenticator app as a second factor. Revomo staff need multi-factor authentication for administrative access to production, with least privilege, unique identifiers and quarterly access reviews.

    Source: Governance & Security, sign-in and access; DPA Annex 2 §2
  4. How are permissions and approvals controlled?

    Through roles your administrators define. A role grants operations such as view, create, update, delete and export on each resource, for example price lists, pricing models, datasets and views, inside a workspace. Approval authority is assigned separately: each step of a lifecycle policy names who may perform it, so the right to edit a price list never includes the right to approve it.

    Source: Governance & Security FAQ; evidence rows 5 and 7
  5. What is recorded?

    A lifecycle timeline on each price list (actor, action, from and to state), an audit log that includes the actions Copilot performs, row history where it is enabled, and lineage of dependencies. Lineage shows what a change relies on and affects; it does not record why a decision was made.

    Source: Governance & Security evidence, rows 6 and 8
  6. How is our data used with AI?

    Your data is used to provide, support, secure and improve the Service. Separately, the agreement permits Revomo to use aggregated and de-identified data, including to train and improve models, only in a form that cannot reasonably identify you, your users or your customers. Revomo-provided inference runs through Amazon Bedrock, a listed subprocessor. Customer-provided inference is not described in the published agreements; raise it during review.

    Source: SA §5, DPA §3.3, DPA Annex 3
  7. What assurance and documents can our reviewers get?

    The Trust Center shows current compliance status and controls, with policies available on request there. The SOC 2 Type II report, covering Security, Availability and Confidentiality, is provided once per calendar year on written request, under confidentiality. The Subscription Agreement, Service Level Agreement, Data Processing Addendum and subprocessor list are provided in full on request.

    Source: DPA §5.2; Trust Center; Governance & Security, Evidence
  8. What is committed on availability, incidents and support?

    99.9% monthly availability, committed in the Service Level Agreement and measured each calendar month, with service credits. During a Severity 1 incident, hourly updates and a root-cause report within five business days. Standard Support on business days, 9:00 to 18:00 US Central.

    Source: SLA §2, §5 and §6
  9. How are security incidents notified?

    The agreements commit Revomo to notify you of a security incident affecting your data without undue delay, with the content the Data Processing Addendum sets out. If your standard requires a fixed notice period, raise it in review so it is agreed in writing.

    Source: DPA §8; Subscription Agreement §6
  10. What happens to our data when the subscription ends?

    You can request a copy. For 30 days after expiry or termination you may request your data in writing, in a commercially reasonable format. After that, Revomo may delete it from active systems in the ordinary course. Backups are removed on standard retention cycles and stay protected until then, subject to any legal hold. Aggregated, de-identified data may be retained.

    Source: SA §5; DPA §10
04 · Your team

What a deployment asks of your IT and business teams.

Standard Activation is included in the subscription with no separate implementation fee, bounded to the modules and workspaces in the Deployment Scope. Revomo configures and loads; your side provides data, access, decisions and a named lead. Each phase ends at a gate you can see.

  1. 01Systems integration5
  2. 02Data requirements6
  3. 03Security and compliance10
  4. 04Your team6
  5. 05Timeline5

What each side brings to each activation phase: three Data & Context Studio phases every activation runs, one phase per module in scope (Analytics & Insights shown), then transition. Marks are items, not time; the gate under each column closes it.

  1. What does Revomo do?

    Standard Activation: Revomo 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 and the production path; and tells you when the Activation Criteria are met. Afterwards, guidance through the Customer Success Process. No separate implementation fee.

    Source: Plan sections 02, 04 and 06; activation phases 01 to 03
  2. What does our side provide?

    Data and access: extracts, connections or credentials for the systems in scope, in the agreed format and cadence. A named activation lead with authority to decide day to day. Pricing, product, finance and IT people in the workshop and the review sessions. Decisions and approvals within the agreed review window. Validation of representative outputs in writing. User accounts, single sign-on and internal approvals. Notice of changes to source systems during activation.

    Source: Plan section 05
  3. Which roles do you ask us to name?

    One named activation lead, a single point of contact with authority to coordinate your people and make day-to-day decisions, plus participation from pricing, product, finance and IT. In practice finance owns the tie-out number the data is checked against, and IT or the ERP owner provides the extracts or connections and the single sign-on setup.

    Source: Plan section 05; activation phase 01
  4. Do we need developers?

    Not for Standard Activation, which uses no-code Revomo capabilities and the data you provide. Your IT provides extracts, connections or credentials and the single sign-on and access approvals. Customer-owned system development, for example changes to your ERP, is outside Standard Activation and is yours to agree separately.

    Source: Plan sections 05 and 06
  5. What do we need to install or host?

    Nothing. Revomo is a cloud service used in the browser, hosted on AWS. Your identity administrator connects single sign-on if you use it, and your systems provide extracts or accept pushes through the patterns above.

    Source: DPA Annex 2 §4; Governance & Security
  6. What is not included?

    Customer-owned system development; 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; and activation of workspaces beyond those named, which is agreed as Workspace Activation. After a module is activated, further configuration by Revomo comes through the Customer Success Process or a separate agreement.

    Source: Plan section 06
05 · Timeline

How a deployment runs, and what moves its dates.

How long an activation takes depends on the modules in scope, how ready the data and access are, and how quickly decisions come back. The Planning & Design Workshop sets an activation window per module, and every phase ends at a gate stated as an outcome.

  1. 01Systems integration5
  2. 02Data requirements6
  3. 03Security and compliance10
  4. 04Your team6
  5. 05Timeline5
  1. Scope agreedFinance tie-out number agreed
  2. Data trustedTotals tie to the finance number
  3. Waterfall agreedYou sign off the definitions
  4. Module phasesAction approved by you
  5. TransitionA configuration change made unaided

The gate that closes each phase, stated as an outcome you can check. Nothing moves on until the gate is met; this page states no durations.

  1. What are the phases?

    Three for the foundation, which every activation runs: scope agreed, closing when the finance tie-out number is agreed; data trusted, closing when totals in Revomo tie to that number; waterfall agreed, closing when you sign off the definitions. Then one phase per module in scope, each with its own gate, for example the first live price change for Price Management. Then transition: your team makes a configuration change unaided.

    Source: Activation phases; Plan section 04
  2. What is recorded about timing?

    An activation window per module, agreed at design alignment after the Planning & Design Workshop has confirmed scope, sequencing and data readiness, with the sequence of modules and the workspaces each is activated in. Timing assumes data, access and decisions arrive within the agreed review window; if dependencies slip well beyond the window, the parties re-plan.

    Source: Plan sections 02, 05 and 06Recorded in your plan
  3. What usually moves the window?

    Data and access arriving late or in a different shape than agreed, decisions and validation outside the review window, user accounts and single sign-on not ready, and changes to source systems or requirements after design alignment, which also put re-work outside Standard Activation.

    Source: Plan sections 05 and 06
  4. How is success measured?

    A module counts as activated when its five criteria are met, and every phase before that ends at a gate stated as an outcome: a finance number tied, definitions signed off, an action approved, a first live price change. After activation, adoption, realized outcomes and next opportunities are reviewed on a business-review cadence you agree.

    Source: Plan sections 04 and 07; activation phases
  5. Can you give us a number of weeks?

    Not on this page. The Planning & Design Workshop sets an activation window per module once scope, data readiness and sequencing are confirmed, and that window in your plan is the one that counts, with the dependencies that move it written beside it.

    Source: docs/faq-standard.md, "Implementation time"; Plan section 02Recorded in your plan
Documents

What your reviewers can read, and how to get it.

Availability is stated as it is: public only where anyone can open it without asking.

  • Trust Center

    Public

    Current compliance status and security controls. Policies and the system description are available on request from there.

    Visit Trust Center
  • SOC 2 Type II report

    On written request

    Independent assurance over Security, Availability and Confidentiality. Provided once per calendar year on written request, under confidentiality.

    Request the report
  • Data Processing Addendum

    Request access

    How personal data is processed and protected, including the technical and organizational measures in Annex 2.

    Request the DPA
  • Subprocessor list

    Request access

    Each subprocessor, what it does and where it is located, with notice of changes.

    Request the list
  • Service Level Agreement

    Request access

    The monthly availability commitment, service credits, support hours and response targets.

    Request the SLA
  • Subscription Agreement

    Request access

    Ownership and use of your data, security obligations, breach notice, and return of data at the end of the term.

    Request the agreement
  • Activation and Success Plan

    Request access

    Schedule 1 to the Order Form: objective, approach, deployment scope, activation criteria, responsibilities and boundaries.

    Request the template
  • Standard Capacity Schedule

    Request access

    The operating allowances a subscription includes, in four categories, and how use above them is handled.

    Request the schedule
Requests

One form for documents and questionnaires.

Name the documents and the reviewer who should receive them. Security questionnaires in your own format go through the same form, and the Trust Center handles its own policy requests.

FAQ

Common questions

Do you replace our ERP, CRM or CPQ?

No. Revomo reads from and publishes back to the systems that run the business; it does not replace them. Transactions, masters and costs come in through connectors, files or the API, and approved prices go back out through the same patterns or as published documents.

How long does implementation 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 and data readiness and sets an activation window for each module, recorded in the Activation and Success Plan with the dependencies beside it.

Is our data used to train models?

Your data is used to provide, support, secure and improve the Service. Separately, the agreement permits Revomo to use aggregated and de-identified data, including to train and improve models, only in a form that cannot identify you, your users or your customers. Third-party models are used for inference through Amazon Bedrock, a listed subprocessor.

Can we see the Activation and Success Plan before we sign?

Yes. Its structure, the Standard Activation scope, the five Activation Criteria, the responsibilities on both sides and the gated phases are described on the implementation page, and the template is provided on request. It supports activation alignment only and amends no agreement; an optional acknowledgment records that it reflects the current alignment.

Where do we send a security questionnaire?

Through the contact form, in whatever format your review uses. The answers draw on the Trust Center, the agreements and the Governance & Security page; anything those do not cover is raised with you in writing rather than assumed.

What is included in the subscription?

Every subscription includes the Commercial Data & Context foundation; capabilities are added individually at published Growth rates. Standard Activation of the use cases in the Deployment Scope is included with no separate implementation fee; customer-owned system development, bespoke development and major data remediation are agreed separately.

Bring your evaluation questions.

Send them in the form your review uses. The documents above are provided on request, and anything they do not cover is answered in writing.

Plate B2 · Series 2026