Soundly RunSound familiar?

A deepfake executive asks for payment

A video call with your CEO's face and voice asks finance for an urgent transfer. It looks completely real.

InsteadRelease needs two approvers, not a familiar face.

The video

Video planned56 secondsHow every video is made
The script
The one point
A familiar face on a call is not enough: release needs two approvers, each confirming payee and amount.
Why a video
The same moment shown twice: one urgent call down a short money path, then the same call held. Then Jo’s own refusal on the real screen, held two seconds.
  1. Intro0:00-0:03sting

    Picture
    Brand mark and sound, then the heading ‘A deepfake executive asks for payment’ on the site’s background, fading straight into the guide with no black.
    On screen
    A deepfake executive asks for payment
  2. The moment0:03-0:11person

    Picture
    Guide in the usual place, medium shot, same room and framing as every video. Lower third on first appearance.
    Voice
    A video call with your CEO’s face asks finance to pay, today. Where one urgent call from the top can move money, a good fake is enough.
    On screen
    Guide’s first name, Soundly Run guide
  3. The cost0:11-0:19motion

    Picture
    One call, one person under pressure, one button: money leaves along a short path, and nobody else looks. No figures anywhere.
    Voice
    One call and one person under pressure is the whole path. The money is gone before anyone checks.
    On screen
    One call. One person. The money leaves.
  4. The mechanism0:19-0:37screen

    Picture
    Drawn Needs you screen, Example tag top left, context ‘Jo’s crew’, cursor visible, step band prepare, review, decide. Rows reveal in order: The call, New payee, Your confirm step, Second approver, Callback, Paid. Three numbered callouts on the two confirm steps and the callback.
    Voice
    A helper logs the call as a payment request and holds the new payee. Both approvers’ confirm steps show the payee and $480,000. Jo calls Dana on the number held: she made no call.
    On screen
    Example · A video call as Dana asks you to pay $480,000
  5. The decision0:37-0:45person and screen

    Picture
    Refuse to release, Change and Pass all visible. Jo’s cursor clicks Refuse; the click holds two seconds; the heading turns to ‘Refused: $480,000 not released’. Guide in picture-in-picture, lower corner.
    Voice
    Jo decides: refuse to release, change, or pass. She refuses, and the decision record keeps it with her name.
    On screen
    Refused. Nothing paid; recorded with your name.
  6. The difference0:45-0:52person

    Picture
    Guide back in the same place and framing as The moment. Beside her, Example badge top left, the same call meets a hold marker and the money path stops.
    Voice
    Nobody has to judge a face under pressure any more. The helper holds and logs; people decide. It does not watch, score or replace anyone.
    On screen
    Release needs two approvers, not a familiar face.
  7. Outro0:52-0:56sting

    Picture
    Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
    On screen
    A deepfake executive asks for payment

On screen as proof

  • Example-tagged Needs you screen, rows in order from The call to Paid
  • Both confirm steps showing the new payee and $480,000
  • Jo’s click on ‘Refuse to release’, held two seconds, with Change and Pass visible
  • No sourced figure: cost shown as a money path with no number

Before and after

Before
Authority verified by recognising a face or voice
After
Authority verified by a passkey in a signed-in session
Before
Urgent, secret, from the CEO: saying no feels riskier than paying
After
Release needs two approvers
Before
Impersonation attempts vanish unless someone reports them
After
Every payment request from a call or message logged and counted

How it works

Two people approve, each confirming who is paid and how much on their own device (transaction signing).

  1. The person asked flags the request in one tap; a helper records channel, claimed sender and amount.
  2. New payee or changed bank details: hold, then call back on the number already held, never one given.
  3. Release needs two approvers; either one can refuse, and the decision record keeps who did.
Needs youExample

Jo’s crew

A video call as Dana asks you to pay $480,000

The call
Video call as Dana, 16:42: pay today, tell no one
New payee
Added today; held until a callback on the number held
Your confirm step
Shows the new payee and $480,000 on your device
Second approver
Grace sees the same payee and amount on hers
Callback
Dana, on the number held: she made no call
Paid
Nothing yet

Source: call log and payment request, 14 Oct

Refuse to releaseChangePass

Built to work in the email, calendar, chat, finance and sales tools you already use.

What it never does

  • Acts alone only inside limits a person sets; asks first for anything else.
  • Reaches only what its job needs.
  • Never watches, scores or replaces anyone.