SaaS Pricing Strategy
Run ID: 69cb4bee61b1021a29a87bb02026-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 SaaS Product Launch/Promotion

This document outlines a comprehensive marketing strategy designed to support the successful launch and ongoing promotion of your SaaS product, integrating closely with the overarching SaaS Pricing Strategy. The aim is to effectively reach your target audience, communicate value, and drive adoption and revenue growth.


1. Target Audience Analysis

Understanding your target audience is paramount to crafting effective marketing messages and selecting appropriate channels. We will define Ideal Customer Profiles (ICPs) and detailed user personas.

1.1 Ideal Customer Profiles (ICPs)

Definition: The type of company that would most benefit from and derive the most value from your SaaS product.

  • Industry: (e.g., B2B SaaS, E-commerce, Healthcare Tech, Fintech, Manufacturing)
  • Company Size: (e.g., SMBs: 10-100 employees, Mid-Market: 101-1,000 employees, Enterprise: 1,000+ employees)
  • Revenue Range: (e.g., $1M - $10M ARR, $10M - $100M ARR)
  • Geographic Location: (e.g., North America, EMEA, Global)
  • Technological Maturity: (e.g., Early adopter, tech-savvy; Traditional, slow to adopt new tech)
  • Pain Points/Challenges: (e.g., Inefficient workflows, high operational costs, poor data visibility, difficulty scaling, compliance issues)
  • Goals/Desired Outcomes: (e.g., Improve efficiency, reduce costs, increase revenue, enhance customer experience, gain competitive advantage)
  • Current Solutions Used: (e.g., Manual processes, spreadsheets, competitor products, legacy systems)

1.2 User Personas

Definition: Fictional representations of your ideal users within the ICP organizations, based on research and data.

For each persona, we will detail:

  • Demographics: Age, Job Title, Department, Years of Experience, Education.
  • Role & Responsibilities: Day-to-day tasks, reporting structure, key performance indicators (KPIs) they are measured against.
  • Goals & Motivations: What they aim to achieve personally and professionally.
  • Pain Points & Frustrations: Specific challenges related to their role that your product can solve.
  • Technology Comfort Level: How open they are to new software, preferred tools.
  • Information Sources: Where do they get their industry news, research solutions (e.g., industry blogs, specific forums, LinkedIn, peers)?
  • Decision-Making Influence: How much influence do they have on purchasing decisions for solutions like yours? (e.g., user, influencer, budget holder, approver).
  • Objections to New Software: Common hesitations or concerns they might have (e.g., cost, implementation time, learning curve, data security).

Example Personas (Illustrative):

  • Persona 1: "The Efficiency Seeker" (e.g., Operations Manager)

Pain Points:* Manual data entry, disparate systems, lack of real-time insights.

Goals:* Streamline processes, reduce errors, improve team productivity.

  • Persona 2: "The Strategic Leader" (e.g., Head of Product/VP of Sales)

Pain Points:* Difficulty scaling, lack of actionable data for strategic decisions, high customer churn.

Goals:* Drive revenue growth, enhance customer satisfaction, improve competitive positioning.

  • Persona 3: "The Budget Holder" (e.g., CFO/CEO)

Pain Points:* High operational costs, unclear ROI of current tech stack, slow time-to-value.

Goals:* Cost optimization, measurable ROI, long-term business growth.


2. Channel Recommendations

A multi-channel approach is crucial for reaching diverse personas and guiding them through the buyer's journey. Channels will be prioritized based on audience analysis and budget.

2.1 Inbound Marketing Channels

  • Content Marketing (Blog, Whitepapers, Ebooks, Case Studies):

* Purpose: Attract organic traffic, educate prospects, establish thought leadership, nurture leads.

* Content Types: Blog posts addressing pain points, how-to guides, industry trends, data-driven reports, success stories, comparative analyses.

* Actionable: Develop a content calendar mapped to buyer journey stages and persona interests. Optimize for relevant long-tail keywords.

  • Search Engine Optimization (SEO):

* Purpose: Increase organic visibility for relevant search queries.

* Actionable: Conduct comprehensive keyword research (informational, commercial intent). Optimize website structure, on-page content, technical SEO, and build high-quality backlinks.

  • Social Media Marketing (Organic):

* Purpose: Build community, engage with prospects, share content, establish brand voice.

* Key Platforms: LinkedIn (B2B focus, professional networking, thought leadership), Twitter (real-time updates, industry conversations), potentially Facebook/Instagram (if relevant for specific B2B niches or employer branding).

* Actionable: Create a consistent posting schedule, engage with comments and messages, share valuable industry insights, promote blog content and webinars.

  • Email Marketing:

* Purpose: Nurture leads, announce new features, share product updates, drive conversions, build customer loyalty.

* Actionable: Develop segmented email lists (e.g., prospects, free trial users, paying customers). Implement automated drip campaigns for onboarding, lead nurturing, and re-engagement.

  • Webinars & Virtual Events:

* Purpose: Generate high-quality leads, educate prospects on product value, demonstrate expertise.

* Actionable: Host webinars on industry challenges, product deep-dives, customer success stories. Partner with industry influencers or complementary businesses.

2.2 Outbound & Paid Marketing Channels

  • Paid Search (SEM - Google Ads, Bing Ads):

* Purpose: Capture high-intent users actively searching for solutions.

* Actionable: Target keywords related to your product, pain points, and competitor names. Develop compelling ad copy and optimize landing pages for conversions (e.g., demo request, free trial sign-up).

  • Paid Social Media Ads (LinkedIn Ads, Facebook/Instagram Ads):

* Purpose: Target specific demographics, job titles, interests, and company firmographics.

* Actionable: Create highly segmented campaigns. Utilize retargeting to re-engage website visitors or non-converting leads. Leverage video ads for product demos or testimonials.

  • Display Advertising & Programmatic Ads:

* Purpose: Increase brand awareness, drive traffic to content, retarget prospects across the web.

* Actionable: Use high-quality visual creatives. Target relevant websites and audiences based on interests and behavior.

  • Review Platforms (G2, Capterra, TrustRadius):

* Purpose: Build trust and social proof, influence purchase decisions.

* Actionable: Actively encourage satisfied customers to leave reviews. Monitor and respond to all reviews (positive and negative).

  • Affiliate & Partner Marketing:

* Purpose: Leverage existing networks to reach new audiences and drive referrals.

* Actionable: Identify potential partners (e.g., complementary software providers, consultants, industry associations). Develop clear partnership agreements and commission structures.

  • Public Relations (PR):

* Purpose: Build brand credibility, secure media coverage, establish thought leadership.

* Actionable: Develop compelling press releases for product launches, funding rounds, significant milestones. Pitch relevant journalists and industry publications.


3. Messaging Framework

A consistent and compelling messaging framework ensures all marketing efforts communicate a unified value proposition.

3.1 Core Value Proposition

Template: "We help [Target Audience] to [Solve Problem] by [Unique Solution] resulting in [Key Benefit]."

Example: "We help mid-market SaaS companies to reduce customer churn and increase LTV by providing an AI-powered customer success platform that offers proactive risk identification and personalized engagement automation, resulting in improved customer retention and accelerated recurring revenue growth."

3.2 Key Benefits (tied to Pain Points)

Translate features into tangible benefits for each persona.

  • For "The Efficiency Seeker": "Eliminate manual data entry and consolidate disparate tools, saving X hours per week and reducing operational errors by Y%."
  • For "The Strategic Leader": "Gain real-time, actionable insights into customer health and predict churn risk, enabling proactive interventions to safeguard revenue and inform strategic product development."
  • For "The Budget Holder": "Achieve a clear ROI within Z months by reducing customer acquisition costs through improved retention and optimizing resource allocation with data-driven insights."

3.3 Unique Selling Points (USPs)

What makes your product distinct and superior to competitors?

  • (e.g., Patented AI algorithm for predictive analytics, seamless integration with X and Y platforms, industry-leading uptime guarantee, 24/7 dedicated support, specific compliance certifications).

3.4 Tone of Voice

  • (e.g., Professional, innovative, empathetic, data-driven, approachable, confident, visionary). Maintain consistency across all channels.

3.5 Messaging by Buyer Journey Stage

  • Awareness Stage: Focus on pain points, industry trends, educational content. (e.g., Blog posts: "5 Ways Inefficient Workflows are Hurting Your Bottom Line").
  • Consideration Stage: Focus on solutions, product capabilities, competitive advantages, case studies. (e.g., Whitepaper: "A Guide to Selecting the Right Customer Success Platform").
  • Decision Stage: Focus on pricing, implementation, demos, testimonials, ROI. (e.g., "Request a Demo," "Start Your Free Trial," "Compare Our Tiers").

3.6 Calls to Action (CTAs)

Clear, concise, and compelling CTAs tailored to the context and stage of the buyer's journey.

  • Awareness: "Read More," "Download the Report," "Learn More."
  • Consideration: "Watch Demo," "Get a Free Trial," "Explore Features," "Contact Sales."
  • Decision: "Start Your Subscription," "Request a Quote," "Schedule a Consultation."

4. Key Performance Indicators (KPIs)

Defining and tracking KPIs is essential for measuring marketing effectiveness and optimizing strategies.

4.1 Awareness Metrics

  • Website Traffic: Unique visitors, page views, traffic sources (organic, paid, referral).
  • Social Media Reach & Impressions: Number of unique users who saw your content, total times content was displayed.
  • Brand Mentions: Number of times your brand is mentioned across the web.

4.2 Acquisition Metrics

  • Lead Volume: Number of new leads generated (MQLs - Marketing Qualified Leads, SQLs - Sales Qualified Leads).
  • Conversion Rates:

* Website Visitor to Lead Conversion Rate.

* Lead to MQL Conversion Rate.

* MQL to SQL Conversion Rate.

* Free Trial Sign-ups.

* Demo Requests.

  • Customer Acquisition Cost (CAC): Total marketing and sales expenses / Number of new customers.
  • Cost Per Lead (CPL): Total marketing spend / Number of leads generated.

4.3 Activation & Engagement Metrics

  • Free Trial Activation Rate: Percentage of free trial users who complete key onboarding steps or use core features.
  • Feature Adoption Rate: Percentage of active users utilizing specific key features.
  • Engagement Rate: Time spent on platform, frequency of login.

4.4 Revenue Metrics

  • Monthly Recurring Revenue (MRR) / Annual Recurring Revenue (ARR): Total predictable revenue.
  • Average Revenue Per User (ARPU): Total revenue / Number of users.
  • Customer Lifetime Value (LTV): Average revenue a customer generates over their lifespan.
  • LTV:CAC Ratio: Critical indicator of business health.
  • Sales Cycle Length: Time from first contact to closed-won.

4.5 Retention & Advocacy Metrics

  • Customer Churn Rate: Percentage of customers who cancel their subscription.
  • Net Promoter Score (NPS): Measures customer loyalty and willingness to recommend.
  • Referral Rate: Number of new customers acquired through referrals.

5. Integration with Pricing Strategy (Overview)

The marketing strategy will be meticulously aligned with the defined SaaS pricing strategy (tier design, feature gating, etc.).

  • Value Communication: Marketing messages will clearly articulate the value proposition of each pricing tier, justifying the cost based on features, support, and expected ROI.
  • Feature Gating Explanation: Messaging will explain why certain features are gated to higher tiers, focusing on the advanced benefits and target personas for those tiers.
  • Migration Path Promotion: If applicable, marketing will communicate upgrade paths and the value of moving to higher tiers, potentially with targeted campaigns.
  • Competitive Positioning: Marketing will highlight how your pricing and value compare favorably to competitors, addressing potential objections upfront.

This comprehensive marketing strategy provides a robust framework for driving awareness, acquiring customers, and supporting the growth of your SaaS product in alignment with your pricing model. Regular monitoring of KPIs and agile adjustments will be crucial for sustained success.

gemini Output

SaaS Pricing Strategy Document

Date: October 26, 2023

Prepared For: [Client Name/Organization]

Prepared By: PantheraHive


1. Executive Summary

This document outlines a comprehensive, data-driven pricing strategy designed to optimize revenue, enhance customer acquisition, and improve long-term customer value for [Your SaaS Product Name]. The strategy is built upon a thorough analysis of market dynamics, competitive landscapes, customer willingness-to-pay, and internal cost structures.

Key recommendations include:

  • A value-based pricing model with clearly differentiated tiers.
  • Strategic feature gating to encourage upgrades and capture diverse customer segments.
  • Competitive positioning that leverages our unique value proposition.
  • A phased migration plan to ensure a smooth transition for existing customers.

The proposed strategy aims to align product value with pricing, ensuring sustainable growth and market leadership.

2. Introduction and Strategic Objectives

The objective of this document is to define a robust SaaS pricing strategy that supports [Your SaaS Product Name]'s business goals, including:

  • Maximize Revenue & Profitability: Optimize pricing to capture maximum value from each customer segment.
  • Enhance Customer Acquisition: Offer compelling entry points and clear value propositions.
  • Improve Customer Retention & LTV: Foster clear upgrade paths and align pricing with evolving customer needs.
  • Strengthen Market Position: Differentiate from competitors and communicate superior value.
  • Support Product Growth: Enable future feature development and market expansion.

Our approach is rooted in data, combining quantitative analysis with qualitative insights to create a strategy that is both financially sound and market-responsive.

3. Data-Driven Pricing Framework

Our pricing strategy is founded on a multi-faceted, data-driven framework, prioritizing Value-Based Pricing while cross-referencing with competitive benchmarks and cost considerations.

  1. Value-Based Pricing: This is the primary driver, focusing on the perceived and realized value our product delivers to customers. This requires a deep understanding of customer pain points, the benefits our solution provides, and the quantifiable ROI for different segments.
  2. Competitive Pricing: Analysis of competitor pricing models, feature sets, and market positioning helps us identify opportunities for differentiation and ensure our pricing is competitive yet premium where justified.
  3. Cost-Plus Pricing (as a Floor): While not the primary driver, understanding our Customer Acquisition Cost (CAC), Cost of Goods Sold (COGS), and operational expenses sets a minimum price floor to ensure profitability and sustainable operations.
  4. Willingness-to-Pay (WTP) Analysis: Direct customer insights inform the acceptable price range and sensitivity for various features and value propositions.

4. Competitive Analysis

A comprehensive analysis of key competitors' pricing models, feature sets, and target markets was conducted.

4.1. Key Competitors Identified:

  • [Competitor A]: Known for [specific characteristic, e.g., enterprise focus, basic features, low cost].
  • [Competitor B]: Strong in [specific characteristic, e.g., niche market, advanced analytics, premium pricing].
  • [Competitor C]: Offers [specific characteristic, e.g., freemium model, extensive integrations, mid-market focus].

4.2. Pricing Model Comparison:

| Competitor | Pricing Model | Entry Price (Monthly) | Key Differentiators | Gaps/Opportunities |

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

| Competitor A | Per-user + Storage | $15/user | Basic functionality, strong brand recognition | Lacks advanced reporting, poor scalability. |

| Competitor B | Tiered (feature-based) | $49/month (Pro) | Niche-specific features, excellent support | High entry barrier, limited integrations. |

| Competitor C | Freemium + Tiered | Free / $29/month | Broad feature set, extensive integrations | Complex pricing, support issues at scale. |

| [Your Product] | Proposed below | [To be defined] | [Your Unique Value Proposition] | [Our identified advantages] |

4.3. Key Findings & Strategic Implications:

  • Market Gaps: Identified unmet needs in [specific market segment, e.g., mid-market for comprehensive automation, small businesses needing enterprise-grade security].
  • Pricing Anchors: Competitors have established certain price points that customers expect for specific feature sets. Our pricing should be mindful of these anchors while justifying any deviations with superior value.
  • Differentiation Opportunities: Our [specific unique feature/benefit, e.g., AI-driven insights, unparalleled ease-of-use, superior integration capabilities] provides a strong basis for premium pricing in certain tiers.
  • Commoditization Risk: Basic features are becoming commoditized. Our strategy must focus on gating advanced, high-value features effectively.

5. Willingness-to-Pay (WTP) Analysis

To understand customer price sensitivity and perceived value, a WTP analysis was conducted using a combination of techniques:

5.1. Methodology:

  • Customer Surveys: Administered surveys (e.g., Van Westendorp's Price Sensitivity Meter, Gabor-Granger) to a representative sample of target customers to identify acceptable price ranges, too cheap/expensive points, and optimal price points.
  • Customer Interviews: Conducted in-depth interviews with existing and prospective customers to understand their budget constraints, perceived value of specific features, and ROI expectations.
  • Feature Prioritization: Asked customers to rank features by importance and indicate how much more they would pay for specific premium features.
  • Historical Data Analysis: Analyzed past pricing experiments, trial conversion rates, and churn data to infer price sensitivity.

5.2. Key Findings:

  • Segmented WTP:

* Small Businesses/Startups: Highly price-sensitive, seeking core functionality at an affordable entry point (e.g., $15-$30/month). Value simplicity and ease of use.

* Mid-Market Businesses: Willing to pay more for advanced features, integrations, and dedicated support (e.g., $50-$150/month per user/organization). Value efficiency and scalability.

* Enterprise Clients: Less price-sensitive, prioritize security, compliance, custom integrations, dedicated account management, and robust performance (e.g., $200+/month per user or custom pricing). Value reliability and strategic partnership.

  • Feature Value: Features related to [e.g., automation, advanced analytics, security, collaboration] consistently showed higher WTP. Features perceived as "table stakes" (e.g., basic reporting, user management) have low incremental WTP.
  • Pricing Model Preference: A tiered, feature-based model with a clear "per-user" or "per-seat" component for core functionality, and potential "usage-based" add-ons for specific high-cost resources (e.g., API calls, storage), resonated best.
  • Discounting: Annual billing discounts (10-20%) are highly appealing across all segments.

6. Proposed Tier Design and Feature Gating Strategy

Our proposed pricing structure consists of three core tiers, designed to cater to distinct customer segments, with clear value differentiation and logical upgrade paths.

6.1. Guiding Principles for Tier Design:

  • Simplicity: Easy for customers to understand and choose the right plan.
  • Value Alignment: Each tier offers compelling value for its price point.
  • Scalability: Plans grow with the customer's needs, encouraging upgrades.
  • Differentiation: Clear distinctions between tiers based on features, limits, and support.
  • Avoid Over-Gating: Ensure entry-level plans are still valuable and usable.

6.2. Proposed Tier Structure:


Tier 1: Basic / Starter

  • Target Audience: Small businesses, startups, individuals requiring core functionality.
  • Value Proposition: Affordable entry point to leverage essential features and get started quickly.
  • Pricing Model: Per-user, monthly or annual.
  • Example Price Point: $19/user/month (or $199/user/year)

Feature Gating:

  • Core Features:

* Basic User Management (up to 5 users)

* Standard Dashboards & Reporting

* [Feature A]: Basic functionality

* [Feature B]: Limited functionality

* Standard Integrations (e.g., [App 1], [App 2])

* Limited Data Storage (e.g., 5GB)

  • Usage Limits:

* [Usage Metric 1]: Up to X units/month

* [Usage Metric 2]: Up to Y units/month

  • Support: Email support (24-48 hr response time)
  • SLAs: Standard (non-guaranteed)

Tier 2: Professional / Growth

  • Target Audience: Growing businesses, teams needing advanced capabilities, automation, and better support.
  • Value Proposition: Comprehensive tools for increased productivity, collaboration, and deeper insights.
  • Pricing Model: Per-user, monthly or annual.
  • Example Price Point: $49/user/month (or $499/user/year)

Feature Gating:

  • Includes all Basic features, PLUS:

* Advanced User Management (unlimited users)

* Customizable Dashboards & Advanced Reporting

* [Feature A]: Full functionality (e.g., AI-powered suggestions)

* [Feature B]: Enhanced functionality (e.g., advanced automation rules)

* Premium Integrations (e.g., [App 3], [App 4])

* Increased Data Storage (e.g., 50GB)

* Role-Based Access Control (RBAC)

* API Access (limited calls)

  • Usage Limits:

[Usage Metric 1]: Up to X5 units/month

[Usage Metric 2]: Up to Y5 units/month

  • Support: Priority Email & Chat support (within 12-24 hrs)
  • SLAs: 99.5% Uptime Guarantee

Tier 3: Enterprise / Custom

  • Target Audience: Large organizations, enterprises with complex needs, compliance requirements, and high scalability demands.
  • Value Proposition: Tailored solution with maximum performance, security, dedicated support, and custom integrations.
  • Pricing Model: Custom Quote (negotiated based on users, usage, and specific requirements).
  • Example Price Point: Starting from $199/user/month (or custom annual contracts)

Feature Gating:

  • Includes all Professional features, PLUS:

* Single Sign-On (SSO) & SAML integration

* Audit Logs & Advanced Security Features

* Dedicated Account Manager

* Onboarding & Training Services

* Custom Integrations & API Access (high volume)

* Unlimited Data Storage

* Advanced Compliance Features (e.g., GDPR, HIPAA readiness)

* Dedicated Infrastructure Options

* Uptime SLAs (99.9%+)

  • Usage Limits: Fully customizable, often based on negotiated terms.
  • Support: 24/7 Phone, Email & Chat support, dedicated Slack channel, guaranteed response times.
  • SLAs: Premium (e.g., 99.9% Uptime, specific response/resolution times)

6.3. Add-on Modules (Optional):

To provide flexibility and capture additional value, consider offering specific high-value features as optional add-ons, regardless of the base tier:

  • Advanced Analytics Suite: (e.g., $X/month)
  • Dedicated IP Address: (e.g., $Y/month)
  • Premium Consulting Hours: (e.g., $Z/hour)

7. Migration Plan for Existing Customers

A well-communicated and fair migration plan is crucial to retain existing customers and minimize churn during a pricing change.

7.1. Communication Strategy:

  • Transparency: Clearly communicate the reasons for the change (e.g., enhanced features, improved service, market alignment).
  • Value Focus: Highlight the benefits and new value customers will receive.
  • Multiple Channels: Email campaigns, in-app notifications, dedicated landing page/FAQ, direct outreach for key accounts.
  • Timeline: Announce changes well in advance (e.g., 60-90 days notice).

7.2. Grandfathering Policy:

  • Option 1 (Recommended for goodwill): Allow existing customers to remain on their current plan and pricing for a defined period (e.g., 12-24 months) or indefinitely, unless they upgrade or exceed current usage limits significantly.

* Pros: High customer satisfaction, reduced churn.

* Cons: Slower revenue realization from existing base.

  • Option 2 (Phased Transition): Offer existing customers a discounted rate on a new comparable plan for a limited time (e.g., 6-12 months) before transitioning to the new standard pricing.

* Pros: Faster revenue growth, encourages adoption of new plans.

* Cons: Potential for higher churn if not managed carefully.

7.3. Upgrade Incentives:

  • Offer a one-time discount (e.g., 20% off for the first 3 months) for existing customers who voluntarily upgrade to a higher tier within a specific timeframe.
  • Provide free access to a premium add-on for customers who switch to an annual plan.

7.4. Downgrade Policy:

  • Clearly define the process and implications of downgrading (e.g., loss of features, data limits).
  • Ensure data integrity and provide clear instructions for data export if needed.

7.5. Phased Rollout:

  • Consider a pilot program with a small segment of new customers to test the new pricing and gather feedback before a full public launch.
  • Internally, ensure sales, marketing, and support teams are fully trained and equipped to answer questions.

7.6. Customer Support & FAQ:

  • Develop a comprehensive internal and external FAQ document.
  • Train customer support teams thoroughly on new pricing, tiers, and migration policies.
  • Establish clear escalation paths for complex customer queries.

8. Key Performance Indicators (KPIs) & Monitoring

The success of the new pricing strategy will be measured and continuously monitored using the following KPIs:

  • **Average Revenue Per User (ARPU
gemini Output

SaaS Pricing Strategy: Data-Driven Proposal

Executive Summary:

This document outlines a comprehensive, data-driven SaaS pricing strategy designed to optimize revenue, enhance customer value, and strengthen market positioning. Based on thorough competitive analysis, willingness-to-pay (WTP) insights, and a focus on tiered value delivery, this strategy proposes a clear pricing structure, intelligent feature gating, and a thoughtful migration plan for existing customers. The goal is to maximize customer lifetime value (CLTV) while ensuring market competitiveness and sustainable growth.


1. Introduction & Objectives

The primary objective of this pricing strategy is to establish a robust, scalable, and customer-centric pricing model that supports our business goals, including:

  • Revenue Optimization: Maximize average revenue per user (ARPU) and total revenue.
  • Market Penetration & Expansion: Attract new customers across various segments and facilitate upsells.
  • Value Alignment: Ensure pricing reflects the perceived value delivered to different customer segments.
  • Competitive Advantage: Position our offering favorably against key competitors.
  • Scalability: Design a pricing model that can adapt to product evolution and market changes.

This strategy is built upon a foundation of data analysis, ensuring decisions are informed by market realities and customer insights.

2. Foundational Principles of Our Pricing Strategy

Our pricing strategy is anchored on the following core principles:

  • Value-Based Pricing: Tiers and features are priced according to the value they deliver to specific customer segments, rather than solely on cost-plus models.
  • Transparency & Simplicity: Pricing should be easy for customers to understand, minimizing friction in the buying process.
  • Flexibility & Scalability: The model allows for growth (upselling) as customer needs evolve and accommodates different business sizes.
  • Data-Driven Iteration: Pricing is not static; it will be continuously monitored and refined based on performance data and market feedback.

3. Competitive Landscape Analysis

A detailed analysis of the competitive landscape has informed our strategic positioning and pricing decisions.

  • Key Competitors Identified: [List specific competitors, e.g., Competitor A, Competitor B, Competitor C]
  • Pricing Models Observed:

* Competitor A: Primarily per-user pricing with feature-based tiers. Offers a limited free trial. Strongest in [specific niche].

* Competitor B: Usage-based pricing (e.g., per API call, per storage unit) with an enterprise-level custom quote. Targets larger organizations.

* Competitor C: Freemium model with significant limitations on the free tier, driving upgrades to paid tiers. Focuses on SMBs.

  • Strategic Positioning:

* Our proposed strategy aims to position our product as a premium value offering in the [specific market segment, e.g., mid-market and growing enterprises] by delivering superior features and support at a competitive price point, while also providing an accessible entry point for smaller businesses.

* We differentiate ourselves through [mention 1-2 key differentiators, e.g., advanced AI capabilities, unparalleled integration ecosystem, dedicated customer success].

  • Pricing Gaps & Opportunities:

* Identified an opportunity to capture a segment underserved by competitors' rigid per-user models by offering [e.g., a more flexible usage-based component within tiers, or more generous user allowances].

* Noted a lack of comprehensive reporting/analytics features in competitor's mid-tiers, presenting an opportunity for us to gate these features strategically.

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

Through a combination of surveys, conjoint analysis, and customer interviews, we have gained critical insights into customer perception of value and their willingness to pay.

  • Methodology: [Briefly mention methods used, e.g., Van Westendorp Price Sensitivity Meter, Gabor-Granger, Conjoint Analysis performed on key features].
  • Key Segments & Their WTP:

* Small Businesses/Startups (1-10 users): Highly price-sensitive, strong WTP for core functionality, ease of use, and basic support. WTP range: $X - $Y/month.

* Growing Teams/Mid-Market (11-50 users): Value collaboration features, integrations, advanced analytics, and priority support. WTP range: $Y - $Z/month.

* Enterprise (50+ users): Demand robust security, custom integrations, dedicated account management, advanced reporting, and SLA guarantees. WTP range: $Z+/month (often custom).

  • Feature Value Perception:

* High Value Features (WTP driver): [List 3-5 features, e.g., Real-time collaboration, AI-powered automation, Advanced analytics dashboard, API access, Single Sign-On (SSO)]. Customers are willing to pay a premium for these.

* Expected/Table Stakes Features: [List 2-3 features, e.g., Basic user management, Standard integrations, Email support]. These are expected in all paid tiers and do not significantly drive WTP for higher tiers.

  • Price Sensitivity:

* Significant price sensitivity was observed for the entry-level paid tier, suggesting the need for a compelling value proposition at a competitive price point to encourage conversion from free trials.

* Less price sensitivity was observed for premium, enterprise-grade features, indicating a strong opportunity for higher-tier monetization.

5. Proposed Pricing Tiers & Structure

Our proposed pricing strategy features four distinct tiers, designed to cater to varying customer needs and budgets, while facilitating a clear upgrade path.

Primary Pricing Metric: Per User, Per Month (PUPM) for core access, with additional usage-based components or feature-gated add-ons for specific functionalities.

Proposed Tiers:

  1. Free (Optional / Limited Trial):

* Target Audience: Individuals, very small teams, prospects evaluating the product.

* Pricing: Free forever or a time-limited/feature-limited trial (e.g., 14-day full access).

* Value Proposition: Risk-free exploration, basic functionality to demonstrate core value.

* Limitations: Restricted user count (e.g., 1 user), limited features, basic storage, community support only. Designed to convert to "Basic."

  1. Basic (Formerly "Starter"):

* Target Audience: Small teams, startups, individuals needing more than free but not advanced features.

* Pricing: $19 PUPM (billed annually at $199/user/year). Minimum 3 users recommended.

* Value Proposition: Essential toolkit for collaboration and productivity.

* Key Features: [List 5-7 core features, e.g., Core platform access, Standard integrations (up to 3), 10GB storage per user, Email support, Basic reporting].

* Metrics: Per user, per month.

  1. Pro (Formerly "Business"):

* Target Audience: Growing teams, mid-sized businesses, departments needing advanced capabilities.

* Pricing: $49 PUPM (billed annually at $499/user/year).

* Value Proposition: Enhanced collaboration, deeper insights, and professional support.

* Key Features: All Basic features PLUS: [List 5-7 differentiating features, e.g., Advanced analytics dashboard, API access, Priority email & chat support, Unlimited integrations, 50GB storage per user, Custom branding, User roles & permissions, Single Sign-On (SSO)].

* Metrics: Per user, per month.

  1. Enterprise (Custom):

* Target Audience: Large organizations, enterprises with complex needs, specific security/compliance requirements.

* Pricing: Custom Quote.

* Value Proposition: Tailored solution, dedicated support, and robust enterprise-grade features.

* Key Features: All Pro features PLUS: [List 5-7 premium features, e.g., Dedicated account manager, Onboarding & training, Custom integrations, Advanced security & compliance (HIPAA, SOC2), Uptime SLA, Audit logs, Data residency options, White-glove support, On-premise deployment options (if applicable)].

* Metrics: Negotiated based on users, usage, and specific requirements.

Add-ons / Optional Modules:

To provide flexibility and capture additional value, consider offering specific features as add-ons, regardless of tier (or from Pro tier upwards):

  • Premium AI Assistant Credits: $X per 1000 credits
  • Advanced Data Archiving: $Y per TB/month
  • Dedicated IP Address: $Z per month

6. Feature Gating Strategy

Feature gating is critical to differentiate tiers and encourage upgrades by aligning specific functionalities with the value customers are willing to pay for.

  • Free Tier Limitations:

* Users: Max 1 user.

* Storage: Limited (e.g., 1GB total).

* Features: Core document creation/editing, basic sharing.

* Support: Community forum only.

* Reporting: No reporting.

* Integrations: No integrations.

  • Basic Tier (Entry-Level Paid):

* Users: Up to 10 users (recommended minimum 3).

* Storage: 10GB per user.

* Features: Full core platform access, Standard integrations (limited to 3), Version history (limited to 30 days).

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

* Reporting: Basic usage reports.

  • Pro Tier (Mid-Market / Growth):

* Users: Unlimited users.

* Storage: 50GB per user.

* Features: All Basic features + API access, Advanced analytics dashboard, Unlimited standard integrations, Custom branding, User roles & permissions, SSO, Version history (unlimited).

* Support: Priority email & chat support (4-8 hr response).

* Reporting: Advanced customizable reports.

  • Enterprise Tier (Premium / Custom):

* Users: Unlimited.

* Storage: Negotiable / Unlimited.

* Features: All Pro features + Dedicated Account Manager, White-glove Onboarding, Custom integrations, Advanced security & compliance, Audit logs, SLA guarantees, Data residency options.

* Support: Dedicated support channel, 24/7 phone support.

* Reporting: Custom reporting dashboards.

7. Implementation & Rollout Plan

A phased approach is recommended for a smooth transition and minimal disruption.

  • Phase 1: Internal Alignment & Preparation (Weeks 1-4)

* Finalize pricing model and tier details.

* Update internal systems (CRM, billing, product entitlement).

* Train sales, marketing, and support teams on new pricing, value propositions, and FAQs.

* Develop internal and external communication materials.

  • Phase 2: Soft Launch / Beta (Weeks 5-8 - Optional but Recommended)

* Introduce new pricing to a small segment of new sign-ups or existing customers willing to participate in a beta.

* Gather feedback and iterate on messaging/pricing.

  • Phase 3: Public Launch (Week 9 onwards)

* Announce new pricing to the market via blog posts, press releases, website updates, and direct customer communication.

* Launch new marketing campaigns aligned with the new pricing and value propositions.

* Monitor key metrics closely.

8. Customer Migration Strategy

A clear and fair migration plan is crucial for retaining existing customers and ensuring a positive experience.

  • Existing Customer Tier Mapping:

* Current "Basic" customers: Will be mapped to the new "Basic" tier.

* Current "Pro" customers: Will be mapped to the new "Pro" tier.

* Current "Enterprise" customers: Will remain on custom agreements, with renewal discussions aligning with new Enterprise tier value.

  • Grandfathering Policy:

* Existing customers on legacy plans will retain their current pricing for a period of 12 months from the launch date, or until their next renewal, whichever comes first. This provides stability and goodwill.

* Upon renewal, they will be transitioned to the new pricing structure, with a clear explanation of the added value and features they will receive.

* Consider offering a one-time special discount (e.g., 10-15% off the new annual price) for existing customers who proactively upgrade to the new structure within the first 3 months of launch.

  • Upgrade/Downgrade Paths:

* Upgrades: Customers can upgrade at any time. Prorated billing will apply, with the new tier's features becoming immediately available.

* Downgrades: Customers can downgrade at their next billing cycle. Features of the higher tier will cease at the end of the current billing period.

  • Communication Plan for Existing Customers:

* Personalized Email: A clear and concise email explaining the new pricing, the benefits of the new tiers, and the grandfathering policy.

* In-App Notification: A prominent in-app banner or message directing users to the pricing update announcement.

* Dedicated FAQ Page: A comprehensive FAQ section on the website addressing common concerns about the new pricing and migration.

* Webinar/Live Q&A: Host a webinar to walk customers through the changes and answer questions live.

* Account Manager Outreach: For larger accounts, direct outreach from their account manager to discuss the changes and address specific concerns.

9. Monitoring & Iteration

Pricing is an ongoing process. Continuous monitoring and iteration are essential for long-term success.

  • Key Performance Indicators (KPIs):

* Conversion Rates: Free-to-paid, trial-to-paid, tier-to-tier upgrades.

* Churn Rate: Per tier.

* ARPU (Average Revenue Per User) / ARPA (Average Revenue Per Account).

* Customer Lifetime Value (CLTV).

* Feature Adoption Rates: Especially for newly gated or premium features.

* Sales Cycle Length & Win Rate.

* Customer Feedback: Direct feedback on pricing perception.

  • Regular Review Cycle: Conduct quarterly reviews of pricing performance against KPIs.
  • A/B Testing Opportunities:

* Test different pricing points for entry-level tiers.

* Experiment with different feature bundles within tiers.

* Evaluate the impact of different messaging around value proposition.

* Test different trial lengths or limitations.

10. Recommendations & Next Steps

Based on this detailed proposal, we recommend the following immediate actions:

  1. Internal Stakeholder Review: Present this strategy to key internal stakeholders (Product, Sales, Marketing, Finance, Leadership) for feedback and final approval.
  2. System Preparation: Initiate development work to update billing systems, product entitlement logic, and CRM to support the new pricing model.
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);}});}