> ## 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.

# Create a project

> A project is the testing job. Create it, pick a type, then add environments, tests, and a cycle.

A **project** is the engagement: one product (or one slice) you are testing now. It is not your whole freelance business, and it is not the client's company record.

Freelancers usually work in **Projects**. **Applications** (products), **Providers**, **Portfolio**, **Inbox**, and **Archive** are the recipient/client side. You can ignore most of that until someone is receiving your delivery. [Project vs product](/concepts/projects-products).

## Create it

From the empty state you'll see **Create First Project** or **Create Client Project**. Fill in a name people will recognize on an invoice.

**Type** is one of: `web` | `ios` | `android` | `admin_portal` | `api` | `wordpress` | `saas` | `other`. Pick the closest. It helps pack recommendations; it does not lock you out of other tests.

Under the org, a project can hold surfaces, features, environments, personas, suites, cases, cycles, and runs. You don't have to fill every bucket on day one.

## After create: empty project

You'll land on setup options:

* **Guided wizard:** eight questions, then the app creates project pieces, environments, suites, starter tests, a first cycle, optional assignments. [Wizard](/setup/getting-started).
* **Import tests:** Excel, CSV, Word, PDF, mixed. [Imports](/imports/bring-existing).
* **From my codebase:** prompt to agent JSON `simpleuat-project-setup.json` to upload to preview to apply. Paid on Pro+. [Codebase](/setup/codebase).
* **Import history:** past codebase setup uploads.
* **Manual:** you add suites and cases yourself.

You can change structure later. [Can I change it?](/setup/can-i-change-it).

<Note>
  **Start guided setup** is the wizard CTA. If you already have a spreadsheet or a pack in mind, skip the wizard. The wizard is a starter, not a contract.
</Note>

## What "done enough" looks like

You can start executing when you have: an environment, at least one case (in a suite), a cycle that includes that case, and you as an active tester. [Can't start a run](/troubleshooting/cant-start).

<Columns cols={2}>
  <Card title="Choose a setup method" icon="sliders-horizontal" href="/start-here/choose-setup">
    Pack, import, manual, codebase, wizard.
  </Card>

  <Card title="Empty project tour" icon="folder" href="/setup/empty-project">
    What each setup option is for.
  </Card>
</Columns>