Complete teaching example
Signal → reasoning → message
Fictional names. The source, date, account fit, and offer must be replaced before use.
- Channel · language
- First-touch email · English (UK), calm and peer-to-peer
- Sender → recipient
- Theo Martin, positioning lead at Northline Creative; works with European payments teams on evidence-led acquisition campaigns → Luca Moretti, Head of Growth at VelaPay (fictional company)
- Sender proof used
- None used; the message makes no vendor-performance claim.
- Account fit without the signal
- VelaPay is a European B2B payments platform competing on settlement speed, cash-flow control, and reconciliation workload, which is the category Northline Creative serves.
- Verified fact
- Public Meta Ad Library pages for Coinrail, SwiftLedger, and ArcPay, captured July 16, 2026, showed 11 ads launched between July 10 and July 15 around same-day settlement.
- Corroboration
- The corresponding public landing pages, checked July 16, 2026, repeated three angles: settlement speed, cash-flow certainty, and fewer reconciliation steps.
- Hypothesis, not a claim
- The new competitor creative may increase pressure on VelaPay to make its strongest settlement claim easier to see and defend.
- Value available now
- A live three-angle market map plus one on-site positioning gap: VelaPay supports speed and cash-flow on its product page, while reconciliation remains in the FAQ.
Subject: Settlement ad angles
This week’s public settlement ads cluster around speed, cash-flow certainty, and fewer reconciliation steps. Luca, VelaPay’s product page supports the first two angles while reconciliation sits in the FAQ. A one-page message map could keep that choice explicit. How is reconciliation treated in the current argument?
- ✓It reports only visible creative and landing-page evidence, never private spend, performance, or account data.
- ✓The message delivers a compact market map and a specific positioning observation before asking anything.
- ✓Its one question invites a factual correction and explicitly allows that no positioning update is planned.
