Symfony Bundle Laravel Package

Product Decisions This Supports

• Build vs. buy for social/ads integrations: v0.2.0 adds "Meta Ads depth," signaling that Fopost is investing in advertising-side capabilities (campaign/ad performance) rather than only organic social publishing. This makes the package a candidate to evaluate against building an in-house Meta Ads integration.
• Feature scoping: If your roadmap includes Meta Ads reporting, campaign management, or unified social + paid-media workflows, this release expands the addressable use cases the package can support.
• Roadmap sequencing: Because the package is still pre-1.0 and explicitly tracks an external SDK (fopost/sdk ^0.2 until 0.3), any decision to depend on it should be sequenced behind a stability/exit-risk review, not treated as a long-term platform commitment.
• Use cases to validate: social publishing plus Meta Ads depth in a PHP backend; marketing automation and campaign tooling where a Symfony/PHP service is the system of record.

When to Consider This Package

Consider it when:

• Your team is on PHP/Symfony (or Laravel with a willingness to integrate a Symfony-oriented package) and wants to avoid building social/ads plumbing from scratch.
• Meta Ads depth is a genuine product requirement, not a hypothetical — this is the headline capability added in v0.2.0.
• You can tolerate pre-1.0 API churn. The 0.x version line permits breaking changes, and the dependency constraint (fopost/sdk ^0.2 until 0.3 is published) indicates active version coupling and likely upgrade work ahead.
• You are comfortable with a small, single-maintainer release cadence and can absorb the maintenance risk or wrap the package behind an internal abstraction.

Look elsewhere when:

• You need a stable, long-term-supported API contract for a revenue-critical integration.
• You require a first-class Laravel package (this is Symfony-oriented; Laravel adoption implies adapter/integration effort).
• Meta Ads is not on your roadmap — the value proposition in this release is concentrated there.
• Your procurement or security review requires demonstrated maintenance depth, test coverage, and a published support policy that a 0.2.0 package typically cannot yet evidence.

How to Pitch It (Stakeholders)

For executives: This is a low-cost way to accelerate a Meta Ads/social integration instead of funding an in-house build. The trade-off is maturity: the package is at v0.2.0, maintained by a single contributor, and tightly coupled to a companion SDK that is itself pre-1.0. Recommend a time-boxed spike, not a platform commitment, until we see a stable 1.0 and a healthier release cadence.

For engineering: v0.2.0 is a feature release adding Meta Ads depth and relaxing the SDK constraint to ^0.2 pending 0.3. Treat the public API as unstable: isolate it behind an internal interface, pin versions, and budget for upgrade work when the SDK moves to 0.3. Before adoption, review test coverage, issue responsiveness, and whether the Symfony-first design creates friction for our Laravel services. The dependency pin is a deliberate compatibility hedge, not a long-term guarantee — plan for a migration checkpoint.