The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Update our existing monthly_29 plan to $35 and the annual_290 to $340, keep the same plan IDs,…
Execute — do the immediate task
+Update our existing monthly_29 plan to $35 and the annual_290 to $340, keep the same plan IDs, maintain the 14-day trial, and mark changes effective for new invoices only. Notify Priya in procurement and Aaron in engineering that proration is disabled and that upcoming invoices should not be retroactively adjusted.
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 push price changes to our plans, make the approval easy: surface the customer segments…
Improve — make it easier to accept
+Before I push price changes to our plans, make the approval easy: surface the customer segments that will face the largest increase, calculate projected churn risk at 5% and 10%, and highlight any customers on coupon codes or legacy discounts who will be affected. List friction points that would make procurement hesitate.
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 changed the plan price for monthly_29 to $35 but our largest client still shows the old rate…
Decide — diagnose the stuck moment
+I updated prices but some legacy customers kept old discounts
I changed the plan price for monthly_29 to $35 but our largest client still shows the old rate because they were on a legacy discount. I can’t find where that discount was applied. What is the likely place the legacy price is stored, which team should I call first, and how do I update their billing without breaking their contract or triggering a refund cascade?
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 keep pushing price updates that require engineering and finance to manually reconcile accounts,…
Become — change the pattern
+Price updates repeatedly cause confusion and manual fixes
We keep pushing price updates that require engineering and finance to manually reconcile accounts, costing hours each release. Should we move price management to a single owner, implement a versioned plan strategy, or require a change window with rollback steps? Recommend one change with how to implement it and a KPI to watch over three months.
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.