# Solutions

> Installable applications built from the platform's own artifacts - five available today, three in development, all of them yours to change after installing

Source: https://aipril.dev/docs/solutions

## A set of applications

You do not start from an empty screen. Applications install into your organisation and run: a CRM, an
employee portal, project management, a service desk, price management.

Each is a **versioned package of platform artifacts** - data model, processes, pages, automations,
catalogues, roles, dashboards - reconciled into live entities on installation. See [Applications](https://aipril.dev/docs/apps/under-the-hood.md).

## Available today

| Application | What it is for |
|---|---|
| [CRM](https://aipril.dev/docs/solutions/sales-crm.md) | Accounts, contacts, the lead-to-deal pipeline, rep tasks and quota goals |
| [Corporate portal](https://aipril.dev/docs/solutions/corporate-portal.md) | Newsroom, media, org structure, idea board, benefits shop |
| [Projects](https://aipril.dev/docs/solutions/projects.md) | Portfolio, project, stage and task hierarchy with roadmaps, risks and workload |
| [Service desk](https://aipril.dev/docs/solutions/service-desk.md) | Triage, routing and SLA tracking for internal requests |
| [Price management](https://aipril.dev/docs/solutions/price-management.md) | Price lists as a live sheet, with approvals and change analytics |

## In development

A **medical CRM**, a **HoReCa guest-loyalty suite** on the platform's ledger, and **campaign
management**. What each is and where it stands:
[In development](https://aipril.dev/docs/solutions/in-development.md).

## What installing one actually gets you

- **A working system on day one**, not a project.
- **Yours to change immediately** - a field, a status, a screen, a rule. You are editing an
  application, not requesting a change to somebody's product.
- **Upgrades as versions**, with a diff and a rollback, and your own edits living as your own commits.
- **One system rather than several.** Two applications installed side by side share the
  [data engine](https://aipril.dev/docs/engine.md), the [process engine](https://aipril.dev/docs/processes.md), the [ledger](https://aipril.dev/docs/ledger.md) and
  the [catalogues](https://aipril.dev/docs/master-data.md) - so a number in one is the number in the other.

## What installing one needs

An application declares what it requires - the platform features, the other applications it depends
on, the entities it consumes - and that is **checked before anything is installed**, not discovered
halfway through.

Dependencies are deliberate. The service desk builds on the corporate portal because its requests
arrive there; price management builds on the shared org structure because approvals route through it.
Installing the dependency is part of installing the app.

## And if what you need is not here

Describe it. An [AI agent builds the application](https://aipril.dev/docs/apps/authoring.md) from the same artifacts these
are made of, against your own catalogues, models and processes - and what it produces is an ordinary
application, indistinguishable from one that shipped with the platform.

That is the point of the catalogue: a starting set, not a boundary.