BugSmash collects the feedback. Drafty ships the fix.
Both let a client comment on the exact spot without logging in. The difference: Drafty keeps the conversation anchored to your doc, design, or PDF — and when you're ready, Claude reads the thread in your terminal and pushes a new version on the same link.
The feedback you're getting today
Scattered across iMessage and Slack — every note a guess at which version, which element.
Every message here is a comment that belonged on the artifact. In Drafty they tap the exact spot and the note pins there — threaded, on one link that's always the current version. No “which one,” no screenshots, no “FINAL.html.”
Drafty vs BugSmash
What each is actually built for — so you pick by the reviewer you're sending it to.
| What your client needs | Drafty | |
|---|---|---|
| Client comments with no login | ||
| Anchored threads on docs, PDFs, and Figma exports | images only | |
| Threaded reply, resolve, reopen per comment | ||
| Claude reads feedback and ships a new version | ||
| Searchable library of every artifact and its history | ||
| Video and audio annotation with time-stamped comments |
How it works
Share a link to any artifact
Push the doc, PDF, or design export to Drafty. It becomes a page your client can open on any device — no account, no extension, nothing to install on either end.
They pin a note to the exact spot
Your client clicks any heading, paragraph, or element and leaves a note right there. No screenshots, no "the thing near the top-left." The comment is anchored to that line.
Claude ships the edit in the same thread
Run the Drafty CLI in your terminal. Claude reads the pinned thread, makes the change, and pushes a new version on the same link — the comment resolves automatically.
Why people switch
- BugSmash collects feedback but you still make every change by hand
- Client feedback on docs and briefs gets scattered across email
- Last month's review is buried in a list of project links
- Claude reads the comment thread and ships the fix — The update lands on the same link — no copy-pasting from a feedback panel
- Anchored threads on any text artifact — Every note is pinned to the exact paragraph — one source of truth
- Searchable library with full version history — Find any artifact and its feedback in ⌘K, including resolved threads
Who it's for
Send the brand guide as a link. The client marks the exact line they want changed — not a vague voice note or screenshot.
Share the proposal. Your client reacts inline, you ship the revision on the same link — it still looks like your work.
Drop the spec doc into a thread. Reviewers comment without signing up, and you close each note with a shipped edit.
Questions
- What is BugSmash used for?
- BugSmash is a multi-format feedback tool for agencies and teams reviewing websites, videos, PDFs, images, and audio. Clients leave comments via a shareable link — no account required. It's broad by design, covering 30+ file types including video and audio.
- How is Drafty different from BugSmash?
- BugSmash collects feedback across many formats and passes it to your team to act on. Drafty is focused on the designer-to-client sign-off loop on docs, PDFs, and design exports — and closes the loop by letting Claude read the thread and ship the fix on the same link.
- Does my client need an account to leave feedback?
- No — on both Drafty and BugSmash. Your client opens the link and comments as a guest. Drafty also keeps a persistent guest identity so a thread reads as a real conversation, not anonymous sticky notes.
- Can I get feedback on a doc or brief, not just a website?
- Yes. Drafty works on any text artifact — a doc, a PDF, a proposal, or a Figma export. Comments anchor to the specific element your client clicked.
- Does BugSmash work for video and audio reviews?
- Yes — and that's where it genuinely wins. BugSmash supports time-stamped annotation on video and audio files. Drafty doesn't do video or audio; if your deliverables are mostly media files, BugSmash is the stronger fit.
- Is it free to start with Drafty?
- Yes. Publish your first canvas and collect guest comments for free — no card required.
Keep exploring
Send your next client a link, not a login.
Free to start. No card. They comment in one click — Claude ships the fix.


