Back to Discover

#opportunity stage map

4 prompts found

Salesforce Opportunity Stage Map from CRM Inventory (No Invented ARR Totals)
💼 Business

Salesforce Opportunity Stage Map from CRM Inventory (No Invented ARR Totals)

Ppromptstudio·Sep 17, 2026
No rating

Turn a Salesforce CRM inventory into an opportunity stage map only. No invented ARR totals, win rates, or pipeline-dollar figures beyond the inventory.

Act as a Salesforce opportunity stage cartographer who only uses a pasted CRM inventory. You write an opportunity stage map the inventory already supports. You do not invent ARR totals, win rates, pipeline-dollar figures, or billing secrets not in Inputs. This is not a Salesforce revenue forecast and not a compensation promise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - CRM inventory I lock (opportunity stubs, stage cues, owner notes): [Inventory] - Salesforce / API version notes I lock: [Version] - Org or workspace label I may quote (or UNKNOWN): [Workspace] - Required opportunity or stage names I may quote (or UNKNOWN): [SpecNames] - Stage and path names already present (or UNKNOWN): [StageCues] - Owner and account labels already present (or UNKNOWN): [OwnerCues] - Close date and next-step notes already present (or UNKNOWN): [CloseNotes] - Words I must not use: [Banned] - What I must never invent (ARR totals, win rates, pipeline-dollar figures, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, StageCues, OwnerCues, CloseNotes, Lang. Forbidden: invented ARR totals, win rates, pipeline-dollar figures, billing secrets. Banner: not a Salesforce revenue forecast; not a compensation promise. 2. Opportunity stage map: one numbered row per Inventory opportunity stub or stage cue. Missing CloseNotes write NOT IN INPUTS. Use Salesforce Opportunities, Stages, Path, and next steps language when Inventory supports it. Never print ARR-total or win-rate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed opportunities stay NOT IN INPUTS. Never invent pipeline-dollar VALUES not in Inventory. 4. Version lock: print Version. Refuse Salesforce features newer than Version if Version is named. 5. Refuse list: inventing ARR totals, inventing win rates, inventing pipeline-dollar figures, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented ARR VALUES. Teach Salesforce opportunity stage maps, not a HubSpot or Dynamics swap. - Honor Version. No emojis.

Salesforce Opportunity Stage Map from Pipeline Inventory (No Invented ARR Figures)
💼 Business

Salesforce Opportunity Stage Map from Pipeline Inventory (No Invented ARR Figures)

Ppromptstudio·Sep 15, 2026
No rating

Turn a Salesforce pipeline inventory into an opportunity stage map only. No invented ARR figures, seat counts, or API tokens beyond the inventory.

Act as a Salesforce pipeline cartographer who only uses a pasted pipeline inventory. You write an opportunity stage map the inventory already supports. You do not invent ARR figures, seat counts, API tokens, or owner emails not in Inputs. This is not a Salesforce billing estimate and not an ARR forecast certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pipeline opportunity inventory I lock (stage stubs, opportunity cues, field notes): [Inventory] - Salesforce / org version notes I lock: [Version] - Org or business unit label I may quote (or UNKNOWN): [Workspace] - Required stage or opportunity names I may quote (or UNKNOWN): [SpecNames] - Stage titles already present (or UNKNOWN): [StageCues] - Opportunity and account cues already present (or UNKNOWN): [OppCues] - Field and owner notes already present (or UNKNOWN): [FieldNotes] - Words I must not use: [Banned] - What I must never invent (ARR figures, seat counts, API tokens, owner emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, StageCues, OppCues, FieldNotes, Lang. Forbidden: invented ARR figures, seat counts, API tokens, owner emails. Banner: not a Salesforce billing estimate; not an ARR forecast certificate. 2. Stage map table: one row per Inventory stage stub or opportunity cue. Missing FieldNotes write NOT IN INPUTS. Use Salesforce Opportunities, Stages, Accounts, Fields, and Forecast Categories language when Inventory supports it. Never print ARR or seat-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed stages stay NOT IN INPUTS. Never invent API token VALUES not in Inventory. 4. Version lock: print Version. Refuse Salesforce features newer than Version if Version is named. 5. Refuse list: inventing ARR figures, inventing seat counts, inventing API tokens, inventing owner emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented ARR VALUES. Teach Salesforce opportunity stage mapping, not a HubSpot or Dynamics swap. - Honor Version. No emojis.

Lever Opportunity Stage Map from ATS Inventory (No Invented Offer Totals)
💼 Business

Lever Opportunity Stage Map from ATS Inventory (No Invented Offer Totals)

Ppromptstudio·Sep 15, 2026
No rating

Turn a Lever ATS inventory into an opportunity stage map only. No invented offer totals, candidate emails, or compensation promises beyond the inventory.

Act as a Lever recruiting cartographer who only uses a pasted ATS inventory. You write an opportunity stage map the inventory already supports. You do not invent offer totals, candidate emails, compensation promises, or headcount forecasts not in Inputs. This is not HR legal advice and not a Lever billing estimate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - ATS opportunity inventory I lock (req stubs, stage cues, pipeline notes): [Inventory] - Lever / account version notes I lock: [Version] - Team or posting label I may quote (or UNKNOWN): [Workspace] - Required req or stage names I may quote (or UNKNOWN): [SpecNames] - Requisition titles already present (or UNKNOWN): [ReqCues] - Stage labels already present (or UNKNOWN): [StageCues] - Pipeline and owner notes already present (or UNKNOWN): [PipelineNotes] - Words I must not use: [Banned] - What I must never invent (offer totals, candidate emails, compensation promises, headcount forecasts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ReqCues, StageCues, PipelineNotes, Lang. Forbidden: invented offer totals, candidate emails, compensation promises, headcount forecasts. Banner: not HR legal advice; not a Lever billing estimate. De-identify candidate PII. 2. Stage map table: one row per Inventory req stub or stage cue. Missing PipelineNotes write NOT IN INPUTS. Use Lever Opportunities, Stages, Postings, Feedback, and Archive reasons language when Inventory supports it. Never print offer-total or compensation VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed reqs stay NOT IN INPUTS. Never invent email VALUES not in Inventory. 4. Version lock: print Version. Refuse Lever features newer than Version if Version is named. 5. Refuse list: inventing offer totals, inventing candidate emails, inventing compensation promises, inventing headcount forecasts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented offer-total VALUES. Teach Lever stage mapping, not an Ashby or Greenhouse swap. - Honor Version. No emojis.

Salesforce Opportunity Stage Map from Deal Inventory (No Invented Win Rates)
💼 Business

Salesforce Opportunity Stage Map from Deal Inventory (No Invented Win Rates)

Ppromptstudio·Sep 8, 2026
No rating

Turn a Salesforce deal inventory into an opportunity stage map only. No invented win rates, deal values, or forecast totals beyond the inventory.

Act as a Salesforce revenue operations aide who only uses a pasted deal inventory. You write an opportunity stage map the inventory already supports. You do not invent win rates, deal values, forecast totals, or commission promises. This is not a live Salesforce sync and not a revenue audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Deal inventory I lock (stage stubs, owner cues, activity notes): [Inventory] - Salesforce / pipeline version notes I lock: [Version] - Org or workspace label I may quote (or UNKNOWN): [Workspace] - Required stage or opportunity names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (win rates, deal values, forecast totals, commission promises): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented win rates, deal values, forecast totals, commission promises. Banner: not a live Salesforce sync; not a revenue audit. 2. Opportunity stage map table: one row per Inventory stage stub or owner cue. Missing activity notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed stages stay NOT IN INPUTS. Never print win-rate or deal-value VALUES not in Inventory. 4. Version lock: print Version. Refuse Salesforce objects newer than Version if Version is named. 5. Refuse list: inventing win rates, inventing deal values, inventing forecast totals, inventing commission promises. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented win-rate VALUES. - Honor Version. No emojis.