# Packaging Designer

> This skill designs the product packaging, tier structure, and feature allocation for commercial launch. Use when preparing a new product or major version for market release. Also consider when restructuring existing tiers after competitive shifts or customer segmentation changes. Suggest when deal-desk escalations reveal recurring packaging friction or when expansion revenue stalls.

- Skill: `mittuled/packaging-designer` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add mittuled/packaging-designer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mittuled/packaging-designer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Finance & Business
- Author: mittuled (https://skillmd.com/u/mittuled)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mittuled/packaging-designer

---


# packaging-designer

## Agent: VP Product
L1 product leader responsible for opportunity framing, MVP definition, PRD assembly, go-live coordination, and post-launch monitoring. Owns the product strategy and roadmap from idea through GA.

Department ethos: [ideal-product.md](../../../../departments/product/ideal-product.md)

## Skill Description
Designs the product packaging and tier structure for commercial launch.

## When to Use
- When a new product or major feature set is approaching GA and needs a packaging model
- When win/loss data or deal-desk escalations indicate the current tier structure creates friction
- When entering a new market segment that requires differentiated packaging
- When competitive intelligence reveals packaging misalignment with buyer expectations

## Workflow
1. **Segment the buyer personas**: Map ICP segments to willingness-to-pay bands and primary use cases. Deliverable: persona-tier matrix.
2. **Catalogue the feature inventory**: List every GA and near-GA feature, tagging each with cost-to-serve, perceived value, and competitive parity status. Deliverable: feature inventory spreadsheet.
3. **Define tier boundaries**: Assign features to tiers (e.g., Free, Pro, Enterprise) using a good-better-best framework, ensuring each tier has a clear upgrade trigger. Deliverable: tier allocation map.
4. **Validate with stakeholders**: Run the proposed packaging through Sales, CS, and Finance to stress-test deal mechanics, margin impact, and supportability. Deliverable: stakeholder feedback log.
5. **Model revenue impact**: Simulate ARPU, conversion rates, and expansion paths under the proposed packaging versus the status quo. Deliverable: revenue impact model.
6. **Draft packaging spec**: Write the final packaging document including tier names, feature allocations, usage limits, and upgrade/downgrade rules. Deliverable: packaging spec document.
7. **Publish and socialize**: Hand off the approved packaging spec to Marketing for positioning, Sales for enablement, and Engineering for entitlement enforcement. Deliverable: distribution confirmation.

## Anti-Patterns
- **Feature-count tiers**: Differentiating tiers solely by number of features rather than value delivered. *Why*: Customers compare feature lists and feel the lower tier is artificially crippled, eroding trust.
- **Kitchen-sink enterprise tier**: Dumping every feature into the top tier with no clear upgrade narrative from mid-tier. *Why*: Mid-market buyers see no stepping stone and churn or never expand.
- **Packaging in isolation**: Designing tiers without Sales and CS input on real deal mechanics. *Why*: Packaging that looks clean on paper creates friction in negotiation and renewal workflows.
- **Static packaging**: Treating the tier structure as permanent after launch. *Why*: Market conditions, competitive moves, and product evolution require periodic repackaging reviews.

## Output
**On success**: A packaging spec document containing tier definitions, feature allocations, usage limits, upgrade triggers, and revenue impact projections — ready for cross-functional enablement.
**On failure**: Report which step stalled (e.g., stakeholder misalignment, insufficient usage data), what alternatives were evaluated, and recommend whether to ship a simplified two-tier model or delay until data gaps close.

## Related Skills
- [`business-model-sketcher`](../business-model-sketcher/SKILL.md) — sibling skill under the same agent — combine with business-model-sketcher for end-to-end coverage
- [`competitive-response-monitor`](../competitive-response-monitor/SKILL.md) — sibling skill under the same agent — combine with competitive-response-monitor for end-to-end coverage
- [`goal-framer`](../goal-framer/SKILL.md) — sibling skill under the same agent — combine with goal-framer for end-to-end coverage