The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I need the opportunity closed with the right number and day. Set the close date to June 30, 2026…
Execute — do the immediate task
+I need the opportunity closed with the right number and day. Set the close date to June 30, 2026 and the amount to $48,750 on the ACME Corp renewal opportunity, then save and leave a one-line note: "Updated close and amount per contract sent May 12." Confirm the record validates and the forecast category stayed the same before you finish.
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 lock the renewal amount and date on ACME Corp, make the key facts obvious to a reviewer:…
Improve — make it easier to accept
+Before I lock the renewal amount and date on ACME Corp, make the key facts obvious to a reviewer: put the contract start and end dates and the original signed amount at the top, show the calculation that produced $48,750, and flag any discounts or pending legal approvals that would make a finance reviewer 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 updated ACME Corp to close June 30, 2026 for $48,750 and saved, but I don't see the expected…
Decide — diagnose the stuck moment
+I just changed the close date and amount but I'm not sure it mapped to the right forecast bucket
I updated ACME Corp to close June 30, 2026 for $48,750 and saved, but I don't see the expected booking in the forecast. I need to know whether the record failed validation, the opportunity record type moved buckets, or a required field is missing. What should I check first and what quick fixes are safe without breaking approvals?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across multiple deals I keep having to change close dates and amounts after finance rejects the…
Become — change the pattern
+I keep correcting close dates and amounts after finance flags forecasts
Across multiple deals I keep having to change close dates and amounts after finance rejects the forecast. Where am I losing credibility: bad source documents, doing changes in the wrong field, or not validating with procurement? Recommend one habit to stop the back-and-forth and a single checklist item to run before I update any opportunity.
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 work people do in Salesforce.
Run pipeline and forecast reportsSchedule dashboard refresh and emailsSchedule follow-up tasks and remindersSend proposal or quote to prospectSet email alerts for key eventsSet role hierarchy and sharing rulesSet up recurring revenue schedulesSync calendar events with recordsTrack campaign ROI and influenceTrack competitor information on opportunity
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.