Spark Billing Provider Laravel Package

Product Decisions This Supports

• Build vs. buy for admin/back-office UI. Filament is an established, MIT-licensed Laravel UI framework (32k+ stars, active releases). The decision it removes is "do we hand-roll CRUD screens, tables, filters, and forms, or standardize on a framework?" Standardizing is almost always cheaper.
• Roadmap sequencing for internal tooling. Shipping admin panels, ops dashboards, and support consoles can move from weeks of bespoke Blade/React work to days of declarative PHP. That frees engineering capacity for customer-facing roadmap items.
• Vendor/ops tooling for SaaS billing (the specific package). filament/spark-billing-provider is a thin bridge that surfaces Laravel Spark subscription and billing data inside a Filament panel. It supports the decision to expose billing state (plans, subscription status, invoices) to support/success teams without building a custom billing console.
• Feature surface for customer self-service. Filament panels + this provider can back a "manage my subscription" area, reducing inbound support tickets — a measurable product outcome, not just a dev convenience.
• Extensibility decision. No final/readonly classes and app()-based resolution in the codebase mean customization is a first-class path, lowering the risk of adopting and then outgrowing it.

When to Consider This Package

Adopt Filament (core) when:

• Your stack is Laravel and you're comfortable in PHP/Livewire — ideally the team is not React/Vue-heavy.
• You need Eloquent-backed CRUD, data tables, filters, actions, and notifications, and want consistency across many screens.
• You need internal tooling fast and value convention over bespoke design.
• You want an MIT-licensed, extendable foundation with an active community and clear upgrade path.

Consider spark-billing-provider specifically only when:

• You are already using Laravel Spark for billing. It is an adapter, not a billing system.
• You want billing/subscription visibility inside an existing Filament panel without writing custom pages.

Look elsewhere when:

• Your billing is Stripe/Cashier, Paddle, or Lemon Squeezy — this package does nothing for you; use Filament core plus custom pages instead.
• You need a highly bespoke, pixel-controlled consumer frontend or heavy client-side interactivity (React/Vue SPA).
• Your team has no PHP/Laravel depth, or the app is not Laravel.
• You need a framework with an independent, package-level ecosystem footprint — see the caveat below.

Adoption caveat for the PM: the 32k stars and release cadence belong to the Filament monorepo, not to this subpackage. Reported dependents for filament/spark-billing-provider are effectively zero, and its opportunity score is low (3.63). Treat the strategic bet as "adopt Filament," and treat this package as an optional, low-cost convenience layer inside that bet — not as a standalone evaluated dependency.

How to Pitch It (Stakeholders)

To executives: Filament is a mature, MIT-licensed framework with a large community and current releases — no licensing cost, no per-seat fees, and low lock-in. The business case is speed: internal admin tooling and support consoles that would take weeks of custom frontend work can ship in days, redirecting engineering toward revenue-facing features. Risk is contained because it's open source and extensible.

To engineering: It's a composable Laravel/Livewire framework — forms, tables, actions, notifications, and panels as separate packages — with a consistent fluent PHP API and strong testing story (Pest, browser tests, static analysis). It's designed to be extended, not fought. For billing, spark-billing-provider is a small, optional adapter if we're on Spark; otherwise we use core Filament and build billing views ourselves.

To product/support leads: Faster delivery of back-office and self-service screens means support teams get the subscription and account visibility they need sooner, and customers get self-service controls that reduce ticket volume.

The one honest caveat to state up front: we are standardizing on Filament core; the Spark billing package is a minor add-on with limited independent adoption. If we're not on Spark, we skip it entirely — and the recommendation stands unchanged.