drafty

BugHerd is for your dev team. Drafty's for your client.

Send a link to the design, the PDF, or the live site. Your client comments on the exact spot — no login, no extension, nothing to install. Whether you built it in Figma, v0, or by hand.

Public linkNo loginWorks on any tool
drafty.im/canvas/logo-conceptv1v2
Logo concept
make the logo bigger
claude code
$ drafty comments inbox
make the logo bigger· Logo concept
✦ Claude is working…
pushed v2 — same link · thread resolved
Your client comments on the exact spot — Claude ships the fix. No account.

The feedback you're getting today

Scattered across iMessage and Slack — every note a guess at which version, which element.

Maya (client)
Today 4:12 PM
saw the landing page, looks great 🙌
can you make the logo bigger though
which one — header or footer?
this one
that's the old version 😅 are you on the link I sent, or a screenshot?
…the screenshot

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 BugHerd

What each is actually built for — so you pick by the reviewer you're sending it to.

What your client needs DraftyBugHerd
Comment with no account
Works on any artifact (Figma, v0, hand-built)
Anchored, threaded human discussion
Turn any live site into a review board
Claude reads the feedback and ships the fix
Built for dev/QA bug tracking

How it works

01

Share a link that opens anywhere

Drafty turns your artifact into a page that renders in any browser, on any phone. Send the link — no install, no signup.

.html.md
drafty.im/x9k
02

They point at the exact spot

Your client hovers any element, clicks, and leaves a note pinned right to it. No screenshots, no “the bit near the top.”

03

The fix lands on the same link

Claude reads the comments in your terminal, makes the change, and ships a new version on the same URL — then marks it done.

we are really very goodfaster, every loop
make it punchier

Why people switch

The old way
  • Client won't install an extension or make an account
  • BugHerd is built for dev/QA, not client sign-off
  • Feedback scattered across email, Slack and calls
With Drafty
  • Guest commenting on a public linkThey comment in one click, on phone or desktop
  • Cross-tool review of any artifactDesigner → client approval, not engineer → tester
  • Anchored threads on the artifactOne source of truth, pinned to the exact spot

Who it's for

Freelance designer

Send the client a mockup link. Get notes on the design, not a vague email thread.

Solo consultant

Share the deliverable. The client reacts inline — and it looks like your work.

Indie builder

Drop your v0 app in a thread. Testers comment without signing up for anything.

Questions

Does my client need an account to comment?
No. They open the link and comment as a guest — no signup, no login.
Can I collect feedback on something I didn't build in Drafty?
Yes. Drafty works on any artifact — a Figma export, a v0 app, a PDF, or a live website.
How is Drafty different from BugHerd?
BugHerd is built for dev teams tracking bugs in a browser extension. Drafty is built for sending a client a link and getting anchored feedback back, on any artifact, with no account.
Is it really free to start?
Yes — you can publish your first canvas and collect 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.