For the readouts, scope docs & prototypes you build as HTML with AI

Your client comments. You fix it in one click. They re-approve — all on the same link.

No account for them. No re-sending files. No “which version was that?”

Share an interactive HTML doc at a private link. Your client pins comments right on it. Turn any comment into an AI edit with one click — the doc updates, the old approval downgrades itself, and they stamp the version they actually saw.

$99 flat for the whole team · $29 solo · free to start — unlimited clients and reviewers.

“That wasn't in scope.”

Every approval is bound to a version, and the record shows what changed since. When the conversation gets expensive, you have the receipt.

You built it in HTML. Sign-off shouldn't mean a screenshot.

Your deliverable is interactive now — a filterable report, live charts, a readout Drive won't render. So feedback scatters across email and Slack, and the yes shows up as a looks good with no version attached. Restamp keeps the whole loop — comments, fixes, approval — on the doc itself.

From delivered draft to signed-off record

1

Share a private link

Send one link. Anyone reviewing — including people at the client's company — comments and approves with no login and no account. Nothing to install.

2

They comment, you fix

Clients pin comments right on the doc. Turn any comment into an AI edit with one click — Restamp proposes the change and only touches the doc when you accept.

3

They stamp — you keep the receipt

Your client stamps approval when it's ready. The stamp binds to that exact version, and the approval record is your receipt of who signed off on what.

Change the doc and the old stamp downgrades to “approved an earlier version,” so you request a fresh yes on what actually changed. Approval always reflects the current version — automatically, no chasing.

Every version, and every yes — on one link.

As comments turn into fixes, each version is saved, and each approval binds to the version your client actually saw. The approval record is the natural byproduct: who approved what, when, and what changed since — one link, always current.

Already building in Claude Code? Push straight from the terminal.

The publish-to-restamp skill puts a new version live from wherever you already work. Fix the doc in Claude Code, push, and the client's earlier stamp downgrades on its own — same link, no re-send, no “here's v4 attached.” Or fix it in the browser with one click. Both paths end at the same record.

In Claude Code: “publish this HTML to Restamp” → you get a review link back.

Built for the work you deliver

Data & analytics consultancy

A monthly findings readout the client signs off before the retainer renews — on record, tied to the numbers they saw.

Agency scope doc

Scope approved up front, then re-approved every time it moves — so the invoice matches what was actually agreed.

Prototype sign-off before build

A clickable prototype the stakeholder actually uses before anyone writes production code — approved on the version they clicked, not on a screenshot in a thread.

Private by default — you control who gets in.

Free artifacts

Live at an unguessable URL that search engines don't index. Anyone with the link can view — which is what Free is for: sharing in the open.

Solo & Team

Private artifacts with access control. Invite specific emails — including your client's domain — and a forwarded link alone won't open it.

Verified identity

Makers sign in with a passwordless magic link. Every comment and every stamp is bound to a real, non-impersonable identity.

Simple pricing

Get sign-off for free. Go private with Solo for your own client work, or Team for a whole shop.

Free
$0

For one-off, public work.

  • Unlimited public artifacts
  • Unlimited reviewers — no account needed
  • Figma-style comments & approval stamps
  • ~25 AI fixes / month
  • Full version history
Get started
Team
$99 / month

One flat price for your whole team — or $990 / year (2 months free). Everything in Solo, plus:

  • Unlimited makers in one shared workspace
  • Shared client folders
  • Unlimited AI edits
Upgrade to Team

Unlimited clients and reviewers, flat — they never count as seats. Proofing tools run $199–399/mo and e-signature bills per seat.

Questions

Do my clients need an account?

Never. They open the link, read, pin comments, reply, and place an approval stamp — no login, no signup, nothing to install. That includes reviewers at other companies.

Why not Google Slides or PowerPoint?

If a slide deck is what you're making, make it — you don't need Restamp for that. Restamp isn't a builder; it's where an AI-built HTML doc gets reviewed, fixed, and signed off, by reviewers who need no account. If your work already lives in HTML and someone has to approve it, that's the fit.

I build in Claude Code or Cursor. Does this fit my workflow?

Yes — the publish-to-restamp skill pushes a new version from your terminal, and the approval state updates automatically. You don't have to switch to the browser to ship a fix; the one-click browser AI edit is there for when you'd rather not.

What happens if my client forwards the link?

On Free, anyone with the link can view — so use it for work you're fine sharing openly. On Solo and Team, private artifacts are gated by access control: the recipient has to be an invited email, so a forwarded link by itself doesn't grant access.

Is this legally binding?

No — your MSA still signs in DocuSign. Restamp is the working record of what was approved and when, across the engagement: scope going in, changes in the middle, acceptance at the end.

What if I just need to host the HTML?

The free tier does that. Plenty of free hosting tools do too — Restamp is for when the yes matters and you need it on record, tied to the exact version.

What happens when I change the document?

Any earlier stamp downgrades to “approved an earlier version,” the record shows what changed between versions, and you request a re-stamp on the current one. Nothing silently stays approved.

We got burned once on “that wasn't in scope.” Does this help?

Yes — that's the edge case it's built for. Every approval binds to a specific version, and re-approval is requested whenever the doc changes, so there's always a record of what was agreed and when.

Restamp is a small, independent tool built in the open. It does one thing: keeps comments, fixes, and the yes on one link. If it's missing something you need for real client work, I want to hear it — try it and tell me.

— Jeremy