> ## Documentation Index > Fetch the complete documentation index at: https://docs.meetsquad.ai/llms.txt > Use this file to discover all available pages before exploring further. # Quickstart > Set up a new workspace, from the opening conversation to your first source and your first insights. Quickstart Quickstart Squad sets a workspace up by talking to you. There's no setup wizard and no form to fill in. Create a workspace and the chat panel starts a conversation, asks what your product is, and writes what it learns straight into the workspace as you answer. ## The opening conversation Until a workspace is set up, the chat panel opens on its own, docked to the right, and sends the first message for you. Squad's first question is waiting by the time the page settles. This happens once, on a workspace with no conversations yet. On a phone the panel stays closed until you tap **Ask your Squad**. Answer in prose. Squad saves as it goes rather than at the end, so a conversation you abandon halfway still leaves the workspace better off. ### What it asks first Squad works out what your product is before anything else. * **Product name and what it does.** Written to your workspace immediately. * **Your website URL.** Squad reads the site and writes a product overview document from what it finds, tagged `product`. * **The tools your team uses.** Name Slack, GitHub, Linear, Notion and it points you at [Integrations](/integrations) to connect them. * **Tech stack and target users.** Saved to the workspace description. ### What it asks next Once it can describe your product back to you, Squad moves on to the market around it. * **Competitors.** Name who you compete with and Squad researches each one and writes it up. * **Current priorities.** Tell it what matters this quarter and it creates [goals](/goals). * **Background research.** Squad kicks off a research run that keeps working after the conversation ends, writing competitor, market, trend and persona documents into your knowledge base. Documents appear as they land, so there's nothing to refresh. ### When onboarding is done Squad closes onboarding itself once it's confident it understands your business. The background research run also closes it when the workspace reaches five documents and one goal. After that the chat panel stops opening on its own and returns to whatever mode you last left it in. Your knowledge base already has five folders waiting. **Product**, **Competitors**, **Feedback**, **Market** and **Research**. Squad files what it writes into them and adds folders when a topic needs one. ## Then, in this order Work through these five and the workspace starts producing insights of its own. Give Squad the product name, the URL and at least one competitor. Everything downstream reads this context, so a thin workspace produces weak insights. Open [Integrations](/integrations) and connect where your feedback actually lives. Support conversations, sales calls, issue trackers, review sources. One busy source beats four sparse ones. [Slack](/integrations/slack) is the most common starting point. Squad breaks incoming text into [data signals](/signals), each keeping the customer's verbatim words and a link back to where it came from. Watch them land under **New evidence** on the [Dashboard](/dashboard). Signals that mean the same thing group into [clusters](/signal-clusters), and a cluster stays unnamed until it reaches three members, so expect the clusters view to look sparse at first. Clusters get synthesised into [insights](/insights), scored on how well evidenced they are and whether the theme is growing. An insight scoring 0.65 or above gets a ranked list of [actions](/actions) under **Squad recommends**. Read the top insight, check the signals behind it, then start or dismiss what it suggests. Create a [goal](/goals) and give it an importance from 1 to 5. Goals never change an insight's score. They change which work Squad puts in front of you, because it weighs relevance to your goals when it ranks actions. ## Checking your work The **Context health** card on the [Dashboard](/dashboard) scores the workspace from 0 to 100 and labels it Starved, Lean, Healthy, Bloated or Flooded. Press **Improve** for a breakdown by category and a list of specific things to fix, each with a button that takes you there. A fresh workspace starts Starved. Connecting a source and adding goals is what moves it. You can use Squad without finishing the setup conversation. It has less to work from, so its recommendations are more generic. Add context later by talking to the assistant, editing [workspace settings](/workspace-settings), or connecting a source that carries product context. ## Where to go next The sidebar, the command palette and reference chips What Squad can do for you once the workspace is running This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.