Extended License

Extended License

Note: this page is practical guidance for buyers, not legal advice. Always read the exact marketplace license terms that apply to your purchase.

Regular License vs Extended License

A Regular License is commonly enough when the product is used for one end product where end users are not paying specifically to access the LeadFlow AI-powered application. An Extended License is commonly required when you sell paid SaaS access, charge customers for plans, monetize customer-facing access, or include the product as a paid hosted service.

When Regular Is Enough

Regular usage may fit an internal business tool, a single company installation, or a non-resold project where customers are not paying for access to the app. It may also fit a buyer using LeadFlow AI only to manage their own forms, funnels, and leads.

When Extended Is Required

Extended usage is usually the safer choice for SaaS launches, paid plans, paid workspaces, recurring subscriptions, premium lead generation access, or selling access to multiple customers. If customers pay to use forms, responses, funnels, surveys, AI builders, QR tools, files, custom domains, reports, automation, support, integrations, or billing features, review Extended License requirements before launch.

Marketplace Addon License Types

Addons can have separate license requirements. A core product Extended License does not automatically grant unlimited resale rights for every addon unless the addon license says so. Track purchase codes and license status per package.

What Buyers Can Do

• Install and configure the product for the licensed domain or project.
• Create plans, workspaces, users, forms, responses, funnels, surveys, QR tools, reports, files, domains, support, and billing workflows according to the license.
• Customize branding, content, settings, and operational workflows for their business.
• Buy and install compatible addons from the marketplace.

What Buyers Should Not Do

• Redistribute the source code as a competing downloadable product.
• Share purchase codes publicly.
• Sell addon access without the required addon license.
• Ignore license terms for paid SaaS or customer-facing monetization.

Agency and SaaS Launch Checklist

1. Confirm license type before selling access.
2. Create paid plans only after checking marketplace terms.
3. Configure billing, invoices, taxes, refunds, support, and privacy pages.
4. Test customer signup, plan limits, payment webhooks, and portal visibility.
5. Document installed addons and their license status.

Common Mistakes and FAQ

Can I charge customers for form and funnel work managed by my agency?
Agency service billing may differ from selling SaaS access. Review the license and choose Extended if customers directly access paid product features.

Can I use one license on many domains?
Marketplace licenses are commonly tied to one end product or installation. Check the exact license terms.

Do addons need separate purchases?
Yes, when sold separately or licensed separately. Keep addon purchase codes available for updates.

Buyer Readiness Notes

Before using Extended License in production, confirm that the application has been installed on the correct licensed domain, cache has been cleared after configuration changes, and all relevant workspace permissions have been tested with realistic user accounts. LeadFlow AI is often used as a customer-facing SaaS product, so a setting that looks internal during setup can affect paid users, published forms, funnel redirects, lead records, invoices, files, domains, or addon visibility.

For agency deployments, prepare a repeatable launch checklist for each workspace. The checklist should include workspace branding, form fields, consent copy, funnel pages, tracking fields, notification recipients, lead assignment rules, reports, file storage, custom domains, support ownership, and team permissions. For SaaS deployments, prepare a platform checklist that covers plans, payment gateways, mail delivery, queue workers, cron, file storage, AI provider settings, marketplace packages, backups, privacy pages, and production debug mode.

When troubleshooting this area, separate configuration problems from data problems. Configuration problems usually involve cache, plan permissions, missing addons, provider credentials, mail settings, queue workers, or route discovery. Data problems usually involve workspace ownership, hidden fields, duplicate slugs, invalid imports, deleted parent records, old embed codes, or team permission rules. Testing with a fresh private browser session and a non-admin account helps confirm the real customer experience.

Operational FAQ

Who should review this page?
Product owners, SaaS admins, agency operators, support staff, and implementation partners should review it before changing related production workflows.

What should be documented internally?
Record any custom domain rules, installed addons, plan limits, payment provider settings, AI provider settings, integration credentials, and client-specific visibility decisions.

What is the safest production habit?
Back up first, change one thing at a time, clear cache when the change affects Laravel configuration or package discovery, then test the exact user or client workflow that depends on the change.