Sendinblue Laravel Package

Product Decisions This Supports

• Lead capture and lifecycle marketing: Connects Statamic v5 contact/lead forms directly to Brevo (formerly Sendinblue), supporting decisions about whether website demand flows into email lists, segmentation, and nurture campaigns without manual export.
• Build vs. buy for integrations: The package is a narrow adapter—form submission to Brevo subscription. Product should treat it as a candidate for a time-boxed pilot, not a strategic platform decision.
• Marketing ops roadmap: Informs whether to prioritize native CRM/email-provider integrations, consent capture, double opt-in, field mapping, and campaign attribution in the roadmap.
• Vendor consolidation: Relevant if Brevo is already the email/CRM system of record; the package can reduce friction for small marketing teams. Not relevant if Brevo is not chosen.
• Feature experiments: Useful for testing newsletter signup, gated content, event registration, or contact-form-to-list workflows without committing engineering sprint capacity.
• Risk and maintenance planning: Zero stars and zero dependents are adoption signals, not proof of quality. The decision should include a maintenance owner, version pinning, and an exit plan.

When to Consider This Package

Consider it when:

• The site is on Statamic v5 and uses Statamic’s contact form or form submissions.
• Brevo is already the approved email/CRM destination, and the immediate need is simple list subscription—not two-way sync.
• The team wants a low-effort pilot and can accept community-grade maintenance.
• Engineering can review, pin, and if necessary fork the package; the integration surface is small enough to vendor.
• Consent, double opt-in, field mapping, rate limits, and error handling can be handled explicitly.

Look elsewhere when:

• You need enterprise support, SLA, security certification, or a large maintainer community.
• You require complex sync: custom objects, deal pipelines, two-way updates, deduplication at scale, or multi-brand routing.
• The site is not on Statamic v5, or a Statamic v6 migration is imminent.
• You are building on plain Laravel without Statamic; a direct Brevo SDK or HTTP client integration is likely simpler.
• Compliance requirements are high: GDPR/CCPA consent evidence, data residency, retention, or auditability.
• The team cannot tolerate single-maintainer and zero-dependent risk without forking.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost integration that turns website form submissions into Brevo subscribers. It could improve lead capture and reduce manual list management, but it has no visible adoption and should be treated as a pilot, not a platform bet. Approve only with a defined owner, success metric, and fallback plan.

For engineering: It is a thin Statamic v5 addon that subscribes form submissions to Brevo. The scope is small enough to review or replace with a direct Brevo API integration in a short effort. Pin the version, add tests around form submission, consent, API failures, and rate limits, and keep an exit path.

For product/marketing: Use it to validate whether faster form-to-Brevo flow improves list growth, segmentation, and follow-up. Measure conversion, subscription success, duplicate rate, and manual effort saved. If the pilot shows value, either harden the integration internally or replace it with a supported path.