Pillar 04 · Cinematic Conversion Media
Ecommerce Video Production
Product ads, brand films and UGC-style content for Meta, Google and social, scripted around testable hooks and cut natively for each platform.
System diagram · Hook-testing matrix
One brief, twelve cuts, budget on the hook that sells.
Scripting, grading and UGC-style proof are the inputs; the server-side purchase signal is what decides between them. Pick an input, then step the test through its rounds.
Fig. 01Illustrative test design
01 · Inputs
- A Problem first Loss aversion Opens on the frustration the product removes.
- B Proof first Demonstration Opens on the product doing the job, in one take.
- C Desire first Aspiration Opens on the end state: the outfit, the room, the result.
- D Objection first Risk reversal Opens on the doubt (is it worth the price?) and answers it.
Script beats · Panarch template
- Hook 0–3 s
- Proof 3–15 s
- Offer Last 5 s
What we build
Four hook angles per product, each scripted to the same proof and offer beats, so the only variable in the test is the opening.
Revenue link
The first seconds decide whether the rest of the ad is seen at all. Testing angles side by side shows which reason to buy actually moves this product.
- Log footage
- Exposure & balance
- Brand look
- Skin-tone check
- Rec.709 delivery
What we build
A grade built from the identity's colour tokens and checked against skin tones, then delivered in Rec.709 for every feed placement.
Revenue link
The product looks the same colour in the ad, on the product page and out of the box, so the return reason 'looked different online' has less to work with.
- T1 Creator's own voice Unscripted phrasing over the scripted beats.
- T2 Handheld, natural light Framed like a phone video, not a studio set.
- T3 Use in context Worn, poured or unboxed where the buyer would.
- T4 Real review text Quoted from verified buyers, with permission.
What we build
UGC-style cuts alongside the studio cuts: creator voice, handheld framing, the product in use, and review text quoted only from verified buyers.
Revenue link
Studio footage proves quality; UGC-style footage proves other people bought it. Testing both shows which proof this audience needs before it pays.
- 01 Ad click Ad name carries hook and ratio, e.g. B·9:16
- 02 Storefront purchase Order ID and event ID recorded
- 03 Server event Meta Conversions API · Google Ads enhanced conversions
- 04 Platform read Order attributed to the cut, deduplicated against the pixel
What we build
On storefronts Panarch builds or audits, purchases are sent server-side through Meta's Conversions API and Google Ads enhanced conversions, with each ad named by hook and ratio.
Revenue link
Browser pixels miss orders when scripts are blocked. A server-side event keeps the per-cut read intact, so budget follows purchases rather than views or likes.
02 · Test matrix · 4 hooks × 3 ratios
| Hook | 9:16 | 4:5 | 1:1 | Budget |
|---|---|---|---|---|
| A Problem first | A 9:16: low relative signal | A 4:5: low relative signal | A 1:1: low relative signal | 25% |
| B Proof first | B 9:16: high relative signal | B 4:5: high relative signal | B 1:1: mid relative signal | 25% |
| C Desire first | C 9:16: mid relative signal | C 4:5: mid relative signal | C 1:1: low relative signal | 25% |
| D Objection first | D 9:16: low relative signal | D 4:5: mid relative signal | D 1:1: low relative signal | 25% |
Server-side purchase events attribute orders to each cut. The bars show an illustrative relative index, not campaign data.
Bars: relative signal index, illustrative · not campaign data
Revenue outcome
Spend follows the hook that sells. Every cut is a labelled test, so each round tells the ad account which angle earns the purchase, and the next shoot starts from the winner instead of a guess.
Illustrative test design. Hook names, the relative signal index and the budget shares demonstrate the method; they are not results from any client account, and Panarch does not publish ROAS figures without the account data behind them. Panarch delivers the cuts and the naming scheme, plus the server-side events on storefronts it builds; who runs the media budget is agreed at scoping.
The problem
Product video that looks like every other ad in the feed gets scrolled past, and a single cut can't be tested, so you never learn which hook actually sells.
What we build
We script several hooks per product, shoot with cinema-grade lighting and colour, and cut variants for each placement so your media buyer can test them against each other.
Why it pays back
A steady supply of testable creative variants means each campaign learns which hook sells instead of guessing.
Stack
- Adobe Premiere
- After Effects
- DaVinci Resolve
- Blender 3D
How the engagement runs
6-Week Production Cycle
- Step 01
Script & Hooks
Hook variants, scripts and storyboards built around what the product has to prove.
- Step 02
Production
On-location or studio shoot in Delhi NCR, with casting and macro product close-ups.
- Step 03
Post-Production
Edit, colour grade, VFX and sound mix.
- Step 04
Delivery
Exports in every aspect ratio each platform needs, ready to hand to your paid-social team.
FAQ
Cinematic Conversion Media, answered.
Both. Scale and Dominance include on-location and studio shoots in Delhi NCR. Foundation is edited from footage you already have.
Platform-native cuts in the right aspect ratio for Instagram Reels, YouTube Shorts, Meta ads and LinkedIn.
Foundation: 6 assets (4 ad assets plus 2 UGC-style cuts). Scale: 1 brand film plus 8 variations. Dominance: no fixed cap; volume follows your testing plan.
Next step
Not sure which tier fits? Talk to the team that builds it.
30-minute call to plan hooks, formats and a first shoot.