Easy Install Solar CRM includes a full SaaS administration layer. Master admins can configure plans, public signup, cPanel automation, routing, shared paths, platform subdomains, custom domains, Stripe, PayPal, billing lifecycle handling, and tenant support operations from inside the product.
Plans control both pricing and capability
Plans are more than pricing labels. They can control availability of AI, domain options, conversation limits, and other customer-facing capabilities. Use plans intentionally so feature access matches the product strategy you want to offer.
If you add a new plan, test the public pricing page, signup flow, and billing behavior together. Plan configuration mistakes often show up at the moment of checkout or provisioning, not just on the admin form.
Public signup is designed to reduce friction
The signup flow is streamlined so buyers do not have to think about tenant terminology, slugs, or domain strategy up front. The system can store partial signups before payment completes and keep useful lead context like IP, browser, and referrer for follow-up.
This is useful for sales recovery because admins can see who started the process but did not finish it, then re-engage those prospects with context.
Routing supports shared paths, subdomains, and custom domains
The platform supports access via shared path, platform subdomain, and custom or branded domains depending on the plan and routing rules. Users can be given choices based on plan allowances, and admins can manage the routing strategy centrally.
When custom domains are involved, remember that DNS still has to point to the server even if the platform automates the internal setup work.
- Use shared paths when you want the fastest path to launch.
- Use branded subdomains for a cleaner SaaS experience.
- Reserve custom domains for plans and customers that need them.
Billing lifecycle is a system, not just a checkout button
Stripe and PayPal are both supported, along with billing portal actions, webhook tracking, failed-payment handling, grace periods, dunning, auto-suspend, and reactivation flows.
Treat payment settings, webhooks, plans, and billing operations as one operating surface. A billing issue is easier to solve when the platform team can see webhook logs, retry actions, and tenant status in one place.