DAISORO

T2.1 / Portfolio Architecture

Global Plan Archetype Library

Normalizes plan structures into archetypes so portfolio teams can compare positioning, value mechanics, and gaps.

Plannedsecondary priority
Industry

Telecom

Family

Portfolio Architecture

Delivery

Direct file delivery / API access

Schema preview

Plan Archetype Library

sample structure
01Archetype name and segment fit
02Price bands and allowance bands
03Commitment, contract, and recharge pattern
04Positioning pattern and value mechanic
05Comparable peer plan references
06Version status and source evidence

What it captures

  • Archetype name and segment fit
  • Price bands and allowance bands
  • Commitment, contract, and recharge pattern
  • Positioning pattern and value mechanic
  • Comparable peer plan references
  • Version status and source evidence

Decision workflows supported

  • Portfolio architecture comparison
  • Product gap analysis
  • Segment proposition review

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.

Archetype name and segment fitidentifier / label
Price bands and allowance bandsidentifier / label
Commitment, contract, and recharge patternstructured value
Positioning pattern and value mechanicstructured value
Comparable peer plan referencesevidence metadata
Version status and source evidenceevidence 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
T2.2

Feature Attachment & Upsell Structure

PlannedTelecomPortfolio Architecture

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

Use cases
Upsell path analysisFeature monetization comparison
Key fields
Feature name and add-on categoryPricing uplift and incremental allowance
View dataset
T2.4

Portfolio Gap & White Space Analysis

PlannedTelecomPortfolio Architecture

Converts offer and archetype records into structured white-space signals for product and portfolio teams.

Use cases
Portfolio gap detectionSegment proposition planning
Key fields
Missing price pointsOvercrowded price or allowance ranges
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