← Back to Work Case Study

Multi-Brand Newsletter Infrastructure for a Financial Media Company

Adam Garcia, Little Cup Marketing / ALG Financial · Case Study
4Brands audited
5Scenarios verified and corrected
$10K+Additional work identified

The Situation

Adam Garcia runs Little Cup Marketing, the marketing arm of ALG Financial, operating four newsletter brands focused on stock market content. Subscribers come from multiple sources: landing pages, Meta ads, beehiiv opt-ins, and partner referrals. The infrastructure was a mix of WordPress, Cloudflare Workers, beehiiv, SimpleTexting, and Make.com scenarios tying it together.

The routing between brands was fragile. Scenarios broke, webhooks misfired, and subscribers ended up in the wrong pipeline. One brand's SMS scenario was silently pointing to a different brand's delivery account. Nobody had a clear view of which source was driving subscribers to which brand.

What We Built

A full audit and rebuild of the subscriber routing infrastructure across all four brands.

Phase one mapped every Make.com scenario, traced every webhook, documented sendQ URLs per brand, and found where data was being misrouted. The audit uncovered a brand's SMS scenario pointing to the wrong sendQ account and broken IO integrations on two landing pages.

Phase two fixed and standardized the routing. Every scenario verified against correct sendQ URLs. IO integrations deployed on new landing pages with proper source tags. All five active scenarios corrected and tested.

Ongoing work expanded into infrastructure monitoring, security audits, and scoping for n8n migration, a unified subscriber dashboard, and landing page standardization.

Results

Misrouted subscriber pipeline identified and corrected. IO integrations deployed on 2 new landing pages with source tagging. All 5 active Make.com scenarios verified and corrected. Security audit completed across brand WordPress sites. $10,000+ in additional project work identified.

Tech Stack

Make.com IO sendQ beehiiv SimpleTexting WordPress / Cloudflare Workers

What Made This Work

The value was tracing the full data flow across a multi-brand infrastructure and finding where it was silently broken. The misrouted sendQ connection had been sending subscribers to the wrong brand's pipeline with no one aware. That kind of problem surfaces from mapping the entire system end to end and checking every connection against what it's supposed to be doing.

Running multi-brand infrastructure that's grown organically? Let's map it and find what's broken.

Book a Call