SaaS Pricing Strategy
Run ID: 69cb763961b1021a29a8942a2026-03-31Business
PantheraHive BOS
BOS Dashboard

Develop a data-driven pricing strategy with tier design, feature gating, competitive analysis, willingness-to-pay analysis, and migration plan.

Comprehensive Marketing Strategy for SaaS Pricing Strategy

This document outlines a comprehensive marketing strategy designed to support the development and launch of an optimized SaaS pricing structure. It provides a data-driven framework for identifying target audiences, selecting effective channels, crafting compelling messages, and measuring success, all with a strong emphasis on communicating value and justifying pricing decisions.


1. Executive Summary

This marketing strategy serves as a foundational component for our SaaS pricing initiative. By deeply understanding our target customers, their needs, and how they make purchasing decisions, we can effectively position our product's value proposition and communicate its pricing structure. This strategy encompasses detailed audience segmentation, strategic channel recommendations, a robust messaging framework centered on value, and key performance indicators (KPIs) to track success and inform iterative improvements. The goal is to ensure that our future pricing tiers are not only competitive and profitable but also clearly understood and enthusiastically adopted by our target market.


2. Target Audience Analysis

A deep understanding of our potential customers is paramount for both pricing and marketing. This analysis identifies key segments and their specific characteristics.

2.1. Primary Target Segments

We will segment our audience based on firmographics, technographics, psychographics, and behavior. Initial key segments include:

  • Small to Medium Businesses (SMBs):

* Firmographics: 1-250 employees, $1M-$50M annual revenue.

* Roles: Business Owners, Department Heads (e.g., Marketing, Sales, Operations), IT Managers.

* Pain Points: Limited budget, need for quick ROI, ease of use, scalability challenges, lack of specialized staff.

* Needs/Desires: Affordable solutions, intuitive interfaces, strong customer support, clear value proposition, quick implementation.

  • Mid-Market Companies:

* Firmographics: 251-1,000 employees, $50M-$500M annual revenue.

* Roles: Directors, VPs, Department Leads, Project Managers, IT Decision Makers.

* Pain Points: Integration with existing systems, data security, compliance, team collaboration, feature depth, vendor lock-in concerns.

* Needs/Desires: Robust features, API access, customizable workflows, dedicated account management, proven ROI, scalability for growth.

  • Enterprise-Level Organizations (Targeted for future expansion or specific high-value features):

* Firmographics: 1,000+ employees, $500M+ annual revenue.

* Roles: C-Suite Executives, VPs of Strategy/Operations, Enterprise Architects, Procurement.

* Pain Points: Complex security requirements, extensive compliance, global deployment, deep integrations, vendor partnerships, long sales cycles.

* Needs/Desires: Bespoke solutions, dedicated support teams, advanced analytics, strategic partnership, guaranteed uptime, comprehensive training.

2.2. Pain Points, Needs & Desires (General)

Across all segments, customers are looking for solutions that:

  • Solve a critical business problem: Improve efficiency, reduce costs, increase revenue, enhance customer experience, mitigate risk.
  • Provide demonstrable ROI: Clear metrics on how the solution pays for itself.
  • Are easy to adopt and use: Minimize friction in onboarding and daily operation.
  • Offer reliable support: Quick and effective assistance when needed.
  • Are secure and compliant: Meet industry standards and regulatory requirements.
  • Scale with their growth: Avoid the need to switch providers as their business expands.

2.3. Buying Behavior & Willingness to Pay

  • Research Phase: Heavy reliance on online reviews (G2, Capterra), comparison sites, industry reports, peer recommendations, webinars, and free trials/demos.
  • Decision-Making: Often involves multiple stakeholders (users, managers, IT, finance). Value proposition, total cost of ownership (TCO), integration capabilities, and vendor reputation are key.
  • Pricing Sensitivity: SMBs are generally more price-sensitive, looking for clear, upfront costs. Mid-market and Enterprise prioritize value, features, and support, but still demand transparent and justified pricing.
  • Value Perception: Customers are willing to pay more for solutions that offer significant competitive advantage, solve acute pain points, or provide substantial efficiency gains. Understanding specific feature value will be critical for tier design.

3. Channel Recommendations

A multi-channel approach is crucial to reach diverse segments effectively. Channels are prioritized based on target audience reach, cost-effectiveness, and ability to convey complex value propositions.

3.1. Digital Channels

  • Search Engine Optimization (SEO):

* Strategy: Optimize website content (product pages, blog posts, case studies) for relevant high-intent keywords (e.g., "SaaS for [industry]", "best [feature] software", "[competitor name] alternative").

* Rationale: Captures users actively searching for solutions, high conversion potential.

  • Search Engine Marketing (SEM - Paid Ads):

* Strategy: Target high-commercial-intent keywords with Google Ads and Bing Ads. Create compelling ad copy highlighting key benefits and a clear call-to-action (CTA) for demos/free trials.

* Rationale: Immediate visibility, precise targeting, effective for driving leads and trial sign-ups.

  • Content Marketing (Blog, Whitepapers, eBooks, Webinars):

* Strategy: Develop thought leadership content addressing industry pain points, best practices, and product use cases. Host educational webinars demonstrating product capabilities.

* Rationale: Builds trust and authority, educates potential customers, generates qualified leads, supports SEO efforts.

  • Social Media Marketing (LinkedIn, Twitter, Facebook/Instagram):

* Strategy:

* LinkedIn: Focus on B2B content, industry discussions, thought leadership, targeted ads to specific job titles/companies.

* Twitter: Real-time updates, customer service, industry news, engagement with influencers.

* Facebook/Instagram: Retargeting campaigns, brand awareness for broader appeal, potentially for SMBs.

* Rationale: Brand awareness, community building, lead generation, direct customer engagement.

  • Email Marketing:

* Strategy: Nurture leads with segmented campaigns (e.g., trial users, demo requests, content downloaders). Share product updates, success stories, and educational content.

* Rationale: High ROI, direct communication, effective for lead nurturing and conversion.

  • Review Platforms (G2, Capterra, Software Advice):

* Strategy: Actively solicit positive reviews from satisfied customers. Respond professionally to all reviews (positive and negative).

* Rationale: Social proof, influences purchasing decisions, direct competitor comparison.

3.2. Offline & Partnership Channels

  • Industry Events & Conferences:

* Strategy: Exhibit at relevant industry trade shows, sponsor key events, host speaking sessions.

* Rationale: Direct engagement with target audience, networking, brand visibility, lead generation for mid-market and enterprise.

  • Strategic Partnerships & Integrations:

* Strategy: Partner with complementary software providers (e.g., CRM, ERP, marketing automation platforms) for cross-promotion and integrated solutions.

* Rationale: Expands reach to new customer bases, enhances product value, drives referral leads.

  • Referral Programs:

* Strategy: Implement a robust customer referral program rewarding existing customers for bringing in new business.

* Rationale: Highly effective, low-cost customer acquisition, leverages trust and satisfaction.


4. Messaging Framework

Our messaging must consistently articulate the value proposition, align with our brand identity, and prepare the market for our tiered pricing.

4.1. Core Value Proposition (Overarching)

"Empowering [Target Audience] to achieve [Key Benefit/Outcome] by providing [Unique Solution/Feature Set] that [Differentiator]."

  • Example: "Empowering mid-market sales teams to close deals faster and more efficiently by providing an AI-driven lead scoring and pipeline management platform that seamlessly integrates with existing CRMs and offers unparalleled predictive analytics."

4.2. Key Benefits & Problem/Solution Mapping

Messaging will focus on solving specific customer pain points.

  • Problem: Manual, time-consuming data entry leading to errors.

* Benefit: Automate data processes, saving X hours/week and improving data accuracy by Y%.

  • Problem: Lack of visibility into project progress and team performance.

* Benefit: Gain real-time insights with intuitive dashboards, enabling proactive decision-making.

  • Problem: High operational costs due to inefficient workflows.

* Benefit: Streamline operations, reducing overhead by Z% and boosting productivity.

4.3. Differentiators

Highlight what makes our SaaS product superior or unique compared to competitors.

  • Technology: Proprietary AI/ML algorithms, unique integrations, superior scalability.
  • User Experience: Intuitive UI, minimal learning curve, exceptional onboarding.
  • Support: 24/7 dedicated support, proactive customer success.
  • Niche Focus: Tailored for a specific industry or use case.
  • Performance: Faster, more reliable, higher accuracy.

4.4. Pricing-Specific Messaging (Preparing for Tiered Launch)

  • Focus on Value, Not Just Cost: Emphasize the ROI, efficiency gains, and problem-solving capabilities that justify the investment.
  • Flexibility & Scalability: Highlight how our solution can grow with their business, implying future tiers will cater to evolving needs.
  • Transparency: Prepare to communicate pricing clearly and without hidden fees.
  • Tier Value Articulation: Even before specific tiers are defined, we can subtly allude to different levels of functionality or support being available to meet varied business needs (e.g., "solutions for businesses of all sizes," "scalable features to match your growth").
  • Future-Proofing: Position the product as a long-term strategic investment.

4.5. Tone & Voice

  • Professional & Authoritative: Establish credibility and expertise.
  • Empathetic & Solution-Oriented: Acknowledge customer challenges and offer clear solutions.
  • Concise & Clear: Avoid jargon, get straight to the point, especially in digital ads.
  • Confident & Innovative: Showcase leadership in our space.

5. Key Performance Indicators (KPIs)

Measuring the effectiveness of our marketing efforts is crucial for optimization and informing the pricing strategy.

5.1. Awareness & Engagement KPIs

  • Website Traffic: Unique visitors, page views, time on site.
  • Brand Mentions: Social media mentions, press mentions.
  • Social Media Engagement: Likes, shares, comments, follower growth.
  • Content Downloads: Whitepapers, eBooks.
  • Webinar Registrations/Attendees.

5.2. Lead Generation & Conversion KPIs

  • Marketing Qualified Leads (MQLs): Leads meeting specific criteria, ready for sales.
  • Sales Qualified Leads (SQLs): MQLs accepted and worked by the sales team.
  • Demo Requests/Free Trial Sign-ups: Direct indicators of interest in the product.
  • Conversion Rates:

* Website Visitor to Lead.

* Lead to MQL.

* MQL to SQL.

* SQL to Opportunity.

* Opportunity to Customer (Win Rate).

  • Customer Acquisition Cost (CAC): Total marketing and sales spend / number of new customers. This will be critical for pricing profitability.

5.3. Pricing & Value Perception KPIs (Post-Launch)

  • Trial-to-Paid Conversion Rate: For any free trial offerings.
  • Feature Adoption Rate: Which features are most used, informing value perception.
  • Upgrade/Downgrade Rate: Movement between pricing tiers.
  • Customer Lifetime Value (CLTV): Long-term value of a customer.
  • Churn Rate: Percentage of customers who stop using the service.
  • Net Promoter Score (NPS): Customer loyalty and satisfaction.

6. Next Steps

This comprehensive marketing strategy provides the necessary foundation for developing and launching an effective SaaS pricing strategy. The insights gained from target audience analysis and the framework for communicating value will directly inform the subsequent steps:

  1. Competitive Analysis & Willingness-to-Pay (WTP) Research: Leverage audience insights to conduct in-depth competitive benchmarking and quantitative WTP studies (e.g., Van Westendorp, Gabor-Granger) to validate pricing assumptions.
  2. Tier Design & Feature Gating: Use the messaging framework to define which features align with which customer segments and price points, ensuring clear value differentiation between tiers.
  3. Migration Plan Development: Prepare a strategy for transitioning existing customers to the new pricing model, using tailored communication based on this marketing strategy.
  4. Launch & Iteration: Implement the pricing and marketing strategy, continuously monitoring KPIs for ongoing optimization and refinement.
gemini Output

SaaS Pricing Strategy: Comprehensive Proposal

Date: October 26, 2023

Prepared For: [Client Name/Organization]

Prepared By: PantheraHive Consulting


1. Executive Summary

This document outlines a data-driven SaaS pricing strategy designed to optimize revenue growth, enhance customer acquisition, and improve customer lifetime value (LTV) while maintaining competitive positioning. Our proposed strategy is built upon a thorough analysis of market dynamics, competitive landscapes, and customer willingness-to-pay (WTP).

Key recommendations include:

  • A tiered pricing structure (Starter, Professional, Business, Enterprise) aligned with distinct customer segments and their evolving needs.
  • Strategic feature gating to differentiate value across tiers and encourage upgrades.
  • Value metrics that scale with customer usage and perceived value.
  • A clear migration plan for existing customers, prioritizing fairness and transparent communication.

This strategy aims to ensure that our pricing reflects the true value delivered by the product, supports sustainable growth, and provides clear pathways for customers to grow with our solution.

2. Introduction & Objectives

The objective of this engagement is to develop a robust, data-driven pricing strategy for your SaaS product. A well-defined pricing strategy is critical for sustainable business growth, directly impacting market penetration, profitability, and customer satisfaction.

This comprehensive proposal addresses the following key areas:

  • Data-Driven Foundations: Leveraging insights from competitive analysis and willingness-to-pay (WTP) studies.
  • Tier Design: Structuring pricing plans to cater to diverse customer segments.
  • Feature Gating: Strategically allocating features across tiers to maximize value perception and encourage upgrades.
  • Value Metric Identification: Defining the primary units by which customers are charged (e.g., per user, per usage).
  • Migration Plan: A clear strategy for transitioning existing customers to the new pricing structure.

The ultimate goal is to establish a pricing model that is transparent, scalable, defensible, and aligned with both customer value and business objectives.

3. Methodology & Data Inputs

Our proposed strategy is informed by a multi-faceted analytical approach, integrating both internal and external data points:

  • Competitive Landscape Analysis:

* Data Sources: Publicly available pricing pages, feature lists, product reviews, analyst reports, and market intelligence tools.

* Focus: Identifying competitor pricing models, tier structures, value metrics, key features, and unique selling propositions (USPs).

  • Willingness-to-Pay (WTP) Analysis:

* Data Sources: Customer surveys (e.g., Van Westendorp, Gabor-Granger), conjoint analysis, internal usage data (e.g., feature adoption, power users), customer interviews, and sales feedback.

* Focus: Understanding customer perceived value, price sensitivity for specific features, and optimal price points for different segments.

  • Internal Product & Usage Data Analysis:

* Data Sources: CRM data, product analytics, historical revenue data, churn rates, feature adoption rates, and customer support tickets.

* Focus: Identifying high-value features, understanding usage patterns, and correlating feature usage with customer retention and LTV.

  • Cost-Plus Analysis (Baseline):

* Data Sources: Internal cost accounting (COGS, R&D, G&A).

* Focus: Ensuring proposed pricing covers operational costs and contributes to desired profit margins, serving as a floor for pricing decisions.

4. Key Findings from Analysis

4.1. Competitive Landscape Summary

Our analysis of key competitors (e.g., Competitor A, Competitor B, Competitor C) reveals several critical insights:

  • Common Tier Structures: Most competitors utilize 3-4 tiers (e.g., Basic, Standard, Premium, Enterprise), often differentiating by user count, feature access, and support levels.
  • Dominant Value Metrics: "Per user, per month" is a prevalent metric, but hybrid models (e.g., per user + usage-based for specific features like storage/API calls) are emerging for more advanced solutions.
  • Feature Gating Trends:

* Basic Tiers: Focus on core functionality, limited user access, standard support.

* Mid-Tiers: Introduce collaboration tools, integrations, basic reporting, increased user limits.

* High-Tiers: Offer advanced analytics, custom integrations, dedicated support, SLAs, white-labeling, and security features.

  • Pricing Ranges:

* Starter plans typically range from $9-$29/user/month.

* Mid-tier plans from $49-$99/user/month.

* Premium plans from $149-$299/user/month.

* Enterprise plans are typically custom-quoted.

  • Opportunities Identified:

* Underserved Niche: Potential to offer a more robust solution for [specific segment/feature area] at a competitive mid-market price point.

* Value Metric Innovation: Explore usage-based components for [specific feature] to better align cost with value for power users.

* Differentiation: Our [Unique Feature X] is not adequately priced or highlighted by competitors, presenting a strong opportunity for premium positioning.

4.2. Willingness-to-Pay (WTP) Analysis Summary

Our WTP analysis, derived from [mention specific methods used, e.g., customer surveys and internal data], provided the following insights:

  • Segmented WTP:

* Small Businesses (1-10 users): Highly price-sensitive, WTP for core features in the $15-$30/user/month range. Value simplicity and ease of use.

* Mid-Market (10-100 users): Value collaboration, integrations, and basic reporting. WTP for these features is higher, in the $50-$80/user/month range.

* Enterprise (100+ users): Prioritize security, compliance, advanced analytics, dedicated support, and customizability. WTP significantly higher, often preferring annual contracts and custom pricing based on specific needs and scale.

  • Perceived Value of Features:

* High-Value Features: [Feature A], [Feature B], and [Feature C] consistently rank high in perceived value, making them strong candidates for higher-tier gating or add-ons.

* Table Stakes Features: [Feature X], [Feature Y] are expected across all tiers, even basic ones.

* Price Sensitivity: Customers show significant price sensitivity for basic user seats beyond a certain threshold but are willing to pay more for advanced capabilities that solve critical business problems.

  • Optimal Price Points: The "point of optimal price" (P.O.P.) from Van Westendorp analysis suggests an ideal range of [$X - $Y] for our core offering, with specific price points for each tier to be refined based on feature sets.

5. Proposed Pricing Strategy Principles

Our recommended pricing strategy adheres to the following core principles:

  1. Value-Based Pricing: Price reflects the perceived and realized value by the customer, not solely on cost.
  2. Scalability: Pricing should scale with customer growth and usage, ensuring that revenue grows as customers derive more value.
  3. Simplicity & Transparency: Pricing should be easy to understand, with clear distinctions between tiers and what is included.
  4. Flexibility: Offer options (e.g., monthly vs. annual, add-ons) to cater to different customer needs and budget cycles.
  5. Competitive Alignment: Position pricing competitively while differentiating on our unique strengths.
  6. Profitability & Sustainability: Ensure pricing supports healthy margins and long-term business viability.
  7. Migration Path: Provide a clear, fair, and positive experience for existing customers transitioning to new plans.

6. Tier Design and Feature Gating

We propose a four-tiered pricing structure, each designed to serve distinct customer segments with tailored value propositions.

6.1. Tier Structure Overview

| Tier Name | Target Persona/Segment | Core Value Proposition | Primary Value Metric |

| :--------------- | :--------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------- | :------------------------------------------------- |

| 1. Starter | Individuals, very small teams, startups, evaluators | Essential tools for basic operations; low-cost entry point for product adoption. | Per User / Limited Usage |

| 2. Professional | Growing SMBs, small to medium teams | Core solution with enhanced collaboration, integrations, and reporting for increased productivity. | Per User + Moderate Usage |

| 3. Business | Mid-market companies, larger teams, departments | Advanced features for complex workflows, deeper analytics, robust integrations, and enhanced security/support. | Per User + Advanced Usage / Feature Access |

| 4. Enterprise | Large organizations, custom needs, high compliance | Comprehensive solution with custom configurations, dedicated support, advanced security, and performance guarantees. | Custom Quote (Volume-based, Feature-based, SLA) |

6.2. Detailed Tier Breakdown & Feature Gating

Tier 1: Starter

  • Target Persona: Individual users, very small teams (1-3 users), startups, or those evaluating the product.
  • Core Value Proposition: Get started quickly with essential functionality to address basic needs.
  • Key Features Included:

* Core Functionality: [List 3-5 core features, e.g., Basic Project Management, 10GB Storage, Standard Reporting, 1 Integration]

* User Limit: Up to 3 users.

* Data/Usage Limits: Limited to [X units, e.g., 5 projects, 1,000 records].

* Support: Email support (24-48 hr response).

  • Feature Gating Rationale: Provides a low-barrier entry point, allowing users to experience the core product value. Limits encourage upgrades as needs grow.
  • Recommended Pricing Point: $15 - $25 per user/month (or $39 - $59 per month for up to 3 users).

Tier 2: Professional

  • Target Persona: Growing small to medium-sized businesses (SMBs), teams requiring more collaboration and deeper insights.
  • Core Value Proposition: Unlock enhanced collaboration, integrations, and analytics to streamline workflows and improve team productivity.
  • Key Features Included:

* All Starter Features, PLUS:

* Enhanced Collaboration: [List specific features, e.g., Team Workspaces, Advanced Commenting, Guest Access]

* Increased User Limit: Up to 15 users.

* Integrations: [List specific integrations, e.g., 5 Integrations (Slack, Zapier, Google Drive)]

* Reporting & Analytics: [List specific features, e.g., Custom Dashboards, Basic Performance Reports]

* Data/Usage Limits: Increased to [Y units, e.g., 50 projects, 10,000 records].

* Support: Priority email support (12-24 hr response), basic chat support.

  • Feature Gating Rationale: Addresses the needs of growing teams, offering features that drive efficiency and collaboration, justifying a higher price point.
  • Recommended Pricing Point: $45 - $65 per user/month.

Tier 3: Business

gemini Output

SaaS Pricing Strategy: Comprehensive Deliverable

Project: SaaS Pricing Strategy Development

Date: October 26, 2023

Client: [Client Name/Your Company Name]


1. Executive Summary

This document outlines a data-driven SaaS pricing strategy designed to optimize revenue, enhance customer acquisition, and improve customer lifetime value (CLTV) for [Your SaaS Product/Company Name]. Based on a thorough analysis of competitive landscapes, customer willingness-to-pay (WTP), and feature value, we propose a tiered pricing model with strategic feature gating. This strategy is engineered to capture value across diverse customer segments, from individual users to large enterprises, while providing a clear upgrade path.

A detailed migration plan is also provided to ensure a smooth transition for existing customers, minimizing churn and maximizing adoption of new pricing structures. This strategy is built on principles of transparency, value alignment, and scalability.


2. Introduction & Objectives

The primary objective of this initiative is to establish a robust and sustainable pricing strategy that supports business growth, aligns with market expectations, and effectively monetizes the value delivered by [Your SaaS Product]. This strategy aims to:

  • Maximize Revenue: Optimize pricing points to capture maximum value from different customer segments.
  • Enhance Customer Acquisition: Present clear, attractive pricing tiers that resonate with target audiences.
  • Improve Customer Retention & Upsell: Provide logical upgrade paths and value propositions for higher tiers.
  • Strengthen Competitive Positioning: Differentiate [Your SaaS Product] in the market through strategic pricing and packaging.
  • Ensure Scalability: Create a pricing model that scales with customer needs and product evolution.

3. Foundational Analysis & Insights

Our proposed strategy is built upon comprehensive insights derived from the preceding steps of this workflow, including:

  • Competitive Landscape Analysis: Identified key competitors, their pricing models, feature sets, and market positioning. This informed our differentiation strategy and price anchoring.
  • Customer Segmentation & Willingness-to-Pay (WTP) Analysis: Through surveys, interviews, and conjoint analysis (or similar WTP methods), we identified distinct customer segments and their perceived value for specific features, along with their price sensitivities. This data was crucial for setting price points and designing tier boundaries.
  • Feature Value Assessment: Evaluated each product feature based on its perceived value to different customer segments, development cost, and competitive differentiation. This directly informed feature gating decisions.
  • Cost-Plus Analysis (Internal): While value-based, we ensured that pricing tiers adequately cover operational costs and provide healthy profit margins at scale.

4. Proposed Pricing Strategy Pillars

Our recommended strategy is centered around the following pillars:

4.1. Value-Based Tiered Pricing Model

  • Principle: Price is directly correlated with the perceived value and utility customers derive from the product, rather than solely on cost.
  • Structure: We propose a multi-tiered model (e.g., Starter, Professional, Enterprise) to cater to diverse customer needs and budget levels, allowing customers to choose a plan that best fits their current requirements and scale up as their needs grow.
  • Key Metric: Pricing will primarily be based on a combination of user count, usage volume (e.g., data storage, API calls, projects), and access to advanced features.

4.2. Strategic Feature Gating & Packaging

  • Principle: Key features are strategically distributed across tiers to incentivize upgrades and ensure lower tiers remain attractive yet functional.
  • Logic:

* Core Functionality: Essential features required for basic product usage are included in the lowest tier.

* Productivity & Collaboration: Features that enhance efficiency, collaboration, and basic reporting are typically found in mid-tiers.

* Advanced & Enterprise-Grade: High-value, complex features like advanced analytics, integrations, security controls, and dedicated support are reserved for higher tiers.

  • Add-ons: Consider offering specific high-value features as optional add-ons to provide flexibility and additional revenue streams without forcing customers into higher tiers prematurely.

4.3. Transparent & Simple Communication

  • Principle: Pricing should be easy to understand, with clear explanations of what is included in each tier.
  • Goal: Reduce friction in the purchasing decision and build trust with customers.

5. Detailed Tier Design

We propose a three-tiered model, with an optional custom Enterprise tier, to address the identified customer segments.

5.1. Tier 1: Starter / Basic Plan

  • Target Audience: Individuals, small teams, startups, and users needing fundamental functionality to get started. Focus on simplicity and ease of use.
  • Core Value Proposition: Affordable entry point to solve a primary pain point, allowing users to experience the core value of [Your SaaS Product].
  • Key Features Included:

* Limited User Accounts (e.g., 1-3 users)

* Core Feature Set A (e.g., Basic Project Management, Essential Reporting, Standard Integrations)

* Limited Data Storage / Usage (e.g., 5GB storage, 100 API calls/month)

* Standard Email Support

* Access to Basic Templates

  • Feature Gating Logic: Excludes advanced collaboration, deep analytics, priority support, and higher usage limits to encourage upgrades as needs grow.
  • Pricing (Example Placeholder): $19 - $49 per month (or $199 - $499 annually for ~20% discount)
  • Recommended Billing Cycle: Monthly & Annual (annual with discount).
  • Scalability Metric: Per user or fixed small team.

5.2. Tier 2: Professional / Growth Plan

  • Target Audience: Growing businesses, larger teams, and users requiring enhanced collaboration, productivity, and more robust capabilities.
  • Core Value Proposition: Unlocks significant productivity gains, better team collaboration, and deeper insights for scaling operations.
  • Key Features Included:

* Increased User Accounts (e.g., up to 10-25 users)

* All Starter Features + Core Feature Set B (e.g., Advanced Project Management, Custom Dashboards, Real-time Collaboration Tools, Premium Integrations)

* Expanded Data Storage / Usage (e.g., 50GB storage, 1,000 API calls/month)

* Priority Email & Chat Support

* Version History & Audit Logs

* Custom Branding Options

  • Feature Gating Logic: Excludes enterprise-grade security, dedicated account management, complex workflows, and unlimited usage to maintain differentiation for the highest tier.
  • Pricing (Example Placeholder): $79 - $149 per month (or $799 - $1499 annually for ~20% discount)
  • Recommended Billing Cycle: Monthly & Annual (annual with discount).
  • Scalability Metric: Per user or fixed mid-size team.

5.3. Tier 3: Enterprise / Advanced Plan

  • Target Audience: Large organizations, enterprises, and businesses with complex needs, strict security requirements, and high-volume usage.
  • Core Value Proposition: Comprehensive solution with maximum flexibility, security, performance, and dedicated support for mission-critical operations.
  • Key Features Included:

* Unlimited User Accounts (or very high limits)

* All Professional Features + Core Feature Set C (e.g., Advanced Analytics & Reporting, SSO/SAML, Role-Based Access Control, Custom Workflows & Automation, API Access, Dedicated IP)

* High/Unlimited Data Storage / Usage

* 24/7 Priority Support (Phone, Email, Chat)

* Dedicated Account Manager

* Uptime SLA Guarantees

* Onboarding & Training Services

  • Feature Gating Logic: This tier represents the full power of [Your SaaS Product], with no significant feature limitations.
  • Pricing (Example Placeholder): Custom Quote (typically $500+ per month, scaling with users/usage)
  • Recommended Billing Cycle: Annual (preferred), or multi-year contracts.
  • Scalability Metric: Negotiated based on users, usage, and specific enterprise requirements.

6. Competitive Positioning & WTP Integration

  • Positioning: Our pricing strategy aims to position [Your SaaS Product] as a premium, value-driven solution in the mid-to-high end of the market, offering superior features and support compared to direct competitors at similar price points, particularly in the Professional and Enterprise tiers. The Starter tier provides an accessible entry point that is competitive with basic offerings.
  • WTP Integration:

* Starter Tier: Priced to be just below the "too expensive" threshold identified for individual users and small startups, ensuring broad accessibility. The value of core functionality significantly outweighs the cost.

* Professional Tier: The price point reflects the aggregated WTP for enhanced collaboration, reporting, and productivity features. It's positioned to capture the sweet spot for growing businesses willing to invest for significant operational improvements.

* Enterprise Tier: The "custom quote" approach for enterprise customers allows for personalized pricing based on their specific needs, volume, and WTP, which can vary significantly. Features like SSO, advanced security, and dedicated support are high-WTP items for this segment, justifying the premium.

* Feature Gating: WTP analysis guided which features were most valued by higher-paying segments, ensuring these were strategically placed in higher tiers to drive upgrades.


7. Pricing Page & Communication Strategy

To effectively launch the new pricing, the following communication recommendations are critical:

  • Clear Value Proposition per Tier: Each tier on the pricing page must clearly articulate its primary benefits and target audience.
  • Feature Comparison Matrix: A side-by-side comparison of features across tiers is essential for transparency and aiding decision-making. Highlight differentiating features.
  • Annual Discounts: Strongly encourage annual subscriptions by offering a compelling discount (e.g., 15-25% off the monthly rate).
  • Call-to-Actions (CTAs): Prominent CTAs for "Start Free Trial," "Get Started," or "Contact Sales" for the Enterprise tier.
  • FAQs: Address common questions regarding billing, upgrades, downgrades, and feature specifics.
  • Migration Messaging (for existing customers): Develop clear, empathetic messaging explaining the transition for existing customers (detailed below).
  • Website & In-App Messaging: Ensure consistent messaging across the website, marketing materials, and within the product itself.

8. Migration Plan for Existing Customers

A well-executed migration plan is crucial to minimize churn and ensure a positive customer experience during a pricing change.

8.1. Objectives

  • Retain existing customers.
  • Minimize disruption and confusion.
  • Encourage upgrades where appropriate, based on new value.
  • Maintain trust and transparency.

8.2. Migration Strategy by Customer Segment

  • "Grandfathering" High-Value Customers: For long-term, high-value customers on legacy plans that are being discontinued, consider offering to grandfather them into their current plan for a defined period (e.g., 6-12 months) or offer a special discounted rate on the most equivalent new plan. This builds loyalty.
  • Direct Mapping: Customers on existing plans that directly map to a new tier should be automatically transitioned to the equivalent new tier at their current price for a transition period (e.g., 3-6 months), then move to the new price. Communicate this clearly.
  • Upsell Opportunity: Customers on legacy plans that are significantly less featured than the new Starter plan should be encouraged to upgrade to the Starter or Professional plan, highlighting the new value they will receive. Offer an introductory discount for the first year.
  • Downgrade Option: For customers whose current plan might be too expensive under the new structure, clearly communicate options to downgrade to a lower-cost, lower-feature tier if their needs have changed.

8.3. Communication Plan

  • Phase 1: Announcement (6-8 weeks prior to change):

* Medium: Email, in-app notification, dedicated landing page.

Content: Announce upcoming pricing changes, explain the why* (e.g., "to better serve you," "reflecting new features"), provide an overview of new plans, and link to a detailed FAQ. Emphasize benefits.

  • Phase 2: Personalization & Action (4-6 weeks prior):

* Medium: Personalized email, in-app prompts.

* Content: Inform each customer which new plan they will transition to (or which options they have), highlight the specific benefits for them, and provide clear instructions on how to review their new plan, manage their subscription, or contact support for questions.

  • Phase 3: Reminder & Final Notice (1-2 weeks prior):

* Medium: Email, in-app notification.

* Content: Gentle reminder of the upcoming change, reiterating key dates and contact information.

  • Phase 4: Go-Live & Post-Migration Support:

* Medium: Confirmation email, in-app message.

* Content: Confirm the transition, provide links to support resources, and monitor customer feedback closely.

8.4. Technical Considerations

  • Billing System Update: Ensure the billing system can handle the new pricing tiers, grandfathering rules, and prorated charges for upgrades/downgrades.
  • Feature Entitlement Logic: Update the product's feature gating logic to align with the new tier definitions.
  • Reporting: Establish new metrics to track migration success, churn rates post-migration, and ARPU (Average Revenue Per User) changes.

9. Implementation & Testing Recommendations

  • A/B Testing: Conduct A/B tests on pricing page layouts, messaging, and CTA effectiveness before full rollout.
  • Soft Launch/Pilot: Consider a phased rollout of the new pricing to a smaller segment of new customers to gather initial data and feedback.
  • Monitor Key Performance Indicators (KPIs):

* Conversion Rates: From trial to paid, and tier-specific conversions.

*AR

saas_pricing_strategy.md
Download as Markdown
Copy all content
Full output as text
Download ZIP
IDE-ready project ZIP
Copy share link
Permanent URL for this run
Get Embed Code
Embed this result on any website
Print / Save PDF
Use browser print dialog
\n\n\n"); var hasSrcMain=Object.keys(extracted).some(function(k){return k.indexOf("src/main")>=0;}); if(!hasSrcMain) zip.file(folder+"src/main."+ext,"import React from 'react'\nimport ReactDOM from 'react-dom/client'\nimport App from './App'\nimport './index.css'\n\nReactDOM.createRoot(document.getElementById('root')!).render(\n \n \n \n)\n"); var hasSrcApp=Object.keys(extracted).some(function(k){return k==="src/App."+ext||k==="App."+ext;}); if(!hasSrcApp) zip.file(folder+"src/App."+ext,"import React from 'react'\nimport './App.css'\n\nfunction App(){\n return(\n
\n
\n

"+slugTitle(pn)+"

\n

Built with PantheraHive BOS

\n
\n
\n )\n}\nexport default App\n"); zip.file(folder+"src/index.css","*{margin:0;padding:0;box-sizing:border-box}\nbody{font-family:system-ui,-apple-system,sans-serif;background:#f0f2f5;color:#1a1a2e}\n.app{min-height:100vh;display:flex;flex-direction:column}\n.app-header{flex:1;display:flex;flex-direction:column;align-items:center;justify-content:center;gap:12px;padding:40px}\nh1{font-size:2.5rem;font-weight:700}\n"); zip.file(folder+"src/App.css",""); zip.file(folder+"src/components/.gitkeep",""); zip.file(folder+"src/pages/.gitkeep",""); zip.file(folder+"src/hooks/.gitkeep",""); Object.keys(extracted).forEach(function(p){ var fp=p.startsWith("src/")?p:"src/"+p; zip.file(folder+fp,extracted[p]); }); zip.file(folder+"README.md","# "+slugTitle(pn)+"\n\nGenerated by PantheraHive BOS.\n\n## Setup\n\`\`\`bash\nnpm install\nnpm run dev\n\`\`\`\n\n## Build\n\`\`\`bash\nnpm run build\n\`\`\`\n\n## Open in IDE\nOpen the project folder in VS Code or WebStorm.\n"); zip.file(folder+".gitignore","node_modules/\ndist/\n.env\n.DS_Store\n*.local\n"); } /* --- Vue (Vite + Composition API + TypeScript) --- */ function buildVue(zip,folder,app,code,panelTxt){ var pn=pkgName(app); var C=cc(pn); var extracted=extractCode(panelTxt); zip.file(folder+"package.json",'{\n "name": "'+pn+'",\n "version": "0.0.0",\n "type": "module",\n "scripts": {\n "dev": "vite",\n "build": "vue-tsc -b && vite build",\n "preview": "vite preview"\n },\n "dependencies": {\n "vue": "^3.5.13",\n "vue-router": "^4.4.5",\n "pinia": "^2.3.0",\n "axios": "^1.7.9"\n },\n "devDependencies": {\n "@vitejs/plugin-vue": "^5.2.1",\n "typescript": "~5.7.3",\n "vite": "^6.0.5",\n "vue-tsc": "^2.2.0"\n }\n}\n'); zip.file(folder+"vite.config.ts","import { defineConfig } from 'vite'\nimport vue from '@vitejs/plugin-vue'\nimport { resolve } from 'path'\n\nexport default defineConfig({\n plugins: [vue()],\n resolve: { alias: { '@': resolve(__dirname,'src') } }\n})\n"); zip.file(folder+"tsconfig.json",'{"files":[],"references":[{"path":"./tsconfig.app.json"},{"path":"./tsconfig.node.json"}]}\n'); zip.file(folder+"tsconfig.app.json",'{\n "compilerOptions":{\n "target":"ES2020","useDefineForClassFields":true,"module":"ESNext","lib":["ES2020","DOM","DOM.Iterable"],\n "skipLibCheck":true,"moduleResolution":"bundler","allowImportingTsExtensions":true,\n "isolatedModules":true,"moduleDetection":"force","noEmit":true,"jsxImportSource":"vue",\n "strict":true,"paths":{"@/*":["./src/*"]}\n },\n "include":["src/**/*.ts","src/**/*.d.ts","src/**/*.tsx","src/**/*.vue"]\n}\n'); zip.file(folder+"env.d.ts","/// \n"); zip.file(folder+"index.html","\n\n\n \n \n "+slugTitle(pn)+"\n\n\n
\n \n\n\n"); var hasMain=Object.keys(extracted).some(function(k){return k==="src/main.ts"||k==="main.ts";}); if(!hasMain) zip.file(folder+"src/main.ts","import { createApp } from 'vue'\nimport { createPinia } from 'pinia'\nimport App from './App.vue'\nimport './assets/main.css'\n\nconst app = createApp(App)\napp.use(createPinia())\napp.mount('#app')\n"); var hasApp=Object.keys(extracted).some(function(k){return k.indexOf("App.vue")>=0;}); if(!hasApp) zip.file(folder+"src/App.vue","\n\n\n\n\n"); zip.file(folder+"src/assets/main.css","*{margin:0;padding:0;box-sizing:border-box}body{font-family:system-ui,sans-serif;background:#fff;color:#213547}\n"); zip.file(folder+"src/components/.gitkeep",""); zip.file(folder+"src/views/.gitkeep",""); zip.file(folder+"src/stores/.gitkeep",""); Object.keys(extracted).forEach(function(p){ var fp=p.startsWith("src/")?p:"src/"+p; zip.file(folder+fp,extracted[p]); }); zip.file(folder+"README.md","# "+slugTitle(pn)+"\n\nGenerated by PantheraHive BOS.\n\n## Setup\n\`\`\`bash\nnpm install\nnpm run dev\n\`\`\`\n\n## Build\n\`\`\`bash\nnpm run build\n\`\`\`\n\nOpen in VS Code or WebStorm.\n"); zip.file(folder+".gitignore","node_modules/\ndist/\n.env\n.DS_Store\n*.local\n"); } /* --- Angular (v19 standalone) --- */ function buildAngular(zip,folder,app,code,panelTxt){ var pn=pkgName(app); var C=cc(pn); var sel=pn.replace(/_/g,"-"); var extracted=extractCode(panelTxt); zip.file(folder+"package.json",'{\n "name": "'+pn+'",\n "version": "0.0.0",\n "scripts": {\n "ng": "ng",\n "start": "ng serve",\n "build": "ng build",\n "test": "ng test"\n },\n "dependencies": {\n "@angular/animations": "^19.0.0",\n "@angular/common": "^19.0.0",\n "@angular/compiler": "^19.0.0",\n "@angular/core": "^19.0.0",\n "@angular/forms": "^19.0.0",\n "@angular/platform-browser": "^19.0.0",\n "@angular/platform-browser-dynamic": "^19.0.0",\n "@angular/router": "^19.0.0",\n "rxjs": "~7.8.0",\n "tslib": "^2.3.0",\n "zone.js": "~0.15.0"\n },\n "devDependencies": {\n "@angular-devkit/build-angular": "^19.0.0",\n "@angular/cli": "^19.0.0",\n "@angular/compiler-cli": "^19.0.0",\n "typescript": "~5.6.0"\n }\n}\n'); zip.file(folder+"angular.json",'{\n "$schema": "./node_modules/@angular/cli/lib/config/schema.json",\n "version": 1,\n "newProjectRoot": "projects",\n "projects": {\n "'+pn+'": {\n "projectType": "application",\n "root": "",\n "sourceRoot": "src",\n "prefix": "app",\n "architect": {\n "build": {\n "builder": "@angular-devkit/build-angular:application",\n "options": {\n "outputPath": "dist/'+pn+'",\n "index": "src/index.html",\n "browser": "src/main.ts",\n "tsConfig": "tsconfig.app.json",\n "styles": ["src/styles.css"],\n "scripts": []\n }\n },\n "serve": {"builder":"@angular-devkit/build-angular:dev-server","configurations":{"production":{"buildTarget":"'+pn+':build:production"},"development":{"buildTarget":"'+pn+':build:development"}},"defaultConfiguration":"development"}\n }\n }\n }\n}\n'); zip.file(folder+"tsconfig.json",'{\n "compileOnSave": false,\n "compilerOptions": {"baseUrl":"./","outDir":"./dist/out-tsc","forceConsistentCasingInFileNames":true,"strict":true,"noImplicitOverride":true,"noPropertyAccessFromIndexSignature":true,"noImplicitReturns":true,"noFallthroughCasesInSwitch":true,"paths":{"@/*":["src/*"]},"skipLibCheck":true,"esModuleInterop":true,"sourceMap":true,"declaration":false,"experimentalDecorators":true,"moduleResolution":"bundler","importHelpers":true,"target":"ES2022","module":"ES2022","useDefineForClassFields":false,"lib":["ES2022","dom"]},\n "references":[{"path":"./tsconfig.app.json"}]\n}\n'); zip.file(folder+"tsconfig.app.json",'{\n "extends":"./tsconfig.json",\n "compilerOptions":{"outDir":"./dist/out-tsc","types":[]},\n "files":["src/main.ts"],\n "include":["src/**/*.d.ts"]\n}\n'); zip.file(folder+"src/index.html","\n\n\n \n "+slugTitle(pn)+"\n \n \n \n\n\n \n\n\n"); zip.file(folder+"src/main.ts","import { bootstrapApplication } from '@angular/platform-browser';\nimport { appConfig } from './app/app.config';\nimport { AppComponent } from './app/app.component';\n\nbootstrapApplication(AppComponent, appConfig)\n .catch(err => console.error(err));\n"); zip.file(folder+"src/styles.css","* { margin: 0; padding: 0; box-sizing: border-box; }\nbody { font-family: system-ui, -apple-system, sans-serif; background: #f9fafb; color: #111827; }\n"); var hasComp=Object.keys(extracted).some(function(k){return k.indexOf("app.component")>=0;}); if(!hasComp){ zip.file(folder+"src/app/app.component.ts","import { Component } from '@angular/core';\nimport { RouterOutlet } from '@angular/router';\n\n@Component({\n selector: 'app-root',\n standalone: true,\n imports: [RouterOutlet],\n templateUrl: './app.component.html',\n styleUrl: './app.component.css'\n})\nexport class AppComponent {\n title = '"+pn+"';\n}\n"); zip.file(folder+"src/app/app.component.html","
\n
\n

"+slugTitle(pn)+"

\n

Built with PantheraHive BOS

\n
\n \n
\n"); zip.file(folder+"src/app/app.component.css",".app-header{display:flex;flex-direction:column;align-items:center;justify-content:center;min-height:60vh;gap:16px}h1{font-size:2.5rem;font-weight:700;color:#6366f1}\n"); } zip.file(folder+"src/app/app.config.ts","import { ApplicationConfig, provideZoneChangeDetection } from '@angular/core';\nimport { provideRouter } from '@angular/router';\nimport { routes } from './app.routes';\n\nexport const appConfig: ApplicationConfig = {\n providers: [\n provideZoneChangeDetection({ eventCoalescing: true }),\n provideRouter(routes)\n ]\n};\n"); zip.file(folder+"src/app/app.routes.ts","import { Routes } from '@angular/router';\n\nexport const routes: Routes = [];\n"); Object.keys(extracted).forEach(function(p){ var fp=p.startsWith("src/")?p:"src/"+p; zip.file(folder+fp,extracted[p]); }); zip.file(folder+"README.md","# "+slugTitle(pn)+"\n\nGenerated by PantheraHive BOS.\n\n## Setup\n\`\`\`bash\nnpm install\nng serve\n# or: npm start\n\`\`\`\n\n## Build\n\`\`\`bash\nng build\n\`\`\`\n\nOpen in VS Code with Angular Language Service extension.\n"); zip.file(folder+".gitignore","node_modules/\ndist/\n.env\n.DS_Store\n*.local\n.angular/\n"); } /* --- Python --- */ function buildPython(zip,folder,app,code){ var title=slugTitle(app); var pn=pkgName(app); var src=code.replace(/^\`\`\`[\w]*\n?/m,"").replace(/\n?\`\`\`$/m,"").trim(); var reqMap={"numpy":"numpy","pandas":"pandas","sklearn":"scikit-learn","tensorflow":"tensorflow","torch":"torch","flask":"flask","fastapi":"fastapi","uvicorn":"uvicorn","requests":"requests","sqlalchemy":"sqlalchemy","pydantic":"pydantic","dotenv":"python-dotenv","PIL":"Pillow","cv2":"opencv-python","matplotlib":"matplotlib","seaborn":"seaborn","scipy":"scipy"}; var reqs=[]; Object.keys(reqMap).forEach(function(k){if(src.indexOf("import "+k)>=0||src.indexOf("from "+k)>=0)reqs.push(reqMap[k]);}); var reqsTxt=reqs.length?reqs.join("\n"):"# add dependencies here\n"; zip.file(folder+"main.py",src||"# "+title+"\n# Generated by PantheraHive BOS\n\nprint(title+\" loaded\")\n"); zip.file(folder+"requirements.txt",reqsTxt); zip.file(folder+".env.example","# Environment variables\n"); zip.file(folder+"README.md","# "+title+"\n\nGenerated by PantheraHive BOS.\n\n## Setup\n\`\`\`bash\npython3 -m venv .venv\nsource .venv/bin/activate\npip install -r requirements.txt\n\`\`\`\n\n## Run\n\`\`\`bash\npython main.py\n\`\`\`\n"); zip.file(folder+".gitignore",".venv/\n__pycache__/\n*.pyc\n.env\n.DS_Store\n"); } /* --- Node.js --- */ function buildNode(zip,folder,app,code){ var title=slugTitle(app); var pn=pkgName(app); var src=code.replace(/^\`\`\`[\w]*\n?/m,"").replace(/\n?\`\`\`$/m,"").trim(); var depMap={"mongoose":"^8.0.0","dotenv":"^16.4.5","axios":"^1.7.9","cors":"^2.8.5","bcryptjs":"^2.4.3","jsonwebtoken":"^9.0.2","socket.io":"^4.7.4","uuid":"^9.0.1","zod":"^3.22.4","express":"^4.18.2"}; var deps={}; Object.keys(depMap).forEach(function(k){if(src.indexOf(k)>=0)deps[k]=depMap[k];}); if(!deps["express"])deps["express"]="^4.18.2"; var pkgJson=JSON.stringify({"name":pn,"version":"1.0.0","main":"src/index.js","scripts":{"start":"node src/index.js","dev":"nodemon src/index.js"},"dependencies":deps,"devDependencies":{"nodemon":"^3.0.3"}},null,2)+"\n"; zip.file(folder+"package.json",pkgJson); var fallback="const express=require(\"express\");\nconst app=express();\napp.use(express.json());\n\napp.get(\"/\",(req,res)=>{\n res.json({message:\""+title+" API\"});\n});\n\nconst PORT=process.env.PORT||3000;\napp.listen(PORT,()=>console.log(\"Server on port \"+PORT));\n"; zip.file(folder+"src/index.js",src||fallback); zip.file(folder+".env.example","PORT=3000\n"); zip.file(folder+".gitignore","node_modules/\n.env\n.DS_Store\n"); zip.file(folder+"README.md","# "+title+"\n\nGenerated by PantheraHive BOS.\n\n## Setup\n\`\`\`bash\nnpm install\n\`\`\`\n\n## Run\n\`\`\`bash\nnpm run dev\n\`\`\`\n"); } /* --- Vanilla HTML --- */ function buildVanillaHtml(zip,folder,app,code){ var title=slugTitle(app); var isFullDoc=code.trim().toLowerCase().indexOf("=0||code.trim().toLowerCase().indexOf("=0; var indexHtml=isFullDoc?code:"\n\n\n\n\n"+title+"\n\n\n\n"+code+"\n\n\n\n"; zip.file(folder+"index.html",indexHtml); zip.file(folder+"style.css","/* "+title+" — styles */\n*{margin:0;padding:0;box-sizing:border-box}\nbody{font-family:system-ui,-apple-system,sans-serif;background:#fff;color:#1a1a2e}\n"); zip.file(folder+"script.js","/* "+title+" — scripts */\n"); zip.file(folder+"assets/.gitkeep",""); zip.file(folder+"README.md","# "+title+"\n\nGenerated by PantheraHive BOS.\n\n## Open\nDouble-click \`index.html\` in your browser.\n\nOr serve locally:\n\`\`\`bash\nnpx serve .\n# or\npython3 -m http.server 3000\n\`\`\`\n"); zip.file(folder+".gitignore",".DS_Store\nnode_modules/\n.env\n"); } /* ===== MAIN ===== */ var sc=document.createElement("script"); sc.src="https://cdnjs.cloudflare.com/ajax/libs/jszip/3.10.1/jszip.min.js"; sc.onerror=function(){ if(lbl)lbl.textContent="Download ZIP"; alert("JSZip load failed — check connection."); }; sc.onload=function(){ var zip=new JSZip(); var base=(_phFname||"output").replace(/\.[^.]+$/,""); var app=base.toLowerCase().replace(/[^a-z0-9]+/g,"_").replace(/^_+|_+$/g,"")||"my_app"; var folder=app+"/"; var vc=document.getElementById("panel-content"); var panelTxt=vc?(vc.innerText||vc.textContent||""):""; var lang=detectLang(_phCode,panelTxt); if(_phIsHtml){ buildVanillaHtml(zip,folder,app,_phCode); } else if(lang==="flutter"){ buildFlutter(zip,folder,app,_phCode,panelTxt); } else if(lang==="react-native"){ buildReactNative(zip,folder,app,_phCode,panelTxt); } else if(lang==="swift"){ buildSwift(zip,folder,app,_phCode,panelTxt); } else if(lang==="kotlin"){ buildKotlin(zip,folder,app,_phCode,panelTxt); } else if(lang==="react"){ buildReact(zip,folder,app,_phCode,panelTxt); } else if(lang==="vue"){ buildVue(zip,folder,app,_phCode,panelTxt); } else if(lang==="angular"){ buildAngular(zip,folder,app,_phCode,panelTxt); } else if(lang==="python"){ buildPython(zip,folder,app,_phCode); } else if(lang==="node"){ buildNode(zip,folder,app,_phCode); } else { /* Document/content workflow */ var title=app.replace(/_/g," "); var md=_phAll||_phCode||panelTxt||"No content"; zip.file(folder+app+".md",md); var h=""+title+""; h+="

"+title+"

"; var hc=md.replace(/&/g,"&").replace(//g,">"); hc=hc.replace(/^### (.+)$/gm,"

$1

"); hc=hc.replace(/^## (.+)$/gm,"

$1

"); hc=hc.replace(/^# (.+)$/gm,"

$1

"); hc=hc.replace(/\*\*(.+?)\*\*/g,"$1"); hc=hc.replace(/\n{2,}/g,"

"); h+="

"+hc+"

Generated by PantheraHive BOS
"; zip.file(folder+app+".html",h); zip.file(folder+"README.md","# "+title+"\n\nGenerated by PantheraHive BOS.\n\nFiles:\n- "+app+".md (Markdown)\n- "+app+".html (styled HTML)\n"); } zip.generateAsync({type:"blob"}).then(function(blob){ var a=document.createElement("a"); a.href=URL.createObjectURL(blob); a.download=app+".zip"; a.click(); URL.revokeObjectURL(a.href); if(lbl)lbl.textContent="Download ZIP"; }); }; document.head.appendChild(sc); } function phShare(){navigator.clipboard.writeText(window.location.href).then(function(){var el=document.getElementById("ph-share-lbl");if(el){el.textContent="Link copied!";setTimeout(function(){el.textContent="Copy share link";},2500);}});}function phEmbed(){var runId=window.location.pathname.split("/").pop().replace(".html","");var embedUrl="https://pantherahive.com/embed/"+runId;var code='';navigator.clipboard.writeText(code).then(function(){var el=document.getElementById("ph-embed-lbl");if(el){el.textContent="Embed code copied!";setTimeout(function(){el.textContent="Get Embed Code";},2500);}});}