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

# Quickstart

> From signup to your first tracked AI answers in about ten minutes.

## 1. Create your project

Sign in at [app.mavel.ai/login](https://app.mavel.ai/login) (if you're
new, the same magic link creates your account) and follow the
onboarding wizard. Give it your website and target markets, and Mavel drafts your
project profile, an initial topic set, and a starter prompt list from your
actual site content. You confirm or edit everything before anything runs.

## 2. Review your prompts

Prompts are the questions your buyers actually ask AI assistants: the core
input to everything Mavel measures. The wizard seeds a starter set; review it
and add the questions you care about most. Guidance on writing prompts that
produce meaningful measurements is in
[Setting up your prompts](/setup/prompts).

## 3. Confirm your brands and competitors

Mavel tracks your brand and the competitors you name in every captured answer.
Check the suggested competitor list and adjust it: Share of Voice is only as
good as the competitor set behind it. See
[Brands and competitors](/setup/brands).

## 4. Let the first crawl run

Your prompt set runs against the enabled AI surfaces shortly after setup
completes, then daily after that. The dashboard fills in as the first answers
land. You don't need to wait on an empty screen; early results appear within
minutes.

## 5. Read your first results

Start on the Overview: visibility, position, sentiment, and Share of Voice for
your brand and competitors, per surface and over time. Then open
[Sources](/results/sources) to see which domains and URLs the AI engines cited:
that list is where your content strategy starts.

<Note>
  Answers vary between runs even for identical prompts: AI engines are not
  deterministic. Mavel measures trends across daily runs, which is why metrics
  stabilize after a few days of data. Judge weeks, not single answers.
</Note>

## Next steps

* Organize prompts with [topics and tags](/setup/topics-and-tags)
* Turn source gaps into a content plan with [Actions](/actions/overview)
* Query your data from Claude or Cursor via the [MCP server](/mcp/introduction)