Normalized terminology for governed revenue architecture. Tight, hierarchical, unambiguous. Every term used across Screens 01–09 is defined here exactly once.
| Legacy Term | Normalized Term | Why |
|---|---|---|
| MQL | Qualified Account Signal (or eliminate) | MQL conflates lead with account, individual with committee |
| Funnel (blended) | Stage Ledger + Swim Lanes | One funnel hides mode-specific conversion and CAC variance |
| Attribution (credit-based) | Influence Mapping → Weight Calibration | Credit ≠ causality. Attribution feeds learning, not budget |
| Awareness | Conditioning | Awareness implies passive. Conditioning implies deliberate probability building |
| Demand Gen | Revenue Development | Demand gen implies top-of-funnel only. Revenue development spans full lifecycle |
| Lead | Account Signal | Individual leads misrepresent buying committee dynamics |
| CPL | Cohorted Segment CAC | CPL without intent normalization is meaningless. CAC by segment is actionable |
| ROI (campaign-level) | Lift vs Baseline + Learning Latency | Campaign ROI ignores mode, segment, and time-to-validated-lift |
The terms on the left remain in active use across OpptyCon today and across most buyer CRMs. The lexicon names where the framework is going, not where the product is.
OpptyCon currently models the funnel as Inquiry → MQL → SQL → SQO → Won — the primitives the buyer's CRM is built on. No buyer's pipeline forecasts from APS thresholds yet. As the framework matures, the product evolves with it. For where each concept lives today — shipped, on the roadmap, or research — see the roadmap.