Customers told us. Nothing changed.
Sales, support and success all heard the same complaint this quarter. The roadmap never did.
InsteadA complaint customers keep repeating becomes a proposed priority, with its sources.
The video
Video planned60 secondsHow every video is made
The script
- The one point
- A complaint customers keep repeating reaches the list’s owner as a proposed priority, quoted and sourced.
- Why a video
- Cause and effect rippling: one complaint told to three teams drops into three unconnected systems while the calendar runs toward renewal; then the three are linked and reach the list’s owner, who decides live.
- Picture
- Brand mark and sound, then the heading ‘Customers told us. Nothing changed.’ on the site’s background, fading straight into the guide with no black.
- On screen
- Customers told us. Nothing changed.
- Picture
- Guide in the standard room and place. Lower third: guide’s first name, ‘Soundly Run guide’. Burned-in captions.
- Voice
- Sales, support and success all heard the same complaint this quarter. The roadmap never did. As a company grows, each team hears customers in its own system.
- On screen
- The roadmap never did.
- Picture
- Three speech bubbles carrying one complaint fall into three separate boxes: sales notes, tickets, review notes. The boxes never connect. A calendar flips toward a renewal date; the roadmap card stays unchanged. No numbers.
- Voice
- One story sits in three places, and nobody connects them until the renewal conversation.
- On screen
- Three teams heard it. Nobody connected it.
- Picture
- Drawn Priorities screen, Example tag top left, context ‘Company crew’, cursor visible. Step band on prepare. Callout 1 on ‘At stake’; callout 2 on the three quotes, each with source and date. Step band moves to review; callout 3 on ‘Leads asked, 2 of 2 answered’. Cursor ends on Drafted.
- Voice
- A helper links three accounts telling one story, with the revenue at stake, and brings it to the list’s owner. Each quote keeps its date and source. Both team leads say what it frees up.
- On screen
- Example · Three customers, one story: scheduled reports
- Picture
- Step band on decide. ‘Add to the list’, ‘Change’ and ‘Pass’ visible. Click on Add to the list held two seconds. Row becomes ‘Proposed priority, added by Dana’. Guide in picture-in-picture.
- Voice
- Dana owns the list, so she decides: add to the list, change it, or pass. Account owners tell the customers after.
- On screen
- Added. Customers are told after.
- Picture
- Guide in the same framing as The moment.
- Voice
- Nobody waits for the renewal to connect what three teams heard any more. The helper reads and links; Dana decides. It does not watch, score or replace anyone.
- On screen
- A complaint customers keep repeating becomes a proposed priority, with its sources.
- Picture
- Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
- On screen
- Customers told us. Nothing changed.
On screen as proof
- Example Priorities screen: three quotes with source and date (sales call 2 Oct, ticket 6 Oct, review 9 Oct)
- ‘Leads asked: 2 of 2 answered’ and a drafted proposal, with no rank
- ‘Add to the list’ click held two seconds, Change and Pass visible
Before and after
- Before
- Customer feedback splits across sales notes, tickets and quarterly reviews (QBRs)
- After
- One helper reads calls, tickets and review notes together
- Before
- Each team hears it once, and once looks like a one-off
- After
- Three accounts, one story: quoted, sourced, yearly revenue (ARR) attached
- Before
- Signs a customer may leave show at the renewal, too late
- After
- The list’s owner hears it before the renewal does
How it works
Repeated customer stories reach the list's owner, quoted and sourced, in time; the owner decides what goes on the list.
- Accounts telling the same story are linked, each quote with its date, source and yearly revenue, and brought to the list's owner, whichever team heard it.
- Each affected team lead says what the change would free up or cost; the owner sees every answer.
- The list's owner adds it as a proposed priority or passes; account owners close the loop with customers after.
PrioritiesExample
Company crew
Three customers, one story: scheduled reports
- At stake
- 3 mid-market finance accounts, $410k ARR, 2 renew by Q1
- Finance lead
- “We rebuild the report by hand every Monday.” Sales call, 2 Oct
- Ops director
- “We pay a contractor to build it each week.” Support ticket, 6 Oct
- Controller
- “I copy rows out two hours a week.” Success review, 9 Oct
- Leads asked
- 2 of 2 answered: frees Monday reporting, drops the contractor
- Drafted
- Add as a proposed priorityProposed priority, added by Dana
Source: calls, tickets and reviews, 2 to 9 Oct
Add to the listChangePassAdded. Customers are told after.
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.