--- title: "Understanding Product Concept in Agile.Now" slug: "understanding-product-concept-in-agilenow" updated: 2025-04-16T10:25:47Z published: 2025-04-16T10:25:47Z canonical: "docs.agilenow.io/understanding-product-concept-in-agilenow" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.agilenow.io/llms.txt > Use this file to discover all available pages before exploring further. # Understanding Product Concept in Agile.Now A **Product** is a commercially packaged and configurable offering composed of a bundle of applications, tailored to serve the specific needs of enterprise users. Products are designed to provide a structured, reusable, and easily manageable way to deliver value through application-based services. Each product is linked to an enterprise through a **subscription** (see [Subscriptions](https://portal.document360.io/06417a5c-658f-4a8a-ad57-27f6e06c9e0d/document/v1/category/02e936f8-b02b-43ab-b825-c8ee7db9ed91) for more details). **Agile.Now** supports the creation of Product bundles, which form a catalog of customizable offerings. These bundles are designed to meet varying business needs through grouped applications and configurations. The list of product bundles and product catalogues can be accessed from the main menu. Each product bundle follows a defined **lifecycle**, which includes the following statuses: | **Status** | **Status description** | | --- | --- | | In Progress | The product is currently being configured. | | Active | The product is fully configured and available for use. | | Cancelled | The product is decommissioned and no longer available. | Important: Only **Active** products can be linked to a subscription. A product bundle must have all its core components configured before it can be activated and made available for use.  ## Core components of a product 1. **General Information** Basic product metadata such as name, description, and product code (used for external system mapping, if applicable), and product base. 2. **Price Plan** The pricing model assigned to the product, including base pricing and optional pricing tiers or add-ons. 3. **Applications** A set of applications grouped under the product, each serving specific business capabilities. 4. **Application Feature Configuration** Feature-level settings within each application, allowing for customization based on tenant or user needs. ## **Key advantages** **Modular Structuring** Enables grouping of applications into reusable, configurable offerings tailored to specific enterprise needs. **Scalability** Supports expansion of offerings over time by adding or updating applications and configurations without disrupting existing setups. **Operational Efficiency** Simplifies subscription management by allowing enterprises to subscribe to a single product bundle instead of managing multiple standalone applications. **Centralized Configuration** Provides a unified structure for managing pricing, application access, and feature-level settings across enterprise units. **Catalog-Driven Management** Products are organized into catalogues, making it easier to maintain, search, and select offerings based on business requirements. **Lifecycle Control** Status-based lifecycle management (In Progress, Active, Cancelled) ensures products are properly validated before they are made available for subscription. **External System Integration** Product codes allow seamless mapping to external catalogues, billing systems, or provisioning platforms.