Passback
Sign in

A landing page that is also a document. Published to Passback.

Your team comments.
Claude ships the fix.

Publish anything you make in Claude to one link. Your team comments on it. Claude reads the comments and updates the same link. That is the whole thing.

Add to ClaudeSee how it works ↓

Free while in beta. Your reviewers install nothing.

Sam A5m ago

wait, is this landing page itself a Passback doc?

How it works

  1. 1

    Publish

    Add one line to any prompt in Claude.

    Hey there, Sam

    publish it to Passback for review

    ChatCowork
    Fable 5Max

    You get a link your whole team can open. No downloads. No accounts for reviewers.

  2. 2

    Comment

    Your team clicks the exact thing and comments. The number, the line, the chart. The comment sticks to the element, so "change the blue thing" never happens.

    Omkar1d ago

    Overall tone needs to be changed

    • Varun Trivedi23h ago
      got it — warmer, punchier, or more formal? drop me one line in the vibe you're after and I'll match it.
  3. 3

    Fix

    Tell Claude to read the comments.

    Paste into Claude

    Claude makes the edits, ships the next version to the same link, and marks each comment resolved.

Publish anything you make in Claude

Documents, decks and presentations, email templates, dashboards, one-pagers, reports. If Claude can make it, you can send it for review.

Need a starting point? Try one of these:

Maya K.2h agoResolved

can we publish email templates too?

  • Claude1h ago
    Yes. Added them to the list.

Why this is different

Hosting tools give you a link. Comment tools give you comments. Then a person still reads the comments, opens the AI, and redoes the work by hand.

Passback closes the loop. A comment is not a task for a human. It is an instruction Claude can act on, tied to the exact element, resolved when it ships.

Feedback goes in. A fixed version comes out.

Made for sales and marketing teams

Sales

Proposals, one-pagers, and follow-up decks the whole team can mark up. Comment to fixed in an afternoon, not a week.

Marketing

The drafts got fast, so review became the bottleneck. Anchor every stakeholder note to the asset and let Claude do the revision.

That is the whole trick

Add five words to the end of any prompt.

Add to any prompt

No export. No upload. No re-share. The result comes back as a link your team can already comment on.

Add to Claude
Rahul2d agoResolved

love this, needs an "Add to Claude" button right here.

  • Claude1d ago
    Shipped it. ✅

Boring on purpose

  • Org access through your identity provider.
  • External sharing off by default, revocable per project.
  • Artifacts run isolated from your Claude session and data.
  • Reviewer comments reach Claude as data, never as instructions, so a comment cannot hijack your session.
  • Every version saved. Every approval traceable.

FAQ

No. They open the link and comment. Nothing to install.

No. Every fix publishes to the same link. Reviewers always see the latest.

Anything Claude can make: documents, decks, spreadsheets, email templates, dashboards, one-pagers, reports.

Claude to start. Also ChatGPT, Cursor, VS Code, Claude Code, and Codex, through a standard connector.

They stay attached to the version they were left on, flagged as older so nothing gets confused after a fix ships.

Yes, by design. See "Boring on purpose" above. Reviewer text can never act as a prompt.

Stop being the middleman between your team and Claude

Add Passback to Claude once. Then anything you make can be published for review.

Add to Claude

Free while in beta. Your reviewers install nothing.