RCM Insights concepts - the mental model and the words behind the answers
Objective. Give Sales and CSM a clean mental model of RCM Insights and the vocabulary to use it precisely: what the app is built on, the key terms defined plainly, how the concepts chain from question to trusted answer, and the one concept people most often get wrong.
RCM Insights rests on a single idea: an answer is only as good as the evidence and scope you can see behind it. Everything else - Ask, Discover, Data, Metrics, Dashboards, Saved, role scope - serves that idea. This module defines the terms plainly and shows how they chain, so a Sales or CSM person can explain the product without selling it as a chatbot.
See it in the demo
The core concept the app is built on
RCM Insights is a natural-language analytics layer, but its core concept is not natural language - it is inspectable evidence. A business user asks a question in plain words and gets an answer, and the thing that makes the answer worth anything is that the data, definition, scope and freshness behind it are one click away.
Fluency gets a non-analyst to an answer. Inspectability lets them decide whether to trust it. A fluent answer on thin or stale data is a liability, not a convenience, so the product is designed to put the evidence next to the answer rather than hide it. Sell and teach the inspectability, not the fluency - the fluency is table stakes.
Key terms, defined plainly
- Ask - the natural-language front door. Pose a question in plain language, get an answer tied to inspectable data. The answer is a starting point to verify, not a verdict.
- Discover - helps a user find what is askable, so they ask questions the data can actually support rather than guessing.
- Evidence - the source, coverage, metric definition and freshness behind an answer. Inspecting it is the skill that keeps a user safe.
- Coverage - how much of the relevant population a source actually covers. Presence of a source is not coverage.
- Freshness - how current the underlying data is; tells you how stale an answer may be.
- Metric definition - what a number counts, over what population and period, with what exclusions. It governs whether two numbers are comparable.
- Scope - the filters, period and data a view or dashboard is built on. A figure means 'this value, for this scope, as of this data'.
- Dashboard / Saved - reused analyses: standing, shareable views and saved questions re-run for real decisions rather than re-derived.
- Role scope - who is allowed to ask and see what, enforced through Admin and role sign-in.
- 'Not enough data' - the honest answer when coverage cannot support the question; a valid answer, not a failure.
How the concepts chain together
The concepts form a single chain from question to trusted decision:
Question -> Ask (answer) -> Evidence (source, coverage, freshness) -> Metric definition (comparability) -> Scope (what the figure means) -> Save / Dashboard (reuse) -> Decision.
Discover sits at the front, helping shape a question the data can support. Role scope wraps the whole chain, bounding what any user can ask and see. The discipline runs end to end: an answer enters the chain as a hypothesis and only earns the right to inform a decision after its evidence, definition and scope have been inspected. Break the chain - skip the evidence, ignore the definition, strip the scope - and a correct-looking number becomes a wrong decision.
The one concept people most often get wrong
The single most common error is treating fluency as proof - believing a confident, well-worded answer must be correct. It is the mistake the whole product is designed to prevent, and the one a CSM must train out of users and a Sales rep must not reinforce in a demo.
The correction is one sentence: an answer is a starting point to verify, not a verdict. A close second is confusing a scoped dashboard figure with a universal truth - forgetting that the number means 'this value, for this scope, as of this data'. Both errors share a root: ignoring the evidence and scope that give a number its meaning. Teach the habit of reading the evidence and the scope before the number, and both errors disappear together.
Interpretation check
The mental model is one idea - an answer is only as good as the evidence and scope behind it. An Ask or Discover answer is a starting point to verify ('not enough data' is valid); a saved dashboard reflects its own filters and scope; a metric definition governs whether a number is comparable. Fluency is table stakes; inspectability is the product.
In the field
KnackGlobal (RCM): explaining to a director that 'AR days' is only comparable once its definition matches, and that a same-day answer must have its evidence inspected before it enters a QBR, is the concept chain applied where a fluent-but-unsupported figure could threaten a large contract.
Practical task
Write a 90-second plain-language explanation of RCM Insights for an RCM director that leads with inspectable evidence, not fluency, and uses at least four of the key terms correctly (Ask, evidence, coverage or freshness, metric definition, scope). Then write one sentence you would deliberately NOT say because it would sell the product as a chatbot.
Self-check
In one sentence, what is RCM Insights actually built on?
Inspectable evidence - the idea that an answer is only as good as the data, definition, scope and freshness you can see behind it. Natural language gets you to the answer; inspectability lets you trust it.
Define 'coverage' and contrast it with a listed source.
Coverage is how much of the relevant population a source actually covers. A listed source only tells you the feed is connected - presence of a source is not coverage, which is why you read coverage before trusting an answer.
Walk the concept chain from question to decision.
Question -> Ask answer -> evidence (source, coverage, freshness) -> metric definition (comparability) -> scope (what the figure means) -> save/dashboard (reuse) -> decision, with Discover shaping the question and role scope bounding the whole chain.
What is the single concept people most often get wrong, and the one-sentence correction?
Treating fluency as proof. Correction: an answer is a starting point to verify, not a verdict - read the evidence and scope before the number.
Why is 'scope' a core term rather than a detail?
Because a figure means 'this value, for this scope, as of this data'. Without its scope a correct number can mislead, and two correctly scoped dashboards can legitimately disagree.
Verified vs demo. The concepts and terms describe the demo-shown ask-and-inspect model on seeded data. The exact controls, metric definitions and figures are SME-validation-pending, and live sources, coverage, freshness, definitions and role scope are customer-specific - confirm with product before any term is given a customer-specific value.