Filament Companies Laravel Package

Product Decisions This Supports

• Multi-Tenant SaaS Roadmap: Accelerates development of company-based tenancy models (e.g., "HubSpot for X" or "Slack-like workspaces") by providing pre-built authentication, role management, and employee onboarding flows.
• Build vs. Buy: Eliminates 3–6 months of custom development for core SaaS features (e.g., company creation, role-permission systems, or invite workflows) while maintaining flexibility via Filament’s admin panel.
• Compliance & Trust: Built-in Terms & Privacy Policy and GDPR-ready session management reduce legal/engineering overhead for regulated industries (e.g., healthcare, finance).
• Scalable Onboarding: Auto-accept invitations and email-driven employee flows align with product-led growth (PLG) strategies, reducing churn from friction.
• Monetization Experiments: Role-based permissions enable A/B testing of freemium tiers (e.g., "Company Admin" vs. "Employee") without rewriting auth logic.
• Developer Experience: Reduces context-switching for backend teams by unifying auth, tenancy, and admin UI under Filament’s ecosystem.

When to Consider This Package

Adopt When:

• Your product requires company-level tenancy (e.g., workspaces, agencies, or organizational accounts) with individual user management beneath them.
• You’re using Filament 4.x for your admin panel and want to avoid reinventing auth/tenancy from scratch.
• Your roadmap includes SaaS-specific features like:
  • Multi-tenant dashboards.
  • Role-permission hierarchies (e.g., "Owner" > "Manager" > "Member").
  • Collaborative onboarding (e.g., "Invite teammates").
• You prioritize rapid iteration over customization (e.g., MVP launch, pivot testing).
• Your stack already includes Laravel + Sanctum (or you’re open to adopting it).

Look Elsewhere If:

• You need B2C authentication (e.g., individual user accounts without companies). Use Laravel Breeze/Jetstream instead.
• Your tenancy model is user-based (e.g., "subscriptions per person") rather than company-based.
• You require highly custom UI/UX for auth flows (this package uses Filament’s default styling).
• Your team lacks Filament experience—the package assumes familiarity with Filament’s admin panel.
• You need enterprise-grade SSO (e.g., Okta, Azure AD); this package supports Socialite but may require extensions for deep SSO integrations.
• Your product is not SaaS-adjacent (e.g., e-commerce, content platforms).

How to Pitch It (Stakeholders)

For Executives:

"This package lets us launch a multi-tenant SaaS product 60% faster by giving us pre-built company management, role-based access, and team onboarding—all without hiring extra engineers. For example:

• Reduce churn: Auto-accept invitations and email-driven workflows cut friction for team signups.
• Scale compliance: Built-in terms/privacy policies and session management align with GDPR/CCPA requirements.
• Test monetization: Role-permission systems enable A/B testing of freemium tiers (e.g., ‘Company Admin’ vs. ‘Employee’) in weeks, not months. It’s a drop-in solution for Filament users—like using Stripe for payments, but for SaaS authentication."

For Engineering:

"This is a Filament-native way to handle company-based tenancy with minimal trade-offs:

• Pros:
  • Batteries included: Social login, password resets, profile management, and Sanctum auth—all configured.
  • Admin-ready: Uses Filament’s UI for company/employee management (no separate backend dashboards).
  • Extensible: MIT-licensed, so we can fork/modify if needed (e.g., custom invite emails).
  • Future-proof: Built for Filament 4.x, so upgrades align with the panel.
• Cons:
  • Assumes we’re using Filament (but that’s a given for our admin panel).
  • Limited docs, but the code is clean and modular.
• Migration effort: ~2–3 dev days to integrate (vs. 3–6 months to build from scratch). Recommend adopting for [Product Name]’s SaaS roadmap—it’s a force multiplier for auth/tenancy."

For Design/Product:

"This package handles the ‘plumbing’ of company-based workflows so we can focus on UX:

• What it covers:
  • Company creation/management (e.g., ‘Add a new workspace’).
  • Employee invitations (e.g., ‘Send invites via email’).
  • Role assignment (e.g., ‘Set permissions for team members’).
• What we still own:
  • The public-facing onboarding flow (e.g., ‘Create your company’ page).
  • Custom email templates for invites/resets.
  • UI tweaks to match our brand (Filament is customizable but not a design system). Think of it like using a pre-built auth library—we get the backend logic for free, and our team designs the ‘front-end’ experience."