← Revan Analytics

Revan Analytics by DataMaaS

How your data is read

You ask a question in plain English. Everything that makes the answer trustworthy happens behind it.

In practice

You only ever talk to Revan.

  • 01
    You Ask A question in plain English, inside Revan Analytics.
  • 02
    Business Definitions Revan reads your definitions first — the rules, metrics and terminology written for each Source System, Dataset and column — so it knows what the question means in your business.
  • 03
    Revan It works out what the question needs and sends a request, never a query. Revan holds no credentials and has no connection to your systems.
  • 04
    Secure Query Service Inside the platform, it applies the permissions of whoever asked, runs a read-only query against your governed source, and returns only the rows and fields that person is entitled to see. Excluded data is not filtered out afterwards; it is never retrieved.
  • 05
    Your Answer Revan establishes which basis the question needs, and gives you the call with the evidence behind it.

Your definitions

Margin means what your business means by margin.

Ask a general AI assistant for last quarter’s margin and it guesses from a column name. Revan doesn’t have to. Your definitions are written into the governed data layer it reads, so a question comes back answered your way.

  • Your schema Your tables, your joins, and what each field actually means.
  • Your KPIs Margin, churn, on-time delivery, defined the way you define them.
  • Your business rules What counts, what’s excluded, and which basis a figure is reported on when there’s more than one.

It doesn’t matter what you run. One system or several — ERP, PSA, CRM, a warehouse, a lake, a reporting database — in one country or many, in as many currencies. Wherever it lives, your definitions can sit in front of it, and figures can be aligned to your business requirements before Revan reads them.

Who sees what

Revan inherits the permissions you already set.

You decide who sees margin. You decide who sees which sites. Those calls are yours and they are already made — Revan works inside them and has no way to widen them.

Sales sees sales A rep who can’t get to margin in your systems can’t get it out of Revan either.
Sites stay separate Someone scoped to North America won’t find other regions in an answer.
Your settings, not ours These are your entitlements, configured in your platform. We apply them; we don’t define them.
Revan can’t tell what it’s missing Because excluded data never comes back, Revan sees no gap. It has no idea there was more to ask for.

Access is enforced at the database — not by trusting the AI.

Assurance

Read-only, and under your control.

Nothing can be written Revan reads. It has no ability to change, delete or add anything, at either layer.
Never used to train AI Your questions and the answers are contractually excluded from training the AI provider’s models. That is in the contract, not a setting someone can switch on.
Looks outward, never inward Revan can check current public facts when a question needs them. Nothing of yours goes with it.
You control what’s kept Your questions, chats and uploaded files stay in the DataMaaS Platform as long as you keep them, and go when you delete them. Separately, the AI provider clears what passed through it within 30 days.
SOC 2 Type II The DataMaaS Platform is SOC 2 Type II attested, and Revan runs inside that scope.

Getting started

Three steps, wherever you are starting from.

Some businesses already have a data foundation worth building on. Others have data spread across systems and spreadsheets that has never been pulled together. Either way the first job is the same: establish what you have, and get it into a state that is fit for analytics.

  • 01
    Identify the sources that matter Sales, financials, supply chain, operations, HR. Most start with one — often the one where getting a straight number takes the longest — and add others as they go.
  • 02
    Get that data into shape DataMaaS works out how to reach it, brings it together, and gets it clean and consistent enough to analyze with confidence. How much work that is depends on where you are starting from.
  • 03
    Set down your definitions Margin, on-time, who counts as a customer, what is excluded. This part is done together, because every answer afterwards is built on it.

That foundation is what every answer stands on. We build it with you, and we keep it current as your business changes.

It also means the answer does not depend on who asked. Your definitions live in the foundation rather than in the prompt, so margin means the same thing whether it is the CFO asking or a data analyst — and nobody has to be good at phrasing questions to get a figure that matches how the business reports.

Where next

Keep going.

That’s what Revan can read. What it does with it is a different discipline.

Judgment How Revan thinks → The ten reflex lenses every answer is stress-tested from, and how ten views resolve into one recommendation. Overview Back to the overview → What Revan is, the five standing commitments, and the shape a Revan answer always takes.

Ready to put it on a real question?

Start with one you would normally have to chase someone for.

Ask Revan →