# What to ask for

> Four example requests, from a sales pipeline to equipment booking, and what the agent builds in your app for each one.

Each example below is a request you can send as it is, followed by what the agent builds. The parts named on the right are described in [What an app can do](https://golocomotive.fr/docs/apps.md).

## A sales pipeline

> We follow leads from first call to signed deal. A lead has a company, a contact, a value and a stage (new, contacted, proposal, won, lost). Sales people see their own leads, the manager sees all of them. I want the total value per stage.

- A `leads` kind of record with its fields, the stage as a fixed list of values, and a link to the sales person.
- A rule: a sales person lists and changes only their own leads. The manager sees all.
- A summary that adds up the value per stage, computed by the database.
- A list with filters on the stage and the sales person, and a board view by stage if you ask for one.
- AI tools: your assistant lists and updates leads through the app's tools, so it can answer "which proposals are older than two weeks?".

## An invoice tracker

> We send invoices to clients and follow payments. An invoice has lines, a total, a due date and a status. Show me what is overdue, and mail the invoice to the client from its page.

- `invoices` and `invoice_lines`, linked, with a total kept up to date on the server each time a line changes.
- A summary of overdue invoices per client.
- A record page with its lines, a **Mail the invoice** button that makes the PDF and sends it with the app's mail template.
- A nightly task that marks invoices past their due date as overdue.
- A journal line for each invoice mailed.

## Equipment booking

> We lend equipment to our teams. A booking has an item, a person, a start and an end. Two bookings of the same item must not overlap. Show the bookings of a day.

- `equipment` and `bookings`, with a check on the server that refuses an overlapping booking and says which booking is in the way.
- A day view of the bookings, and a list per item.
- An AI tool that answers "is the large drill free on Friday?" from the bookings list.

## A client knowledge base

> Our clients read help articles in the app. Admins write them. Clients only read. Articles have a category and can be searched.

- `articles` with a category, a body and a published switch.
- Rules: clients list and read published articles only. Admins create, change and delete.
- A searchable list for clients, and the full list with editing for admins.

## After the first version

Each of these grows by requests: a new field, an export, a reminder mail, a second language. Each request comes back as its own card.