> ## Documentation Index > Fetch the complete documentation index at: https://docs.beaconrevenue.io/llms.txt > Use this file to discover all available pages before exploring further. # Data model — is my data ready to trust? > How Beacon joins your tools into one model of six objects, what it shows today, what it needs, which modules depend on it, and what it does not calculate yet. **Data model** answers one question: *Is my data complete, linked and fresh enough to trust every module built on it?* It joins what each of your tools knows into one model of your company, shows which tool fills each part of it, and watches whether that data stays on time and joined up. Every other module is built on it. It belongs to the Shared foundation — see [Modules](/modules/overview). ## What it does Your tools each hold part of the picture: your billing system knows what a customer pays, your CRM knows their deals, your product analytics knows how they use your product. Data model joins these into **six objects** — Customer, Deal, Subscription, Invoice, Product usage and Ledger — each made of parts and fields, and records which tool fills each one. On every read it counts what is in the model, checks whether each tool delivered on time and whether the key links between your tools hold, and shows which modules your data allows. It only reads. It never changes a record in your tools. ## What it produces Its headline is one score: | KPI | What it measures | Today | | - | - | - | | **[Data readiness score](/definitions/data-readiness-score)** | One score from 0 to 100 for how complete, fresh and linked your data is — the line that decides which kinds of module may switch on | Not calculated yet | It is shown on the module's page in Beacon as not yet calculated. Its name links to its definition, which also says how the [Data API](/api-reference) and [MCP](/mcp-tools) will carry it — neither serves it yet. Behind it, the page shows today: | What | What it tells you | Today | | - | - | - | | **Tools connected** | The tools Beacon reads your data from | Shown | | **Objects in your model** | How many of the six objects a connected tool fills | Shown | | **Customers joined across tools** | Billing customers joined to their CRM company on an exact match — read from [Data integrity](/modules/data-integrity)'s check | Shown | | **Key links holding** | Billing to CRM, product usage to customer, marketing to pipeline | Billing to CRM shown; the other two not checked yet | | **Which modules your data allows** | Each module, what it needs, and whether it is on | Shown | | **Every field, and the tool that fills it** | Field by field, for each part of each object | Shown | | **How full each field is** | The share of records with each field filled | Not measured yet | ## The model | Object | Its parts | Filled by | | - | - | - | | **Customer** | Company · Contacts · Support tickets · Email engagement | Billing, CRM, product usage, accounting, marketing | | **Deal** | Deals · Stage history · Line items | CRM | | **Subscription** | Subscriptions · Products & prices · Monthly revenue | Billing — monthly revenue is worked out by Beacon from it | | **Invoice** | Invoices · Credit notes & refunds · Aged debt | Billing; due dates, payments and aged debt need accounting | | **Product usage** | Usage events · People | Product analytics | | **Ledger** | Ledger entries · Chart of accounts · Companies in your group | Accounting | An object counts as in your model when a connected tool fills it. With billing and a CRM connected, four of the six are in: Product usage waits for product analytics, and Ledger for your accounting tool. **What your tools unlock.** Each tool you connect moves you a step: **Connected** (billing and CRM — your data model, revenue and the customer view), **Validated** (adds product usage with 30 days of history — modules that report and alert), **Ready** (adds accounting — forecasts, which wait for this step) and **Full** (adds support, marketing and HR — the last detail). ## What you see on its page In Beacon, open **The Brain** and choose **Data model**. The page has seven tabs: * **Overview** — the four counts, the six objects and which tools fill them, what your tools unlock, the tools it reads, and when it last read. * **Dashboard** — the readiness score (not calculated yet), what each area gives the model, which modules your data allows, your model over time, and the three key links. * **Signals & alerts** — what it watches and its alert rules. * **Scorecard** — how each count is counted, how the readiness score will be worked out, and the rules. * **Map** — one object at a time, in three columns: your tools, the object's parts, and what it powers. * **Objects** — each object's parts and every field, with the tool that fills it, and what each tool leaves out on purpose. * **Setup** — the questions the module uses, and the answers in use. ## What it needs | Tool | | What it unlocks | | - | - | - | | **Billing** | Needed to start | Customers, subscriptions, invoices and products — the revenue half of every customer | | **CRM** | Needed to start | Companies, contacts, deals and their stage history, joined to billing | | **Product usage** | Adds detail | Who uses your product and how much. With 30 days of history it takes you to Validated | | **Accounting** | Adds detail | Your ledger, payment terms and aged debt. Forecasts wait for it (Ready) | | **Support, marketing and HR** | Optional | The last detail (Full). Support tickets can already come from your CRM | See [Connect your tools](/connect-your-tools) for how each connection is made. ## Reads from * **Customer matching** — gives every customer one ID across your tools. The model is built on it. * **Data integrity** — sends back how complete and checked the records are. Customers joined and the billing-to-CRM link are read from its check. ## Which modules read it | Module | What it uses Data model for | | - | - | | **Every module** | Each module switches on only when the data it needs is in the model | | **Data integrity** | Checks every record in the model | | **Segments** | Groups customers using fields from billing and CRM together | | **Signals** | Every signal is read from a record in the model | | **Customer fit** | Scores each customer from the joined record | | **Revenue forecast** and **Segment revenue paths** | Switch on at the Ready step — they wait for your accounting tool | The readiness score itself gates nothing yet, because it is not calculated. Today a module switches on when the tools it needs are connected and delivering. The **Modules** page in The Brain shows which modules are running for you. ## Alerts | Alert | When it fires | Where | | - | - | - | | **A module is waiting on your data** | A module tries to switch on while your data is not yet ready for it. Waits for the readiness score | Slack and email | | **A key link between tools broke** | Billing stops joining to your CRM, product usage to customers, or marketing to pipeline | Slack and email | | **Required fields are missing** | Fields an object needs are missing or not mapped. Sent once, with Data integrity | In Beacon | | **A tool has stopped delivering** | A tool has not delivered within its minimum sync time | In Beacon | | **A change to your data model needs review** | Someone proposes a change to an object, a field or a link | In Beacon | **No alert is sent yet.** The page lists each rule; sending waits for the setting that switches alerts on. ## Setup questions * **From what level of data readiness should forecasts switch on?** Recommended: 80, the standard line. 85 suits larger companies, 75 small ones. * **Which links between your tools should count?** Recommended: all three. * **How late can a tool be before Beacon tells you?** Recommended: one day for every tool. * **Which fields must each tool fill?** Recommended: Beacon's list. Which tools you use, how big your company is and who owns your data are asked once and used here too. Today the Setup tab shows each question with the answer in use, and the module runs on those answers. Saving your own answers is not available yet. ## What is not calculated yet * **The data readiness score** — and with it the 15% cut for a broken key link and the cut for a late tool. * **How full each field is.** * **Two of the three key links** — product usage to customer, and marketing to pipeline. * **Your model over time**, week by week. * **Alerts** — the rules are in place; none is sent yet. * **Saving your own Setup answers.** ## Related The ten module families and which modules are available today. The checks that run over every record in the model. What each connection unlocks, and which modules switch on with it. What Beacon shows when a tool is not connected. When each figure was last worked out. What Beacon reads, what it never changes, and what it does not decide. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.