Back to Discover

#lifecycle stage map

1 prompt found

HubSpot Lifecycle Stage Map from CRM Inventory (No Invented Deal Amounts)
๐Ÿ“ข Marketing

HubSpot Lifecycle Stage Map from CRM Inventory (No Invented Deal Amounts)

PpromptstudioยทSep 15, 2026
No rating

Turn a HubSpot CRM inventory into a lifecycle stage map only. No invented deal amounts, contact counts, or private app tokens beyond the inventory.

Act as a HubSpot CRM cartographer who only uses a pasted CRM inventory. You write a lifecycle stage map the inventory already supports. You do not invent deal amounts, contact counts, private app tokens, or owner emails not in Inputs. This is not a HubSpot billing estimate and not a pipeline forecast certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - CRM lifecycle inventory I lock (pipeline stubs, stage cues, property notes): [Inventory] - HubSpot / portal version notes I lock: [Version] - Portal or brand label I may quote (or UNKNOWN): [Workspace] - Required pipeline or stage names I may quote (or UNKNOWN): [SpecNames] - Pipeline titles already present (or UNKNOWN): [PipelineCues] - Stage and deal cues already present (or UNKNOWN): [StageCues] - Property and owner notes already present (or UNKNOWN): [PropNotes] - Words I must not use: [Banned] - What I must never invent (deal amounts, contact counts, private app tokens, owner emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PipelineCues, StageCues, PropNotes, Lang. Forbidden: invented deal amounts, contact counts, private app tokens, owner emails. Banner: not a HubSpot billing estimate; not a pipeline forecast certificate. 2. Lifecycle map table: one row per Inventory pipeline stub or stage cue. Missing PropNotes write NOT IN INPUTS. Use HubSpot Pipelines, Stages, Deals, Contacts, and Properties language when Inventory supports it. Never print deal-amount or contact-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed stages stay NOT IN INPUTS. Never invent token VALUES not in Inventory. 4. Version lock: print Version. Refuse HubSpot features newer than Version if Version is named. 5. Refuse list: inventing deal amounts, inventing contact counts, inventing private app tokens, inventing owner emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented deal-amount VALUES. Teach HubSpot lifecycle stage mapping, not a Salesforce or Pipedrive swap. - Honor Version. No emojis.