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

# Projects vs applications (products)

> A project is the testing job. Applications are the recipient UI for products. Most freelancers only need a project.

Two words that sound like "the thing we're testing." They are not the same screen.

## Project

Where **you** build suites, run tests, and log findings. **Create Client Project** / **Create First Project**. Type is the platform (`web`, `ios`, and so on). This is the job folder.

## Application / product

On the **recipient** side, **Applications** is the UI for products they hold in a portfolio. **Portfolio**, **Inbox**, **Archive**, **Providers** sit with that world. That's "we receive UAT packets about our products," not "freelancer test execution."

## What you should do

If Acme hired you to test checkout: one **project**. Connect Acme as a client/recipient. Deliver. You do not need to model Acme's entire product catalog as Applications in *your* org.

If you *are* the client org receiving a freelancer's delivery, you'll spend time in **UAT Inbox**, **Receiving UAT**, Applications, and review actions.

<Note>
  Copy in the app sometimes says "product" in empty states and "Applications" in nav. Same mismatch we document internally. When in doubt, execution = **Projects**.
</Note>

<Columns cols={2}>
  <Card title="How it's organized" icon="layers" href="/concepts/how-organized">
    Full hierarchy.
  </Card>

  <Card title="Connect a client" icon="link" href="/delivery/connect">
    Delivery ID, code, invitation.
  </Card>
</Columns>