The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Create coupon code WELCOME50 to give 50% off the first two invoices for new monthly subscribers,…
Execute — do the immediate task
+Create coupon code WELCOME50 to give 50% off the first two invoices for new monthly subscribers, cap redemptions at 500, set expiration for December 31, and add a note for support explaining redemption limits. Verify that coupon usage is tracked per customer and that reporting will show total redemptions by December 31.
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 publish these coupon codes, make them approval-ready: surface the expected revenue impact,…
Improve — make it easier to accept
+Before I publish these coupon codes, make them approval-ready: surface the expected revenue impact, show which customer segments will use them most, flag how the coupon interacts with existing promos and trials, and list any limits or expiry behavior that would make finance 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
+Coupon WELCOME50 has exceeded its 500 redemption cap and kept accepting redemptions. I set the cap…
Decide — diagnose the stuck moment
+A coupon exceeded its redemption cap
Coupon WELCOME50 has exceeded its 500 redemption cap and kept accepting redemptions. I set the cap but redemptions continued. Where do caps commonly fail, which log or team should I check first, and how do I stop further redemptions immediately without affecting customers who already received the coupon?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over every quarter we end up giving away more discount than planned because coupon caps, expiries…
Become — change the pattern
+We keep burning coupon budgets unintentionally
Over every quarter we end up giving away more discount than planned because coupon caps, expiries or segmenting are misconfigured. Should we centralize coupon creation in finance, enforce a coupon creation template, or add automated alerts when redemptions hit thresholds? Recommend one operational change, how to implement it, and the metric to prove it worked after 90 days.
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 payments work people do in Stripe.
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.