> ## Documentation Index > Fetch the complete documentation index at: https://docs.getmeasure.com/llms.txt > Use this file to discover all available pages before exploring further. # Core Concepts This guide provides a comprehensive overview of the core concepts for revenue management in Measure. It details the fundamental entities and workflows applicable to both dashboard-based and API-driven billing operations. ## Operating Modes Measure can be leveraged in **no-code mode** through the dashboard. For deeper integration, the platform also provides a robust **API** so you can perform any dashboard action as a white-labeled experience in your own product, including usage-based and seat-based billing. **Test account**: Request a separate test account from [support@getmeasure.com](mailto:support@getmeasure.com) with distinct credentials so you can experiment before going live. ## Key Concepts ### Company When you sign up, Measure provisions a **company** for your business. All entities described below belong to that company. You can configure the company with an address, timezone, currency, and branding so it represents your product or business. ### Billable Items and Metrics Billable items and metrics are the core units for billing. **Billable items** are distinct billable entities in your product, for example Licenses, API Calls, or Users. Items can be **usage-based** and transient (e.g., API calls) or **object-based** and persistent (e.g., users). **Billable metrics** are rules and aggregators applied to billable items. They query events or objects and produce an aggregate value that is ultimately billed to the customer. ### Events and Objects Measure supports metering for: * **Usage-based items** (transient): e.g., API calls, bandwidth, compute minutes * **Object-based items** (persistent): e.g., seats, licenses, stored objects **Why both?** Events drive usage-based metrics; objects drive object-based metrics. Measure treats them separately because **revenue from persistent objects** (e.g., seats) counts as recurring revenue, while **revenue from transient events** does not, unless you have minimum pre-purchased events. ### Prices and Plans Pricing starts with **item prices** for each billable metric. You then combine them into **product pricing** (plans) with one or more billable components. Product prices represent different offerings (e.g., Basic, Pro, or Enterprise plans). ### Customers A **customer** is a business or user you bill through Measure. You can begin billing with just an email; for taxation and more advanced needs, add a customer address. Customers are central: they link to events, objects, contracts, subscriptions, invoices, and payments. ### Subscriptions A **subscription** represents recurring service for a customer. A subscription can include one or more product pricing, so a single invoice can cover multiple offerings. ### Contracts A **contract** is a proposal for a subscription or one-time charge. Contracts include a signature step before the subscription starts, which is common in enterprise sales. Measure Contracts simplify CPQ: create and share contracts, follow up to get them signed, and automatically create the associated subscriptions. ### Invoices and Payments An **invoice** can represent recurring or one-time charges. For active subscriptions, you can also preview upcoming invoices, which is useful for usage-based charges. Measure integrates with multiple payment providers to process payments for invoices. ## Explore Product Guides Configure your product catalog, plans, and packaging Set up rules and aggregators for usage-based and object-based billing Create and manage customers for billing Manage recurring subscriptions and plan changes Create, share, and sign proposals before subscriptions start Issue invoices, collect payments, and automate revenue collection