The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Send the June newsletter to the Active Subscribers list on June 30 at 9:00 a.m. Send the marketing…
Execute — do the immediate task
+Send the June newsletter to the Active Subscribers list on June 30 at 9:00 a.m. Send the marketing email named June Newsletter — Final Version to Active Subscribers, suppress any address with hard bounces or unsubscribed status, set the from name to Elena Morales, and enable click tracking. Pause the send if delivery rate falls below 95% within the first hour.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I send the June newsletter, make it easy for the compliance reviewer: show the unsubscribe…
Improve — make it easier to accept
+Before I send the June newsletter, make it easy for the compliance reviewer: show the unsubscribe and privacy links, surface any tracked parameters appended to external links, list which recipients will be excluded by suppression rules, and flag links that point to staging or internal URLs that would make a reviewer hesitate to approve.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I queued the June Newsletter for June 30 and a last-minute delivery test shows a spike in bounces…
Decide — diagnose the stuck moment
+Send queued but delivery test shows sudden high bounce rate
I queued the June Newsletter for June 30 and a last-minute delivery test shows a spike in bounces from a recent data import. I don’t know if the import added malformed addresses or if my suppression list failed to run. I’m afraid sending will harm our domain reputation. What is the most likely root cause and what exact immediate steps stop the send safely without missing the deadline?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Each quarter we import a new lead list and repeatedly encounter high bounce rates that force us to…
Become — change the pattern
+Repeated data-import bounces threaten sending reputation
Each quarter we import a new lead list and repeatedly encounter high bounce rates that force us to delay or pause sends, damaging our deliverability. It’s costing launches and trust. Which habitual change in our list management would reduce these bounce incidents, and what two pre-send validations would prevent bad imports from reaching the live send?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other CRM and marketing work people do in HubSpot.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.