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

# Quickstart

> From sign-in to your first source-linked answer in under ten minutes.

This walks you from sign-in to a useful answer. If your organization has SSO enabled, log in with your work credentials. If not, your GetWhys contact will provision your account.

<Steps>
  <Step title="Sign in">
    Go to [app.getwhys.io](https://app.getwhys.io) and sign in with your work email.
  </Step>

  <Step title="Take the tour">
    Most new users complete a 30-minute white-glove onboarding with a GetWhys team member. Worth doing. Email [support@getwhys.io](mailto:support@getwhys.io) to book one.
  </Step>

  <Step title="Ask your first question">
    Click **Chat** in the left navigation. Type a question you actually need answered. Specificity is the cheat code. Questions that consistently work on day one:

    * "What pain points drive mid-market IT directors to evaluate new endpoint detection tools?"
    * "When CMOs at SaaS companies between $50M and $200M ARR shop for ABM platforms, what features do they prioritize?"
    * "What objections do CFOs raise most often when evaluating finance automation software?"
    * "What language do CISOs use when describing data loss prevention buying decisions?"

    Stuck? Click **View all templates** above the input. Starter prompts for personas, content, brand voice, competitive research, and messaging.
  </Step>

  <Step title="Read the citations">
    Click any citation in the answer to see the source: the interviewee's title, company size, industry, and a snippet from the underlying research interview. Citations are how you verify the answer and learn more about who's behind it. They're also how you handle the "how do we know?" question in your next meeting. More in [Citations](/features/citations).
  </Step>

  <Step title="Follow up">
    Chat keeps context within a conversation. Follow-ups go deeper:

    * "Can you break that down by company size?"
    * "What would a skeptic say about this?"
    * "What questions am I not asking that I should be?"
  </Step>

  <Step title="Set up Customization (recommended)">
    If you'll use Message Testing, or you want Chat to consistently apply your org's context, head to **Customization** in the left nav and set up at least one [Persona](/features/personas), your [Brand Voice](/features/brand-voice), and your [Messaging Framework](/features/messaging-frameworks). Once they're in, every Chat answer and every Message Test runs against them — and they flow through MCP to the rest of your AI stack.

    You can build these from scratch or use Chat to draft them. See the templates inside Chat.
  </Step>

  <Step title="Create a Project">
    If you're working on a specific initiative (launch, campaign, competitive review, persona refresh), create a [Project](/features/projects) and keep the related conversations and artifacts there. Projects are how teams collaborate on a body of work.
  </Step>
</Steps>

## What's next

<CardGroup cols={2}>
  <Card title="Key concepts" icon="lightbulb" href="/getting-started/key-concepts">
    A short tour of the building blocks.
  </Card>

  <Card title="User types" icon="users" href="/getting-started/user-types">
    What's included at each access level.
  </Card>

  <Card title="Prompting tips" icon="sparkles" href="/tips/prompting">
    How to write questions that get sharper answers.
  </Card>

  <Card title="MCP integration" icon="plug" href="/integrations/mcp">
    Connect GetWhys to Claude, Cursor, and your AI stack.
  </Card>
</CardGroup>