Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
Use When
- In this repository, premium positioning is the default for product, web, SaaS, UX, pricing, and client-facing work unless the task is purely internal or explicitly non-commercial.
- A product must justify premium pricing through quality, trust, status, outcomes, speed, certainty, exclusivity, or executive usefulness.
- Building software for CEOs, investors, enterprise buyers, luxury customers, affluent consumers, professional firms, high-value SMEs, or public-sector decision makers.
- The request involves packaging services, designing a premium SaaS/app, pricing a high-ticket offer, or making an agency deliverable feel worth more.
Do Not Use When
- The work is purely internal, non-commercial, and has no buyer, user trust, product, brand, or pricing implications.
- The user explicitly wants a low-cost commodity offer and accepts that it will not support premium positioning.
Required Inputs
- Product or service description, target buyer, business model, price point, and delivery model.
- Current proof assets, differentiators, onboarding/support expectations, and competitive alternatives.
- Any buyer context: executive, enterprise, affluent, luxury, public-sector, SME, or consumer segment.
Core Principle
Premium is not decoration. Premium is a disciplined promise: a sharper customer, a more expensive problem, a differentiated outcome, lower perceived risk, superior experience, and proof that the buyer can trust the seller before money changes hands.
Do not degrade the product standard to chase low-fit customers. If the market or client cannot support premium quality, narrow the scope, change the offer, or decline the work rather than producing commodity output.
Workflow
- Define the premium buyer: role, wealth/status context, decision power, risk, desired identity, urgency, alternatives, buying committee, and proof threshold.
- Identify the expensive problem: revenue gain, cost reduction, risk removal, prestige, time saved, compliance, strategic control, confidence, or access.
- Design the offer around outcomes: dream result, time-to-value, included service layer, guarantees/assurances, implementation path, reporting, and ongoing relationship.
- Build premium product signals: restraint, clarity, speed, reliability, detail, excellent onboarding, proactive support, expert language, strong proof, and no cheap-looking friction.
- Create pricing power: value-based tiers, anchors, scope boundaries, no reflex discounting, fixed-fee packages where appropriate, and commercial trade-offs when budget is challenged.
- Support enterprise selling: account research, stakeholder mapping, executive problem framing, business case, risk handling, and next-step commitments.
- Run the premium product gate before finalising strategy, design, copy, pricing, or implementation.
Premium Product Requirements
- First-use experience must prove competence quickly: fast setup, guided path, meaningful sample data, clear next step, and visible support.
- The product must reduce buyer risk: proof, security, uptime, auditability, references, transparent scope, documented process, and clear handover.
- The product must support executive value: dashboards, ROI logic, board-ready reports, approvals, governance, audit trail, and strategic summaries.
- The service layer must be designed, not improvised: onboarding, check-ins, issue escalation, training, review meetings, renewal/expansion logic.
- The offer must make trade-offs explicit: who it is for, who it is not for, what is included, what costs extra, and what result is realistic.
Quality Standards
- Premium positioning must be supported by actual product quality, proof, service design, operational readiness, and pricing logic.
- Recommendations must make buyer fit, scope boundaries, value evidence, and delivery expectations explicit.
- If the current product cannot credibly support premium pricing, identify the missing product, proof, service, or trust requirements instead of writing aspirational copy.
Anti-Patterns
- Calling a product premium while competing mainly on low price.
- Adding luxury visuals while the workflow is slow, confusing, unreliable, or unsupported.
- Offering unlimited scope, vague outcomes, or generic packages to high-value buyers.
- Selling features to executives instead of business consequences and risk reduction.
- Hiding price because the value case is weak.
Outputs
- Premium product positioning brief.
- Offer architecture and package/tier recommendations.
- Premium product requirements and acceptance criteria.
- Pricing-power and sales-enablement notes.
- Review findings against the premium product gate.
References
references/premium-product-design-gate.md- product, offer, pricing, buyer, service, and proof checklist.- Companion skills:
premium-ui-ux-design,software-pricing-strategy,saas-sales-organization,product-strategy-vision.