Skip to content
For work you do for someone else, with AI help

Show your client the real change.
Ship only what you both approve.

Your client opens one link, tries the change, and taps approve. Only the exact version you both approved goes live, and you both keep a record anyone can check.

Try the demo Use it on a real change

No account, no cookies, nothing for your client to install. The demo takes about a minute in your browser. Your own work needs a GitHub repository with a small ScopeBlind step installed in it.

Rather watch first? See a real completed run from 17 September, and check it in your browser.

Example review · not liveHomepage update: a clearer way to get in touch
BeforeMake something worth finding.Goes nowhere
This version 3f9cMake something worth finding.Opens the contact section
  • Maya, the client, approved3f9c
  • You approved3f9c
  • Live, exactly as approved.
The problem

Sign-off today is a screenshot and an “OK”.

  • Your client approves a picture, not the change.A screenshot or a staging link shows how it looked, not what will go live.
  • The change keeps moving after the yes.With an AI editing quickly, what ships can drift from what was approved.
  • Nobody can show who approved what.When something breaks, the trail is an email thread.
How it works

Four steps, one exact version.

Your AI can do the typing. You and your client make the decisions, and each decision belongs to the exact version it was given to.

  1. You
    Describe the change
    Say what it should do and how you will both check it.Your AI can draft the change; you decide what is asked.
  2. Your client
    Try it, then approve
    They open one link and try the working preview.You each approve this exact version.
  3. Your GitHub repository
    It goes live as approved
    A small ScopeBlind step merges only the approved version.Change anything later and it needs a new yes.
  4. Anyone with the record
    Check it later
    Open the record in any browser, with no account.See who approved what, and what it does not prove.
ScopeBlind controls only the step it installs in your repository: anyone else with access keeps their own permissions. A preview can change after it is recorded, and an AI’s assessment is advice, not an approval.
How it works, in detail
What no one else does

Change one word after approval, and the approval stops counting.

It works like a printer’s proof: the printer prints exactly the proof you signed, and a changed comma needs a new signature. Every change gets the same rule, so what goes live is always what was approved.

  1. You and Maya approve version 3f9c.
  2. The button colour changes: version 7a21.
  3. The approvals do not carry over. 7a21 needs a new yes before it can go live.
Try it in the demo Or practise alone with a scripted partner
What your client sees

One link. The working change. One decision.

No account and nothing to install. They read what the change should do and how you agreed to check it, try the working preview, and approve that exact version. If it needs changing, they say so on the same page.

What you both keep

A record anyone can check.

Who approved which version, when, and what went live. It opens in any browser without an account, and it says plainly what it does not prove. Your client’s sign-off on the result is a separate decision, recorded too.

Open a real record
Trust

Know who you are relying on.

ScopeBlind runs the hosted sandbox and records its outcomes. Your browser signs your decisions; agents receive only the context their connection allows.

  • No accounts, cookies or tracking.Your browser holds your signing key.
  • Your repository keeps its keys.The step that merges runs in your GitHub, under your control.
  • Anyone can check a record.The checker runs in the browser, and its code is open source.
Who sees the data, and what the record provesHosted tasks, local gateways and offline verification
Hosted collaboration

A shared room uses the service

ScopeBlind stores the room’s names, agreement, sample records, actions and results, and runs its sandbox gate and ledger. Browser signing keys stay in their browsers.

Guided
Scripted requests; no live model.
Live agent
The brief and sample records go to the model provider. Your own agent may send them to its configured provider too.
Two-person agreement
Shared mandates and proposals are visible to both people. A private brief is available to its author, their authorized agent, ScopeBlind, and the hosted provider when used. Shared exports omit private briefs.
Rules rehearsal
Tests run in isolated service ledgers. Optional readback sends your text and sample invoice context to the model provider.
Configured local gateway

Your setup defines the boundary

The installed gateway evaluates configured tool calls and writes receipts locally. Credential isolation and coverage depend on your agent, hooks and destination setup.

Your agent’s model and tools have their own data paths. Optional reporting sends disclosed receipts to a hosted standard page; exports share the files you select.

Verification and sharing

Checking a file runs locally

Files opened in Verify are checked in your browser without uploading their contents. A local CLI check can also run offline once its software and files are available.

Publishing a standard or creating a hosted share sends the selected content to the service. Downloaded exports and proof-carrying links disclose their contents to whoever receives them.

Questions

Before you try it

Do I need GitHub?

For your own work, yes: ScopeBlind reviews a pull request in a GitHub repository. The demo needs nothing; it uses a sandbox repository that ScopeBlind owns.

What does my client need?

A browser and the link you send. No account, no GitHub, nothing to install.

Can my AI agent do the work?

Yes. Your agent can prepare the change and assess it against what you agreed, within the permissions you give it. Only people approve. Connect an agent.

What if something changes after we approve?

The approvals stop applying to the changed version, and it needs a new yes before it can go live.

What does ScopeBlind store?

The review itself: the names you enter, the agreed brief, decisions, results, and a copy of the preview your client saw. Your repository stays in GitHub. The privacy policy lists every item and how long it is kept.

Someone sent me a record. How do I check it?

Open it in Verify. It is checked in your browser and never uploaded.

What does it cost?

Trying it is free. Team plans are for recurring client work. See pricing.

Let the work move. Keep the final say.

Try the demo See pricing