# Superflow vs Userback

> Userback is a feedback tool. Superflow is a feedback tool plus AI agents built from your checklist. They check every change; clients approve by link.

This is the Markdown copy of https://usesuperflow.ai/comparisons/superflow-vs-userback, published for AI agents and scripts. The HTML page is canonical.

## Key facts

| Field | Value |
| --- | --- |
| Page type | Head-to-head comparison |
| URL | https://usesuperflow.ai/comparisons/superflow-vs-userback |
| Compares | Superflow vs Userback |
| Facts checked on | 2026-07-01 |
| Disclosure | Published by Superflow. Superflow is one of the tools compared. |
| Last updated | 2026-07-01 |

## Dimension by dimension

| Dimension | Superflow | Userback | Verdict |
| --- | --- | --- | --- |
| Who checks the site | Agents run your checklist. Every change, desktop and mobile. Findings land as pinned comments, rationale attached. | A person reports every issue, through the widget, the browser extension, or a link. Userback's AI runs after that report exists: it categorizes, scores sentiment, drafts titles, and clusters themes. It doesn't look at the site itself. (verified July 2026) | A report is a record of what a person already caught. Userback's AI organizes that record well. Finding it in the first place is the part Superflow removes. |
| How the client says yes | Multi-step review flows: agents check, your team gates, then the client. Your client opens a link and taps Approve. No account, no login, no app, from their phone. | Any reporter submits free, from the widget, the browser extension, or a link. No account, no seat, unlimited. A formal client approval flow: not yet verified. (verified July 2026 except where noted) | Userback's free reporter link is good, and unlimited for everyone who uses it. The difference is the gate: in Superflow, the client's yes is a recorded step, not a submission. |
| Where you review | Superflow lives on the site itself: passwords, Okta, SSO, no extension needed, guests included. Findings tagged by device. | The widget embeds in your own app; the browser extension captures on any site, including staging. Behind third-party logins and SSO: not yet verified. | Both review live pages, not a copy. Behind third-party logins and SSO, the Userback side is pending verification. If it resolves even, it renders even. |
| What stays private | Internal-only notes your team sees and the client never does. The debate stays private; the client sees one settled answer. | Team Comment Controls can restrict members, like developers, to internal-only comments. Gated to the Business plan and up. (verified July 2026) | Userback grants this too, starting on Business. In Superflow, internal-only comments run on every plan. |
| What gets captured | Element and text pins, area comments. A screenshot attaches to every comment automatically. Recordings: screen, video, voice, from the toolbar. | One submission attaches an annotated screenshot, video recording, console logs, network requests, and browser and system metadata. Session replay ships with the report, so your team watches what happened before it was filed. Session replay, console logs, and network requests start at the Business plan. (verified July 2026) | Userback's capture is genuinely strong. Replay and logs start at Business. In Superflow, screenshots and recordings run on every plan. |
| What it remembers | Brand rules and past decisions, learned once, fed to the agents next project. | No persistent memory concept. AI Insights clusters themes inside a project, not across projects. (checked July 2026) | The tenth project should not start like the first. |
| How it fits your stack | Custom statuses, client gates, kanban. Two-way Asana, Monday, ClickUp. Slack built in. | True two-way sync with Jira, Linear, and ClickUp. Status changes move both directions. Support tool integrations like Intercom and Zendesk, plus a REST API and webhooks, are Business Plus only. (verified July 2026) | Userback's two-way sync is real too. The difference is which tools: Jira and Linear there, Asana and Monday here. If Jira or Linear is your spine, weigh that honestly. |

## Scorecard

| Measure | Userback | Superflow |
| --- | --- | --- |
| Who checks the site | a person; AI organizes after the report is submitted | agents, from your checklist |
| How the client says yes | free reporter link, unlimited; approval gate - | a recorded approval: team gate, then client gate |
| Where you review | widget and extension on any site; third-party SSO - | live site, behind logins and SSO, no extension |
| What stays private | internal-only comments, Business plan and up | internal-only comments |
| What gets captured | screenshots, video, session replay, console and network logs; replay and logs start at Business | automatic screenshots; screen, video, voice |
| What it remembers | no | Memory, per client |
| How it fits your stack | two-way Jira, Linear, ClickUp; REST API and webhooks at Business Plus | statuses, client gates, kanban; two-way Asana, Monday, ClickUp; Slack |
| What it costs | Free $0 / Team $29 / Business $79 / Business Plus $159 per month, billed annually (July 2026) | Free plan; Growth $29 per seat/mo ($24 annual); Scale $34; Enterprise custom |

## Where Superflow fits

Userback earned its place. One submission captures an annotated screenshot, video, console logs, network requests, and system metadata. Session replay ships with the report, so your team watches what happened before it was filed. Reporters submit free, with no seat and no account. True two-way sync with Jira, Linear, and ClickUp keeps statuses moving in both directions.

## Pricing

Verified July 2026: Free $0, Team $29, Business $79, Business Plus $159 per month billed annually ($39, $99, $199 monthly). Reporters are unlimited and free on every plan. Feature Portal add-on $31 per month billed annually.

From the Growth plan. See /pricing.

## Sources

- https://userback.io
- https://userback.io/pricing
- https://userback.io/features/feedback-widget
- https://userback.io/features/session-replay
- https://userback.io/integrations

## Questions and answers

### Is Superflow just Userback with AI on top?

No. Userback's AI organizes what a person reports, after the fact; Superflow's agents do the finding. A person makes every call.

### Do the agents replace my reviewers?

No. Agents run the first pass. Your team, then your client, signs off.

### What happens to our Userback projects?

Finish them in Userback. Start new work in Superflow. Nothing migrates on day one.

### Will our clients have to learn a new tool?

No. They get a link and an Approve button. No account, no login, no app, from their phone.

### We sync tickets to Jira and Linear from Userback.

Superflow syncs two-way with Asana, Monday, and ClickUp, plus webhooks and a REST API. Jira and Linear are not built in today; if either runs your delivery, weigh that.

### What does it cost?

From the Growth plan. See /pricing.

## Related pages

Each of these also publishes a Markdown copy at its own path plus `.md`.

- [The 5 best Userback alternatives](https://usesuperflow.ai/alternative/userback-alternative)
- [Superflow vs Usersnap](https://usesuperflow.ai/comparisons/superflow-vs-usersnap)
- [Superflow vs BugHerd](https://usesuperflow.ai/comparisons/superflow-vs-bugherd)
- [AI review agents](https://usesuperflow.ai/ai-review-agents)

## About Superflow

Superflow is a website and creative-asset review tool. Its agents watch every page of a site, report what changed, and route findings to the people who approve them. Teams leave contextual feedback on live sites, staging environments, PDFs, images, videos, and Lottie animations, and comments sync two-way with Asana, ClickUp, Monday, Slack, Webflow, and Google Tag Manager.

Machine-readable entry points:

- Site index: https://usesuperflow.ai/llms.txt
- Full site content in one fetch: https://usesuperflow.ai/llms-full.txt
- Free tools, with a Markdown copy of each: https://usesuperflow.ai/tools.md
- MCP server (Streamable HTTP, no account and no API key): https://usesuperflow.ai/api/mcp
- Agent card: https://usesuperflow.ai/.well-known/agent-card.json