> For the complete documentation index, see [llms.txt](https://docs.riff.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riff.ai/archive/quick-start-tutorials-legacy-staging/what-you-can-build-with-riff-v2.md).

# What you can build with Riff (v2 staging)

Apps and Agents — understand which build type fits your procurement or operations job before you start.

## Two build types. One platform.

Riff gives procurement and operations teams two things to build:

* **Apps** — a screen your team opens and uses. Dashboards, exception trackers, approval portals. Humans drive the interaction. AI is a feature inside the app.
* **Agents** — a configured worker that runs a job. Monitors your ERP, chases confirmations, flags exceptions, posts digests. Runs on its own and escalates only what it cannot decide.

***

### When to build an App

Build an App when a human needs to **see something, review something, or decide something**.

> *Procurement and ops examples:*
>
> * Open PO status dashboard — your team opens it each morning
> * Supplier delivery performance tracker — updated daily from your ERP
> * Invoice exception review portal — finance approves or queries each line
> * GR/IR reconciliation view — accountants match goods receipts to invoices

***

### When to build an Agent

Build an Agent when the job **runs on its own and acts on what it finds**.

> *Procurement and ops examples:*

> * Supplier confirmation chaser — detects unconfirmed deliveries, sends reminders, logs responses
> * Invoice matching agent — compares invoices to POs, flags mismatches, routes to the right approver
> * Delivery exception monitor — runs daily, alerts buyers to overdue POs, escalates aged items
> * RFQ outreach agent — sends requests to supplier list, collects quotes, summarises responses

***

### Quick decision guide

| If you need to...             | Build...        | Procurement example                                    |
| ----------------------------- | --------------- | ------------------------------------------------------ |
| See live ERP data             | App / Dashboard | Open POs, delivery status, GR/IR balance               |
| Track KPIs over time          | App / Dashboard | On-time delivery rate %, invoice cycle time            |
| Monitor and chase             | Agent           | Supplier confirmation chaser, overdue delivery monitor |
| Match, reconcile, flag        | Agent           | Invoice matching agent, GR/IR reconciliation agent     |
| Combine visibility and action | App + Agent     | Dashboard shows exceptions; Agent chases open items    |

***

### You can combine them

Most procurement teams use both:

* An **App** shows your team the current state — open POs, delivery performance, invoice queue
* An **Agent** works in the background — chasing confirmations, matching invoices, flagging exceptions

***

### Get started

| Build type    | What you'll build                                                                         | Link                                                                                                                           |
| ------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| **Agent**     | Monitor overdue deliveries from your ERP and alert your team automatically every morning. | [Quickstart Agent](https://github.com/ElleNealAI/riff-docs/blob/main/quick-start-tutorials/quickstart-agent/README.md)         |
| **Dashboard** | Supplier delivery performance dashboard connected to your ERP.                            | [Quickstart Dashboard](https://github.com/ElleNealAI/riff-docs/blob/main/quick-start-tutorials/quickstart-dashboard/README.md) |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.riff.ai/archive/quick-start-tutorials-legacy-staging/what-you-can-build-with-riff-v2.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.