Create a B2B Meta ad that makes one product use case concrete through a real question and answer. Use the observed reference and respect its evidence limits.

REFERENCE OBSERVED IN A PUBLIC AD
Salesforce ran a square static ad with Salesforce and Live Nation marks. A fan looks at her phone. A message asks, “Are backpacks allowed?” and a reply points to the bag policy. The headline says “Get answers without missing a beat.” The ad body says Agentforce answers fan questions about bag policies, parking and show times across 120 North American venues. The pictured question helps a buyer imagine the use case. The 120-venue statement is Salesforce's advertiser claim; the public ad record does not independently audit it. The API returned a tracking destination whose final page was not resolved. Source record: https://www.facebook.com/ads/library/?id=1025567766894244

WORKED FICTIONAL ADAPTATION
ClearLedger could show a finance lead asking, “Who owns the next follow-up on invoice 1042?” A clearly labeled demo screen answers, “Morgan in AR; next email due Thursday.” The point is to make ownership visible in one row. If no verified customer is willing to be named, show a fictional demonstration with made-up invoice data and no customer mark. Do not call it a client result or imply that ClearLedger has shipped that exact feature unless the owner verifies it.

MY INPUTS
- Product/service and exact capability that answers the question:
- Buyer role and one real recurring question:
- Accurate answer or screen state the product can show:
- Customer name, permission and approved story, if a customer will appear:
- Source for any scale, speed, outcome or adoption number:
- Demo data and privacy restrictions:
- Destination and offer:
- Logo, photograph and illustration rights:

METHOD
Start with a question the buyer has heard at work. Put the answer next to a visible interface, document or process. Keep the question short enough for a phone screen. A named customer can add credibility only when the customer approved the story and the claim is verified. Otherwise use an honest product demonstration labeled as such. Avoid a vague “AI can do anything” headline. The destination should let the buyer inspect how this one question is answered.

DELIVER
1. The exact question, accurate answer and why the answer matters to this buyer.
2. A square composition: subject, question bubble, answer bubble, product proof and CTA, with reading order and text sizes.
3. Exact primary text, headline and destination heading.
4. A variant for a different buyer question using the same verified capability.
5. A proof inventory: which claims are observed in the interface, which come from a customer, and which lack evidence.
6. A production list with demo-data setup, anonymization, permissions, design and mobile checks.
7. A downstream measurement question about qualified responses, without predicting results.

If the capability, answer, customer approval or destination is missing, mark it pending. Substitute a clearly fictional demo for an unapproved customer story only when the product owner confirms the capability. Never invent a named client, quote, deployment count, response speed, product feature or business result.