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 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.
- 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.Finish the setup conversation
Give Squad the product name, the URL and at least one competitor. Everything downstream reads
this context, so a thin workspace produces weak insights.
Connect a source
Open Integrations and connect where your feedback actually lives. Support
conversations, sales calls, issue trackers, review sources. One busy source beats four sparse
ones. Slack is the most common starting point.
Let evidence arrive
Squad breaks incoming text into data 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. Signals that mean the same thing group into
clusters, and a cluster stays unnamed until it reaches three members, so
expect the clusters view to look sparse at first.
Review your first insights
Set a goal
Create a goal 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 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.Where to go next
Getting around
The sidebar, the command palette and reference chips
Chat assistant
What Squad can do for you once the workspace is running