A white-label CRM you own, not one you rent.

A white-label CRM is a customer relationship management platform you rebrand and sell to your clients under your own brand. The versions that hold up long term ship with the source code, so you control the features, the pricing, and the roadmap without a per-seat fee going back to a SaaS parent.

Yes. The commercial license included with your purchase lets you rebrand the platform and sell it to your clients without publishing your source changes. That is the difference from an open-source AGPLv3 project, which requires you to offer users the source of any modified version you host for them.

Yes. Demo mode blurs personal information across the app, covering contacts, conversations, integrations, billing, the dialer, reputation and the account screens. You can run a live walkthrough in a real, populated account rather than a hollow sandbox, without a prospect reading a current client's phone number off your screen.

There is a guided setup that walks you through it, rather than a wiki page and good luck. It generates the secrets, creates your first admin account and handles the steps that used to be manual, so getting from purchase to a running CRM is a session rather than a project.

No. Snapshots clone a designated sub-account into a new one, carrying the pipelines, templates, custom fields, forms and the rest of the configuration you have already refined. Your tenth client onboarding takes the time your first one did minus everything you learned, which is the difference between an agency that scales and one that is a bottleneck.

Yes. A client can have their own domain for public pages and email links, so booking pages, forms and the links inside their emails all sit on their brand rather than yours or ours. White-labelling that stops at the logo is not white-labelling.

You can define custom roles rather than picking from fixed tiers, group people into teams, and control access per sub-account. There is a full audit log recording who did what, which matters the first time a client asks that question about their own account.

Turn on single-business mode. The CRM is built around an agency holding many client accounts, and that model puts a client switcher, an agency layer and a sub-account concept in front of someone who never needed any of it. Single-business mode collapses that so the workspace presents as one business. Nothing is deleted and the multi-client machinery is still underneath, so you can switch it back on the day you take your first client.

Yes. Add your own fonts and use them across the app and the public-facing pages, so a client's booking page and emails match their brand rather than approximating it with whatever the system shipped with.

Yes. The platform takes add-on modules, so a purchased module installs into the CRM you already run rather than arriving as a separate app to keep in sync. A module can drop ready-made workflows into your template gallery, add its own field types to your forms, attach its own context to automations you already built, and tag invoice and estimate templates with a service type. Seedly Dispatch is the first one, and it turns the same install into field-service software without touching what already works.

A reseller program lets you sell someone else's product for a commission or a discount, and the parent SaaS keeps a share of every account forever. Owning the source means you set the price, you keep the margin, and you can change the software itself when a client needs something it does not do yet.

The two most common shapes are a one-time setup fee of $500 to $2,000 plus $49 to $149 per month for hosting, or an all-inclusive monthly subscription of $99 to $299. Because your marginal cost per client is close to zero once you own the source, the ceiling is set by the niche you serve rather than by the platform.

No. You pay $1,499 once for the source code and the commercial license. Adding your eleventh client or your hundredth does not change what you owe, because there is no vendor metering your accounts.

You need someone comfortable deploying a web application, and the setup documentation walks through it step by step. Running it as it ships takes no code at all. Changing how it works is where having the source matters, and that is the part a developer or an AI coding tool handles for you.