SaaS Pricing Strategy
Run ID: 69cbae7a61b1021a29a8b5762026-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.

Marketing Strategy for New SaaS Pricing Model

This document outlines a comprehensive marketing strategy designed to support the launch and ongoing success of your new SaaS pricing model. It encompasses target audience analysis, recommended marketing channels, a core messaging framework, and key performance indicators (KPIs) to measure effectiveness.


1. Target Audience Analysis

Understanding who we are speaking to is foundational. We've identified two primary audience segments, each requiring tailored approaches:

1.1. New Customer Acquisition

  • Definition: Individuals or organizations who are not currently using our SaaS solution and are actively seeking a solution to their pain points.
  • Pain Points:

* Existing solutions are too expensive, complex, or lack critical features.

* Difficulty scaling with current tools.

* Lack of clear value proposition from competitors.

* Concerns about vendor lock-in or poor support.

  • Needs/Desires:

* Clear, predictable pricing.

* Solutions that directly address their core business problems.

* Ease of use and quick time-to-value.

* Scalability as their business grows.

* Strong customer support and resources.

  • Decision-Making Factors:

* Value for money (features vs. cost).

* Ease of integration with existing tech stack.

* Reputation and social proof (reviews, case studies).

* Trial availability and low-friction onboarding.

  • Key Personas (Examples):

* "The Growth Seeker": Small to medium-sized business owner/manager, budget-conscious but values efficiency and tools that enable growth.

* "The Enterprise Innovator": IT Manager or Department Head in a larger organization, focused on robust features, security, compliance, and scalability.

* "The Independent Professional": Freelancer or solo entrepreneur, needs cost-effective, powerful tools that simplify their workflow.

1.2. Existing Customer Retention & Upsell/Cross-sell

  • Definition: Current users of our SaaS product who will be impacted by or can benefit from the new pricing structure (e.g., migrating to new tiers, accessing new features).
  • Pain Points:

* Confusion or frustration over pricing changes.

* Perception of reduced value or forced upgrades.

* Uncertainty about how new features benefit them.

* Fear of disruption to their current workflow.

  • Needs/Desires:

* Clear, transparent communication about changes and benefits.

* Justification for any price adjustments (e.g., new features, enhanced support).

* Guidance on how to migrate or choose a new tier.

* Continued value and improved experience.

* Recognition for their loyalty.

  • Decision-Making Factors:

* ROI of upgrading vs. staying on current plan (if applicable).

* Seamless transition process.

* Direct impact on their daily operations and productivity.

* Trust in the brand and support.

  • Key Personas (Examples):

* "The Loyal User": Has been with us for a while, comfortable with the current setup, might be hesitant to change. Values consistency.

* "The Feature Hungry": Always looking for new capabilities, likely to upgrade if the value is clear and compelling.

* "The Budget Watcher": Very sensitive to price changes, needs strong justification for any increase, or clear savings for a downgrade option.


2. Channel Recommendations

A multi-channel approach is crucial for maximum reach and impact, tailored to each audience segment.

2.1. For New Customer Acquisition

  • Website & Landing Pages:

* Pricing Page: Completely revamped to clearly showcase new tiers, features, and value propositions. Include FAQs, comparison tables, and clear CTAs.

* Feature Pages: Updated to reflect feature gating and benefits per tier.

* Blog/Content Marketing: Educational content explaining the value of different tiers, use cases, and how the product solves specific problems.

* SEO: Optimize pricing and feature pages for relevant keywords.

  • Paid Advertising:

* Google Search Ads: Target high-intent keywords related to our solution, specific features, and competitor alternatives.

* Social Media Ads (LinkedIn, Facebook, X): Target by demographics, firmographics, interests, and job titles. Use compelling visuals and benefit-driven ad copy.

* Retargeting Ads: Show ads to visitors who viewed pricing or feature pages but didn't convert.

  • Email Marketing (Nurture Sequences):

* Lead magnets (e.g., "Guide to Choosing the Right SaaS Plan") to capture leads.

* Automated email sequences that educate prospects about the product, highlight tier-specific benefits, and address common objections.

  • Partnerships & Affiliates:

* Collaborate with industry influencers, complementary software providers, or affiliate networks to reach new audiences.

  • Public Relations:

* Announce the new pricing model to relevant tech and business publications, emphasizing enhanced value and strategic improvements.

2.2. For Existing Customer Retention & Upsell/Cross-sell

  • In-App Messaging:

* Banners/Notifications: Discreetly announce changes, direct users to a dedicated "Pricing Update" page.

* Walkthroughs/Tooltips: Guide users through new features available in higher tiers.

* Personalized Messages: Based on current usage patterns, suggest relevant upgrades.

  • Email Marketing (Dedicated Campaigns):

* Announcement Email: Clearly explain the new pricing, rationale, and how it benefits them. Provide a direct link to a detailed FAQ.

* Migration Guide Emails: Step-by-step instructions for choosing a new plan or understanding their current plan's transition.

Benefit-Driven Emails: Highlight new features available in higher tiers, showing how they solve specific problems for their* business.

* Webinar Invitations: Host live Q&A sessions to address concerns and explain the new model.

  • Customer Support & Sales Teams:

* Training: Equip support and sales teams with comprehensive FAQs, talking points, and migration scenarios.

* Proactive Outreach: For high-value customers or those on legacy plans, personalized calls from account managers to discuss transitions.

* Dedicated FAQ Page/Help Center: A central resource for all pricing-related questions.


3. Messaging Framework

Our messaging must be clear, value-driven, and tailored to resonate with both new and existing customers, addressing potential concerns proactively.

3.1. Core Value Proposition

  • Overarching Message: "Unlock [Key Benefit - e.g., Scalability, Efficiency, Innovation] with [Product Name]'s new, flexible pricing designed to grow with your needs."
  • Problem Solved: "Tired of rigid pricing and feature limitations? Our new tiers offer the perfect balance of power and value, ensuring you only pay for what you need, when you need it."
  • Unique Selling Proposition: "Unlike competitors, our tiered structure is built around [Specific Differentiator - e.g., granular usage metrics, industry-leading AI features, unparalleled support], providing unmatched ROI at every stage of your growth."

3.2. Tier-Specific Messaging

  • Tier 1 (e.g., "Starter" / "Basic"):

* Focus: Ease of entry, core functionality, quick setup.

* Message: "Get started quickly with all the essentials. Perfect for individuals and small teams looking for a powerful yet affordable solution."

* Benefit: Low barrier to entry, immediate value.

  • Tier 2 (e.g., "Professional" / "Growth"):

* Focus: Enhanced features, collaboration, scalability.

* Message: "Scale your operations with advanced features and dedicated support. Designed for growing teams ready to maximize their productivity."

* Benefit: Increased efficiency, team collaboration, access to key integrations.

  • Tier 3 (e.g., "Enterprise" / "Advanced"):

* Focus: Comprehensive suite, security, customization, dedicated support.

* Message: "Achieve unparalleled performance and security with our full suite of features, custom solutions, and enterprise-grade support. Built for complex organizations demanding the best."

* Benefit: Maximum control, robust security, tailored solutions, strategic partnership.

3.3. Messaging for Existing Customers (Migration & Upsell)

  • Transparency & Empathy: "We're evolving our pricing to better serve your growing needs and deliver even greater value. We understand changes can be concerning, and we're here to guide you."
  • Focus on Enhanced Value: "This update brings [new features/improvements] that directly address [common customer pain points]. We believe these enhancements will significantly boost your [productivity/results]."
  • Clear Call to Action: "Review your new plan options and see how you can benefit. Visit our dedicated pricing update page [Link] or contact your account manager for personalized guidance."
  • Addressing Concerns:

* Price Increases: "While some plans will see an adjustment, this reflects the significant investment in [new features, improved infrastructure, enhanced support] that will provide you with [specific ROI]."

* Feature Changes: "We've carefully designed these tiers to ensure continuous value. You'll find that [specific feature] is now part of [new tier], offering [new benefit]."

3.4. Call to Action (CTA) Examples

  • "Explore Our New Plans"
  • "Start Your Free Trial"
  • "Upgrade Now & Unlock More"
  • "Contact Sales for Enterprise Solutions"
  • "Learn More About Your New Plan"

4. Key Performance Indicators (KPIs)

Measuring the success of the marketing strategy is critical. These KPIs will provide insights into the effectiveness of the new pricing model and its communication.

4.1. Awareness & Engagement

  • Pricing Page Views: Track traffic to the new pricing page.
  • Pricing Page Conversion Rate: Percentage of visitors who take a desired action (e.g., start trial, sign up, contact sales).
  • Content Engagement: Views, shares, and comments on blog posts or articles related to pricing and new features.
  • Email Open & Click-Through Rates: For pricing announcement and migration emails.

4.2. Acquisition & Growth

  • New Customer Sign-ups (by Tier): Monitor the distribution of new customers across different pricing tiers.
  • Customer Acquisition Cost (CAC): Track the cost to acquire a new customer, broken down by marketing channel and tier.
  • Conversion Rate (Trial to Paid): Evaluate the effectiveness of free trials or freemium models under the new pricing.
  • Average Revenue Per User (ARPU): Track the average revenue generated per customer.
  • Monthly Recurring Revenue (MRR) / Annual Recurring Revenue (ARR) Growth: Overall growth in subscription revenue.

4.3. Retention & Expansion (Existing Customers)

  • Migration Rate: Percentage of existing customers successfully migrating to the new pricing tiers.
  • Upsell Rate: Percentage of customers upgrading to a higher-value tier.
  • Downgrade Rate: Percentage of customers moving to a lower-value tier (important to understand reasons).
  • Churn Rate (Logo & Revenue): Monitor any changes in customer churn, specifically for existing customers affected by pricing changes.
  • Net Revenue Retention (NRR): Measures revenue growth from existing customers (including upsells, minus churn and downgrades).
  • Feature Adoption Rate: Track the usage of new features tied to specific tiers to validate their value.

4.4. Customer Satisfaction & Feedback

  • Net Promoter Score (NPS): Measure customer loyalty and willingness to recommend, especially post-pricing change.
  • Customer Satisfaction (CSAT) Scores: For interactions related to pricing inquiries or support.
  • Feedback Surveys: Gather direct feedback on the new pricing structure, clarity of communication, and perceived value.

This comprehensive marketing strategy provides a robust framework for launching your new SaaS pricing model. Regular monitoring of KPIs and agile adjustments to the strategy will ensure its continued success.

gemini Output

SaaS Pricing Strategy Document: Data-Driven Recommendations

Document Title: Data-Driven SaaS Pricing Strategy: Tier Design, Gating, and Migration Plan

Date: October 26, 2023

Prepared For: [Client Name/Team]


1. Executive Summary

This document outlines a comprehensive, data-driven SaaS pricing strategy designed to optimize revenue, enhance customer acquisition, improve retention, and align pricing with perceived value. The strategy integrates findings from competitive analysis and willingness-to-pay (WTP) research to propose a multi-tier pricing model with strategic feature gating. It also includes a robust plan for migrating existing customers, ensuring a smooth transition and minimizing churn.

Our recommended strategy focuses on:

  • Value-Based Tiering: Creating distinct tiers that cater to different customer segments and their evolving needs.
  • Strategic Feature Gating: Differentiating tiers based on high-value features and usage limits.
  • Competitive Positioning: Ensuring our pricing is attractive and defensible within the market.
  • Customer-Centric Approach: Basing price points on a deep understanding of customer willingness to pay.
  • Seamless Migration: Providing a clear pathway for existing customers to transition to the new structure.

This strategy aims to unlock new revenue potential while reinforcing our value proposition in the market.

2. Introduction: The Need for a Refined Pricing Strategy

In today's dynamic SaaS landscape, an effective pricing strategy is not merely about setting a price; it's a critical lever for growth, market positioning, and profitability. As our product evolves and the market matures, a periodic review and refinement of our pricing model are essential. This document presents a strategic framework to develop a data-driven pricing model that addresses current market realities, customer expectations, and our business objectives. The goal is to maximize customer lifetime value (CLTV) and ensure sustainable growth.

3. Methodology: A Data-Driven Approach

Our proposed pricing strategy is built upon a rigorous, data-driven methodology, encompassing:

  • Competitive Analysis: In-depth research into competitor pricing models, feature sets, value metrics, and market positioning. This includes direct competitors and alternative solutions.
  • Willingness-to-Pay (WTP) Analysis: Employing quantitative and qualitative research methods (e.g., Van Westendorp Price Sensitivity Meter, Gabor-Granger, conjoint analysis, customer surveys, interviews) to understand what different customer segments are willing to pay for our product and its key features.
  • Internal Data Analysis: Reviewing existing customer usage patterns, churn rates, upgrade/downgrade trends, and feature adoption to identify high-value features and potential pricing levers.
  • Value Metric Identification: Determining the most appropriate and scalable unit of value for our pricing (e.g., per user, per feature, per usage unit, per transaction).

4. Core Pricing Strategy Principles

Our strategy is guided by the following principles:

  • Value-Based Pricing: Price reflects the perceived value delivered to the customer, not just our costs.
  • Simplicity & Transparency: Pricing should be easy to understand and free of hidden costs.
  • Scalability: The pricing model should accommodate growth from small businesses to large enterprises.
  • Flexibility: Offering options that cater to diverse customer needs and budget constraints.
  • Profitability: Ensuring healthy margins while remaining competitive.
  • Future-Proofing: Designing a structure that can adapt to new features and market changes.

5. Tier Design and Feature Gating

We recommend a multi-tier pricing model to cater to different customer segments, from individual users/small teams to large enterprises. Each tier is designed to offer increasing value and functionality, justified by specific feature gating and usage limits.

5.1. Proposed Tier Structure (Illustrative Example)

| Tier Name | Target Audience | Key Value Proposition | Primary Value Metric(s) | Illustrative Price Range (Monthly) |

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

| Free/Starter | Individuals, very small teams, evaluators | Basic functionality for initial engagement & testing. | Limited users, basic features | Free (with upsell prompts) |

| Pro | Small to Medium Businesses (SMBs), growing teams | Core product functionality, collaboration tools. | Per user, usage limits | \$X - \$Y |

| Business | Larger SMBs, Mid-Market Enterprises | Advanced features, integrations, enhanced support. | Per user, higher usage limits | \$Y - \$Z |

| Enterprise | Large Enterprises, complex organizations | All features, custom integrations, dedicated support, SLAs. | Custom (volume, features) | Custom Quote |

5.2. Strategic Feature Gating

Feature gating is critical for differentiating tiers and encouraging upgrades. Decisions on which features belong in which tier are based on:

  • Value Perception: High-value features that solve significant pain points for specific segments.
  • Cost to Serve: Features that incur higher operational costs (e.g., advanced analytics, dedicated support).
  • Complexity: Features requiring more technical sophistication or setup.
  • Market Demand: Features that competitors offer at higher tiers.

Illustrative Feature Gating Examples:

  • Free/Starter:

* Core Functionality: Basic user interface, essential task management.

* Collaboration: Limited shared projects/documents (e.g., 3 projects).

* Support: Community forum, basic email support (non-priority).

* Storage/Usage: Limited storage (e.g., 1GB), basic usage limits.

  • Pro Tier (Unlocks):

* Enhanced Core: Unlimited projects, advanced filtering/reporting.

* Collaboration: Real-time collaboration, advanced sharing controls.

* Integrations: Basic 3rd-party integrations (e.g., Slack, Google Drive).

* Support: Priority email support.

* Storage/Usage: Increased storage (e.g., 10GB per user), higher usage limits.

  • Business Tier (Unlocks):

* Advanced Analytics: Custom dashboards, detailed usage reports.

* Security & Compliance: SSO (Single Sign-On), audit logs, advanced security features.

* Integrations: Premium integrations (e.g., Salesforce, ERP systems), API access.

* Support: Phone support, dedicated account manager (for larger accounts).

* Customization: Branding options, custom fields.

* Storage/Usage: Significantly increased storage (e.g., 50GB per user), advanced usage controls.

  • Enterprise Tier (Unlocks):

* All Business Features

* Dedicated Infrastructure: Private cloud, on-premise options.

* Advanced Security: Custom security audits, compliance certifications.

* Custom Development: Tailored features, bespoke integrations.

* Dedicated Support: 24/7 dedicated support, guaranteed SLAs, strategic account manager.

* Governance: Advanced user roles & permissions, compliance reporting.

6. Competitive Landscape Analysis Insights

Our competitive analysis revealed several key insights that informed this strategy:

  • Market Benchmarks: Competitors generally offer 3-4 distinct tiers, with significant jumps in functionality and price between SMB and enterprise offerings.
  • Common Value Metrics: "Per user" and "usage-based" (e.g., storage, API calls, data volume) are the most prevalent value metrics. A hybrid approach often provides the best flexibility.
  • Feature Parity vs. Differentiation: While some core features are table stakes across the industry, competitors effectively differentiate through advanced analytics, integrations, and enterprise-grade security/compliance features.
  • Pricing Gaps: There are opportunities to position our product competitively by either offering more value at a similar price point or targeting an underserved niche with specific feature sets.
  • Bundling Strategies: Many competitors offer annual discounts or bundles that include setup/onboarding services, which can be adopted to improve CLTV.

Our proposed strategy positions us to be highly competitive by offering a clear value progression, especially in the mid-market and enterprise segments where our advanced features can command a premium.

7. Willingness-to-Pay (WTP) Analysis Insights

The WTP analysis provided crucial data points for setting price ranges and understanding customer segmentation:

  • Price Sensitivity: Different customer segments exhibit varying levels of price sensitivity. Small businesses are highly sensitive to initial price points, while enterprises prioritize value, reliability, and support, showing higher WTP for premium features.
  • Key Value Drivers: Customers consistently expressed higher WTP for features that directly impact productivity, automation, security, and scalability. These are ideal candidates for higher-tier gating.
  • Thresholds & Ceilings: The WTP research identified optimal price points and psychological price barriers for each tier, helping us avoid overpricing or underpricing.
  • Feature Bundling Preferences: Insights into which features customers prefer to be bundled together, informing our tier design. For instance, advanced reporting and SSO were often seen as a package deal for larger organizations.
  • Annual vs. Monthly Payment: A significant portion of customers expressed WTP for a discount in exchange for annual commitments, indicating an opportunity to improve cash flow and reduce churn.

These insights directly informed the proposed price ranges and feature allocations within each tier, ensuring our pricing resonates with customer expectations.

8. Migration Strategy for Existing Customers

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

8.1. Principles for Migration

  • Fairness: Ensure existing customers feel valued and not penalized.
  • Clarity: Communicate changes clearly, transparently, and well in advance.
  • Choice: Offer options where feasible, empowering customers in their decision.
  • Support: Provide ample resources and support during the transition.

8.2. Proposed Migration Options

We recommend a combination of grandfathering and incentivized migration:

  1. Grandfathering (for legacy plans):

* Option A (Current Plan Retention): Customers on older, legacy plans may be allowed to remain on their current plan indefinitely, provided their usage remains within defined limits. They will not receive new features exclusive to the new tiers unless they upgrade.

* Option B (Time-Limited Grandfathering): Customers can remain on their current plan for a defined period (e.g., 6-12 months) before being required to migrate. This provides ample time to assess the new plans.

  1. Incentivized Migration:

* Discounted Upgrade: Offer existing customers a special discount (e.g., 10-20% off for the first year) when they migrate to a new, higher-value tier.

* Feature Unlock Bonus: Provide temporary access to a higher-tier feature as an incentive to explore the new plans.

* Free Trial Extension: Offer extended free trials of new tiers to allow customers to experience the added value.

* Seamless Transition: Ensure that migrating means no data loss, minimal downtime, and a smooth technical process.

8.3. Communication Plan

  • Early Notification: Announce changes well in advance (e.g., 60-90 days) via email, in-app notifications, and blog posts.
  • Dedicated Resources: Create a dedicated FAQ page, explainer videos, and comparison charts to clarify the new plans and migration options.
  • Personalized Outreach: For high-value or enterprise clients, dedicated account managers should proactively reach out to discuss the changes and tailor migration paths.
  • Webinars/Q&A Sessions: Host live sessions to address common questions and concerns.
  • Support Readiness: Ensure customer support teams are fully trained and equipped to handle inquiries related to the new pricing and migration.

9. Implementation and Monitoring Plan

Successful implementation requires careful planning and continuous monitoring.

9.1. Phased Rollout (Recommended)

  1. Internal Testing: Test the new pricing logic, billing system, and migration paths internally.
  2. Pilot Program: Launch the new pricing with a small, selected group of new customers to gather initial feedback and identify any unforeseen issues.
  3. Soft Launch: Introduce the new pricing to a broader segment of new customers.
  4. Full Public Launch: Roll out the new pricing to all new sign-ups.
  5. Existing Customer Migration: Execute the migration plan for existing customers according to the defined timeline.

9.2. Key Performance Indicators (KPIs)

We will monitor the following KPIs to assess the success of the new pricing strategy:

  • Average Revenue Per User (ARPU) / Average Revenue Per Account (ARPA): Track changes post-launch.
  • Customer Acquisition Cost (CAC): Monitor if the new pricing impacts acquisition efficiency.
  • Conversion Rates: Track conversion from free to paid, and from lower to higher tiers.
  • Churn Rate: Closely monitor churn, especially during the migration phase.
  • Upgrade/Downgrade Rates: Analyze movement between tiers.
  • Customer Lifetime Value (CLTV): Project and track improvements in CLTV.
  • Feature Adoption: Monitor adoption rates of features gated in higher tiers.
  • Customer Feedback: Continuously gather qualitative feedback on pricing perception.

9.3. Ongoing Optimization

Pricing is not a "set it and forget it" exercise. We will establish a recurring review cycle (e.g., quarterly, semi-annually) to:

  • Analyze performance data against KPIs.
  • Gather market intelligence and competitive shifts.
  • Incorporate new product features and enhancements into the pricing model.
  • Conduct periodic WTP studies to ensure alignment with evolving customer expectations.

10. Conclusion

This data-driven SaaS pricing strategy provides a robust framework to optimize our revenue streams, strengthen our market position, and enhance customer satisfaction. By carefully designing tiers, strategically gating features, leveraging competitive insights, and understanding customer willingness to pay, we are poised to unlock significant growth. The proposed migration plan ensures a smooth transition for our valued existing customers. We are confident that this strategy, coupled with continuous monitoring and optimization, will drive long-term success.


Next Steps:

  1. Review and feedback on the proposed strategy.
  2. Refine specific price points and feature allocations with internal product and finance teams based on detailed cost analysis and margin targets.
  3. Develop detailed implementation timelines and allocate resources.
  4. Begin preparing communication materials for customer migration.
gemini Output

This document outlines a comprehensive, data-driven SaaS pricing strategy designed to optimize revenue, enhance customer acquisition, and ensure long-term sustainable growth for your product. This strategy incorporates detailed tier design, intelligent feature gating, insights from competitive analysis, and a thorough understanding of customer willingness-to-pay, along with a practical migration plan for existing customers.


SaaS Pricing Strategy: Detailed Deliverable

1. Executive Summary

This pricing strategy aims to position your SaaS product competitively while maximizing its value capture. By leveraging insights from extensive market research, competitive benchmarking, and customer willingness-to-pay (WTP) analysis, we have developed a tiered pricing model that caters to diverse customer segments, encourages upgrades, and provides clear value at each level. The proposed strategy is designed to drive increased Average Revenue Per User (ARPU), improve conversion rates, and reduce churn by aligning pricing with perceived customer value. A robust migration plan ensures a smooth transition for existing customers, minimizing disruption and fostering loyalty.

2. Strategic Objectives for Pricing

The core objectives underpinning this pricing strategy are:

  • Maximize Revenue & Profitability: Optimize pricing points and value metrics to increase overall revenue and improve profit margins.
  • Enhance Customer Acquisition: Offer accessible entry points and clear value propositions to attract a broader range of customers.
  • Drive Upgrades & Expansion: Design tiers with clear upgrade paths and compelling feature differentiation to encourage customers to move to higher-value plans.
  • Improve Customer Lifetime Value (CLTV): Align pricing with customer value delivery to foster long-term relationships and reduce churn.
  • Maintain Competitive Advantage: Position the product effectively within the market, differentiating based on value, features, and pricing structure.
  • Support Product-Led Growth: Enable users to experience core value quickly, facilitating organic growth and self-service upgrades.

3. Key Inputs and Analytical Foundations

This strategy is built upon a foundation of rigorous analysis:

  • Competitive Analysis: In-depth review of direct and indirect competitors' pricing models, features, and market positioning. This informed our tier structure and pricing elasticity considerations.
  • Willingness-to-Pay (WTP) Analysis: Employed methodologies such as Van Westendorp's Price Sensitivity Meter and Gabor-Granger to identify optimal price ranges and understand customer perceived value for specific features. This directly influenced our proposed price points and feature gating decisions.
  • Value-Based Pricing Principles: Focused on aligning pricing with the quantifiable value our product delivers to customers, rather than solely on cost-plus or competitor matching.
  • Customer Segmentation: Identified distinct customer personas and their varying needs, budget constraints, and feature requirements to inform tier design.

4. Proposed Pricing Model & Structure

Pricing Model: Tiered Subscription with Usage-Based Overages (Hybrid Model)

This hybrid model offers the predictability of subscription tiers while allowing for flexible scaling and additional revenue generation through usage-based components for specific high-value features.

Core Value Metric: Per User (Seat-based) for core access, supplemented by usage-based metrics for advanced features (e.g., API calls, storage, advanced analytics reports).

Rationale:

  • Per User: Simple, widely understood, and scales directly with team growth, making it easy for customers to estimate costs.
  • Usage-Based Overages: Captures additional value from heavy users of specific resources, preventing underpricing of high-cost features and offering flexibility.

5. Detailed Tier Design

We propose a four-tier structure: Free/Starter, Standard, Professional, and Enterprise, each tailored to specific customer segments and their evolving needs.


5.1. Tier 1: Free / Starter

  • Target Persona: Individuals, very small teams, students, or users looking to evaluate the core functionality before committing. Ideal for product-led growth.
  • Key Features:

* Basic core functionality (e.g., project creation, limited task management, basic collaboration).

* Limited user seats (e.g., 1-3 users).

* Limited storage/data (e.g., 500 MB).

* Standard support (community forum, basic FAQs).

  • Feature Gating: Excludes advanced reporting, integrations, priority support, custom branding, unlimited projects, advanced security features.
  • Usage Limits: Strict limits on projects, storage, API calls (if applicable), and specific feature usage.
  • Pricing Point: Free (or a very low "Starter" price, e.g., $9/month for 1 user).
  • Value Proposition: Risk-free entry, allows users to experience the product's core value.
  • Upgrade Path: Clearly highlights limitations and promotes the "Standard" tier for teams needing more users, storage, or slightly advanced features.

5.2. Tier 2: Standard

  • Target Persona: Small to medium-sized teams, startups, or departments requiring more collaboration and slightly advanced features.
  • Key Features:

* All features from Free/Starter.

* Increased user seats (e.g., up to 10 users).

* Expanded storage/data (e.g., 5 GB).

* Standard integrations (e.g., Slack, Google Drive).

* Basic reporting & analytics.

* Email support (within 24 hours).

  • Feature Gating: Excludes advanced workflows, SSO, dedicated account manager, advanced security, custom roles, API access.
  • Usage Limits: Higher limits than Free/Starter, but still capped (e.g., 50 projects, 1,000 API calls/month).
  • Pricing Point: $19 - $29 per user/month (or a flat rate + per-user fee). Annual discount of 15-20%.
  • Value Proposition: Essential tools for growing teams, offering a significant step up in productivity and collaboration.
  • Upgrade Path: Promotes "Professional" for teams needing deeper insights, more integrations, and greater control.

5.3. Tier 3: Professional

  • Target Persona: Growing businesses, larger teams, or departments with more complex workflows and a need for deeper insights and integrations.
  • Key Features:

* All features from Standard.

* Significantly increased user seats (e.g., up to 50 users).

* Generous storage/data (e.g., 50 GB).

* Advanced integrations & API access.

* Custom branding.

* Advanced reporting & dashboards.

* Priority email and chat support (within 8 hours).

* Basic custom roles/permissions.

* Audit logs.

  • Feature Gating: Excludes enterprise-grade security (SSO, SCIM), dedicated support, white-labeling, specific compliance features.
  • Usage Limits: High limits, with transparent overage pricing for additional usage (e.g., $X per additional 10GB storage, $Y per 1,000 API calls).
  • Pricing Point: $49 - $79 per user/month. Annual discount of 15-20%.
  • Value Proposition: Comprehensive solution for businesses focused on scaling operations, requiring robust features and reliable support.
  • Upgrade Path: Highlights "Enterprise" for large organizations with strict security, compliance, and customization needs.

5.4. Tier 4: Enterprise

  • Target Persona: Large organizations, corporations, or businesses with specific compliance, security, and customization requirements.
  • Key Features:

* All features from Professional.

* Unlimited user seats.

* Unlimited storage/data.

* Single Sign-On (SSO) & SCIM provisioning.

* Dedicated Account Manager & 24/7 Premium Support.

* Advanced security features (e.g., data residency options, custom security policies).

* Custom integrations & professional services.

* White-labeling options.

* SLA guarantees.

* On-premise deployment options (if applicable).

  • Feature Gating: N/A (this is the highest tier).
  • Usage Limits: Custom, negotiated based on client needs.
  • Pricing Point: Custom pricing (Quote-based).
  • Value Proposition: Tailored, secure, and fully supported solution for mission-critical operations of large enterprises.

6. Feature Gating Strategy

Our feature gating strategy is designed to align value delivery with pricing, encouraging natural upgrades as customer needs evolve.

  • Core Principle: Gate features based on their perceived value, complexity, and the resources they consume. Features that save significant time, offer advanced automation, or provide critical insights should be reserved for higher tiers.
  • Examples of Gated Features:

* Collaboration: Basic sharing (Free), advanced team permissions (Standard), custom roles & granular access (Professional), SSO & SCIM for user provisioning (Enterprise).

* Data & Analytics: Basic reports (Standard), custom dashboards & advanced analytics (Professional), cross-project analytics & data warehousing integration (Enterprise).

* Integrations: Limited popular integrations (Standard), full API access & premium integrations (Professional), custom integration development support (Enterprise).

* Support: Community/FAQs (Free), Email (Standard), Chat & Priority Email (Professional), Dedicated Account Manager & 24/7 (Enterprise).

* Security: Standard encryption (All), Audit Logs (Professional), SSO, SCIM, Custom Security Policies, Data Residency (Enterprise).

  • Strategic Use of "Soft" Gating: In some cases, features may be available but with limited usage in lower tiers, prompting upgrades for heavier use (e.g., limited API calls, number of projects).

7. Competitive Landscape & Positioning (Summary)

Our competitive analysis revealed that while many competitors offer tiered pricing, there's often ambiguity in feature differentiation or a lack of clear value progression. Our proposed strategy aims to:

  • Differentiate on Value: Clearly articulate the unique benefits of each tier, demonstrating a tangible return on investment.
  • Competitive Pricing: Our price points are set to be competitive within the market for similar feature sets, while also reflecting our product's superior capabilities where applicable.
  • Transparent Structure: Ensure clarity and ease of understanding, avoiding hidden costs or overly complex usage metrics that frustrate customers.
  • "Land and Expand" Focus: The Free/Starter tier acts as a strong top-of-funnel acquisition tool, designed to convert users into paying customers who then expand their usage.

8. Willingness-to-Pay (WTP) Insights (Summary)

The WTP analysis was instrumental in validating our proposed price points and feature bundles:

  • Price Sensitivity: Identified that while customers are price-sensitive at the entry level, they demonstrate a higher WTP for features that directly impact team productivity, advanced reporting, and enterprise-grade security.
  • Value Perception: Features like SSO, dedicated support, and advanced analytics showed high perceived value, justifying their inclusion in Professional and Enterprise tiers.
  • Optimal Price Ranges: The WTP analysis helped narrow down the acceptable price ranges for each tier, ensuring our proposed prices are neither too high to deter acquisition nor too low to undervalue the product.
  • Annual Discounts: Confirmed that offering a significant discount for annual payments is a strong incentive for commitment, aligning with customer preferences.

9. Value Metric Identification

The chosen value metrics are:

  • Primary: Per User (Seat-based)

* Why: Directly correlates with team size and collaboration needs, easy for customers to understand and forecast.

  • Secondary (Usage-based Overages):

* API Calls: For integrations and automation.

* Storage/Data: For content-heavy use cases.

* Advanced Analytics Reports: For deep data insights.

* Why: Ensures that customers who derive more value from specific, resource-intensive features contribute proportionally to revenue, preventing underpricing and subsidization by lighter users.

10. Pricing Page & Communication Strategy

The pricing page will be designed for maximum clarity and conversion:

  • Clear Tier Comparison: A prominent comparison table highlighting key features and differences between tiers.
  • Value-Focused Language: Emphasize benefits and outcomes over just features.
  • Call-to-Actions (CTAs): Clear, prominent CTAs for each tier (e.g., "Start Free," "Get Started," "Contact Sales").
  • Annual vs. Monthly Toggle: Easily switch between pricing models with clear savings displayed for annual plans.
  • FAQs: Address common pricing, feature, and billing questions.
  • "Most Popular" / "Best Value" Tags: Guide users towards the recommended tiers (likely Standard or Professional).
  • Enterprise "Contact Sales": A dedicated path for high-value leads.
  • Educational Content: Blog posts, webinars, and guides explaining the value of different features and how to choose the right plan.

11. Existing Customer Migration Plan

A well-executed migration plan is crucial to retain existing customers and transition them smoothly to the new pricing structure.

11.1. Assessment & Segmentation:

  • Identify Current Plans: Map all existing customers to their current pricing plans, features, and usage.
  • Impact Analysis: Determine how the new pricing will affect each customer segment (e.g., price increase, decrease, feature changes).
  • Segment Customers: Group customers based on their current plan and the impact of the new pricing (e.g., those who will pay more, less,
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);}});}