> ## Documentation Index
> Fetch the complete documentation index at: https://failfast.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Business modules overview

> How Fail Fast delivers CRM, sales, purchasing, inventory, and finance as pages in your workspace

Fail Fast delivers its business modules — CRM, sales, purchasing, inventory, finance, and more — as sets of **Programs** pages built on the platform's core primitives: tables, forms, views, and dashboards. There is no separate application to install for each module. When a module is enabled for your workspace, its pages and tables appear in your **Programs** menu alongside everything else your company uses.

## How modules work

Every business module follows the same pattern:

* **Tables** hold the module's records — quotes, purchase orders, stock movements, policies.
* **Forms** create and edit those records, with the fields and validations your workspace has configured.
* **Views** let you search, filter, sort, and export the same records in the layout that suits the job.
* **Action buttons** on the relevant pages perform operations such as confirming a document or generating the next one in the flow.

Because everything is built on the same primitives, the skills you learn in one module carry over to all the others. If you know how to filter a table and fill a form, you already know how to work in any module.

Two modules add dedicated screens on top of their **Programs** pages: **POS** provides a fast-sale screen for stores and counters, and **Marketplace** provides a visual catalog-and-cart way to build commercial documents.

<Info>
  Which modules you see depends on the applications enabled for your workspace, your company template, and your role and permissions. If a page described in these guides is missing from your **Programs** menu, ask your workspace administrator whether the module is enabled for you.
</Info>

## Operations modules

<CardGroup cols={2}>
  <Card title="CRM and stakeholders" icon="address-book" href="/docs/operations/crm">
    Shared master records for people and companies, plus leads, opportunities, campaigns, and tickets.
  </Card>

  <Card title="Sales quotes and orders" icon="handshake" href="/docs/operations/sales">
    Order-to-cash: quotes, orders, customer invoices, price lists, and receivables.
  </Card>

  <Card title="Purchasing" icon="basket-shopping" href="/docs/operations/purchasing">
    Procure-to-pay: purchase orders, goods receipts, supplier invoices, and payables.
  </Card>

  <Card title="Inventory" icon="boxes-stacked" href="/docs/operations/inventory">
    Products and variants, warehouses, movements, lots, serials, and average cost.
  </Card>

  <Card title="Point of sale" icon="cash-register" href="/docs/operations/pos">
    A dedicated fast-sale screen with full cash-session and branch-closure control.
  </Card>

  <Card title="Marketplace" icon="store" href="/docs/operations/marketplace">
    Build quotes, orders, and invoices from a visual product catalog and cart.
  </Card>

  <Card title="Insurance and legal registries" icon="scale-balanced" href="/docs/operations/insurance-and-legal">
    Register insurance policies and legal processes with their supporting catalogs.
  </Card>
</CardGroup>

## Finance and transport

<CardGroup cols={2}>
  <Card title="Treasury" icon="building-columns" href="/docs/finance/treasury">
    Record income and payments, and settle the balances your operations create.
  </Card>

  <Card title="Accounting" icon="calculator" href="/docs/finance/accounting">
    The ledger where operational documents post their accounting entries.
  </Card>

  <Card title="Transport" icon="truck" href="/docs/transport/overview">
    Manage transport operations, billing and settlement, and fleet monitoring.
  </Card>
</CardGroup>

## How it all fits together

The through-line across every module is that operational documents feed Finance:

* **Sales** produce accounts receivable balances that you collect through Treasury.
* **Purchases** produce accounts payable balances that you pay through Treasury.
* **POS** sales move inventory and cash session money with every ticket.
* Everything posts to **accounting**, so your books reflect what operations actually did.

Start with the module closest to your daily work, and follow its connections from there.
