What Running a White Label CRM SaaS Script Actually Takes
What launching a CRM SaaS on a white label CRM SaaS script involves: tenant onboarding, plans and feature gates, billing, and the work you still own.
Every agency that resells lead generation eventually hits the same fork in the road: keep paying per-seat fees to someone else’s CRM forever, or run the platform yourself and charge your own customers for it. Building a multi-tenant CRM from scratch means writing tenancy, roles, billing, dunning and audit logging before you can send a single invoice. A white label CRM SaaS script compresses that: you buy the codebase, install it on your own server, and sell branded workspaces on plans you define. Full disclosure before we go further: we build and sell LeadHub, the script this post uses as its worked example.
This is a business post, not an architecture tour. The honest framing up front is that a script solves the product problem. It does not solve the hosting, support or marketing problems, and anyone who tells you otherwise is selling a dream rather than software.
What a white label CRM SaaS script covers (and what it does not)
LeadHub is a self-hosted Laravel 13 application with a Filament 4 admin. You get the complete unencrypted source - no IonCube, no obfuscation - which matters more than it sounds: your business should not depend on code you cannot read. A browser-driven installer sets it up without SSH or Composer, and updates run from the browser too, including database migrations. That makes shared hosting a realistic starting point: URL-based cron, an optional sync mail driver for hosts where queue workers cannot run, and a health endpoint that probes DB, cache and storage are in the box.
The multi-tenant part is the point. Each tenant - your paying customer - gets a workspace with its own leads, pipelines, automations, forms, booking calendar and team, isolated at the query level so tenants never see each other’s leads, deals or settings. White labeling is per tenant: logo, favicon, primary and accent colors, app name and footer text, so your platform brand never leaks into their dashboard. Access is governed by six roles, from super-admin down to customer.
You operate everything from a super-admin panel: tenant management (create, suspend, activate, restore, refund, hard-delete), a plan builder, coupons, tax rates, gateway credentials, audit logs, database backups, and a dashboard showing total tenants, active subscriptions, MRR, ARR and churn rate. Those are the numbers you will actually stare at as an operator.
Tenant onboarding, from signup to first invoice
A tenant’s lifecycle starts with a configurable free trial that expires automatically. From there the built-in email machinery takes over: a Day 0 / Day 2 / Day 5 / Day 10 onboarding sequence, a behavior-based trial drip with localized subjects in four languages, trial-expiry notices, and plan-limit alerts as tenants approach their lead, seat or storage caps. That is retention plumbing you would otherwise have to script yourself in week one.
New tenants also do not start from a blank slate. A built-in marketplace ships pre-built automations, sequences, forms and pipelines that install in one click; you curate the library from the super-admin panel and can feature-gate installs per plan. The 2.0.0 release seeded it with free starter templates: a welcome automation, a contact form, a B2B pipeline and a 3-day onboarding sequence. Tenants invite their own team through signed, single-use expiring links with role pre-assignment.
If you sell to businesses, two compliance details save time in procurement reviews: an Article 28 Data Processing Agreement is a public download, and erasure is a 30-day cool-off workspace deletion with a reachable cancellation banner rather than an instant wipe.
And when a tenant emails you confused, one-click impersonation opens a 60-minute audited session inside their workspace, with no password requests and a full audit trail. For a small operator that is the difference between fixing the problem yourself and a long screenshot thread with a frustrated customer.
Plans, packages and feature gates
Plans carry monthly and annual pricing, with an operator-configurable annual discount per plan, plus usage limits and seat caps. Feature gates control access per plan: lead sources, the AI Lead Coach, marketplace installs, white-label, API access, webhook quota and team seats. Since 2.0.9, plan feature flags can also hide entire admin sections per tier - Reports, Brand and Domain, Communications, Advanced, Tools and Templates - so a starter tier does not even see what it has not paid for.
A coupon system covers percentage and fixed-amount discounts, trial extensions, usage limits, date ranges and plan restrictions, which is enough to run launch promos and win-back offers without touching code.
One packaging detail worth planning around: the AI layer (the Lead Coach, the LeadBot website chatbot and the AI SDR follow-up agent) is optional and plan-gated, and the CRM runs fully without any LLM key. The three features run on the single key you set as platform owner, with built-in daily caps, so AI can be your premium-tier differentiator at a predictable cost rather than a fixed expense in every plan.
Billing: five gateways, receipts and dunning
The billing engine speaks five gateways: Stripe (Hosted Checkout, Customer Portal, recurring subscriptions, webhook idempotency, refunds with credit-note receipts), PayPal (billing-subscriptions API with signed-webhook verification and an out-of-order event guard), Razorpay for the Indian market, Paystack for Sub-Saharan Africa, and manual bank transfer with super-admin confirmation and configurable bank-detail templating.
Receipts are tax-compliant with sequential numbering (LH-YYYY-NNNNNN), EU VAT and US sales tax support, and per-tenant currency; refunds auto-generate negative credit notes for clean year-end accounting. Tenants enter their own business name, VAT or GST id and billing address, so the paperwork is right from the first charge. Failed payments trigger escalating dunning emails that end in suspension. An affiliate engine with referral codes, recurring 20% commission tracking and a payout audit trail lets your earliest happy customers become an acquisition channel.
What you still have to bring yourself
Be clear-eyed about this list, because the script does none of it:
- Hosting and operations. Self-hosted means your server, your uptime, your SSL, your backup discipline. The app generates verifiable, downloadable database backups, but storing them off-server and testing restores is on you.
- Accounts and keys. Gateways bill into your own Stripe, PayPal, Razorpay or Paystack accounts. Email needs your SMTP provider. Click-to-call and SMS need a Twilio or Plivo account. The AI features need an LLM API key you pay for.
- Support. To your tenants, you are the vendor. Impersonation and audit logs make troubleshooting fast, but someone still has to answer the tickets, and the pre-sales questions, and the refund requests.
- Marketing. No codebase acquires customers. There is a platform landing-page builder for your own public site, but positioning, pricing strategy, content and ads are your actual job as a SaaS operator. Expect it to take more of your time than the software ever will.
When this is the wrong tool
If you want zero operational responsibility, a hosted CRM subscription is the better deal. You are trading recurring fees for ops work, and that trade only pays off if you have, or intend to build, a paying customer base. If your niche needs deep custom features, full source makes forking possible, but you then own the merge work on every update, and possible is not free. LeadHub is also a young product: version 2.0.9, updated 2026-07-30, with 27 sales on CodeCanyon, which is a real but small install base. We think shipping the entire unencrypted source is the honest counterweight to that risk, because whatever happens, the code runs on your server and stays yours. Finally, if you only ever need a private CRM for one team, self-service registration can be disabled so LeadHub runs as a single internal workspace, but a simpler single-tenant tool may serve you just as well.
Key facts
| Fact | Detail |
|---|---|
| Current version | 2.0.9 (updated 2026-07-30) |
| Server requirements | PHP 8.4+, MySQL 5.7+/8.x or MariaDB 10.3+, SMTP |
| Payment gateways | Stripe, PayPal, Razorpay, Paystack, manual bank transfer |
| Lead capture channels | 19 native sources |
| Delivery | Full unencrypted source, free updates |
| Track record | 27 sales on CodeCanyon |
Links
If you are weighing the operator side - dunning flows, feature-gate strategy, what tenant support actually costs in hours - ask away in the comments and we will answer from experience.
A copy of this article is also published on dev.to, where the comments are open.