Performance feedback rewrites the prompt automatically so copy gets sharper with every send cycle.
Tool-interchange map · every layer is swappable
What it does
Most outbound teams write a prompt, ship it, and leave it there. This template closes the loop. Performance data flows back in, Claude identifies what is working and what is not, and the prompt gets rewritten automatically before the next send cycle.
The prompt store can live in Google Docs, a Notion page, a Supabase row, or a Git repo. Whatever your team already uses to manage templates, this workflow writes to it. The next generation of copy inherits everything the last generation learned.
It compounds. After three cycles the reply rate is measurably higher than what you shipped on day one.
Default tool stack
Sample prompts
Time + scope
2 to 3 days
To ship
Fixed
Pricing model
Included
Source JSON
14 days
Tweak window
Live in these engines
Related templates
Webhook triggers research, qualification, personalisation, and delivery in one pipeline.
View →Template · 2 to 3 daysEvery recorded meeting becomes structured tasks with owners and deadlines, delivered to your project tool before the call ends.
View →Template · 2 to 3 daysBooking confirmed, CRM updated, and the right person notified before the prospect has closed the confirmation tab.
View →Ready to ship this?
Book a call. I review your stack, confirm the fit, and we start the same week.