Pricing and packaging analysis
Test how price points, tiers and bundles affect volume, mix and revenue, and model the impact of a proposed change on the installed base.
varies by archetype
1The task exists in this business archetype but behaves differently. The note is the point of the edge: it must say how it differs, not merely that it does.
Price is set per unit of consumption, so a packaging change moves revenue and cost of revenue at the same time and in the same direction. Elasticity has to be estimated on usage volume rather than on seat count, and a price cut can raise gross profit while lowering gross margin.
produces
1The modeling object or downloadable deliverable the task creates.
consumes
3A canonical data object the task needs as input.
owned by
1The business-partner org unit accountable for the task.
runs in
1The end-to-end shared-services process the task sits inside.
serves
1The verb-level intent the task exists to satisfy.
Unresolved from the source registry
not yet modelledFree-text strings from the source spreadsheet that have not been resolved to a node. Preserved verbatim so nothing is silently dropped — these are backlog, not content.
Produces: Packaging scenario model