Write a recordable 20–30-second B2B video using the task-to-product structure below.

REFERENCE, supplied so you do not need to open the link:
Asana's public Meta partnership ad with creator Leah Shin is about 27 seconds. It opens with campaign briefs, legal notes and stakeholder updates written above the presenter. She describes chasing approvals across messages, documents and email. Around 10 seconds, product-board views show where work and approvals live. Later overlays introduce named AI teammates. The close asks the viewer to try Asana, with a Learn more ad button linking to its AI Teammates page.
Source: https://www.facebook.com/ads/library/?id=1660648119181191
This is an observed creative structure, not evidence of advertising performance. Do not copy the creator's appearance, voice, words or personal experience.

METHOD:
Start with 2–3 concrete tasks the buyer recognizes. Show one real work item moving through the product or service process. Explain only features that support that change. End with one deliverable or next action we can actually provide. Use a presenter plus readable screen or document shots. Do not fill the screen with a whole dashboard if one row explains the point.

FICTIONAL ADAPTATION FOR CONTEXT:
ClearLedger, fictional accounts-receivable software, could open with “Invoice sent. Follow-up due. Who owns it?” Show one overdue invoice row with no owner; assign an owner and next action; finish with a 30-minute invoice-process review and a preview of the owner-and-next-action sheet. This is a made-up creative plan, not a case study.

MY INPUTS:
- Product/service and what it actually does:
- Buyer and 2–3 tasks they handle:
- One concrete problem:
- Real feature or service step that resolves it:
- Available screen, document or physical demonstration:
- Offer and what the buyer receives:
- Destination and CTA:
- Presenter (employee, founder or disclosed partner):
- Claims or customer proof we can substantiate:
- Recording limits (time, equipment, material we cannot show):

If the problem, actual capability, demonstration or offer is missing, ask focused questions. Draft any independent parts, but label incomplete scenes; do not invent a feature, result, testimonial or firsthand experience. A presenter can explain a workflow without claiming to be a customer.

DELIVER:
1. Explain the audience, problem and offer in three sentences.
2. A timed script table: seconds, spoken words, on-screen text, exact shot or screen action, and source for each factual claim. Aim for a natural spoken read; time the word count and shorten if it will not fit.
3. Two alternative opening lines that name different tasks or consequences; keep the rest of the test comparable.
4. Exact primary text, headline and CTA, consistent with the destination.
5. A shot list, demo-data preparation list and phone-legibility checklist.
6. A claim check: supplied facts, clearly labeled assumptions, and claims requiring evidence.
7. One measurable hypothesis to test with qualified responses. Do not predict lift, CPL or revenue.

The result should let a teammate record the video without reading the reference article. Use plain sentences and concrete screen directions, not “make it engaging” or “add a compelling visual.”