Questions, answered

Yes — 14 days. No credit card. The trial covers 1 project, 2 insight runs, and uploads up to 500 rows — enough to run a real batch of your own feedback and see the memo before you decide. One trial per account. You only enter payment details if you decide to continue.

6 sources connect once and then fill themselves: Zendesk tickets, Intercom conversations, App Store and Google Play reviews, a Slack channel (or the /signal command), and a private email address per project you can auto-forward to. For anything without an integration, upload a CSV or paste text. It all lands in the same ranked readout.

It groups by meaning, not keywords. Every entry becomes an embedding, and recurring complaints cluster into emergent themes — so problems like Checkout or Search surface on their own — ranked into a Top 5, each with real sub-issue counts and customer quotes.

No — that's the point. Connect a source or upload a CSV, and GliddeSignal normalizes entries, drops empty rows, removes duplicates, and embeds everything on the way in. For a messy CSV it even auto-detects the column that holds the feedback. There's no taxonomy to design and no tags to maintain.

No. An intent gate classifies every entry as a complaint, praise, suggestion, or neutral before anything is grouped, and drops the praise so it can't pad a count. Everything else feeds the themes, so the numbers stay honest.

A ranked Top 5 of problems — each with quotes and sub-issue counts — a feature-level pain map, a view of what changed since your last run, a sprint-sized action per problem, and a one-page executive memo with exactly three recommended actions you can export as a PDF or share as a read-only link. You can also ask the run free-text questions, answered strictly from its own evidence.

Up to 5,000 entries per run. A full 5,000-entry run takes roughly five to six minutes end to end; smaller batches finish faster. Runs process in the background, so you can close the tab — we'll email you when it's done.

Whenever you have a fresh batch — many teams run monthly. The 'What Changed' view only appears once there's a previous run to compare against, so a regular cadence is where GliddeSignal becomes most useful.

You correct outputs inline — re-tag a quote, rename a problem, edit or 👍/👎 an action or the memo. Each correction is remembered for that project and quietly steers future runs toward your vocabulary. There's no model fine-tuning, and with zero corrections behavior is unchanged.

Yes. Connect a project to Linear or Jira and any top problem's action can be filed as a real issue in one click, with the supporting customer quotes attached — the button then links straight to the ticket. You can also export the one-page memo as a PDF or share it as a read-only link, and copy anything into Slack.

No — plans are metered by runs, not by seats. The outputs are built to travel instead: turn any memo into a read-only link colleagues open with no account, export it as a one-page PDF, or file an action into Linear or Jira with the customer quotes attached. The people who need the readout get the readout, not a login.

No. There's no model fine-tuning on your data, and the corrections you make stay scoped to your own project. The Security page has the full detail — where your data is processed, who the subprocessors are, and how deletion works.

Starter is $99/mo (3 projects, 5 runs a month, last 10 runs visible). Pro is $199/mo (5 projects, 10 runs, last 50). Annual billing gives you two months free, and runs reset monthly on either interval. On either paid plan you can buy extra runs or project slots at any time — unused run credits roll over. Pro also gets a weekly digest that runs a batch and emails you the memo.

They're different shapes of tool. Dovetail is a research repository your team curates and works inside; Productboard is a platform your roadmap lives in; Canny is a board your customers post requests on. GliddeSignal is none of those — it's a recurring readout: point it at a batch of feedback, get ranked problems, what changed since last run, and a one-page memo, then leave. Our comparison pages say plainly when each of those tools is the better buy.