Data & Context Studio

Turn commercial data into decision-ready context.

Connect your sources, prepare your data and define what it means, so analysis, AI and pricing execution work from a shared commercial foundation.

Data Hub / Datasets / Invoice lines

Source records, business definitions and dependencies in one workspace.

01 · Connect & prepare

Bring your commercial data together.

Connect systems and files, review their structure, and resolve data issues before they flow into commercial decisions.

Staging

Bad rows wait to be fixed, not lost.

A value that fails its type or a validation rule holds the row with its original text. Fix one row or many at once, and rows that pass move into the dataset.

Profiling

See gaps and inconsistencies before they reach a price.

Profile a dataset to see each column’s missing and unique share, its distribution or most frequent values, with an AI summary of what to look at first.

Import and schema

Review the structure before the first row lands.

Prepare a file, check the detected types, and accept or edit suggested names, types, descriptions and tags for each column.

Integrations

Keep connected sources current.

Connected datasets refresh on their own schedule, and columns that appear in a source can be added and backfilled.

How it works: files, suggestions, connectors and staging
Workbooks
Imports read CSV and TSV files. For an Excel workbook, choose the sheets you need in File Manager (with the header row), and each becomes a CSV file ready to import.
Column suggestions
Suggestions are drawn from each column’s header and up to five sample values. Every suggestion stays editable, and none carries a confidence score.
Connectors
Databricks, Salesforce and Google Drive connect today. Syncs run manually or on a schedule (hourly to monthly, or cron); Salesforce syncs incrementally, the others refresh in full.
Staging
Each column can parse strictly (failing values go to staging) or leniently (failing values become empty). An import with rows in staging is a partial load, and the count says so.
02 · Build & transform

Build the data your decisions depend on.

Combine sources, calculate measures and create reusable views on a visual canvas, with each transformation open to inspection. Below, one example: a sales data model.

Data Hub / Views / Sales Data Model

The canvas follows Revomo’s view builder. The data is illustrative, and the stage guide and explanations are added for this page.

  • Every operation you needJoin, filter, aggregate, union, pivot, sort and calculate, with any step stored as a table.
  • Time-aware joinsJoin conditions compare as well as match, so a cost or price applies only within its effective dates.
  • Every step openEach node shows its columns and row count; open it to see its configuration or preview its data.
Formulas and lookups

Calculate across datasets, views and price lists.

Formula columns live in views and price lists. A lookup pulls a value from another dataset, view, price list or ruleset, and a plain-English description can draft the formula for you to check.

Also in the model
  • KeysChoose the columns that identify a record; an impact check shows how many rows are unique before you save, and duplicates leave the live table and are exported for audit. With no key in the source, number rows automatically.
  • RecordsAdd records through a typed form, lock columns that shouldn’t change, and update or remove records. Price list and staging grids edit inline.
  • Explore and exportFilter any column by its values, chart a selection, save layouts for yourself or a role, and export to CSV with real column names.
How it works: views and formulas
Operations
Views combine datasets, price lists and other views with joins (inner, left, right, full, cross, matching-only and without-match), filters, aggregates, unions, pivots, sorts and formula columns.
Join conditions
Each condition compares two columns with ==, !=, >, <, >= or <=, which is how effective-dated matching is written.
Formulas
Datasets hold imported rows; formula columns belong to views and price lists. A formula is checked when you save it, and the view builder can also draft a pipeline from a stated goal for you to review.
03 · Define context

Give your data shared business meaning.

Define measures, units and relationships so teams and AI can interpret commercial data in context.

  1. Source fieldNET_PR_2
  2. Business definitionNet price, on Invoice lines
  3. RelationshipsCustomers, Products, by key
  4. Used inCommercial model, analysis
Commercial Context GraphNet price
CustomersJoined on Customer ID
ProductsJoined on SKU

The Commercial Context Graph for Net price, from the source field to every use, built from what the workspace records: the column’s definition, tag and rules, the joins in the view, and lineage. Select any column to see its meaning and connections. Illustrative data.

Validation rules

Write down what a valid value is.

Add a numeric range, allowed values, a pattern, a comparison with another column, or a value that must exist in another dataset. A blocking rule stops a value that fails; other rules let it through and flag it.

Semantic tags

Tag what each column means.

Tags come from a built-in commercial vocabulary plus your own, so a column reads as net revenue, a unit cost or a customer identifier wherever it appears.

  • measure:price:net_invoiceNet price
  • measure:cost:standardStandard cost
  • identifier:customer:sold_toCustomer ID
  • time:event:invoice_dateInvoice date
How commercial context works
How it works: definitions and relationships
Definitions
Each column carries a description, a type (with currency for money), semantic tags and validation rules. Copilot reads them when it answers.
Relationships
Relationships are carried by keys, joins and lookups in your model. The labels in the example describe the commercial relationship; they are not a separate stored graph.
04 · Govern & trace

Control access. Understand every change.

Manage permissions, inspect dependencies and review recorded changes across your commercial data.

Lineage

See what depends on this data before you change it.

Lineage shows what a dataset, view, commercial model, price list or ruleset depends on, and what depends on it, across the workspace.

Record history

Know what changed, when and by whom.

Turn on history for a dataset and every row change is recorded: the field, the old and new value, who changed it and when.

Permissions

Grant each role what it needs.

Permissions are set per feature, so a role can edit price lists without changing the commercial model behind them.

Audit

Keep the record of who did what.

  • Audit logSearchable and exportable record of actions across the workspace.
  • Item sharingShare an individual item with named users or roles.
  • SeparationOrganizations keep data apart, and workspaces partition it within one.
Governance and security
How it works: lineage and history
Lookups bind by name
A lookup refers to its source by name, so renaming or deleting a dataset, view or column can leave a dependent formula empty. Check its dependents in Lineage first; Lineage shows them, it does not block the change.
History
History is off until you enable it for a dataset, and it keeps changes for the retention period you set.
05 · Power every capability

Prepare once. Put it to work across Revomo.

Use shared data and definitions across analytics, planning, pricing and AI-assisted work.

Revomo Copilot

Ask about the data in your own terms.

Copilot reads schemas, definitions, tags, rules and lineage through its tools, within the asking user’s permissions.

Revomo Copilot
Automation

Act when a refresh changes something that matters.

After a dataset refreshes or a source syncs, an automation can check a watched value against a threshold, then alert someone or recalculate a price list.

AI Agents & Automation

Automations run each time data refreshes or syncs, not as a live stream. Price lists and rulesets carry their own review, approval and revisions in Price Management. Data & Context Studio is part of the Commercial Data & Context foundation that every Revomo subscription includes (pricing).

See how your data becomes commercial context.

Walk through how your sources, definitions and rules come together in Data & Context Studio.

Plate B2 · Series 2026