# Fictional example output

## Concept A — Trial first

- Hypothesis: opening with the approved trial offer encourages qualified finance-team prospects to explore the product.
- Hook: “Try team budget software for 14 days.” Source: claim1.
- Execution: open on that offer title, use the supplied screen recording as provided, and close with “Explore the 14-day trial.” All spoken and caption copy uses only claim1's approved product and trial facts; subtitles and the existing recording come from prod1. Confirm the recording and destination match those facts before publishing.

## Concept B — Product first

- Hypothesis: opening on the existing product demonstration improves qualified intent compared with an offer-first opening.
- Hook: “A quick look at team budget software.” Source: claim1.
- Execution: show the same supplied recording, then the same trial offer and CTA; change only the opening/story order. Avoid invented speed, savings, security, or workflow-capability claims.

**Production dependency:** insight1 establishes that finance teams want a shared view; it does not establish that Acme provides that capability. Any shared-view messaging or a sequence that combines team views into an overview requires an approved product-capability fact and matching demo frames. That concept is not included in these ready copy/story proposals.

**Test proposal:** compare trial-first and product-first openings under a feasible consistent assignment design; primary metric qualified demos per eligible assigned prospect, with offer/landing page constant. Instrument qualification first because obs1 does not establish it. Budget, duration, sample feasibility, and guardrail acceptance remain decisions for the experiment plan. These are unvalidated concepts and production briefs; no ads published.