Figure 12 Sept 2026From “Revenue analytics needs an event schema”

Revenue lifecycle event dictionary

A standardized revenue event schema captures immutable commercial state transitions across the complete customer lifecycle.

Cite Embed

Figure 1Revenue lifecycle event dictionary

Lifecycle phase	Event name	Trigger condition	Core schema payload	Source	Primary analytical consumers
Prospecting	`account.qualified`	Pass ICP firmographic verification.	`account_id`, `tier_level`, `sdr_id`	CRM	SDR use, tiering distribution.
Pipeline	`opportunity.created`	Verified discovery meeting complete.	`opp_id`, `account_id`, `initial_arr`	CRM	Inbound, outbound pipeline, CAC.
Sales Validation	`opportunity.technical_win`	Architecture approved by buyer.	`opp_id`, `eval_days`, `product_tier`	CRM	Stage conversion efficiency.
Commitment	`contract.signed`	Binding signature received.	`contract_id`, `committed_arr`	E-Sign	Net bookings, forecast check.
Provisioning	`workspace.provisioned`	Production instance deployed.	`workspace_id`, `allocated_seats`	Backend	Setup time, handoff latency.
Value Realization	`telemetry.first_value`	Activation milestone reached.	`account_id`, `days_to_value`	Telemetry	Time to value, retention risk.
Expansion	`subscription.expanded`	Seats added or tier upgraded.	`account_id`, `delta_arr`, `type`	Billing	Net revenue retention (NRR).
Renewal	`contract.renewed`	Renewal agreement executed.	`contract_id`, `renewed_arr`	Billing	Gross retention, cohort decay.
Churn	`subscription.churned`	Contract expired or terminated.	`account_id`, `lost_arr`, `reason`	Billing	Cohort decay, win-loss cause.

Swipe or scroll horizontally if the table is wider than your screen.

Source: Author's revenue data architecture framework. All event names, payloads, and triggers represent synthetic technical standards.

PNG4:3, 1600 × 1200, with the title, the source line and the attribution set in the image isoglu-2026-revenue-analytics-needs-an-event-schema-fig01.png

From the essay

Revenue operations & AI

Revenue analytics needs an event schema

Revenue dashboards aggregate conflicting CRM statuses; scalable revenue analytics requires an immutable event schema with explicit state transitions.

2 Sept 2026

Read the essay

This exhibit belongs to an essay: the numbers live here, the argument lives there.

Cite or embed

APA 7

Isoglu, S. (2026). Revenue lifecycle event dictionary [Figure]. isoglu.com. https://isoglu.com/insights/exhibits/isoglu-2026-revenue-analytics-needs-an-event-schema-fig01/

BibTeX

@misc{isoglu-2026-revenue-analytics-needs-an-event-schema-fig01,
  author = {Isoglu, Sinan},
  title = {{Revenue lifecycle event dictionary}},
  year = {2026},
  howpublished = {Figure 1, isoglu.com},
  url = {https://isoglu.com/insights/exhibits/isoglu-2026-revenue-analytics-needs-an-event-schema-fig01/},
  note = {From the essay {Revenue analytics needs an event schema}}
}

Embed this exhibit

Copy this HTML to use the PNG exhibit on your site with its source line and a link back to the exhibit page.

<figure>
  <a href="https://isoglu.com/insights/exhibits/isoglu-2026-revenue-analytics-needs-an-event-schema-fig01/">
    <img src="https://isoglu.com/social/isoglu-2026-revenue-analytics-needs-an-event-schema-fig01.png" alt="Figure 1: Revenue lifecycle event dictionary" width="3200" height="2400">
  </a>
  <figcaption>Figure 1: Revenue lifecycle event dictionary. Source: Author&#39;s revenue data architecture framework. All event names, payloads, and triggers represent synthetic technical standards. <a href="https://isoglu.com/insights/exhibits/isoglu-2026-revenue-analytics-needs-an-event-schema-fig01/">View exhibit</a>.</figcaption>
</figure>