LLC A
- Leads
- Sellers
- Stripe
This walkthrough demonstrates how Ledrix is configured when each legal entity needs its own book — without a second SaaS login per LLC. It is an example scenario, not a customer case study.
Agency or holding-company owner
Consider an operator with three LLCs. LLC A and LLC B each collect on Stripe. LLC C collects on PayPal. Each entity has its own leads and closers. The owner still needs one admin login.
Screen to film: Admin Brands list with three rows and a merchant status on each.
In Ledrix an LLC is not a second tenant. You create one agency workspace, then add each legal entity as a brand. That is the split: pipelines live on the brand, the bill and admin login stay on the workspace.
Brands inside an agency workspaceSave Stripe or PayPal keys on the brand record. Ledrix does not invent a merchant. Until those keys are on LLC C, LLC C cannot generate a PayPal link under its own account.
Brand-level Stripe / PayPal configurationInbound and imported rows land on a brand. Admins assign a closer. The seller is notified when a lead is assigned. Ownership sits on the lead — not in a shared sheet.
Lead assignment to brand + sellerSeller A opens the seller panel and sees assigned records only. They can follow up and send a payment link on those deals. They cannot browse LLC B’s leads, agency-wide lists, or admin tools.
Seller panel, assigned book onlyThe workspace owner still opens the admin CRM and sees every LLC’s pipeline, routing, and cash. Central visibility does not require giving closers the same database.
Admin CRM across brands14-day free trial, no credit card. Sandbox is shared sample data — a trial is your own workspace.
Straight answers about how Ledrix is configured — not claimed customer results.