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

# Getting started

> What you need before you build your first Speedtrain task, and the path you will follow.

This walkthrough takes you from an empty tenant to approved content in a destination. Work through it in order — each step assumes the one before it.

## Prerequisites

Before you begin, you need:

* Access to a Speedtrain tenant at [app.speedtrain.ai](https://app.speedtrain.ai)
* Structured records to work on — a product export, an article list, or any consistent set of documents
* A clear idea of what "good output" means for your job, specific enough to write down

<Tip>
  That last point is the one people underestimate. If you cannot yet say what would make an output wrong, start there. The quality rules are what turn this from a prompt into a pipeline.
</Tip>

## The path

<Steps>
  <Step title="Set up your tenant" stepNumber={1}>
    Understand tenants, environments, and where your data lives. [Tenants and environments](/speedtrain/getting-started/tenants-and-environments)
  </Step>

  <Step title="Add a content source" stepNumber={2}>
    Create an index and get your records into it. [Add a content source](/speedtrain/getting-started/content-source)
  </Step>

  <Step title="Build a task configuration" stepNumber={3}>
    Define the specialist, the variants, and the quality rules. [Build a task configuration](/speedtrain/getting-started/task-configuration)
  </Step>

  <Step title="Preview and review" stepNumber={4}>
    Run it over a handful of documents and read what comes back. [Preview and review](/speedtrain/getting-started/preview-and-review)
  </Step>

  <Step title="Publish the results" stepNumber={5}>
    Send accepted content to a destination. [Publish the results](/speedtrain/getting-started/publish)
  </Step>
</Steps>

## How long it takes

Getting a first configuration generating plausible output takes under an hour. Getting it to a trustworthy approval rate takes a few rounds of previewing, reading rejections, and sharpening rules — that is the real work, and [Iterating a configuration](/speedtrain/authoring/troubleshooting) covers it.