Parallax Source-to-Shorts

Fictional demonstration from an actual local trial. This is not a real customer result. Local links and machine-specific paths are displayed as text.

Three scripts for Alex

Audience: freelance brand designers in the UK who manage their own client feedback. Speaker: Alex, FrameBrief's founder. I used Sources A–C and the supplied filming options. British spelling and neutral UK-friendly phrasing are used; no prices, outcomes, offers, or downloads are added. The beta facts are owner-supplied and were not independently verified.

Script 1 — The tiny change you missed

I changed the background colour and still sent the wrong revision. The change I missed was a small subtitle, buried in feedback across eleven emails and two image attachments. That happened on one packaging job, and it was my mistake.

What I needed was a way to see which requests were still open before I sent another version. That is why I built FrameBrief. In the beta, comments can sit on an image area or a PDF page, and you can mark them open or resolved.

But the useful habit comes before the send button: scan the unresolved comments, then confirm which requests belong in this revision. The big visual change is easy to notice. The small instruction still needs a deliberate check.

123 words; estimated 49–59 seconds, at 140–160 words/minute plus 3–6 seconds of pauses. Not a timed read.

Film Alex talking to camera for the opening, then show the fictional tea-shop demonstration with a clearly labelled subtitle request. Do not present it as the real packaging job. Show a current beta open/resolved comment only if the supplied recording demonstrates it. End on the unresolved-comment scan. Caption moments: “One missed subtitle”; “Open or resolved”; “Check the requests in this revision.”

Sources: A 00:16; B2, dated 6 September 2026 beta; C4. The first-person incident belongs to Alex. The tea-shop visuals are illustrative, not client evidence.

Script 2 — “Maybe brighter” is not a decision

“Maybe brighter.” Would you change the design, or ask what that means? If you start adjusting colours now, you could be revising before the client has made a choice.

I separate a comment from a decision. “Maybe brighter” gives us something to discuss. “Use version B and keep the current subtitle” gives me something I can act on.

Before sending work, write the decision you need. For example: “Please choose the cover image; we are not choosing typefaces in this round.” That gives the review a useful boundary.

Then keep the agreed decision beside the work. A board can hold the answer, but it cannot choose for the client. When the comment is unclear, the next step is a clearer question, not another version.

124 words; estimated 50–59 seconds, at 140–160 words/minute plus 3–6 seconds of pauses. Not a timed read.

Film a talking-head take with two simple on-screen notes: “Maybe brighter” and “Use version B; keep subtitle.” These are example wording, not testimonials. Show two fictional cover options when Alex asks for a choice. Caption moments: “Comment ≠ decision”; “What choice do you need?”; “Ask before revising.”

Sources: A 00:54; C1. The opening conditional consequence and final advice are interpretations of Alex's method, not measured performance claims. “Colours” follows the requested UK locale.

Script 3 — Two reviewers, two directions

One reviewer says, “Use version A.” Another says, “Use version B.” Putting both comments in one place does not tell you whose decision to follow.

When people want different things, I still need a conversation. Before I begin the next revision, I ask who is making the final call.

There is another check I make before that conversation: which version are we discussing? Put its name in the message and ask the reviewer to confirm they are looking at it.

Those are two separate questions: are we discussing the same work, and who can settle the choice? Once those are clear, confirm the requests that belong in the next revision. A status label can record a decision. It does not make the decision for you.

125 words; estimated 50–60 seconds, at 140–160 words/minute plus 3–6 seconds of pauses. Not a timed read.

Film Alex beside the fictional tea-shop A/B designs. Label the opening as an example; do not invent a customer disagreement. Add a version name to a mock message and show a simple “Final decision: [agreed role]” teaching card without suggesting a new beta feature. If showing an actual beta status label, demonstrate a person setting it. Caption moments: “Same version?”; “Who makes the final call?”; “A label records a decision.”

Sources: A 01:26; B3, B5; C2–C4. The illustrative opening is a hypothetical version of the documented conflict problem, not Alex claiming another real incident.

Source and claim record

Pricing, performance comparisons, time saved, automatic decisions, and integrations were not added. FrameBrief is mentioned once by name. No unresolved source gap blocks these three spoken drafts. Product-screen filming still needs the actual beta capture; the writing does not assert that footage or captions have been rendered.

Timing uses the actual script word counts and 140–160 spoken words per minute plus 3–6 seconds for pauses. This is a drafting estimate, not a timed read. Read Alex's takes aloud before recording, especially where a screen demonstration needs extra time. No video, voice track, or post was created.