Foreplay

What Stevin gets out of Foreplay

Foreplay solves a real problem: the swipe file that otherwise gets scattered across Slack, folders, and screenshots. Winning competitor ads in one place, organized by theme, with monitoring on Meta and TikTok on top. As a library it is strong. Where the thinking goes wrong is the assumption that collecting is the same as knowing what works. Foreplay shows what competitors are running, not whether it pays off, and an ad that runs long is not by definition an ad that converts. Teams get stuck there: inspiration becomes proof without anyone testing it. Stevin connects that library to your own performance. It reads via API which formats actually deliver results in your channels and lays that next to what you saved in Foreplay, so a brief rests on a proven pattern and not on a pretty screenshot. The person decides what goes to market.

What you pair it with

Foreplay replaces the loose folders and the chat screenshots, so your inspiration is finally organized and shareable. But it is a collection tool, not a measurement tool: it does not know your results and says nothing about whether a saved ad converts with your audience. Count on building the bridge to your own ad data yourself, alongside a tool that returns performance per creative, otherwise it stays a nice wall of examples nobody tests. The question is not whether you have enough references, but whether the reference you copy also works for your audience.

Common mistakes

• →Mistaking a long-running competitor ad for a proven winner.
• →Collecting inspiration without linking it to your own results.
• →Copying a format because it looks good, not because it works for you.
• →Letting the library fill up until nobody remembers which example was saved and why.