The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Publish the product webcast landing page Thursday at 10:00 and make it live to public access.…
Execute — do the immediate task
+Publish the product webcast landing page Thursday at 10:00 and make it live to public access. Before publishing, verify the form posts to the Product Webcast — Q2 list, the confirmation email is enabled with the right date and link, and the page has the correct metadata and social preview image. After publishing, test the form and forward the live URL to the events team and the head of content.
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 hit publish for the landing page, make the final checklist obvious: list the confirmation…
Improve — make it easier to accept
+Before I hit publish for the landing page, make the final checklist obvious: list the confirmation email subject and body, show whether the form routes to the right list, surface the social preview and metadata, and flag any broken images or scripts. Point out anything that would cause a failed registration like missing GDPR consent or incorrect time zone in the event copy.
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’m about to publish the webcast landing page tomorrow at 09:00, but the confirmation email uses…
Decide — diagnose the stuck moment
+The page is ready but I'm nervous about the confirmation email.
I’m about to publish the webcast landing page tomorrow at 09:00, but the confirmation email uses the old event date from a prior draft. The events team is out until noon and I can’t make changes after publish without causing confusion. I’m afraid we'll send incorrect confirmations to registrants. Should I delay publishing until they return, or publish and immediately unpublish if needed? What is the least risky move given we need the page live to enable partner promos?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We regularly push landing pages live with minor but impactful errors—wrong event dates, broken…
Become — change the pattern
+We publish pages with errors and then scramble fixes post-launch.
We regularly push landing pages live with minor but impactful errors—wrong event dates, broken images, or missing GDPR checkboxes—and then scramble to fix them while partners promote the link. I suspect our publish checklist and preflight testing are weak and approvals are rushed. What three changes to our publish workflow will stop these post-launch scrambles while keeping time-to-live fast enough for marketing windows?
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.