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

This document outlines a comprehensive marketing strategy, designed to support the overall SaaS pricing strategy by effectively reaching the target audience, communicating value, and driving customer acquisition and retention.


Step 1 of 3: Marketing Strategy Development

1. Target Audience Analysis

Understanding our ideal customer is paramount to developing an effective marketing and pricing strategy. We will define both Ideal Customer Profiles (ICPs) and detailed user personas.

1.1 Ideal Customer Profile (ICP)

  • Company Size: Small to Medium-sized Businesses (SMBs) and Mid-Market companies (e.g., 50-1,000 employees).
  • Industry: (Specify relevant industries, e.g., Software Development, Digital Agencies, E-commerce, Financial Services, Healthcare, Manufacturing).
  • Revenue: Companies generating between \$5M - \$100M+ annually.
  • Growth Stage: Companies experiencing moderate to rapid growth, actively seeking solutions to scale operations, improve efficiency, or gain a competitive edge.
  • Technological Maturity: Open to adopting new technologies, often already using other SaaS tools, and possess internal resources or partners to manage new integrations.
  • Pain Points: Struggling with manual processes, lack of data insights, inefficient workflows, high operational costs, or difficulty in scaling existing solutions.

1.2 User Personas

Primary Persona: "The Growth-Oriented Operations Manager / Department Head"

  • Role: Operations Manager, Project Manager, Head of Marketing, Head of Sales, IT Manager.
  • Demographics: 30-50 years old, often with 5+ years of experience in their role.
  • Company Context: Works within an SMB or Mid-Market company, responsible for optimizing team performance and operational efficiency.
  • Goals:

* Improve team productivity and output.

* Reduce operational costs and manual errors.

* Gain better insights from data to inform strategic decisions.

* Ensure smooth adoption of new tools and processes.

* Demonstrate ROI for technology investments.

  • Pain Points:

* Existing tools are fragmented, leading to data silos and manual data entry.

* Lack of real-time visibility into project status or team performance.

* Difficulty in scaling current solutions to meet growing business needs.

* Budget constraints and pressure to justify software spend.

* Resistance to change from team members when new tools are introduced.

  • Motivations: Efficiency, data-driven decision making, scalability, ease of use, strong customer support, clear ROI.
  • Buying Process: Researches solutions online (industry blogs, review sites like G2/Capterra), seeks peer recommendations, evaluates demos, involves team members in trials, presents business case to senior management.

Secondary Persona: "The Strategic Executive / Business Owner"

  • Role: CEO, CTO, VP of Operations, Founder.
  • Demographics: 40-60 years old, typically decision-makers or budget holders.
  • Company Context: Oversees the strategic direction and financial health of the company.
  • Goals:

* Drive overall company growth and profitability.

* Ensure long-term competitive advantage.

* Mitigate business risks and ensure compliance.

* Foster innovation and digital transformation.

  • Pain Points:

* High-level strategic challenges related to market competitiveness, talent retention, and financial performance.

* Concerns about data security and regulatory compliance.

* Fear of vendor lock-in or difficult migrations.

* Need for a scalable, future-proof technology stack.

  • Motivations: Strategic advantage, financial performance, risk mitigation, long-term partnership, security, compliance.
  • Buying Process: Relies on recommendations from their management team (Primary Persona), focuses on high-level ROI, security, scalability, and vendor reputation. Engages in high-level discussions, often involved in final contract negotiations.

2. Channel Recommendations

A multi-channel approach will be employed to reach our target audience effectively across different stages of their buying journey.

2.1 Inbound Marketing

  • Content Marketing:

* Blog Posts: Regular articles addressing pain points, offering solutions, industry trends, and "how-to" guides (e.g., "5 Ways to Automate Your Workflow," "Choosing the Right SaaS for [Industry]").

* Whitepapers/Ebooks: In-depth resources for lead generation, exploring complex topics, best practices, and industry benchmarks.

* Webinars/Online Workshops: Live or on-demand sessions demonstrating product features, use cases, and expert insights, fostering engagement and lead capture.

* Case Studies: Detailed success stories showcasing how existing customers achieved tangible results with our SaaS, crucial for proving ROI.

  • Search Engine Optimization (SEO):

* Keyword Research: Target high-intent keywords related to our SaaS functionality, problem areas, and competitive solutions.

* On-Page SEO: Optimize website content, meta descriptions, and headers for target keywords.

* Technical SEO: Ensure site speed, mobile-friendliness, and crawlability for search engines.

* Local SEO (if applicable): For localized services or specific regional markets.

  • Social Media Marketing:

* LinkedIn: Essential for B2B engagement. Share thought leadership, company news, product updates, and engage with industry groups. Target specific roles and companies.

* Twitter: For real-time updates, industry news, and engaging with influencers and thought leaders.

* Relevant Forums/Communities: Participate in industry-specific online communities (e.g., Reddit subreddits, Slack groups, specialized forums) to provide value and establish expertise.

2.2 Outbound Marketing

  • Paid Advertising:

* Google Search Ads: Target users actively searching for solutions to their problems or specific product features.

* LinkedIn Ads: Highly effective for B2B targeting by job title, industry, company size, and specific interests. Use for lead generation and brand awareness.

* Software Review Sites (e.g., G2, Capterra, Software Advice): Paid listings and review management to capture users actively comparing solutions.

* Retargeting Ads: Re-engage website visitors who didn't convert, showing them tailored messages and offers.

  • Email Marketing:

* Lead Nurturing Campaigns: Automated sequences to educate prospects, build trust, and move them down the sales funnel after they download content or sign up for a webinar.

* Product Updates & Newsletters: Keep existing customers and interested prospects informed about new features, company news, and valuable content.

* Personalized Outreach: Targeted emails from sales representatives to high-value prospects.

  • Partnerships & Affiliates:

* Technology Integrations: Partner with complementary SaaS providers to offer bundled solutions or seamless integrations, expanding reach.

* Referral Programs: Incentivize existing customers to refer new clients.

* Affiliate Programs: Partner with industry influencers, consultants, or agencies to promote our product for a commission.

2.3 Sales Enablement

  • Sales Collateral: Develop high-quality brochures, product sheets, demo scripts, competitive battlecards, and ROI calculators to empower the sales team.
  • Product Demos: Standardized yet customizable demo flows highlighting key value propositions and addressing persona-specific pain points.
  • Free Trials/Freemium Model (if applicable): Offer a low-friction way for users to experience the product's value firsthand, leading to paid conversions.

3. Messaging Framework

Our messaging will focus on value, problem-solving, and differentiation, tailored to specific personas and stages of the buyer's journey.

3.1 Core Value Proposition

"Our SaaS empowers [ICP] to [achieve primary goal - e.g., streamline operations, gain actionable insights, accelerate growth] by [unique differentiator - e.g., providing an intuitive all-in-one platform, leveraging AI-driven analytics, offering unparalleled scalability], resulting in [key benefit - e.g., significant cost savings, increased productivity, enhanced decision-making]."

Example: "Our SaaS empowers growing SMBs to streamline their project management and client communication by providing an intuitive all-in-one platform, resulting in significant time savings and improved client satisfaction."

3.2 Key Message Pillars

  • Problem-Solution Focus:

Awareness Stage:* "Are you struggling with fragmented data and manual processes hindering your team's productivity? There's a better way."

Consideration Stage:* "Discover how [Our SaaS] eliminates data silos and automates routine tasks, freeing up your team to focus on strategic initiatives."

  • Benefit-Driven Outcomes:

* "Achieve [X]% increase in operational efficiency and [Y]% reduction in errors."

* "Gain real-time visibility into your [specific metric] to make faster, more informed decisions."

* "Scale your operations effortlessly without increasing headcount or IT complexity."

  • Differentiation & Uniqueness:

* "Unlike competitors, we offer [specific unique feature/integration/support level] that provides [unique benefit]."

* "Our platform is designed for [specific industry/use case], understanding your unique challenges better than generic solutions."

* "Experience unparalleled ease of use and a rapid onboarding process, getting your team productive faster."

  • Call to Action (CTAs):

* "Start Your Free Trial Today"

* "Request a Personalized Demo"

* "Download Our [Whitepaper/Ebook]"

* "Learn More About Our Pricing Tiers"

* "Talk to an Expert"

3.3 Pricing-Related Messaging

When communicating pricing, the focus will always be on value and ROI.

  • Value Justification:

* "Invest in a solution that pays for itself through [cost savings, efficiency gains, revenue growth]."

* "Our tiered pricing is designed to grow with your business, ensuring you only pay for what you need, when you need it."

  • Tiered Benefits:

* Clearly articulate the value and features unlocked at each tier (e.g., "Basic for essential functionality," "Pro for advanced automation and analytics," "Enterprise for ultimate scalability and dedicated support").

* Highlight the ROI potential for each tier based on the features included.

  • Transparency:

* Clearly display pricing on the website, avoiding hidden fees.

* Use clear, concise language to explain what's included in each plan.

  • Migration/Upgrade Path:

* For existing customers, clearly communicate the value of upgrading and the seamless process.

* "Upgrade to unlock [new features] and take your [outcome] to the next level."

4. Key Performance Indicators (KPIs)

To measure the effectiveness of our marketing strategy, we will track a comprehensive set of KPIs across the customer journey.

4.1 Awareness & Reach

  • Website Traffic: Unique Visitors, Page Views, Traffic Sources (Organic, Paid, Referral, Direct).
  • Brand Mentions: Number of mentions across social media, news, and review sites.
  • Social Media Reach & Engagement: Impressions, Followers, Likes, Shares, Comments.
  • SEO Rankings: Position in search results for key target keywords.

4.2 Acquisition & Lead Generation

  • Lead Volume: Number of Marketing Qualified Leads (MQLs) and Sales Qualified Leads (SQLs) generated.
  • Conversion Rates:

* Website Visitor to Lead (e.g., content download, webinar registration).

* Lead to Trial/Demo Request.

* Trial to Paid Conversion Rate.

  • Customer Acquisition Cost (CAC): Total marketing and sales spend divided by the number of new customers acquired.
  • Trial Sign-ups: Number of users initiating a free trial.

4.3 Engagement & Activation

  • Product Usage Metrics: Daily/Monthly Active Users (DAU/MAU), Feature Adoption Rate, Time Spent in App.
  • Time to First Value (TTFV): How quickly users experience the core benefit of the product.
  • Email Open & Click-Through Rates: For nurturing campaigns and product updates.
  • Demo Completion Rate: Percentage of scheduled demos that are completed.

4.4 Revenue & Retention

  • Monthly Recurring Revenue (MRR) / Annual Recurring Revenue (ARR): Total predictable revenue generated from subscriptions.
  • Customer Churn Rate: Percentage of customers who cancel their subscriptions over a period.
  • Revenue Churn Rate: Percentage of MRR lost from cancellations or downgrades.
  • Customer Lifetime Value (CLTV): The average revenue a customer is expected to generate over their relationship with the company.
  • Average Revenue Per User (ARPU): Total MRR divided by the number of customers.
  • Expansion Revenue: Revenue from upsells, cross-sells, and add-ons from existing customers.
  • Net Promoter Score (NPS):
gemini Output

This document outlines a comprehensive, data-driven SaaS pricing strategy designed to optimize revenue, enhance customer acquisition, improve retention, and align with the market's willingness-to-pay. This strategy encompasses a detailed tier design, strategic feature gating, insights from competitive analysis, and a robust migration plan for existing customers.

Executive Summary

This pricing strategy proposes a tiered model for [Your SaaS Product Name], anchored in a value-based approach derived from extensive competitive analysis and willingness-to-pay (WTP) insights. The recommended structure features [Number] distinct tiers – [Tier 1 Name], [Tier 2 Name], and [Tier 3 Name] – each tailored to specific customer segments and their evolving needs. Strategic feature gating ensures a clear upgrade path and maximizes perceived value. A detailed migration plan addresses the transition for existing customers, aiming for minimal disruption and maximum adoption of the new structure. This strategy is designed to drive sustainable growth, increase average revenue per user (ARPU), and strengthen market positioning.

1. Introduction

The objective of this document is to define a robust and dynamic pricing strategy for [Your SaaS Product Name] that supports business growth, maximizes customer lifetime value (LTV), and ensures market competitiveness. This strategy is built upon a foundation of quantitative and qualitative data, addressing key areas such as market positioning, customer segmentation, value perception, and operational feasibility.

2. Current Landscape & Strategic Objectives

2.1. Current Market Context

[Briefly describe the current market for your SaaS: e.g., "The market for [Your SaaS Product Category] is highly competitive, characterized by rapid innovation and evolving customer expectations. Customers are increasingly seeking solutions that offer flexibility, scalability, and demonstrable ROI."]

2.2. Strategic Pricing Objectives

The overarching goals for this pricing strategy are:

  • Maximize Revenue Growth: Optimize pricing to increase ARPU and overall subscription revenue.
  • Enhance Customer Acquisition: Develop tiers that attract new customers across various segments.
  • Improve Customer Retention & LTV: Create clear upgrade paths and value propositions that encourage long-term engagement.
  • Strengthen Competitive Positioning: Differentiate [Your SaaS Product Name] through strategic pricing and value delivery.
  • Align with Customer Value: Ensure pricing reflects the perceived value and willingness-to-pay of target segments.
  • Support Product Roadmap: Allow for future feature additions and expansions without necessitating a complete pricing overhaul.

3. Data-Driven Pricing Philosophy

Our approach to pricing is fundamentally data-driven, integrating insights from:

  • Market Analysis: Understanding macro-economic trends, industry benchmarks, and technological shifts.
  • Competitive Intelligence: Deep dive into competitor pricing, features, and target audiences.
  • Customer Insights: Direct feedback, usage data, and willingness-to-pay analysis.
  • Internal Cost Analysis: Understanding the cost to serve and deliver features (though value-based pricing often de-emphasizes this, it's a critical baseline).

This holistic view ensures that pricing is not arbitrary but strategically aligned with market realities and customer expectations.

4. Competitive Analysis

4.1. Methodology

A comprehensive analysis was conducted on [Number] key competitors within the [Your SaaS Product Category] market. This involved:

  • Public Data Collection: Scrutinizing competitor websites, pricing pages, feature lists, and public reviews.
  • Product Demos/Trials: Engaging with competitor products where possible to understand user experience and feature depth.
  • Market Reports: Reviewing industry analysis and competitor reports.
  • Customer Feedback: Gathering insights on how customers perceive competitor offerings versus [Your SaaS Product Name].

4.2. Key Competitors Identified

| Competitor Name | Primary Target Segment | Core Value Proposition | Pricing Model | Starting Price (Monthly/Annually) | Key Differentiators |

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

| [Competitor A] | Small Businesses | Simplicity, ease-of-use | Tiered (user-based) | \$29/month | Excellent UI, limited advanced features |

| [Competitor B] | Mid-Market, Enterprises | Advanced features, integrations | Tiered (feature/usage-based) | \$99/month | Robust API, extensive reporting |

| [Competitor C] | Freelancers, SMBs | Affordability, essential tools | Freemium, tiered | \$0 (basic), \$15/month | Low entry barrier, strong community |

| [Competitor D] | Large Enterprises | Customization, dedicated support | Custom/Quote-based | N/A | Highly customizable, premium support |

| [Your SaaS Product Name] | [Current Target Segment(s)] | [Current Value Proposition] | [Current Pricing Model] | [Current Price] | [Current Differentiators] |

(Note: Replace placeholder data with actual competitor analysis findings.)

4.3. Key Takeaways from Competitive Analysis

  • Pricing Tiers are Standard: Most competitors utilize a tiered pricing model, indicating market acceptance.
  • Value Metrics Vary: Common value metrics include per-user, per-feature, per-usage (e.g., data storage, transactions), or a combination.
  • Feature Gating is Crucial: Advanced features, integrations, and higher limits are consistently gated behind higher tiers.
  • Differentiation is Key: Competitors often differentiate on either simplicity/affordability or advanced functionality/scalability. [Your SaaS Product Name] has an opportunity to solidify its unique position.
  • Enterprise Segment Opportunity: A clear enterprise-level offering with bespoke pricing is common for larger players.

5. Willingness-to-Pay (WTP) Analysis

5.1. Methodology

The WTP analysis for [Your SaaS Product Name] utilized a combination of methods to ascertain optimal price points and segment-specific price sensitivities:

  • Van Westendorp Price Sensitivity Meter: Conducted via [Survey Platform/Customer Interviews] with [Number] target customers, asking questions like "At what price would you consider this product too expensive?" and "At what price would you consider this product a bargain?".
  • Conjoint Analysis (Optional/If Performed): Presented various feature bundles at different price points to understand which features drive the most value and how price influences choice.
  • Historical Data Analysis: Reviewing past customer acquisition costs, churn rates at different price points (if applicable), and upgrade patterns.
  • Customer Feedback & Interviews: Direct conversations with existing customers and prospects to understand their budget constraints and perceived value of specific features.

5.2. Key Segments & Price Sensitivity

  • Segment 1: [e.g., Small Business Owners/Solopreneurs]

* Characteristics: Price-sensitive, value simplicity and core functionality, limited budget.

* WTP Range: [\$X - \$Y] per month.

* Key Value Drivers: Ease of setup, immediate productivity gains, basic reporting.

  • Segment 2: [e.g., Growing Teams/Mid-Market]

* Characteristics: Seek collaboration tools, integrations, moderate customization. Balance between cost and functionality.

* WTP Range: [\$A - \$B] per month.

* Key Value Drivers: Team management, advanced analytics, API access, priority support.

  • Segment 3: [e.g., Large Enterprises/Power Users]

* Characteristics: Require high scalability, robust security, extensive customization, dedicated support, compliance features. Price is secondary to functionality and reliability.

* WTP Range: [\$P - \$Q] per month (or custom quote).

* Key Value Drivers: Enterprise-grade security, SSO, dedicated account management, custom integrations, white-labeling.

(Note: Replace placeholder data with actual WTP findings.)

5.3. Optimal Price Points & Ranges

Based on the WTP analysis, the following price ranges are identified as having the highest probability of market acceptance and revenue optimization for each target segment:

  • Entry-Level Tier: [\$X - \$Y]
  • Mid-Level Tier: [\$A - \$B]
  • Premium/Enterprise Tier: [\$P - \$Q] (or custom quotes for highest segment)

6. SaaS Tier Design & Feature Gating

6.1. Core Principles for Tier Design

  • Value-Based: Each tier offers increasing value, justifying the higher price point.
  • Segment Alignment: Tiers are designed to cater specifically to the needs and budgets of identified customer segments.
  • Clear Upgrade Path: Customers should easily understand the benefits of moving to a higher tier.
  • Scalability: Tiers should accommodate growth in user count, usage, or complexity.
  • Simplicity: Pricing should be easy to understand and communicate.

6.2. Proposed Tier Structure

Tier 1: [e.g., Starter / Basic]

  • Target Audience: Solopreneurs, small teams, startups, users needing core functionality.
  • Core Value Proposition: Essential tools to get started quickly and efficiently.
  • Key Features (Included):

* [Feature A]

* [Feature B]

* [Feature C]

* Limited [Value Metric, e.g., 100 records, 1GB storage]

* Email support

* [Number] users included

  • Value Metric(s): Primarily user-based with limits on core usage (e.g., number of projects, storage, transactions).
  • Proposed Price Range: [\$X - \$Y] per user per month (or flat rate up to N users).
  • Rationale: Low entry barrier to attract a wide audience, allowing them to experience core value.

Tier 2: [e.g., Professional / Growth]

  • Target Audience: Growing teams, small to medium-sized businesses requiring enhanced collaboration and deeper insights.
  • Core Value Proposition: Advanced features for team productivity, deeper analytics, and integrations.
  • Key Features (Building on Starter + New):

* All features from Starter

* [Feature D] (e.g., Advanced Reporting & Analytics)

* [Feature E] (e.g., Third-Party Integrations - list 2-3 key ones)

* [Feature F] (e.g., Team Collaboration Tools)

* Increased [Value Metric, e.g., 1,000 records, 10GB storage]

* Priority email & chat support

* [Number] users included, with option to add more at [\$Z]/user.

  • Feature Gating Rationale: Features like advanced reporting, integrations, and team collaboration are typically valued by growing teams and represent a significant step up in capability.
  • Value Metric(s): User-based, with higher limits on core usage, and potentially some feature-based gating.
  • Proposed Price Range: [\$A - \$B] per user per month (or flat rate up to N users).
  • Rationale: Addresses the needs of scaling businesses, offering significant value uplift for a higher price point.

Tier 3: [e.g., Enterprise / Premium]

  • Target Audience: Large organizations, businesses with complex needs, high security/compliance requirements, and extensive usage.
  • Core Value Proposition: Maximum scalability, security, customization, and dedicated support.
  • Key Features (Building on Professional + New):

* All features from Professional

* [Feature G] (e.g., Single Sign-On (SSO) & Advanced Security)

* [Feature H] (e.g., Custom Integrations & API Access)

* [Feature I] (e.g., Audit Logs & Compliance Reporting)

* Unlimited [Value Metric, e.g., records, storage] or very high limits.

* Dedicated Account Manager & 24/7 Phone Support

* Onboarding & Training

* Custom number of users.

  • Feature Gating Rationale: These are critical features for large enterprises, often requiring significant development and support resources. They command a premium.
  • Value Metric(s): Often custom-quoted, based on number of users, specific usage parameters, and required support/customization.
  • Proposed Price Range: Custom Quote / [\$P - \$Q] per user per month (for a baseline).
  • Rationale: Caters to the most demanding customers, providing a highly tailored and supported experience.

6.3. Value Metrics & Monetization Drivers

The primary value metric proposed is per-user, as it directly correlates with team size and collaboration needs, which are central to [Your SaaS Product Name]'s value.

Secondary monetization drivers include:

  • Usage-based Limits: On specific resources like data storage, API calls, or processing units.
  • Feature-based Gating: Locking advanced capabilities behind higher tiers.
  • Add-ons: Optional paid features that can be purchased independently (e.g., premium templates, extended data retention).

7. Pricing Model & Strategy Recommendations

7.1. Overall Pricing Strategy: Value-Based Pricing

We recommend a Value-Based Pricing strategy. This approach sets prices primarily on the perceived or estimated value to the customer rather than on the cost of production or historical prices. This aligns with our data-driven approach, leveraging WTP analysis and competitive differentiation to capture maximum value.

7.2. Specific Pricing Model: Tiered Subscription with Hybrid Elements

  • Core Model: Tiered Subscription (as detailed above).
  • Trial Strategy:

* [Option 1: Free Trial]: Offer a [7/14/30]-day free trial of the Professional tier, no credit card required. This allows users to experience significant value and reduces friction for adoption.

[Option 2: Freemium (if applicable)]: A stripped-down, permanently free version for the 'Starter' tier. This can be a powerful acquisition channel but requires careful management to ensure conversion to paid tiers. Recommendation: Start with a free trial of a mid-tier offering to demonstrate value more effectively.*

  • Annual Discounts: Offer a [1
gemini Output

SaaS Pricing Strategy: Comprehensive Deliverable

Date: October 26, 2023

Prepared For: [Client Company Name]

Prepared By: PantheraHive Consulting


1. Executive Summary

This document outlines a data-driven SaaS pricing strategy designed to optimize revenue, enhance customer acquisition, and maximize customer lifetime value (CLTV) for [Client Company Name]'s [Product Name]. Our approach integrates comprehensive competitive analysis, willingness-to-pay (WTP) insights, and strategic feature gating to create a tiered pricing model that caters to diverse customer segments.

The proposed strategy focuses on value-based pricing, ensuring that customers perceive clear benefits commensurate with their investment. Key recommendations include a three-tiered structure (Starter, Professional, Enterprise), a clear feature gating matrix, a strategic upsell/cross-sell framework, and a detailed migration plan for existing customers. This strategy is designed for flexibility, allowing for continuous iteration based on performance metrics and market feedback.

2. Core Pricing Strategy Principles

Our recommended pricing strategy is built upon the following foundational principles:

  • Value-Based Pricing: Price reflects the perceived and actual value delivered to the customer, rather than solely on cost-plus or competitor matching. This ensures alignment with customer ROI.
  • Data-Driven Decisions: Pricing tiers, features, and points are informed by market research, competitive analysis, and willingness-to-pay studies.
  • Segment-Specific Targeting: Tiers are designed to address the distinct needs, budgets, and value perception of different customer segments (e.g., small businesses, growing teams, large enterprises).
  • Scalability & Growth: The pricing model supports customer growth within the platform, encouraging upgrades as their needs evolve, thereby increasing CLTV.
  • Simplicity & Transparency: Pricing should be easy to understand, clearly communicated, and free of hidden costs, fostering trust and reducing sales friction.
  • Flexibility & Iteration: The strategy includes mechanisms for continuous monitoring and adjustment based on market dynamics, customer feedback, and performance metrics.

3. Competitive Analysis Summary

Our analysis of key competitors in the [SaaS Industry] market, including [Competitor A], [Competitor B], and [Competitor C], revealed several critical insights:

  • Common Pricing Metrics: The dominant pricing metric across competitors is [e.g., per user per month, per feature set, per usage unit]. We recommend aligning with this standard where appropriate, or differentiating if a unique value proposition supports it.
  • Tier Structure: Most competitors employ a 3-4 tier model, typically differentiating by scale (number of users, projects, data points) and advanced features.
  • Pricing Ranges:

* Entry-Level: Averaging between $[X] - [Y]$ per month.

* Mid-Tier: Ranging from $[A] - [B]$ per month.

* Enterprise: Custom quotes are common, but often start at $[C]$ per month for a baseline.

  • Feature Gating Trends: Common features gated at higher tiers include advanced analytics, integrations, dedicated support, API access, and increased storage/usage limits.
  • Differentiation Opportunities: Our analysis identified gaps in competitor offerings related to [specific feature/benefit, e.g., real-time collaboration, AI-driven insights, specific integrations] which [Product Name] can leverage to justify premium pricing or attract specific segments.

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

Our WTP analysis, conducted through [e.g., Van Westendorp Price Sensitivity Meter, Gabor-Granger, conjoint analysis] with [target customer segments], provided crucial data points:

  • Price Sensitivity: Customers showed high sensitivity to prices above $[X]$ for the basic offering, but were willing to pay a premium for specific high-value features such as [Feature 1] and [Feature 2].
  • Value Perception: The most highly valued features, where customers indicated a higher WTP, were [e.g., advanced reporting, seamless integrations, dedicated customer support, specific automation capabilities]. These features are ideal candidates for higher-tier gating.
  • Anchor Pricing: A perceived "fair" price for a mid-tier offering was generally around $[Y]$, establishing a mental anchor for customers.
  • Enterprise Budget Expectations: Large enterprises indicated budget allocations for solutions like [Product Name] typically start from $[Z]$ annually, highlighting the potential for significant revenue from this segment.
  • Psychological Pricing: There's a strong preference for prices ending in .99 or .95 for lower tiers, and round numbers for higher-value, enterprise-level solutions.

5. Proposed Pricing Tiers and Structure

Based on our analysis, we recommend a three-tiered pricing model for [Product Name], with a primary pricing metric of per user, per month, complemented by usage-based add-ons where applicable. Annual billing options will offer a [X]% discount to encourage commitment.

5.1. Tier 1: Starter (Target: Small Teams, Startups, Individual Professionals)

  • Target Audience: New users, small teams, and freelancers seeking core functionality to get started. Focus on ease of use and essential tools.
  • Key Value Proposition: Affordable access to fundamental features, quick setup, and immediate productivity gains.
  • Pricing: $[29] - [49] per user/month (Illustrative. Final price to be determined after further validation.)
  • Features Included:

* Basic [Core Feature Category 1] (e.g., up to 5 projects, 10GB storage)

* Standard [Core Feature Category 2] (e.g., basic reporting, email support)

* [Feature A], [Feature B], [Feature C]

* Limited integrations (e.g., 3 standard integrations)

* Community support

  • Upgrade Triggers: Need for more projects/storage, advanced analytics, team collaboration features, or premium support.

5.2. Tier 2: Professional (Target: Growing Teams, SMBs)

  • Target Audience: Growing businesses and teams requiring more robust features, enhanced collaboration, and deeper insights.
  • Key Value Proposition: Comprehensive toolset for team efficiency, advanced analytics, and priority support to scale operations effectively.
  • Pricing: $[79] - [129] per user/month (Illustrative. Final price to be determined after further validation.)
  • Features Included (All Starter features, PLUS):

* Expanded [Core Feature Category 1] (e.g., unlimited projects, 100GB storage)

* Advanced [Core Feature Category 2] (e.g., custom dashboards, real-time analytics)

* [Feature D], [Feature E], [Feature F] (e.g., API access, 2-way integrations)

* Priority email and chat support

* Team collaboration tools (e.g., shared workspaces, role-based permissions)

* Increased integration limits (e.g., 10 integrations)

  • Upgrade Triggers: Need for enterprise-grade security, dedicated account management, single sign-on (SSO), advanced compliance, or custom development.

5.3. Tier 3: Enterprise (Target: Large Organizations, Corporations)

  • Target Audience: Large enterprises with complex needs, requiring extensive customization, high-level security, and dedicated support.
  • Key Value Proposition: Tailored solution with maximum control, security, scalability, and personalized service to meet specific organizational requirements.
  • Pricing: Custom Quote (Starting from $[1000]+$ per month for a baseline package)
  • Features Included (All Professional features, PLUS):

* Unlimited [Core Feature Category 1] & [Core Feature Category 2]

* Dedicated Account Manager

* 24/7 Premium Support (phone, email, chat)

* Single Sign-On (SSO) & SAML integration

* Advanced Security & Compliance (e.g., SOC 2, HIPAA readiness)

* Custom integrations & API development support

* On-premise deployment options (if applicable)

* White-labeling capabilities (if applicable)

* Uptime SLAs

* Advanced audit logs and user management

  • Upgrade Triggers: No direct upgrade path; tailored solutions based on specific needs.

6. Feature Gating Strategy

Our feature gating strategy is designed to drive upgrades by aligning feature availability with increasing customer value and organizational complexity.

  • Core Principle: Essential functionality is available in the Starter tier, while features that unlock significant productivity gains, advanced insights, or require greater infrastructure/support are reserved for higher tiers.
  • Key Gated Features Examples:

* Collaboration: Basic sharing (Starter), real-time collaboration & advanced user roles (Professional), granular permissions & audit trails (Enterprise).

* Analytics & Reporting: Pre-defined reports (Starter), custom dashboards & advanced filters (Professional), AI-driven insights & predictive analytics (Enterprise).

* Integrations: Limited standard integrations (Starter), expanded integrations & API access (Professional), custom integration development support (Enterprise).

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

* Security & Compliance: Standard encryption (Starter), SSO & advanced user management (Professional), Enterprise-grade compliance & security audits (Enterprise).

* Usage Limits: Storage, project counts, API calls, and data processing limits will progressively increase with each tier.

  • Rationale: This strategy ensures that customers experience clear value at each tier, but recognize the benefits of upgrading as their needs grow more sophisticated. It creates a natural progression path and incentivizes higher-tier adoption.

7. Add-ons and Upsell Opportunities

Beyond the core tiers, we recommend exploring strategic add-ons and upsell opportunities to further monetize specific needs:

  • Additional Storage/Usage: For customers who exceed their tier's limits but don't require a full tier upgrade.
  • Premium Integrations: Offer specific, high-demand integrations as a paid add-on (e.g., advanced CRM sync, specialized accounting software integration).
  • On-Demand Training/Consulting: Personalized sessions for onboarding, advanced feature utilization, or strategic guidance.
  • Dedicated IP Addresses: For customers requiring enhanced security or deliverability for specific functions.
  • Usage Overage Protection: A small fee for exceeding certain limits rather than forcing an immediate upgrade.
  • White-Labeling (as an Enterprise Add-on): For partners or large organizations wishing to fully brand the platform.
  • AI/ML Credits: For features that consume significant computational resources, offer credits as a top-up.

8. Migration Plan for Existing Customers

Transitioning existing customers to the new pricing structure requires careful planning and transparent communication to minimize churn and maximize retention.

8.1. Communication Strategy

  • Early Notification: Inform customers at least [60-90 days] in advance of the new pricing launch.
  • Clear Value Proposition: Articulate the benefits of the new tiers, highlighting improved features, better support, and clearer value alignment.
  • Dedicated FAQ & Support: Create a comprehensive FAQ page and train support staff to handle inquiries.
  • Personalized Communication: For larger or long-standing customers, consider direct outreach from account managers.

8.2. Grandfathering & Grace Periods

  • Option 1: Grandfathering (Recommended for churn reduction): Existing customers on legacy plans can remain on their current plan indefinitely, or for a defined period (e.g., 12-24 months), with no price increase, provided they do not upgrade or downgrade. This builds goodwill.
  • Option 2: Grace Period with Incentive: Offer existing customers a [3-6 month] grace period where they can continue on their current plan and pricing. During this period, provide an incentive (e.g., [10-20]% discount for the first year on a new plan, or a free add-on) to migrate to one of the new tiers.
  • Downgrade Policy: Clearly define the process and implications of downgrading (e.g., loss of features, data archiving policies).

8.3. Migration Process

  1. Identify Current Plan Mapping: Map each existing customer's current plan and usage to the most suitable new tier.
  2. Proactive Recommendation: Based on usage data, proactively recommend the best-fit new tier for each customer.
  3. Self-Service Migration Portal: Develop an intuitive in-app portal where customers can review the new plans, compare features, and select their preferred option.
  4. Assisted Migration: Offer guided support for complex migrations or for Enterprise customers.
  5. Data Integrity: Ensure a seamless transition of all customer data and settings during migration.

9. Implementation and Monitoring

Successful execution of this pricing strategy requires a structured launch plan and continuous performance monitoring.

9.1. Key Implementation Steps

  1. Finalize Pricing Points: Conduct A/B testing or further validation with a small segment of customers to fine-tune exact price points.
  2. Update Product & Marketing Materials: Revise website, in-app messaging, sales collateral, and legal terms to reflect the new pricing.
  3. Train Sales & Support Teams: Equip teams with comprehensive knowledge of the new tiers, feature gating, and migration plan.
  4. System Configuration: Implement the new pricing model within billing, CRM, and analytics systems.
  5. Launch & Announce: Execute the communication plan and officially launch the new pricing.

9.2. Key Performance Indicators (KPIs) for Monitoring

  • Average Revenue Per User (ARPU): Track changes over time for each tier.
  • Customer Acquisition Cost (CAC): Monitor if new pricing impacts acquisition efficiency.
  • Customer Lifetime Value (CLTV): Analyze the long-term value generated by customers on new plans.
  • Churn Rate: Closely monitor overall and segment-specific churn, especially during migration.
  • Upgrade/Downgrade Rate: Track movement between tiers to understand customer progression and pain points.
  • Conversion Rates: From free trial to paid, and between different tiers.
  • Feature Adoption Rates: Understand which features are driving value and upgrades.
  • Sales Cycle Length: Assess impact on sales efficiency.
  • Customer Feedback: Actively solicit and analyze feedback regarding pricing and value perception.

9.3. Iteration Strategy

  • Quarterly Review: Conduct a comprehensive review of pricing performance against KPIs every quarter.
  • A/B Testing: Continuously test minor price adjustments, feature placements, and messaging.
  • Market Intelligence: Stay abreast of competitor pricing changes and broader market trends.
  • Customer Interviews: Regularly engage with customers to understand evolving needs and willingness-to-pay.

10. Recommendations and Next Steps

We recommend proceeding with the proposed data-driven, tiered pricing strategy. This approach offers the best balance between maximizing revenue, attracting diverse customer segments, and ensuring long-term scalability.

Immediate Next Steps:

  1. Internal Stakeholder Review: Present this strategy to key internal stakeholders for feedback and alignment.
  2. Pricing Point Validation: Conduct final internal modeling and external validation (e.g., through surveys or targeted interviews) to finalize exact price points for each tier.
  3. Detailed Feature Mapping: Create a definitive, granular list of features for each tier, ensuring clear differentiation and value perception.
  4. Develop Migration Communication Assets: Begin drafting customer communications, FAQ documents, and sales enablement materials.
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);}});}