The Pre-Sale VSL Teardown: How Agencies Scope and Price

Quoting a VSL rebuild from one look at the page is how agencies inherit jobs they cannot price. Before you send a number, you need to know three things about the prospect's current video: where viewers actually drop, whether their tracking reports conversions at all, and how much of the script rests on proof they cannot substantiate. That is the pre-sale teardown. When you place the second agency node before the sale rather than after, you stop guessing and start scoping.

In this post, we walk through the full teardown process. You will learn what access you need before you start, how to map drop-off on the current video, how to verify pixel and conversion reporting with server-side pixel forwarding, and how to audit testimonials against FTC substantiation rules. Then you will turn those findings into named scope items and price the work, not the outcome. We cover the stack you need, from engagement heatmaps to script analysis, the pitfalls that turn a good teardown into a bad quote, and the exact sequence to run before you quote.

Why Quoting a VSL Rebuild Blind Costs You Later

"Your VSL is underperforming" is not a scope. It has no deliverables, so it has no price. A teardown converts that sentence into named work: hook rewrite, mid-section rewrite, tracking implementation, proof replacement, close rework. Each carries effort you can quote.

Quote before the teardown and you inherit whatever the rebuild turns out to be. You eat the difference on the hook, the tracking fix, the proof assets and the close, because none of them were priced.

This is pre-sale diligence, not the post-sale performance report. You run it on the prospect's current video, tracking and script before signature. Keep the two jobs separate: Step 4: Make Surgical Changes, Not Full Rewrites covers the work after the contract.

Three checks carry the weight: where viewers drop on the current video, whether tracking reports conversions at all, and how much of the sales argument rests on unsupported proof. Unsupported proof is also a claim risk: under the FTC Endorsement Guides, endorsements may not contain representations the advertiser could not substantiate directly.

State it in the proposal: this is a scoping exercise, not legal advice. You flag risk, the client's counsel reviews it, and your scope covers the rewrite.

What You Need Access To Before the Teardown Starts

None of that works without access. Before you schedule the teardown, ask the prospect for four things.

First, the current video plus second-by-second player data: drop-off curve, rewind points, replay points and exits. An average watch time percentage gives you nothing to scope against. Bring this video engagement data as proof of work to the scoping call so the numbers, not opinions, set the boundaries.

Second, ad account and tracking access. Get permission to open Events Manager and Google Tag. You need to see whether conversion events fire at all and which source sends them, browser pixel or server-side.

Third, the full script with claims, testimonials, price terms and guarantees marked up. That turns the proof audit into an hour of work instead of a week.

Fourth, rough traffic and spend context. Volume tells you whether the current video has enough viewers to diagnose from and whether the rebuild will be measurable after launch.

Treat a refusal as a finding. If a prospect will not share data, price the access risk into the scope or walk. Agencies that skip this step quote on the client's opinion instead of the video's numbers.

Step 1: Map Where Viewers Drop on the Current Video

With access in hand, open the player analytics and read the curve second by second, not the average. A 40% average watch time hides three separate cliffs inside one video. Mark the exact seconds where retention breaks.

Isolate the first 30 seconds. If viewers leave there, the promise is not landing before any selling happens. That is a hook problem, a different job from a mid-script fix.

Treat rewind and replay spikes as intent signals. Viewers going back show you what to emphasize and where the pitch confused them. A rewind near a price or offer reveal is a good sign with a bad delivery, not proof the video works.

Separate the mid-video sag from the close drop. A sagging proof section needs a rewrite and new assets. A weak close usually needs offer framing and a clearer ask.

Price from the shape of the curve. Hook failure, proof failure and close failure are three scopes with three effort levels. How to read engagement heatmaps shows where viewers drop, rewind and leave, so you point at the seconds instead of arguing about the video.

Step 2: Verify the Tracking Reports Conversions at All

Step 1 tells you where the video loses people. Step 2 tells you whether you can prove it.

A screenshot of conversions in Ads Manager is not proof. Open Events Manager and Google Tag yourself: does the event fire on the offer page and land in Meta and Google, click through to purchase?

Low counts can be a measurement failure, not a video failure. Browser pixels, ad blockers and iOS privacy settings drop events, and VSLStats puts that hidden share at up to 30% of conversion data. That is a vendor figure, so confirm it inside the client's own accounts, then read the tracking gap that hides conversion data for the setup side.

Then ask one question: is server-side pixel forwarding configured, or does the funnel run on browser pixels alone? That answer decides whether your rebuild is measurable at all.

Reconcile next. Reported conversions against actual sales in the client's backend. Any gap becomes a named line item, not a mystery after signing.

Finally, price the tracking fix explicitly. Measurement work is implementation hours, and quoting a script overhaul on numbers you do not trust sets the retainer up to fail.

Step 3: Audit How Much of the Script Rests on Unsupported Proof

With tracking confirmed, audit the script.

Tally every claim and label its backing: first-party data, third-party verification, documented customer experience, or nothing at all. The unbacked share is the part of your sales argument hanging on air. Pair it against the VSL script audit so each gap points to a section viewers already abandon.

An endorsement must reflect the endorser's honest opinion; under the FTC Endorsement Guides, a representation the advertiser could not substantiate directly is deceptive when the endorser makes it. The advertiser carries that risk, and after the rebuild the script is a document you produced. Performance testimonials imply typical results, so absent substantiation that the endorser is representative, disclose generally expected performance instead.

That risk is live: the FTC sent warning letters to ten companies over deceptive review practices under the Consumer Review Rule, where civil penalties reach up to $53,088 per violation, the 2025 ceiling and likely to rise with the 2026 inflation adjustment (Venable). Testimonial and before-and-after heavy VSLs sit squarely in that exposure.

Flag gaps for the client's counsel rather than quietly softening a claim. Scope the rewrite; their lawyer owns the exposure. Quote proof replacement as its own deliverable so nobody assumes it's included.

Step 4: Turn the Findings Into Named Scope Items

With drop-off, tracking and proof findings in hand, score each one before you write a single line item. Severity drives effort: how many seconds elapse before the first drop, whether conversion events fire at all, and what share of the script's claims have nothing behind them.

Convert findings into named deliverables, never "general optimization": hook rewrite, mid-section rewrite, close rework, tracking implementation, proof asset replacement, disclosure language. A line reads "rewrite seconds 0 to 12" or "map four events in Meta Events Manager."

Bucket each small, medium or large, so the quote maps to work rather than to what you think the prospect will pay.

State what is out of scope: ad creative, landing page, offer structure, media buying. That list stops the rebuild expanding after signature, and it pairs with building a performance story clients understand without needing ad access once delivery starts.

Every line in the client's units: seconds of video, events in the ad account, claims on the page. A scope you can defend in a kickoff call is a scope you can schedule.

Step 5: Price the Scope, Not the Outcome

With your scope items named and effort-bucketed, the quote builds itself. Price bottom-up: each deliverable the teardown produced, multiplied by your own rate card. Never anchor a fee to a promised lift, because you would be selling a forecast you do not control.

Price measurement separately from creative. Server-side tracking setup, event mapping and QA are implementation hours, and burying them inside a script fee is how agencies lose money on rebuilds. Splitting a diagnosis fee from the production fee also means the prospect pays for the teardown even if the rebuild never happens, which filters the free-consulting crowd fast.

Build in a final measurement step: A/B split testing on the new hook or offer, plus revenue attribution mapping every dollar back to a video, a viewer and a watch depth. That turns your rebuild into the baseline for the next teardown. The production cost argument for going analytics-first makes the same case to clients.

Leave outcomes out of the proposal. Sell scope, process and reporting cadence, with a written revision limit sitting next to the price.

What Your Stack Needs to Run This Teardown

Pricing from scope only works if your stack can produce the evidence. Second-by-second engagement heatmaps show where viewers drop, rewind and leave. That is the raw input for Step 1 and the difference between pointing at second 47 and arguing about the whole video. Server-side pixel forwarding sends conversion events straight to Meta and Google even when browsers block tracking. That is the fix Step 2 scopes and quotes. Script analysis tied to watch depth tells you whether a drop aligns with a proof section, an offer reveal or a pricing question, so you rewrite the right section on the first pass. Play gates capture leads, and A/B split testing on the rebuilt funnel makes post-rebuild data comparable to the teardown baseline instead of a fresh guess. Agency white-label sub-accounts let you run the teardown and ongoing reporting under your own brand. Plans run $47 to $497 per month, and any plan can be tried for $1. For a deeper look at turning that data into signed work, see Turning Video Intelligence Into Closed Deals. With this stack, your quote stays tied to measurable inputs.

Pitfalls That Turn a Good Teardown Into a Bad Quote

Good tools do not fix bad process. These five habits turn a clean teardown into a quote you regret.

• Quoting before you have seen the drop-off curve. You bid on an assumption, then negotiate every surprise mid-project. Curve first, price second.

• Skipping the tracking check, then promising a script fix will move conversions you cannot yet count. Flat numbers become your result, from a measurement that never could have shown one.

• Quietly rewriting testimonials and claims instead of flagging them. You become the author of a risky claim and inherit an argument your scope never priced. Under the FTC Endorsement Guides, an altered endorsement that distorts the endorser's opinion is a violation, so flag it and let the client's counsel review.

• Underpricing proof replacement. Gathering documentation, sourcing real customer material and writing compliant disclosure is hours of work, not a copy edit. List it as its own deliverable.

• Letting scope creep in because the quote never listed exclusions. Every rebuild grows. A scope document written from data, not from a call, is your only protection.

Run the Teardown, Then Quote

You have the pitfalls mapped. The fix is sequence discipline: run drop-off, then tracking, then proof, in that order. Each check changes what the next one is worth. A weak hook makes a tracking rebuild a waste of budget; broken tracking makes a script rewrite unmeasurable. All three together set the price.

That order is what makes the quote defensible in a kickoff call. Every line item traces back to something concrete: a second of video where retention breaks, an event that does or does not fire in the ad account, a claim in the script with nothing behind it. No assumptions to renegotiate mid-project.

If the prospect will not hand over video analytics, ad account access and the script, that is data too. Price the access risk into the scope or decline the job. Inheriting a rebuild you cannot scope is how agencies work for free.

Want the drop-off, tracking and conversion numbers without the guesswork? Try any plan for $1.

Conclusion

Scope the work before you price it. Run drop-off, then tracking, then proof, in that order; each finding changes what the next one is worth. Write every line item from data, not from a kickoff call, so nothing gets renegotiated mid-project. And if the prospect won't hand over video analytics, ad account access and the script, price that access risk or walk away.

The next step is to run the teardown first, then quote from what you find. Want the drop-off, tracking and conversion numbers without the guesswork? Try any plan for $1 at /pricing. Stop guessing your scope. Start quoting from evidence.