Background-first execution
Long-running campaign work is separated from the active browser session so closing a tab does not stop processing.
01 / AI automation product
Sendium
A focused campaign automation system built to keep outreach running beyond the browser.
Sendium began as an internal answer to an expensive, repetitive workflow: running and tracking email campaigns without adding more manual operations.
The challenge
Campaign tools often trade simplicity for control. The product needed to coordinate long-running work, preserve state across devices, and make campaign health understandable without turning the interface into an operations console.
The approach
I treated background execution as the product’s foundation rather than an implementation detail. Campaign setup, progress, and exceptions were designed as explicit states so users could leave the browser and return without losing context.
02 / System story
One connected product flow.
01Create campaign
02Validate audience
03Queue work
04Process in background
05Track state
Core stack
ReactNode.jsMongoDBBackground jobsReal-time sync
03 / Key decisions
Designed around the hard parts.
The most important work is often deciding what the system should make obvious, durable, or intentionally limited.
Operational clarity
Status, progress, and failure paths are surfaced as product states instead of being hidden in logs.
Constraint-led scope
The private beta focuses on reliable campaign execution and tracking before expanding into a broad sales suite.
04 / Current outcome
The current private beta supports automated campaign workflows, bulk outreach, background processing, and real-time campaign tracking. Public usage metrics are not yet available.
This case study reports only publicly supportable outcomes. No usage or business metrics have been invented.