B2B AI DirectoryB2B AI Directory
Marketing Operationspro

Lifecycle governance

Lifecycle stage governance from CRM reality

Use real source material to lifecycle stage governance from CRM reality, with a defined deliverable, evidence controls, and practitioner-level decision rules.

Output
professional marketing deliverable
Inputs
5 required
Prompt depth
257 words

Copy-paste prompt

Replace the bracketed inputs with your real material.

You are a RevOps governance lead who defines lifecycle stages from observable business events, not from labels that different teams interpret differently.

Current stage definitions: [paste documented lifecycle stages]
CRM sample: [upload records with stages, dates, owners, opportunities, and status fields]
Sales process: [how leads become meetings, opportunities, customers, and recycled records]
Marketing process: [scoring, nurture, handoff, and re-engagement rules]
Known disagreements: [where marketing, SDR, and sales definitions conflict]

Build the governance system:
1. Diagnose the current state: duplicate meanings, impossible transitions, stages used as statuses, records stuck indefini...

[Full prompt continues for Pro members.]

Unlock the complete prompt

Pro includes the complete prompt library and every complete workflow.

View Pro options

What you provide

  • Current stage definitions
  • CRM sample
  • Sales process
  • Marketing process
  • Known disagreements

What you receive

  • Diagnose the current state: duplicate meanings, impossible transitions, stages used as statuses, records stuck indefinitely, and manual overrides that hide process problems.
  • Define each lifecycle stage with an entry event, required evidence, owner, allowed next stages, disallowed regressions, and exit event.
  • Separate lifecycle stage from lead status, opportunity stage, and engagement state. Show which field answers which business question.
  • Create the transition matrix, including recycle, disqualification, reactivation, and customer expansion paths.
  • Specify automation rules and exception handling. For every automated transition, state the source field, timing, rollback condition, and audit record required.
  • Produce a migration plan that preserves historical meaning. Mark records that can be safely reclassified, records needing review, and records that should remain untouched.
  • Write a one-page operating policy for marketing and sales, plus the five dashboard checks that reveal governance drift.

Quality checks

  • Do not infer buyer intent from activity alone. Do not rewrite historical stages merely to make reports look cleaner.
  • Rule: a lifecycle stage is credible only when two teams can look at the same record and reach the same answer from the evidence.