Soundly RunSound familiar?

Sales promised it. Delivery never heard.

A customer was promised a feature on a sales call. Delivery first heard about it at kickoff.

InsteadDelivery sees the promise the day it's made.

The video

Video planned52 secondsHow every video is made
The script
The one point
A sales call promise stays in one rep’s notes; once confirmed on the account page, delivery sees it that day.
Why a video
Cause and effect: one sentence on a sales call travels unseen to kickoff and renewal. The same promise twice: shut in a notebook, then on delivery’s page that day.
  1. Intro0:00-0:03sting

    Picture
    Brand mark and sound, then the heading ‘Sales promised it. Delivery never heard.’ on the site’s background, fading straight into the guide with no black.
    On screen
    Sales promised it. Delivery never heard.
  2. The moment0:03-0:10person

    Picture
    The guide in the usual place and framing. Lower third with first name and ‘Soundly Run guide’.
    Voice
    A customer was promised a feature on a sales call. Delivery first heard about it at kickoff. Once selling and delivering are separate teams, a promise lives between them.
    On screen
    Delivery first heard about it at kickoff
  3. The cost0:10-0:17motion

    Picture
    A speech bubble leaves a call and lands in one notebook, which closes. A separate delivery plan line moves on its own. At kickoff the bubble and the plan collide; later a renewal card turns amber. No figures.
    Voice
    The promise stays in one person’s notes. It surfaces at kickoff, then again at renewal, as a risk.
    On screen
    A missed promise surfaces at renewal as churn risk
  4. The mechanism0:17-0:26screen

    Picture
    Drawn Needs you screen, Example tag top left, context ‘Lena’s crew’. Step band ‘prepare’. Heading ‘Your promise to Halden Logistics’. Cursor passes Deal: ‘Halden renewal, $96k, closes 30 Nov’. Callout 1 on Heard: the quote. Callout 2 on Drafted: ‘Data export by 1 Dec’.
    Voice
    After the call, a helper drafts each promise it heard. The seller confirms it, corrects it, or marks it as not a promise.
    On screen
    Example: the promise drafted from the call
  5. The mechanism0:26-0:35screen

    Picture
    Same screen, step band on ‘review’. Callout 3 on Delivery’s forecast: ‘12 Dec, from the current plan’. Cursor moves to ‘Once confirmed: On Halden’s page, where delivery reads it’, then ‘The date: Kofi, delivery lead, accepts or counters’. Side panel lists Halden’s promises.
    Voice
    Delivery’s forecast sits right beside it, so the gap shows now. Once confirmed, the promise goes on the account page, where delivery reads it. Only the delivery lead moves the date.
    On screen
    Example: promised 1 Dec, forecast 12 Dec
  6. The decision0:35-0:42person and screen

    Picture
    Step band on ‘decide’. ‘Confirm and send to delivery’, ‘Change’ and ‘Not a promise’ all visible. Cursor clicks ‘Confirm and send to delivery’, held two seconds. Row updates: ‘Kofi sees it today; accept or counter by Fri’. Guide in picture-in-picture.
    Voice
    Lena decides what was promised: confirm and send to delivery, change it, or mark it not a promise. Kofi, the delivery lead, decides the date.
    On screen
    Confirmed. Delivery sees the promise today.
  7. The difference0:42-0:48person

    Picture
    The guide, same place and framing as the moment, so it reads as a return.
    Voice
    Nobody rebuilds a promise from call notes at kickoff. The helper drafts; the seller and delivery decide. It does not watch, score or replace anyone.
    On screen
    Delivery sees the promise the day it’s made.
  8. Outro0:48-0:52sting

    Picture
    Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
    On screen
    Sales promised it. Delivery never heard.

On screen as proof

  • Needs you promise screen, walked row by row, tagged Example
  • Heard quote beside ‘Delivery’s forecast: 12 Dec, from the current plan’
  • Confirm, Change and Not a promise all visible; click held two seconds

Before and after

Before
Side promises live in one rep’s call notes, not the sales system (CRM)
After
Each commitment is on the account page, rep-confirmed
Before
On the call, a roadmap yes closes the deal; delivery pays later
After
Before the call, the rep sees delivery's forecast date
Before
A missed promise surfaces at renewal as churn risk
After
A slipping promise reaches the rep before the customer notices

How it works

A promise made on a call goes on the account page and reaches delivery that day; the seller owns what was promised, the delivery lead owns the date.

  1. Before a call, the seller sees delivery's forecast dates, and decides what to offer.
  2. After the call, each promise heard is drafted; the seller confirms it, corrects it or marks it as not a promise.
  3. A confirmed promise goes on the account page, where delivery reads it that day; only the delivery lead moves the date.
Needs youExample

Lena's crew

Your promise to Halden Logistics

Deal
Halden renewal, $96k, closes 30 Nov
Heard
“Exports will be live by 1 December.”
Drafted
Data export by 1 Dec
Delivery's forecast
12 Dec, from the current plan
Once confirmed
On Halden's page, where delivery reads it
The date
Kofi, delivery lead, accepts or counters

Source: sales call, 14 Oct; delivery plan, 17 Oct

Confirm and send to deliveryChangeNot a promise

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.