premium-software-product-execution

name	premium-software-product-execution
description	Use when designing, building, pricing, packaging, or reviewing premium software products, SaaS systems, ERP/POS tools, dashboards, websites, or agency-built applications for executive, enterprise, affluent, high-ticket, or elite buyers. Converts premium marketing, selling, product, UX, pricing, proof, onboarding, and delivery principles into concrete software requirements and quality gates.
metadata	{"portable":true,"compatible_with":["Codex","codex"]}

Premium Software Product Execution

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, [phone].

Use When

• Building or specifying software where premium is the default: SaaS, ERP, POS, dashboards, web apps, websites, internal platforms sold as high-value services, or agency deliverables.
• The product must make clients feel no need to buy commodity alternatives because the workflow, reporting, controls, UX, support, and business value are visibly superior.
• The buyer is a CEO, investor, executive committee, affluent customer, enterprise team, professional firm, premium SME, or procurement process.
• The work involves product-market fit, premium pricing, sales enablement, website/content quality, onboarding, demos, proposals, or implementation packages.

Do Not Use When

• The task is a tiny internal technical fix with no product, buyer, UX, pricing, proof, or delivery-quality implications.
• The user explicitly wants low-cost commodity execution and accepts weak proof, weak discovery, weak support, or low visual/service quality.

Required Inputs

• Target buyer, paying customer, users, business model, budget range, and competitive alternatives.
• Product purpose, core workflows, financial impact, risk removed, data/control requirements, and service commitments.
• Existing proof assets, case studies, demos, screenshots, references, audits, SEO/content assets, and support process.

Workflow

1. Define the premium buyer and disqualify poor-fit work before scope design.
2. Quantify value: revenue gained, time saved, risk reduced, leakage prevented, trust improved, or status/market position created.
3. Package the product before pricing: name, promise, demo, onboarding, training, documentation, support, reporting, handover, and renewal/expansion path.
4. Design the product experience around simple usable excellence: fewer steps, clearer defaults, strong states, executive visibility, and no cheap-looking friction.
5. Make invisible quality visible through proof: screenshots, live demo, process map, security posture, analytics, audits, performance, testimonials, case studies, and implementation roadmap.
6. Build sales assets into the delivery: website copy, SEO/GEO content, comparison page, diagnostic, calculator, proposal language, demo script, and follow-up sequence.
7. Run the premium software product gate before accepting scope, presenting price, shipping UI, or calling the product market-ready.

Quality Standards

• Premium must be evidenced by product depth, execution quality, service design, proof, measurable business value, and buyer confidence.
• Software must include accounting, reporting, controls, auditability, access governance, analytics, and reconciliation thinking when money, inventory, payroll, billing, subscriptions, or financial decisions are involved.
• Website and content outputs must work as marketing assets for the owner and as proof of the agency's premium capability.
• Pricing must be value-based and protected by scope boundaries, change control, payment terms, and trade-not-give negotiation.
• Low-fit or underfunded work should be narrowed, repositioned, or declined instead of lowering the output standard.

Anti-Patterns

• Calling software premium while delivering generic dashboards, weak reports, thin documentation, unclear onboarding, or commodity copy.
• Selling features before diagnosing situation, problem, implication, payoff, buyer risk, and decision process.
• Discounting without a trade in scope, term, timeline, service level, or risk.
• Building products that look polished but lack controls, performance, supportability, data quality, security, or financial logic.
• Publishing websites that impress visually but do not rank, explain, convert, prove, or sell.

Outputs

• Premium software product brief with buyer, value, proof, package, and refusal criteria.
• Product requirements and acceptance criteria for premium UI, financial/control depth, onboarding, reporting, and support.
• Pricing and packaging recommendation tied to measurable value.
• Sales enablement assets: demo plan, comparison logic, proposal talking points, diagnostic, or content map.
• Review findings against the premium software product gate.

References

• references/premium-software-product-gate.md - execution gate for premium software, websites, SaaS, ERP/POS, dashboards, and agency delivery.
• Companion skills: world-class-engineering, software-pricing-strategy, product-strategy-vision, product-discovery, webapp-gui-design, practical-ui-design, content-writing, ux-writing, it-proposal-writing, saas-sales-organization.