◆ Salesforce

Forecast monthly and quarterly pipeline

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskPrepare the forecast for June and Q3. Build a monthly view showing total pipeline by stage for…+
Prepare the forecast for June and Q3. Build a monthly view showing total pipeline by stage for June 2026 and the projected closed revenue for Q3 2026, then share it with the revenue operations lead and my manager by Friday with a two-line summary of risk: top three deals that could move and one assumption that must hold.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I present the monthly and quarterly forecast to the revenue meeting, make it easy to…+
Before I present the monthly and quarterly forecast to the revenue meeting, make it easy to consume: surface the expected closed revenue for June and Q3 at the top, show the three deals that drive variance with their close dates and confidence levels, and flag any stage or entry-age assumptions that would make a finance reviewer pause.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI aggregated the June pipeline and Q3 projection and variance is 28% larger than last month. I…+
I built the monthly forecast but variance is larger than expected
I aggregated the June pipeline and Q3 projection and variance is 28% larger than last month. I don't know if the gap is from a few outlier deals, incorrect close dates, or mis-assigned stages. Which quick checks will tell me whether to adjust deal confidence, push close dates, or escalate to deal owners?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternMy monthly and quarterly forecasts repeatedly surprise finance with big swings. Am I inflating…+
Every month my forecast surprises finance with large upside or downside moves
My monthly and quarterly forecasts repeatedly surprise finance with big swings. Am I inflating probabilities, relying on stale close dates, or failing to catch rep-stage bias? Recommend one reporting habit and one data hygiene habit I should adopt to make my forecasts credible and cut review cycles in half.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Salesforce's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.