# One Number, Many Truths: How Growth Companies Build a Semantic Layer Before AI Agents Start Calculating Differently > A semantic layer defines revenue and margin once. See how growth companies stop AI agents from calculating the same number in different ways. - Published: 2026-08-21 - Author: Master Mind - Canonical: https://aimaster.fi/en/artikkelit/yksi-luku-monta-totuutta-nain-kasvuyritys-rakentaa-semanttisen-mittarikerroksen- Three AI agents, three different answers to the same question. When a CEO asked last month's revenue from the sales agent, the finance agent, and the executive dashboard agent, he got three different numbers. The problem isn't the AI. It's that each agent calculated revenue from its own, slightly different definition. This problem grows as growth companies deploy more AI agents. One agent pulls data from the CRM, another from the ERP, a third from the data warehouse. Each interprets terms like "revenue" or "active customer" slightly differently — are cancelled orders counted, from which date does a customer count as active, are draft orders included in order volume. A human notices the discrepancy in a meeting. An agent doesn't, because it has no way of knowing another agent calculated it differently. ## Why do agents calculate the same numbers differently? AI agents read data directly from source systems and apply a formula coded or prompted specifically for that agent. When there are as many formulas as there are agents, no single answer is technically wrong — they're just different definitions of the same word. The problem only surfaces when two agents give conflicting answers to the same question on the same day. This isn't a technical detail. It's a trust issue. Once leadership notices agents giving different numbers, they stop using them for decisions — even if the agents are working exactly as coded. One conflicting answer is enough to erode weeks of built trust. ## What is a semantic layer? A semantic layer is middleware that defines a company's core business metrics — revenue, margin, active customer, churn — once, in one place, with one formula. Every agent, dashboard, and report pulls the number from that layer instead of calculating it independently. When the definition changes, it changes once, not separately in every agent and system. In practice, the layer sits between the data warehouse and the agents. It doesn't duplicate raw data — it acts as a contract: "revenue" always means this exact formula, whether the sales agent asks, the finance agent asks, or a human opens a spreadsheet. ## How does a growth company build a semantic layer in practice? Building it takes three stages. First, list the metrics used by more than one system or agent — typically 10 to 20 core numbers is enough to start. Second, define each metric precisely: source table, filters, formula. Third, connect the semantic layer to the interface agents and dashboards use, so each system retrieves the finished number instead of recalculating it. | Stage | What happens | Duration | | --- | --- | --- | | 1. Mapping | List metrics used by more than one agent or system | 1 sprint | | 2. Definition | Document source, filters, and formula for each metric | 1-2 sprints | | 3. Rollout | Connect agents and dashboards to one shared semantic layer | 2-3 sprints | This work is typically part of building [Master Layer](https://aimaster.fi/tuotteet/master-layer). Master Layer is the data foundation layer that connects a company's existing systems (CRM, ERP, documents) securely for AI use — a semantic layer is part of this foundation whenever multiple agents need the same business metrics to align. ## Does a growth company need a semantic layer with just one AI agent? Not yet, necessarily. With a single agent, there's no conflict because only one system calculates the number. The right time to start is when a second agent or system is introduced and needs the same business metrics. It's also easier to document definitions for two systems than to retrofit them for five later. ## What happens if a company skips the semantic layer? The company keeps running, but every new agent increases the risk of conflicting numbers. In an earlier article we covered [Reverse ETL](https://aimaster.fi/artikkelit/reverse-etl-nain-kasvuyritys-vie-analytiikan-takaisin-crmaan-ja-erphen-ai-agentt) — how analytics gets pushed back into operational systems for agents to use. A semantic layer is the logical extension of that work: instead of every pipeline carrying its own calculation logic, every pipeline draws from the same definition from the start. In practice, the problem shows up small first: the sales director and the finance director present different monthly numbers in a leadership meeting. Then it grows larger: an agent makes an automated decision — flagging churn risk or suggesting a price increase — based on a metric nobody has validated as the company's official truth. ## How do you know a semantic layer is working? A working semantic layer shows up as two different agents or systems returning the exact same number to the same question at the same point in time. Another sign: changing a metric's definition — say, updating how churn is calculated — requires one edit, not a separate fix in every agent. A semantic layer doesn't remove the need to validate agent behavior in other ways. It solves one narrow but critical problem: making sure a word means the same thing across the entire company. ## What does a semantic layer cost? Cost depends on the number of metrics and source systems involved. The work proceeds in sprints: mapping, definition, and rollout can each run as 3-day development sprints, so cost is based on completed sprints rather than an upfront guess. ## Do you need a semantic layer before deploying AI agents? Not for the first agent. It's worth building once a second agent or system starts calculating the same business metrics — before conflicting numbers erode trust in what the agents report. ## How is a semantic layer different from regular BI reporting? BI reporting shows a number to a human on a dashboard. A semantic layer serves the same defined number programmatically to every consumer — humans and AI agents alike — from the same source with the same formula. ## Can a semantic layer be added on top of an existing data warehouse? Yes. It doesn't require rebuilding the data warehouse. It's added as a layer between the warehouse and the agents or dashboards, defining formulas once and serving them onward. If your company's agents are starting to give different answers to the same question, the issue isn't one agent. Book a [free Master Mind analysis](https://aimaster.fi/analyysi) and we'll map where your metrics diverge before they erode trust. ## Frequently asked questions ### What does a semantic layer cost? Cost depends on the number of metrics and source systems involved. The work proceeds in sprints: mapping, definition, and rollout can each run as 3-day development sprints, so cost is based on completed sprints rather than an upfront guess. ### Do you need a semantic layer before deploying AI agents? Not for the first agent. It's worth building once a second agent or system starts calculating the same business metrics — before conflicting numbers erode trust in what the agents report. ### How is a semantic layer different from regular BI reporting? BI reporting shows a number to a human on a dashboard. A semantic layer serves the same defined number programmatically to every consumer — humans and AI agents alike — from the same source with the same formula. ### Can a semantic layer be added on top of an existing data warehouse? Yes. It doesn't require rebuilding the data warehouse. It's added as a layer between the warehouse and the agents or dashboards, defining formulas once and serving them onward.