6 Facebook video ad examples with shot-by-shot breakdowns
Most Facebook video-ad galleries give you a thumbnail and call the opening “strong.” That is hard to use when you still need to decide what appears in second one, when the product enters, where proof belongs and what the click should lead to.
This guide takes six real B2B Meta ads apart shot by shot. You can watch each clip, inspect the complete Ad Library card and see the opening, sequence, proof, CTA and destination together.
Then choose one of the six structures and turn it into a production brief. The blank brief, completed fictional example and copied prompts are designed to work outside this article. If a claim or input is missing, the brief should say Hold and ask for it. It should never make one up.
These are creative examples, not performance case studies. A public ad does not reveal its targeting, spend, watch time, conversions or profit.
The six structures at a glance
Choose the row that matches what you can honestly show. The links should take you directly to the full example.
| If you have… | Structure to use | Example | What happens first | Product appears | Main risk |
|---|---|---|---|---|---|
| A presenter and a visible workflow | Person → problem → product | HubSpot | Creator names the missed-follow-up problem | After the problem is clear | Tiny interface shots that cannot be read |
| A named customer and approved result | Identified customer proof | UKG | Customer and job title appear immediately | It does not; the story carries the ad | Turning one customer's claim into a universal promise |
| A customer story with approved work footage | Pain montage → operating value | BuildPass | Paper safety process and job context | Product use appears through site and tablet footage | A vague montage with no specific work problem |
| Someone who can show the product clearly | Presenter → live walkthrough | Outbuild | Presenter names the old reporting burden | By the second beat | Showing every feature instead of one decision |
| A simple interface change | Screen recording + voiceover | TeamGantt | The viewer enters directly in the product | Immediately | A screen that is unreadable on a phone |
| One sharp problem and one different mechanism | Text-led motion ad | Everee | A numeric problem fills the frame | No interface; the pricing mechanism is the idea | A number or contrast you cannot substantiate |
A customer-proof video is not automatically better than a screen recording. It answers a different question. Pick the structure that fits the evidence and material you already have.
What to inspect in every Facebook video ad
Watch each example once without pausing. Then watch it again and stop at five decisions:
- First visible promise. What can someone understand before sound or context?
- First product moment. When does the viewer see the interface, document or method?
- Proof beat. What makes the explanation believable: a named customer, live product action, document, number or nothing yet?
- Offer and CTA. What is the viewer asked to do?
- Destination continuity. Does the page after the click continue the same job?
Do not ask whether the ad “works” unless you have campaign results. Ask whether the sequence is clear, supported and appropriate for the buyer.
1. HubSpot: person, problem, product
HubSpot's ad is a roughly 29-second vertical partnership video with creator Hannah Zhang. The full card identifies Hannah Zhang with HubSpot, carries the Sponsored label, says “Less Admin, More Selling,” and links to a HubSpot CRM page with a Learn more button.
What happens
- 0:00–0:03: problem hook. The creator appears first. On-screen copy says, “Bad follow-ups kill good deals.” A sound-off viewer has the subject immediately.
- 0:03–0:16: workflow. Contact, deal and pipeline views make “follow-up” visible as a work item rather than an abstract CRM promise.
- 0:16–0:27: product connection. The edit alternates the creator and interface while the explanation moves toward less admin and a clear next action.
- 0:27–0:29: close. The creator and brand finish the thought before the card sends the viewer to the CRM page.
The first three seconds do not try to explain Smart CRM. They make one failure recognizable. That gives the later interface something to resolve.
CTA and destination
The card uses Learn more and sends the viewer to HubSpot CRM. The checked destination headline was “The Best CRM Just Got Better,” with Get a demo and Get started free as the main next actions. The path is coherent: missed follow-up becomes organized pipeline work, then a broader CRM offer. The landing headline is less specific than the ad, so the page must reconnect the visitor to follow-up.
What to borrow
Use this structure when a person can name a common mistake and one screen can show how the work changes.
For a fictional revenue-forecasting product, the opening could be: “Friday forecast. Deal’s stale.” Then show one opportunity with no recent activity, flag it and assign the next review.
Keep the same work item on screen. A tour of six dashboards would weaken the idea.
What not to infer
The public card does not show whether the ad generated deals. “Bad follow-ups kill good deals” is creative copy. Treat it as the ad's premise, not measured proof.
2. UKG: identified customer proof
UKG's 22.9-second vertical video stays on Joey Miranda, identified on screen as HR / Total Rewards Leader at Bay Federal Credit Union. The card opens with a specific payroll statement and sends the viewer to a UKG customer page.
What happens
- 0:00–0:04: witness and old process. Name, role and company are visible while Miranda says the old payroll process was manual.
- 0:04–0:12: before and after. He says the full process moved from two days to four hours, maybe less.
- 0:12–0:22: job value. He connects the time to employee experience and the work HR professionals care about.
There is no product tour. Identity and specificity carry the proof. The lower third remains on screen long enough to see who is speaking.
CTA and destination
The card uses Learn more and links to How UKG customers scale without slowing down. The page repeats the four-hour payroll result, identifies Bay Federal Credit Union and invites the visitor to Let's start the conversation. The ad, destination proof and arrival action all continue the same payroll story before the page broadens into UKG Ready.
What to borrow
Use a customer-proof structure only when you have the customer, statement, permission and supporting source. Put the person's identity on screen at the start. Let them describe one process before the result, then say what the reclaimed time or reduced friction changed in their job.
Ask: “Before this changed, what did the process require, and what can your team do with that time now?” The question invites a sequence without feeding the customer a number.
What not to infer
The two-days-to-four-hours statement belongs to the identified customer in a UKG ad. It is not a Maestro result, an audited benchmark or a promise that every UKG buyer will see the same change.
3. BuildPass: customer pain montage
BuildPass uses customer voiceover with office and job-site footage. Its card starts with rework, miscommunication and outdated plans, then says the product gives crews access to drawings, schedules and site updates.
What happens
- 0:00–0:05: first-person pain. The BuildPass mark and a construction scene appear while the subtitle says the speaker had a lot of paper note-taking for safety.
- 0:05–0:11: tangible burden. Office footage accompanies printing hundreds of forms and keeping them organized.
- 0:11–0:18: operating context. The voice explains how easy it is to miss safety when a million things are happening.
- 0:18–0:24: change. Job-site footage and a mobile device support the move to a digital process.
- 0:24–0:28: value in the job. Tablet footage lands on seeing information and feeling connected while off site.
The montage earns its cuts. Each location supports part of the process: office, site and remote view.
CTA and destination
The card uses See details and sends the viewer to BuildPass all-in-one construction software. The checked destination headline was “All-in-one construction software,” followed by safety, scheduling, drawings and compliance, with a Watch the demo action. The ad names rework, miscommunication and outdated plans; the page continues those jobs, then expands into the full platform.
What to borrow
Use this when the customer's problem spans places or people. Write the story first, then capture one shot for each operating condition. A remote manager does not need generic construction b-roll; they need to see how office and site information meet.
For a service business, the same structure could move from an intake spreadsheet, to a handoff call, to the reviewed document the client receives. Every cut should answer “where does this work happen?”
What not to infer
The video shows the customer's description and working context. It does not establish lower rework, higher margin or better safety outcomes.
4. Outbuild: presenter-led walkthrough
Outbuild opens with a presenter describing weekly status requests, several tools, more than a dozen spreadsheets and a meeting about the spreadsheets. Then he says, “Let me show you,” and moves into the product.
What happens
- 0:00–0:08: old process. The presenter makes the reporting burden specific before showing software.
- 0:08–0:20: transition. “Let me show you” is the hinge. The timeline view appears with project start, end, variance and progress.
- 0:20–0:36: first decision. A tooltip distinguishes behind, ahead and on-track projects.
- 0:36–0:48: second decision. The card view shows team members and the next milestone.
- 0:48–0:59: portfolio decision. A trade-partner view shows overlap across active projects before the presenter closes.
This is the longest example here. It earns the time by showing three related decisions, not three unrelated feature categories.
CTA and destination
The card uses Learn more and goes to Outbuild's company dashboard page. Its checked headline was “Control your entire construction portfolio from one screen,” with Get a personalized demo as the arrival action. That directly continues the video: project status, schedule variance and trade-partner overlap lead to a portfolio dashboard and then a demo.
What to borrow
Use the phrase “Let me show you” only when the next frame actually shows the thing. Organize the walkthrough around decisions:
- Which project is off track?
- Who is involved and what happens next?
- Where is one partner overcommitted?
Write those questions before recording. Crop each product view until the answer is readable on a phone. If one screen cannot answer its question at that size, record a closer shot.
What not to infer
The presenter says the company doubled its projects while maintaining real-time visibility with minimal effort. Keep that statement attributed. The creative does not independently prove the operating result or the ad's performance.
5. TeamGantt: compact screen demo
TeamGantt uses a 15.1-second landscape recording. The interface is the subject from the first frame. The card copy asks about rebuilding a schedule when a subcontractor changes dates, while the voiceover focuses on team bandwidth and completion estimates.
What happens
- 0:00–0:04: enter in the product. The viewer sees task rows and the Gantt chart immediately.
- 0:04–0:10: capacity decision. The voiceover explains seeing who can take more work and who has too much.
- 0:10–0:15: benefit. One-click access is connected to more accurate completion-date estimates.
The ad avoids presenter setup. That makes sense when the interface itself is familiar enough to orient the viewer.
CTA and destination
The card uses Learn more and points to TeamGantt construction scheduling software. The checked headline was “Construction Scheduling Software,” and the page offers a personalized demo. The problem stays consistent from changed subcontractor dates to construction scheduling. The destination asks for a larger commitment than the generic button suggests, so the creative should make the product path clear enough to earn that step.
What to borrow
Use this structure for one visible product action. Start the recording on the exact row, chart or object that matters. Move the pointer deliberately. Add a crop or zoom for vertical placements; a full desktop chart can become meaningless inside a phone-width feed.
Write the voiceover after recording the clean path. Describe what the viewer can see rather than reading a separate feature list.
What not to infer
The voiceover says the view gives the user power to estimate completion dates more accurately. The public creative does not verify forecast accuracy in practice.
6. Everee: text-led motion ad
Everee's 12.87-second square video uses no presenter or interface. The full card describes payroll software for a labor pool. The video makes the argument through four text states.
What happens
- 0:00–0:04: numeric problem. “320 workers in your labor pool didn't take a shift last month.”
- 0:04–0:08: common mechanism. “Most payroll tools charge per employee in the system.”
- 0:08–0:11: alternative. “Everee charges per worker paid.”
- 0:11–0:12: close. “Your payroll costs should too,” followed by the mark.
The contrast is the creative. It needs no product tour because the pricing mechanism is what the viewer must understand.
CTA and destination
The card uses See details and sends the viewer to Everee's payroll demo page. The checked headline was “You've got better things to do than fight with payroll,” followed by an invitation to book time. The payroll problem continues, but the specific per-worker-paid mechanism becomes a broader demo offer. A stronger handoff would repeat that mechanism in the landing headline or first visible proof.
What to borrow
Use this when one sentence can state the problem and one sentence can state a meaningfully different mechanism. Make each frame readable before it changes. Keep the background quiet.
The opening number must come from an actual customer/account source or become a variable such as “People in your labor pool who took no shifts last month.” If the number changes by buyer, do not hard-code a dramatic figure without a source.
What not to infer
The creative does not prove savings. Its labor-pool number and pricing contrast are advertiser copy. Verify both before adapting the claim.
What the best examples have in common
The six ads look different. Each one makes four decisions in order.
1. They make the job visible
“Better productivity” is hard to picture. An overdue follow-up, a two-day payroll process, paper safety forms, a late project, a crowded resource view or an inactive worker is easier.
Write the opening around a work object or moment the buyer recognizes.
2. They choose one kind of proof
The proof can be:
- a named customer's attributed statement;
- a visible product action;
- a document or interface state;
- a sourced number;
- a clearly labeled demonstration.
Do not stack weak proof. One readable product action is better than five tiny screens.
3. They let the offer continue the opening
A video about forecast uncertainty should lead to a forecast walkthrough or review. Sending that viewer to a general homepage creates a second explanation job.
Write the destination headline before the final video line. If they do not match, fix the path before recording.
4. They remain understandable with sound off
Captions are part of the message. The first frame, subject and main line should still make sense when the phone is muted.
Captions cannot rescue a cluttered shot. Use fewer words and a closer crop.
Choose your video structure
Use the evidence you already have.
- Choose person → problem → product when a credible presenter can show one real workflow.
- Choose identified customer proof when the customer and result are approved and specific.
- Choose a customer montage when location and handoffs are part of the problem.
- Choose a presenter walkthrough when the product answers two or three related operating questions.
- Choose a compact screen demo when one visible action does most of the explaining.
- Choose text-led motion when the mechanism is the idea and each claim is sourced.
If none fits, hold production. The answer may be to collect a better demonstration, customer permission or destination page first.
Build the brief before the script
Download the blank Facebook video production brief. Complete these sections in order:
- Buyer and job. Name the role, situation and work object visible in the opening.
- Problem and offer. State one problem and the actual next step the viewer can take.
- Available proof. Link the customer approval, product state, document or sourced number.
- Structure. Choose one of the six structures above and explain why it fits the material.
- Shots. For every time block, write the visual, spoken line, on-screen copy, proof source and owner.
- CTA and destination. Make the final line, platform button and landing-page headline continue the same job.
- Unknowns and approval. Assign every missing input. Choose Continue, Revise or Hold.
The completed fictional brief shows the expected detail. It uses a made-up revenue-forecasting product and invented demo data. It is an instructional example, not a case study.
Run the Facebook video brief build prompt after the brief has real inputs. It returns a timed production plan or an exact Hold request. Then run the Facebook video brief review prompt on the finished script and storyboard to find unsupported claims, unreadable shots and breaks between opening, offer and destination.
Inspect and copy the complete build prompt
The prompt works outside this article and returns Hold when required inputs are missing.
You are creating one source-backed B2B Facebook or Instagram video production brief. Work only from the inputs below. Do not rely on an article or hidden context. METHOD REFERENCE Six valid structures are available: 1. Person -> problem -> product: a credible presenter names one familiar work failure, then one readable work item changes in the product. 2. Identified customer proof: an approved named customer describes the old process, an attributed result and what changed in the job. 3. Customer pain montage: a customer voice moves through the places and handoffs where the work happens. 4. Presenter-led workflow walkthrough: a presenter states the old burden, says what they will show, then demonstrates two or three related decisions. 5. Compact screen-recorded demo: the product is visible immediately and one action carries the explanation. 6. Text-led motion: a sourced problem or number moves to one different mechanism and a branded close. REFERENCE EXAMPLE HubSpot ran an approximately 29-second vertical branded-content ad with creator Hannah Zhang. The opening puts the creator on screen with “Bad follow-ups kill good deals.” Contact and deal views appear after the problem is clear. The ad returns to the presenter and links to a CRM page with a Learn more CTA. Source: https://www.facebook.com/ads/library/?id=1445841037399662. This supports analysis of sequence only. It does not reveal targeting, spend, conversions or profitability. Do not copy its footage, wording, creator identity or brand. REQUIRED INPUTS - Product/service and verified capability: - Buyer role, company situation and work object/moment to show: - One specific problem in buyer language and its source: - Actual offer, deliverable, destination and destination headline: - Available product/demo/document footage: - Presenter/customer and their true relationship: - Proof: exact customer statement, product action, document or sourced number, with source and permission: - Claims or numbers we must not use: - Aspect ratios, length and production limits: - Owners for product truth, claims, permissions, destination and final approval: MISSING-INPUT BEHAVIOR Use Known, Unknown or Not applicable. Not applicable requires a branch reason. Never convert Unknown to Not applicable. For every required Unknown, create a stable request ID, name the field and owner, explain why it is needed and write the exact request. Complete independent work, but set the overall decision to Hold when the buyer/problem, used product claim, customer permission, sourced number, offer/destination or producible first-frame subject is missing. Never invent a feature, customer, quote, number, result, permission, destination, targeting fact, performance result or owner opinion. DELIVERABLE Return clean Markdown with these sections in this order: 1. Decision summary: title, owner, Continue/Revise/Hold, reason and next action. 2. Buyer and job. 3. Problem and offer. 4. Available proof table: proof ID, type, exact statement/visible fact, source, owner and state. 5. Chosen structure and why it fits the supplied material. 6. Shot plan table: shot ID, start, end, job, exact visual, spoken line, on-screen copy, proof source, owner and status. Keep words recordable in the allotted time. Calculate words per minute for each spoken shot; target 165 words per minute or less and leave room for the intended pause or visible action. Every shot row must contain all ten fields in the declared order. Write `None` for a field that is intentionally empty; never shift a proof source, owner or status into another column. 7. CTA and destination: final line, platform CTA, URL/owner, destination headline, arrival action and continuity decision. 8. Production inputs: presenter, demo/sample data, privacy, locations/b-roll, aspect ratios, captions, permissions and phone review. 9. Claims and permissions table: claim ID, exact line, type, source, permission and Continue/Revise/Hold. 10. Open requests table: request ID, field, owner, reason and exact request. 11. Approval decision and next action. 12. Technical appendix with reference source IDs and supplied hashes/versions. QUALITY RULES Make the first three seconds understandable muted. Keep one work object continuous where possible. Every product shot must be readable at phone width. Separate observed fact, supplied claim and creative interpretation. The final line, CTA and destination headline must continue the same job. Counts are ceilings; do not add shots to fill a quota. Now process the supplied inputs. If the input block is blank or incomplete, return the useful independent sections plus an exact Hold decision and open requests.
A completed fictional example
Product: Northstar Forecast, fictional revenue-forecasting software.
Buyer: VP Sales at a B2B software company running a weekly forecast call.
Visible problem: an opportunity with no meaningful activity for 21 days still sits in Commit.
Offer: a three-minute interactive walkthrough of stale-opportunity review.
Available proof: a demonstration account can show activity history. The review-flag capability still needs product-owner verification. No customer result is approved.
Chosen structure: person → problem → product, because the presenter can name the forecast-call moment and the interface can show the exact record.
| Time | Visual | Spoken line | On-screen copy | Proof/source | Status |
|---|---|---|---|---|---|
| 0:00–0:03 | Sales leader beside one enlarged demo opportunity | “Friday forecast. Deal’s stale.” | The forecast call is too late | Fictional concept; presenter relationship must be identified | Ready after presenter approval |
| 0:03–0:07 | Demo opportunity shows 21 days since meaningful activity | “It’s still in Commit after 21 quiet days.” | Commit · 21 days quiet | Demonstration account field | Ready |
| 0:07–0:13 | Turn on a review flag and open activity history | “Northstar flags it before the meeting and shows the history behind the warning.” | Review before Friday | Verified demo capability required | Hold until product owner verifies capability |
| 0:13–0:20 | Assign the opportunity to a review queue | “Now the manager knows which deal needs a question and who owns the review.” | Owner · question · due date | Demonstration workflow | Ready after capability check |
| 0:20–0:27 | Walkthrough page preview | “See the three-minute stale-opportunity walkthrough.” | See the 3-minute walkthrough | Destination must exist with this headline | Hold until page is live |
Decision: Hold. The team can prepare the presenter shot and demo data, but it cannot record the product claim or close until the product owner verifies the flag and the destination exists.
The Hold tells the team exactly what blocks production while keeping the ready shots and inputs.
Production checklist
Before recording:
- [ ] The first frame names one buyer job or work problem.
- [ ] Every customer statement has permission and a source.
- [ ] Every number has a source and owner.
- [ ] The product or document is readable at phone width.
- [ ] The presenter relationship is accurate.
- [ ] Captions carry the message with sound off.
- [ ] The final line, CTA button and destination headline agree.
- [ ] Private customer or account data is removed.
- [ ] Missing inputs are assigned and marked Continue, Revise or Hold.
Before launch:
- [ ] Watch the final export at 1× on a phone.
- [ ] Watch again muted.
- [ ] Pause at every product shot and read it.
- [ ] Open the destination and continue the same task.
- [ ] Confirm the exported aspect ratios preserve the safe text area.
- [ ] Record approvals for speaker, customer, brand and claim use.
Frequently asked questions
What makes a good Facebook video ad?
A good ad makes one buyer problem understandable, shows a believable next step and sends the viewer to a matching destination. The best format depends on the evidence available. A customer story needs a real customer. A product demo needs a readable product action. Public creative alone cannot prove advertising performance.
How long should a Facebook video ad be?
Use the shortest length that completes the explanation. The examples here range from about 13 to 60 seconds. Everee can explain a pricing contrast in four text states. Outbuild needs more time because it shows three operating decisions. Do not stretch a five-second idea into 30 seconds or compress a real workflow until the screen becomes unreadable.
Should the product appear in the first three seconds?
It should when the product state is the clearest hook, as in TeamGantt. It can appear later when a person first needs to define the problem, as in HubSpot and Outbuild. Decide what the buyer must understand first. Then make the next beat pay it off.
Do Facebook video ads need captions?
Design the ad to work muted. Use captions for spoken lines and large on-screen copy for the main idea. Keep words inside safe areas and leave each line visible long enough to read. Captions should support a clear shot, not cover a tiny interface.
Can I copy one of these ads?
Copy the decision structure, not the advertiser's footage, wording, customer, creator, brand or result. Start with your buyer, product, proof and offer. Keep source attribution in your research and secure the rights and permissions for every asset you publish.
How do I know which example performed best?
You cannot tell from the public creative. The Ad Library card does not give you the campaign's targeting, spend, conversion quality or profit. Use the examples to study production choices. Use your own campaign and sales data to judge performance.
What should the video link to?
Link to a page that continues the same job. A workflow demo should lead to that workflow. A customer story can lead to the full case study. A comparison ad should lead to the comparison. Repeat the main promise and make the next step clear.
Source note
The examples were inspected from public Meta Ad Library records and preserved research media on 26 September 2026. Advertisers and creators retain their rights. Source captures appear so the full advertiser identity, Sponsored label, opening copy and creative context remain visible. Commentary is limited to observable creative decisions and attributed statements.