Raw feedback to a shipped decision
The full chain, start to finish.
Your weekly triage routine
A repeatable loop built around the dashboard.
Investigate a spike in complaints
Find the theme behind a jump in pain-point feedback.
Turn a quarterly goal into tracked work
Goal, evidence, actions, owners.
Let an agent watch something for you
Configure a trigger, get a report each run.
Trace any decision back to its evidence
Follow a claim down to the original quote.
Bring your own data over the API
POST feedback from a helpdesk, survey tool, or app.
See who changed what
Reconstruct how something got to where it is.
From raw feedback to a shipped decision
Get feedback flowing
Connect a source (see Integrations) or pipe data in over the
ingestion API. Feedback starts arriving as signals under
Insights → Data Signals (Data signals).
Squad groups signals into clusters
Related signals become clusters, themes like “slow search” or “requests for
SSO” (Signal clusters).
A strong theme becomes an insight
When a theme is strong enough, Squad synthesises it into a scored insight (
IN-…). Open it
to read its strength and momentum and the signals behind it.Link the insight to a goal
Link it to a goal it supports (Goals).
Work the recommended actions
Squad recommends actions off the insight (Actions). Prioritise them, assign
an owner, and Start the ones with a chat prompt to hand them to the assistant.
Write the decision up
Generate a brief (Briefs). A PRD specs the work. A decision brief makes the
call. Either one cites the evidence automatically.
Make the call
Review the brief on the Dashboard under Briefs to review, choose Build,
Defer, or Research, and Mark decided.
Your weekly triage routine
Open the dashboard
Open the Dashboard. The caption above the greeting tells you when the daily brief
was written.
Work Prioritized actions top-down
Start, mark done, or dismiss each. What is done drops off automatically.
Clear Briefs to review
Decision briefs waiting on a call, and PRDs sitting in draft or review.
Glance at New evidence
Anything surprising in the last day.
Press Re-brief
Once you have changed the picture, so the next brief reflects it.
Investigate a spike in complaints
Open the Signal Clusters tab
Open Insights and switch to the Signal Clusters tab (Signal clusters).
Filter and sort
Filter by Type → pain point and sort by Data Signals descending.
Read the member quotes
Open the largest cluster and read the Members quotes, the real feedback.
Follow the insight, or draft one
If it’s already an insight, follow the linked
IN-… and decide whether it needs a goal or an
action behind it. If not, ask the assistant to draft one.Turn a quarterly goal into tracked work
Create the goal
Create it on the Goals page.
Link the insights that justify it
Open its Insights tab and link them. This is the evidence for why the goal exists.
Accept the actions and give them owners
From those insights, accept the actions Squad recommends and give them owners
(Actions).
Keep the goal honest
As work lands, the goal’s linked insights and actions keep it honest. You can always trace the
goal down to the feedback driving it (Relationships).
Let an agent watch something for you
Configure what it watches and how often
Go to Agents → New and configure what to watch (a URL, a Slack channel, a Notion space, or
a workspace event) plus how often it runs (Agents).
Give it instructions and an output
Give it instructions and, if you want a written brief each run, a report question and where to
deliver it.
Read what it finds
Each run produces a report and folds new findings into your signals, clusters, and insights,
the same pipeline everything else uses.
Trace any decision back to its evidence
Nothing in Squad is an unsourced claim.Open the entity
A goal, insight, action, or brief.
Follow its links downward
A goal’s Insights tab → an insight’s supporting signals → a
signal’s original quote and source.
Click a reference chip
Anywhere a reference chip like
SI-12, IN-4, AC-7, or BR-3 appears, click it to jump
straight to that entity. See Relationships, or ask the
assistant “what’s the evidence behind this?”.Bring your own data over the API
Ask Squad for an organisation API key
Issuance is not self-service today. Write to
support@meetsquad.ai and say which organisation the key is for.
POST your feedback
From your own system (helpdesk, survey tool, app), POST feedback to
/api/v1/signals with a
sensible title and any metadata you want to keep. Everything arriving this way is recorded
against the api source.Watch it join the pipeline
Ingested signals join the pipeline exactly like integration data. Clustered, scored, and
surfaced as insights, with no further work from you.