SaaS Mode

SECURITY RISK - Your own staff can steal your snapshots and go into business themselves, or sell it for $97
Here's what happened. I upgraded to SaaS because GHL pushes it so much. Cool. Until almost immediately, i hired someone off Upwork to help me out, and he started asking a bunch of questions about what the other staff and i had created. Then i looked on his upwork screen capture (thank god) and realized that he was chatting with other people about how much the logic that i had spent $10,000 in labor fees to my staff to create would be worth. His plan was to slowly get upgraded to Agency User, which allows him to export the snapshot. This software operates like a cheap wordpress theme. There is nothing safe about it from a stability standpoint for a business. FIX: Only the owner should be able to export snapshots. SECURITY ISSUE #2. Did you know that if you don't want your agency sub account users, your SaaS clients, to steal the logic, you should turn off access to workflows? Makes sense. There's NO other software i can think of that gives the regular user access to the logic. Can you go in the back of Evernote and change it for yourself? Bucket? Facebook? No. But did you know that if that agency-admin that has workflows turned off adds a staff member, they can give their staff MORE PERMISSIONS THAN THEY HAVE? They can give their staff access to the logic, then take their time recreating it. We made a really amazing product on this platform, and now we're finding that every moment needs to be watched internally. I never would have gone down this path with GHL had i known it would all be so susceptible to theft. I'd never recommend GHL SaaS to anyone. Be careful who you hire.
13
·

in progress

Enhance Cancellation Flow with Retention Offers
Currently, when a sub-account initiates cancellation within the app, they are presented with a question about their reason for leaving. While this provides valuable feedback, it doesn't actively try to retain the customer. This proposal suggests integrating a retention flow into the cancellation process, offering a compelling reason for the user to stay. Proposed Solution: Implement a phased approach to build a robust retention flow: V1: Basic Retention Offer (Skateboard) * Goal: Introduce a simple retention mechanism to capture some immediate wins and gather data. * Features: * Single retention offer presented to all canceling sub-accounts. * Offer type: Discount on the current plan (e.g., 10% off for 3 months). * Simple acceptance mechanism (e.g., "Yes, I want to stay" button). * Basic tracking of offer acceptance rate. V2: Segmented Offers & A/B Testing (Bicycle) * Goal: Refine the retention flow by targeting specific user segments and testing different offer types. * Features: * Segment users based on plan type (e.g., offer a free add-on to lower-tier plans, offer a discounted upgrade to higher-tier plans). * Introduce A/B testing to compare the effectiveness of different offers (e.g., discount vs. free add-on). * Track acceptance rates for each segment and offer type. * Gather feedback from users who decline the offer. V3: Advanced Customization & Automation (Race Car) * Goal: Maximize retention by personalizing offers and automating the process. * Features: * Advanced segmentation based on usage behavior, cancellation reason, and other relevant data. * Personalized offers tailored to individual user needs and preferences. * Automated offer delivery based on user behavior (e.g., trigger a retention offer if a user hasn't logged in for a certain period). * Integration with other HighLevel features (e.g., email marketing, workflows) to create a seamless retention experience. * Comprehensive reporting and analytics to track the effectiveness of the retention flow and identify areas for improvement. Further Enhancements (Beyond Race Car): * Predictive churn analysis: Utilize machine learning to predict which users are most likely to churn and proactively target them with retention offers. * Gamified retention: Introduce gamification elements (e.g., points, badges, rewards) to incentivize users to stay engaged and loyal. * Win-back campaigns: Develop targeted campaigns to re-engage customers who have already canceled. Benefits: * Reduced churn rate: Proactively address customer churn by incentivizing users to stay. * Increased customer lifetime value (CLTV): Encourage customers to remain subscribed for longer periods. * Improved customer satisfaction: Demonstrate a commitment to customer retention and provide valuable offers. * Valuable data insights: Gain a better understanding of why customers cancel and what types of offers are most effective in retaining them. Implementation Notes: * Ensure the retention offer is prominently displayed and clearly communicated during the cancellation process. * Make it easy for customers to accept the offer with a simple click or button. * Track the effectiveness of the retention flow and make adjustments as needed. This feature enhancement has the potential to significantly impact HighLevel's bottom line by reducing churn and increasing customer lifetime value.
0
SaaS Mode V2
Here are a few ideas for upgrades to the current SaaS mode:1. More than 3 SaaS plans (preferably unlimited).2. Have a way for SaaS users to change their plan or cancel in their billing settings and let us make our own description of what is included in each plan to show here in billing.2a. Give us the ability to control what SaaS plans they can switch to in the billing settings.2b. Let us create a required form for SaaS users to submit if they are trying to cancel that includes the ability to downgrade to a cheaper plan. 2c. Agencies should be able to choose if users have the ability to change plans or cancel in settings, it should not be a required feature.3. Let us "impersonate" any SaaS user and see the app as they see it.4. Give us the ability to turn off some features completely so that no SaaS plan has them.5. Let us create our own banner popups that show for SaaS users.6. Give us the ability to disable certain settings in the settings menu for SaaS plans if we don't need our users to be able to access them. Also, I'd love to be able to add custom menu items to the settings menu, not just the main menu.7. There needs to be a way to fully disable features that SaaS accounts lose access to. For example, if a user cancels their subscription or downgrades to a plan that doesn't have workflows, they will not be able to view workflows anymore but the workflows will still actually work. This is not okay.8. We need some sort of system for managing and sorting our sub accounts. Filtering by SaaS plan would be a good start. Also, would love the ability to be able to select multiple SaaS accounts and bulk edit them (like adding or removing feature permissions). HIGHLVL-I-5285
25
·

planned

Load More