DAISORO

T2.2 / Portfolio Architecture

Feature Attachment & Upsell Structure

Tracks how operators attach features, add-ons, and upsell paths to base plans across public journeys.

Plannedsecondary priority
Industry

Telecom

Family

Portfolio Architecture

Delivery

Direct file delivery / API access

Schema preview

Feature Upsell Structure

sample structure
01Feature name and add-on category
02Pricing uplift and incremental allowance
03Mandatory or optional attachment rules
04Eligible base plans and excluded plans
05Upsell placement and journey step
06Evidence snapshot and version status

What it captures

  • Feature name and add-on category
  • Pricing uplift and incremental allowance
  • Mandatory or optional attachment rules
  • Eligible base plans and excluded plans
  • Upsell placement and journey step
  • Evidence snapshot and version status

Decision workflows supported

  • Upsell path analysis
  • Feature monetization comparison
  • AI-ready recommendation inputs

Buyer roles

  • Pricing strategy leaders
  • CVM and retention teams
  • Product portfolio leaders
  • Data and AI teams
  • Regulatory and market intelligence teams

Delivery models

  • Direct file delivery
  • API access
  • Cloud push

Decision workflows supported

Pricing strategy

Monitor offer changes, bundle mechanics, channel variance, and competitor moves.

CVM / retention

Feed churn, retention, and portfolio-risk workflows with structured market signals.

Data & AI ingestion

Use stable IDs, schema fields, evidence references, and version states in AI pipelines.

Regulatory transparency

Review public terms, fair-use labels, evidence, and change history without overclaiming legal status.

Sample structure

Non-downloadable field preview

Request sample dataset

This preview shows the record structure without presenting field examples as live data.

Feature name and add-on categoryidentifier / label
Pricing uplift and incremental allowanceidentifier / label
Mandatory or optional attachment rulesstructured value
Eligible base plans and excluded plansstructured value
Upsell placement and journey stepevidence metadata
Evidence snapshot and version statusevidence metadata

Dataset scope

Refresh cadence

Periodic by market scope.

Coverage

Expansion by demand.

Evidence depth

Source URL, Capture timestamp, Screenshot archive, HTML or document archive where available, Version hash, QA status

EVIDENCE REFERENCES

Proof fields travel with the record.

Records are designed to preserve the source, capture state, and QA context needed for downstream review.

Source URLCapture timestampScreenshot referenceDocument referenceVersion hashQA state

VERSION HISTORY

Offer change trail.

1First seencapturevh_01a2
2Promo price addedprice deltavh_02b7
3Eligibility changedrule updatevh_03c4
4Allowance updatedbundle deltavh_04f9
5Offer retiredstatus changevh_05d1

Related datasets

Adjacent signals

Request sample dataset
T1.7

Add-On & Booster Catalog

In buildTelecomPricing & Promo Intelligence

Catalogues data boosters, roaming packs, entertainment add-ons, short-term passes, and feature attachments.

Use cases
Competitive pricing intelligencePromo and portfolio monitoring
Key fields
Add-on type and priceAllowance, validity, and included benefit
View dataset
T6.1

Digital Journey Maps

PlannedTelecomDigital Experience Intelligence

Maps public digital journeys, offer steps, eligibility prompts, and friction signals into structured fields.

Use cases
Digital journey benchmarkingOffer flow QA
Key fields
Purchase journey stepRequired fields and document prompts
View dataset

Next step

Request a sample or map this dataset to your workflow.

DAISORO can discuss market scope, evidence depth, delivery model, and sample structure for your workflow.

Back to catalogue