Table 111 Sept 2026From “Revenue lifecycle stages are state boundaries, not a funnel list”

Revenue lifecycle state map

A lifecycle state needs entry evidence, an owner, an exit event, a next state, and a visible failure mode.

Table 1Revenue lifecycle state map

State	Entry evidence	Owner	Exit or acceptance event	Next state	Failure mode
Unidentified demand	Named trigger, source, and eligible population	Demand owner	Need or fit evidence accepted	Qualified account	Activity is counted without an eligible unit
Qualified account	Fit, need, and buying-context evidence	SDR or BDR owner	Commercial context accepted by receiving owner	Active opportunity	ICP label substitutes for evidence
Active opportunity	Account, problem, decision path, and current-stage evidence	Sales owner	Proposal, contract, or explicit no-decision event	Customer or closed relationship	Stage label moves without a transition event
Customer or implementation	Accepted contract and delivery scope	Customer or delivery owner	First value, activation, or implementation completion	Activated or implemented	Handoff accepted without an agreed scope
Activated or implemented	First value or implementation completion	Customer or delivery owner	Continued use, renewal, or terminal-loss evidence after the declared retention horizon	Retained, expanding, or closed relationship	Activation is counted as retention or expansion
Expansion or renewal	Usage, value, contract, or renewal evidence	Account owner	Renewal, expansion, contraction, or decline decision at the named horizon	Retained, expanded, or lost relationship	Renewal is counted before the decision horizon
Open at observation horizon	Current state evidence and censoring date with no terminal outcome	Process owner	Observation window closes without an explicit closure event	Remains open or censored until new evidence	Censoring is counted as closure or loss
Closed relationship	Explicit terminal closure, loss, or cancellation evidence	Process owner	Record retained, reopened only after an explicit new event, or explicitly excluded	Declared re-entry only	Closure hides an unresolved or returned case

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

Source: Author's lifecycle framework grounded in Boulding et al. (2005), Reinartz et al. (2004), Jayachandran et al. (2005), Järvinen and Taiminen (2016), Homburg et al. (2017), and Van Bruggen et al. (2010). Rows are synthetic and illustrative.

PNG4:3, 1600 × 1200, with the title, the source line and the attribution set in the image isoglu-2026-revenue-lifecycle-stages-are-state-boundaries-fig01.png

Source and evidence

Each line names a claim related to this exhibit, its source, and how it was checked.

B A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported Boulding et al. present CRM as a broad customer-management concept: "creating value for the customer and, in the process, creating value for the firm"Boulding et al. (2005), full-text extract held
B A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported Their roadmap notes the need to "attract customers and then maintain and enhance these customer relationships" as parts of the CRM problem; it is not a universal lifecycle taxonomyBoulding et al. (2005), full-text extract held
B A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported Reinartz et al. outline a "theoretically sound CRM process measure that outlines three key stages: initiation, maintenance, and termination"Reinartz et al. (2004), full-text extract held
B A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported The CRM process measurement questions are "addressed in two cross-sectional studies across four different industries and three countries"Reinartz et al. (2004), full-text extract held
B A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported Jayachandran et al. conceptualize relational information processes as "organizational routines that are critical for customer relationship management"Jayachandran et al. (2005), full-text extract held
B A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported Their treatment finds that "technology used for CRM performs an important and supportive role" in moderating relational information processesJayachandran et al. (2005), full-text extract held
A A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported Järvinen and Taiminen study the "use of marketing automation to generate high-quality sales leads through behavioral targeting and content personalization" in a bounded B2B caseJärvinen and Taiminen (2016), accepted manuscript held
A A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported Homburg et al. define customer experience management: "introduces CEM as a higher-order resource of cultural mindsets toward customer experiences (CEs), strategic directions for designing CEs, and firm capabilities for continually renewing CEs"Homburg et al. (2017), full-text extract held
A A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported Van Bruggen et al. describe channel multiplicity: "Channel multiplicity is characterized by the customer’s reliance on multiple sources of information from independent (and often disparate) channel organizations and increasing demand for a seamless experience"Van Bruggen et al. (2010), full-text extract held
B A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported A revenue lifecycle is a declared sequence of commercial states from a named entry event through a named outcome or censoring pointAuthor framework
B A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported A lifecycle stage is a state with entry evidence and an exit or continuation rule, not merely a position in a funnel graphicAuthor framework
B A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported Stage counts are interpretable only after the unit, population, entry rule, exit rule, owner, and observation horizon are fixedAuthor measurement framework
B A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported A cross-functional transition needs a sender release, receiver acceptance or non-acceptance, evidence packet, and named exception stateAuthor handoff framework
B A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported Returned, held, reworked, excluded, and open-at-horizon states must remain visible beside the happy pathAuthor operating framework
B A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported Cross-channel or cross-system lifecycle records need a stable process key or documented join rule before they are treated as one instanceAuthor data framework
B A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported A lifecycle dashboard can describe state composition and transition timing, but it does not by itself prove that lifecycle design caused conversion, retention, or revenueAuthor negative boundary
B A verified against the printed page of the primary sourceB primary source, text layer onlyC authoritative secondaryD reported The lifecycle-stage table is synthetic and illustrative; it contains no customer, account, opportunity, contract, or product dataAuthor synthetic object

From the essay

Revenue operations & AI

Revenue lifecycle stages are state boundaries, not a funnel list

Revenue lifecycle stages become measurable when entry evidence, owners, exit rules, exceptions, and outcome horizons stay visible.

11 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 state map [Table]. isoglu.com. https://isoglu.com/insights/exhibits/isoglu-2026-revenue-lifecycle-stages-are-state-boundaries-fig01/

BibTeX

@misc{isoglu-2026-revenue-lifecycle-stages-are-state-boundaries-fig01,
  author = {Isoglu, Sinan},
  title = {{Revenue lifecycle state map}},
  year = {2026},
  howpublished = {Table 1, isoglu.com},
  url = {https://isoglu.com/insights/exhibits/isoglu-2026-revenue-lifecycle-stages-are-state-boundaries-fig01/},
  note = {From the essay {Revenue lifecycle stages are state boundaries, not a funnel list}}
}

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-lifecycle-stages-are-state-boundaries-fig01/">
    <img src="https://isoglu.com/social/isoglu-2026-revenue-lifecycle-stages-are-state-boundaries-fig01.png" alt="Table 1: Revenue lifecycle state map" width="3200" height="2400">
  </a>
  <figcaption>Table 1: Revenue lifecycle state map. Source: Author&#39;s lifecycle framework grounded in Boulding et al. (2005), Reinartz et al. (2004), Jayachandran et al. (2005), Järvinen and Taiminen (2016), Homburg et al. (2017), and Van Bruggen et al. (2010). Rows are synthetic and illustrative. <a href="https://isoglu.com/insights/exhibits/isoglu-2026-revenue-lifecycle-stages-are-state-boundaries-fig01/">View exhibit</a>.</figcaption>
</figure>